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
