Amanda-Users

Re: amdump: request timed out.. already read FAQ & troubleshooting

2004-04-29 06:00:22
Subject: Re: amdump: request timed out.. already read FAQ & troubleshooting
From: Paul Bijnens <paul.bijnens AT xplanation DOT com>
To: Kris Vassallo <kris AT linuxcertified DOT com>
Date: Thu, 29 Apr 2004 11:57:26 +0200


Increase the "etimeout", see below.



Kris Vassallo wrote:

Increase the "etimeout", see below.

amandad: debug 1 pid 12359 ruid 33 euid 33: start at Wed Apr 28 23:59:01 2004

Completely off topic, but I find it more "logical" to run the backup just after midnight, instead of just before, in the case where 2 minutes don't matter. In that case there is no confusion on the date of backup: the backup dated 29-Apr-2004 is the one from the early morning, and the date on the report is exactly the same. In your case the backup would be labelled 28-Apr-2004, and the corresponding report would be dated 29-Apr-2004.
Completely off-topic anyway.

amandad: time 0.000: got packet:
--------
Amanda 2.4 REQ HANDLE 000-C0710608 SEQ 1083221943
SECURITY USER amanda
SERVICE sendsize
OPTIONS features=fffffeff9f00;maxdumps=1;hostname=venus.berkeley-da.com;
GNUTAR /backup/repo 0 1970:1:1:0:0:0 -1 OPTIONS |;auth=bsd;compress-best;index;
GNUTAR /home 0 1970:1:1:0:0:0 -1 OPTIONS |;auth=bsd;compress-best;index;
--------

amandad: time 0.001: sending ack:
----
Amanda 2.4 ACK HANDLE 000-C0710608 SEQ 1083221943
----

The client received a packet asking for the service "sendsize" and
ackownledged it.

You mentioned there were two debugfiles.
I would have expected that the first "amandad" debug file contained
the request for service "noop" with the acknowledgement.  The "noop"
request just exchanges the features between the client and server.


amandad: time 0.001: bsd security: remote host venus.berkeley-da.com user 
amanda local user amanda
amandad: time 0.001: amandahosts security check passed
amandad: time 0.001: running service "/usr/lib/amanda/sendsize"
amandad: time 600.977: got packet:

To me this seems like /usr/lib/amanda/sendsize has not yet finished,
and the etimeout of 300 seconds times 2 DLE's kicked in.

There should be sendsize.DATETIME.debug file too.


amandad: time 4244.080: sending REP packet:

After 4244 seconds, 1 hours 10 minutes, sendsize finished, but
the server already gave up waiting for it:

----
Amanda 2.4 REP HANDLE 000-C0710608 SEQ 1083221943
OPTIONS features=fffffeff9f00;
/home 0 SIZE 209076080
/backup/repo 0 SIZE 323990
----

The /home filesystem uses over 200 Gbyte.  Is that correct?
I hope your tape is large enough.

Increase etimeout, and/or divide the /home in more
manageable pieces.


--
Paul Bijnens, Xplanation                            Tel  +32 16 397.511
Technologielaan 21 bus 2, B-3001 Leuven, BELGIUM    Fax  +32 16 397.512
http://www.xplanation.com/          email:  Paul.Bijnens AT xplanation DOT com
***********************************************************************
* I think I've got the hang of it now:  exit, ^D, ^C, ^\, ^Z, ^Q, F6, *
* quit,  ZZ, :q, :q!,  M-Z, ^X^C,  logoff, logout, close, bye,  /bye, *
* stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt,  abort,  hangup, *
* PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e,  kill -1 $$,  shutdown, *
* kill -9 1,  Alt-F4,  Ctrl-Alt-Del,  AltGr-NumLock,  Stop-A,  ...    *
* ...  "Are you sure?"  ...   YES   ...   Phew ...   I'm out          *
***********************************************************************