On Fri, Mar 17, 2006 at 10:54:06AM +0000, Chuck Amadi Systems Administrator enlightened us: > FAILURE AND STRANGE DUMP SUMMARY: > server / lev 0 FAILED [server.my.co.ukNAK : amandad busy] > tapeserver.sm /var lev 0 STRANGE >
It looks to me like an amanda process is already running/hung on server.my.co.uk. Can you verify that with ps? > > Thus this was working fine but for some unknown reason the timeout has > exceeded 300 seconds Here is my log using less > command /tmp/amanda/amandad.20060316205008000.debug file > > > amandad: time 600.049: received other packet, NAKing it > addr: peer 193.131.77.174 dup 193.131.77.174, port: peer 63313 dup > 63366 > amandad: time 600.182: sending nack: > ---- > Amanda 2.4 NAK HANDLE 003-60610808 SEQ 1142538305 > ERROR amandad busy > ---- > Negative acknowledgement. amandad must already be running. > amandad: time 617.155: sending REP packet: > ---- > Amanda 2.4 REP HANDLE 003-60610808 SEQ 1142538305 > OPTIONS features=fffffeff9ffe0f; > / 0 SIZE 5303320 > / 1 SIZE 1568330 > ---- > > amandad: time 627.154: dgram_recv: timeout after 10 seconds > amandad: time 627.154: waiting for ack: timeout, retrying > amandad: time 637.154: dgram_recv: timeout after 10 seconds > amandad: time 637.154: waiting for ack: timeout, retrying > amandad: time 647.154: dgram_recv: timeout after 10 seconds > amandad: time 647.154: waiting for ack: timeout, retrying > amandad: time 657.154: dgram_recv: timeout after 10 seconds > amandad: time 660.933: waiting for ack: timeout, retrying > amandad: time 670.924: dgram_recv: timeout after 10 seconds > amandad: time 670.924: waiting for ack: timeout, giving up! > amandad: time 670.936: pid 13540 finish time Thu Mar 16 21:01:19 2006 > > Thus I assume that I need to amend my IPCHAIN rule from ipchains -M -S > 7200 10 300 to > ipchains -M -S 7200 10 800 > I think this is a red herring, but I could be wrong. Matt -- Matt Hyclak Department of Mathematics Department of Social Work Ohio University (740) 593-1263