On Tuesday 21 March 2006 12:22, Edson Noboru Yamada wrote: > One important thing I´ve noticed is that the error allways occurs after 300 > seconds. Is there some tunable timeout I´m forgetting? > > Additional info: strangely, the backup appears successful, even when this > message shows up. The same client is able to backup other file systems, and > the one that fails the most is the / filesystem. > > Any ideas?
Is there a iptables firewall on the client? From my personal amanda howto: > If a DLE is large and the client is behind an iptables firewall, the backup > of that DLE can timeout. This is because: > > 1. amanda uses two connections: a UDP for data and a TCP for errors and > control; > 2. iptables has a timeout (30 minutes) to kill inactive TCP > connections; and > 3. something takes longer than 30 minutes. > > The kernel sends keepalive packets on TCP, but the default time (2 hours > (7200 seconds)) is longer than the iptables timeout so iptables decides the > control/error connection has been abandoned and tears it down. This makes > the backup fail. > > To fix this by setting the kernel keepalive time to 15 minutes, login as > root on the client and: > > 'echo 900 >/proc/sys/net/ipv4/tcp_keepalive_time' > > see http://documents.made-it.com/iptables-timeout.html > 2006/02/06 > > Whenever the client reboots, the kernel's TCP keepalive interval is set to > 2 hours, so this needs to be redone. I've put the line at the end of the > start routine in my /etc/ipfilterfiles/ipfilter.sh iptables configuration > startup file. This doesn't match the time you're seeing, but it matches the symptoms. I wrote this more than a week ago so things may have changed... -- Glenn English [EMAIL PROTECTED] GPG ID: D0D7FF20
