I had a similar problem with amanda 2.4.1p2 on Solaris 8 client (no
auditing..).
After much of the same kinds of debugging techniques (this list is
great!) I discovered that the client side amandad was dying due to
inability to find a shared library. The problem only showed up when
amandad was called by inetd, i.e. if you ran amandad manually on the
client as the backup user, it worked.
I discovered this by doing the shell script hack that John suggested.
The fix was ugly and dumb -
1) set LD_LIBRARY_PATH in /etc/init.d/inetsvc to include the amanda
libs.
2) copy the shared lib it was missing into the $AMANDA/libexec
directory.
One would think that including the path to the libs should have been
enough, but it wasn't. I did not spend more cycles trying to figure out
why.
Hope this helps,
alex
Doug Silver wrote:
>
> This is when I manually ran it.
>
> # cat amandad.out.63688
> Sat Jun 2 10:20:24 PDT 2001: starting amandad
> Sat Jun 2 10:20:54 PDT 2001: amandad done: status is 1
>
> more /tmp/amanda/amandad.xxx.debug
> amandad: debug 1 pid 63690 ruid 0 euid 0 start time Sat Jun 2 10:20:24
> 2001
> [compile info - snip]
> amandad: dgram_recv: timeout after 30 seconds
> amandad: error receiving message: timeout
> error receiving message: timeout
> amandad: pid 63690 finish time Sat Jun 2 10:20:54 2001
>
> /var/log/messages:
> Jun 1 10:55:05 mail inetd[152]: amanda/udp server failing (looping),
> service terminated
> Jun 1 10:57:58 mail inetd[152]: amanda/udp server failing (looping),
> service terminated
>
> Here's the inetd.conf entry:
> amanda dgram udp wait root /usr/local/libexec/amandad.test
> amandad
>
> As best as I can tell, no, amanda is not executing, even though with
> tcpdump I see two udp packets showing up at the machine. It seems that
> inetd shuts off that service after the first packet gets there. Inetd is
> also running pop and imap, so it's not as if inetd isn't working for other
> services.
>
> Any other suggestions?
>
> Thanks!
>
> -doug
>
> On Fri, 1 Jun 2001, John R. Jackson wrote:
>
> > >Done. The script still doesn't execute ...
> >
> > Doesn't execute at all???
> >
> > Is anything logged to /var/adm/messages (or wherever inetd puts
> > stuff)?
> >
> > What happens if you run the script as your Amanda user (root?). It should
> > sit for 30 seconds and then terminate, and you should get the script
> > output file.
> >
> > >-doug
> >
> > John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
> >
>
> --
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> Doug Silver
> Quantified Systems, Inc
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~