Dave Brooks ([EMAIL PROTECTED]):
> I'm trying to get amanda 2.4.2p2 rolling on one of my servers here,
> but I'm having a little issue with amandad (and possibly xinetd,
> though I think I could work around that).
> Basically, if I try to manually invoke amandad from the command line,
> everything seems well for about the first 30 seconds, at which time the
> process terminates and leaves the following ditty in
> /tmp/amanda/amandad*debug:
> amandad: dgram_recv: timeout after 30 seconds
> amandad: error receiving message: timeout
> error receiving message: timeout
> amandad: pid 16566 finish time Wed Sep 26 15:30:11 2001
This is probably the way it's supposed to work. You don't want the
amandad running all the time, only when it's contacted by the amanda
backup server.
> The amandad process is being invoked as root. Same happens if invoked with
> the amanda user.
You should run it as the user that it was compiled to run as. This
should also be set in your xinetd configuration file(s).
> Any ideas on what could be going awry? This of course
> causes problems because amanda then can't connect to the client daemon
> (which, in this case, happens to be on the same machine) and nothing gets
> written to tape.
If you use amcheck it will try to connect to the client daemon
(amandad) the proper way and then tell you if there are any problems.
--
Jeremy Wadsack
Wadsack-Allen Digital Group
