Re: NAK: amandad busy from unfinishing selfchecks

2001-10-12 Thread Chris Marble 

peanut butter wrote:
 
 Hi, I'm using version 2.4.2p2 of Amanda.  For a particular client on
 which I use tar with Amanda to back up a single directory, this entry
 has worked fine until I aborted an amdump several days ago (at least I
 think these are connected).  The next amdump (or one very soon
 afterward) would show a no estimate with an amstatus for this machine
 and finally a FAILED for the email report.  Amchecks started coming
 back with NAK:  amandad busy for this machine.  Investigating this, I
 noticed that two processes from the amanda user were running on the
 client, an amandad and (likely, in retro) a
 /usr/local/libexec/amanda/2.4.2p2/sendsize.  I killed these but an
 amcheck only started two new ones--amandad and
 /usr/local/libexec/amanda/2.4.2p2/selfcheck--which would continue to
 run until I would kill them.  One time I let them run over a
 night or two to see if they would ever finish or be cleaned up.  Alas,
 it would seem they would run forever if I let them.  If I kill them, an
 amcheck will start them again and subsequent amchecks will give me the
 dreaded NAK:  amandad busy message.

I've got a mix of 2.4.2 and 2.4.2p2 on Linux, Solaris, HP-UX and
IRIX systems.  I'm using varients of dump everywhere.  I've never had
a problem with amanda processes restarting once I got them killed.
Have you run an amcleanup on your server?  Is there anything left
around that you need to amflush?
-- 
  [EMAIL PROTECTED] - HMC UNIX Systems Manager

Re: NAK: amandad busy from unfinishing selfchecks

2001-10-12 Thread peanut butter 

-In response to your message-
  --received from Chris Marble--
 
 I've got a mix of 2.4.2 and 2.4.2p2 on Linux, Solaris, HP-UX and
 IRIX systems.  I'm using varients of dump everywhere.  I've never had
 a problem with amanda processes restarting once I got them killed.
 Have you run an amcleanup on your server?  Is there anything left
 around that you need to amflush?
 -- 
   [EMAIL PROTECTED] - HMC UNIX Systems Manager


Hi, and thanks for the response.  It's not that the processes would
restart on their own but that, once started, they wouldn't ever
complete and go away (I would eventually have to kill them).

It now appears that the amdump I killed several days ago, though
any Amanda processes on the client were killed, somehow left the port
for that client used.  System messages were as such:

Oct 11 10:01:01 mamacass inetd[26156]: fs/tcp: bind: Address already in use
Oct 11 10:11:18 mamacass inetd[26156]: fs/tcp: bind: Address already in use
Oct 11 10:21:40 mamacass inetd[26156]: fs/tcp: bind: Address already in use
Oct 11 10:31:59 mamacass inetd[26156]: fs/tcp: bind: Address already in use
Oct 11 10:36:39 mamacass inetd[26156]: /usr/local/libexec/amanda/2.4.2p2/amandad : 
Killed
Oct 11 10:42:17 mamacass inetd[26156]: fs/tcp: bind: Address already in use
Oct 11 10:52:38 mamacass inetd[26156]: fs/tcp: bind: Address already in use

The amandad being killed was a manual kill on my part but you can
see that it was trying to run in the same port that earlier (and
later) messages claimed was already in use.  The particular port
number was unexpected as I have Amanda set up to run on the usual port
numbers.

One thing leading to another, to make a long story short, an
eventual reboot (making a bunch of people unhappy) ended up
resolving the problem.  Thanks, again.

Paul



-- 
Paul Yeatman   (858) 534-9896[EMAIL PROTECTED]
 ==
 ==Proudly brought to you by Mutt==
 ==