Joe Donner (sent by Nabble.com) schreef:

Hi,

I'm running Amanda in a test lab, and every several days or so the backup
job to virtual tape fails because a process called amandad becomes
unresponsive on the backup client.  When doing an amcheck from the Amanda
server it tells me that amandad on the client is "busy".  When having a look
at the client with the ps command, it lists two diferent amandad processes,
with one showing as being "defunct".  I cannot kill this process, but when I
kill the other amandad process I can get rid of both, but then have to
reboot the client to get the backup job to work again.

Do you know how I can avoid doing this reboot, or what may be going on here?

Reboot is a pretty drastic remedy :-)
When the amandad process is killed, doesn't xinetd listen on
port 10080/udp again?

Do you have any idea what is "failing"?  Usually in the debug files

The error "amandad" busy actually indicates to me that the amandad is
still active on that client: that is the response you get from the first
amandad when you want to start another dump or check.


--
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          *
***********************************************************************