Is the clock an hour out on centurion?
It does fail after an hour just things all seem odd
The failure is actually here:
11:19:29 INF - Backup by oracle on client centurion using policy Database_Cold, sched Logs_One_Year:file read failed
So it could be a genuine failure to read something or it could still be a keep alive / timeout issue
See what timeouts are set to one hour and what the keep alive timeouts are - the whole porcess my just be blocked:
check the setting:
# cat /proc/sys/net/ipv4/tcp_keepalive_time
7200
# cat /proc/sys/net/ipv4/tcp_keepalive_intvl
75
# cat /proc/sys/net/ipv4/tcp_keepalive_probes
9
If they look like the above then try changing the settings:
# echo 510 > /proc/sys/net/ipv4/tcp_keepalive_time
# echo 3 > /proc/sys/net/ipv4/tcp_keepalive_intvl
#echo 3 > /proc/sys/net/ipv4/tcp_keepalive_probes
To keep persistent after a reboot see below – use vi editor:
The changes would be rendered persistent with an addition such as the following to /etc/sysctl.conf
## Keepalive at 8.5 minutes
# start probing for heartbeat after 8.5 idle minutes (default 7200 sec)
net.ipv4.tcp_keepalive_time=510
# close connection after 4 unanswered probes (default 9)
net.ipv4.tcp_keepalive_probes=3
# wait 45 seconds for reponse to each probe (default 75
net.ipv4.tcp_keepalive_intvl=3
These do not need a restart to take effect but run : chkconfig boot.sysctl on for the above to apply
