Please keep the discussion on the list, there may be other
people with tips of the solution, and it may help other
people with the same problem.
shoaib r wrote:
The debug logs gave me this as the only error:
/tmp/amanda/amandad.20051021010122.debug
------------------------------------------------
Amanda 2.4 NAK HANDLE 000-000344C0 SEQ 1129852801
ERROR amandad busy
----
amandad: time 3615.713: got packet:
----
Amanda 2.4 REQ HANDLE 000-00034708 SEQ 1129852802
------------------------------------------------
The "amandad busy" means that the server did sent a request while
the client was still busy with processing another request.
That could happen when you have more than one amandaserver and
the amandad on the client is already busy with another server.
Make sure a client has all his disklist entries in only one server.
Or you could have a stuck amandad client, still handling some request
from the previous test. Kill all the amanda processes on the client,
and try again.
--
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, *
* init 0, kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ... *
* ... "Are you sure?" ... YES ... Phew ... I'm out *
***********************************************************************
|
