Could it be that Amanda has a maximum retries that was exceeded ? Scott R. Burns NETCON Technologies Incorporated Suite 135 - 4474 Blakie Road London, Ontario, Canada N6L 1G7 Voice: +1.519.652.0401 Fax: +1.519.652.9275 Web: www.netcontech.com
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Paul Yeatman Sent: Thursday, November 17, 2005 9:03 PM To: Paul Bijnens Cc: Amanda user's group Subject: Re: amanda over wireless network Hmmmm, I set the server side etimeout to 2600s. Still get (from an amstatus) pjmac:/ 0 planner: [Estimate timeout from pjmac] and the amanda report now gives this (mind you, this client is the only entry in this "test" config) Estimate Time (hrs:min) 2:10 2 hours and 10 minutes! The message from amandad on the client is virtually the same <snip> amandad: time 0.038: running service "/usr/local/libexec/amanda/2.4.5p1/sendsize" amandad: time 1244.905: sending REP packet: ---- Amanda 2.4 REP HANDLE 000-30F3BC2A55000000 SEQ 1132261451 OPTIONS features=fffffeff9ffe7f; / 0 SIZE 17648480 ---- amandad: time 1254.905: dgram_recv: timeout after 10 seconds amandad: time 1254.905: waiting for ack: timeout, retrying amandad: time 1264.906: dgram_recv: timeout after 10 seconds amandad: time 1264.906: waiting for ack: timeout, retrying amandad: time 1274.906: dgram_recv: timeout after 10 seconds amandad: time 1274.906: waiting for ack: timeout, retrying amandad: time 1284.906: dgram_recv: timeout after 10 seconds amandad: time 1284.906: waiting for ack: timeout, retrying amandad: time 1294.907: dgram_recv: timeout after 10 seconds amandad: time 1294.907: waiting for ack: timeout, giving up! amandad: time 1294.907: pid 29584 finish time Thu Nov 17 14:52:41 2005 Shouldn't the approx. 1255s required to get the estimate fall clearly within the 2600s allowed? Not sure where things are going wrong now Paul -- Paul Yeatman (858) 534-9896 [EMAIL PROTECTED] ================================== ==Proudly brought to you by Mutt== ==================================
