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