This post is more than 5 years old
139 Posts
1
8725
RPC error: RPC send operation failed; errno = Connection timed out in Networker 7.6.2
Hi All,
We have started oracle dump backup from client behind firewall. After 16 hours, we are getting below error:
39078:save: RPC error: RPC send operation failed; errno = Connection timed out
Kindly suggest what to do??
Networker server version: 7.6.2
Networker server and client OS version: RHEL 5.6
Networker server's TCP Interval settings,
[root@Dc1BkpSrvr proc]# cat /proc/sys/net/ipv4/tcp_keepalive_time
3000
[root@Dc1BkpSrvr proc]# cat /proc/sys/net/ipv4/tcp_keepalive_intvl
60
[root@Dc1BkpSrvr proc]# cat /proc/sys/net/ipv4/tcp_keepalive_probes
10
Firewall timeout is 1 hour (3600 Secs). But i don't think so this is the solution. Please suggest?
SabarnaDeb
139 Posts
0
September 28th, 2011 04:00
Yes, I have changed the KeepAliveTime and KeepAliveInterval on networker server . Now, backup has been completed successfully. Thanks for your valuable reply.
cat /proc/sys/net/ipv4/tcp_keepalive_time
cat /proc/sys/net/ipv4/tcp_keepalive_probes
cat /proc/sys/net/ipv4/tcp_keepalive_intvl
sysctl \
> net.ipv4.tcp_keepalive_time \
> net.ipv4.tcp_keepalive_intvl \
> net.ipv4.tcp_keepalive_probes
net.ipv4.tcp_keepalive_time = 7200
net.ipv4.tcp_keepalive_intvl = 75
net.ipv4.tcp_keepalive_probes = 9
sysctl -w \
> net.ipv4.tcp_keepalive_time=600 \
> net.ipv4.tcp_keepalive_intvl=60 \
> net.ipv4.tcp_keepalive_probes=20
net.ipv4.tcp_keepalive_time = 600
net.ipv4.tcp_keepalive_intvl = 60
net.ipv4.tcp_keepalive_probes = 20
Mark_Bellows
240 Posts
1
September 27th, 2011 18:00
Hi Deb!
Please refer to the Configuring TCP Networks and Network Firewalls for EMC NetWorker Technical Guide.
Please go Powerlink the navigate to Home > Support > Technical Documentation and Advisories > Software ~ J-O ~ Documentation > NetWorker Family > Technical Notes then go to page 2. The document is on the top of the page.
RPC errors are typically network setting issues.
Another possible iss that may be causing this issue is the TCP CHimney stack. Read this article to see if this helps:
http://blogs.msdn.com/b/psssql/archive/2008/10/01/windows-scalable-networking-pack-possible-performance-and-concurrency-impacts-to-sql-server-workloads.aspx
Mark