Jeremy Wadsack ([EMAIL PROTECTED]):
> I am getting consistent timeout errors on a couple hosts. This doesn't > occur when I run amcheck, just during a dump. I'm using tar on all > hosts, so it's not a Linux dump issue. These two hosts are conspicuous > because they are old (so kernel, libraries and software all could be > out of date). > In both cases, the tail of /tmp/amand/amandad.debug looks like this: > amandad: dgram_recv: recvfrom() failed: Connection refused > amandad: waiting for ack: Connection refused, giving up! > The confusing thing is that it handles the sendsize call just fine > without a failed connection. This looks (but I'm not positive) like > the connection from the client to the server is failing, which I > didn't know it did. > Finally, these systems seem to have tar 1.12 (not patched). I am in > the process of upgrading to the latest version, but the tar issues are > not listed in the documentation as causing a 'timeout' error, so I > don't think that's going to fix it. > Anyway, if anyone has any thoughts or insight, I'd appreciate it. Just to follow up on this. I upgraded the two hosts to the latest tar and still get timeouts. I haven't seen this kind of thing in the archives. Does anyone have a clue what's going on here? TIA, -- Jeremy Wadsack Wadsack-Allen Digital Group
