RE: problems using amanda with xinetd
2003-06-10 15:49:04
[...]
> i had to create the /etc/xinetd.d/amanda file as i've installed amanda
> from source. i've confirmed, from the syslog (and the syscall trace),
> that the service is correctly configured.
And the amanda service shows up in netstat -a output as well, I suppose?
> ? i don't notice any change in behavior of amanda. xinetd logs notices
> of service changes, if that's what you're referring to.
I meant, any change in behaviour (xinetd, amanda,...). So, you are changing
the xinetd config, but nothing changes in the resulting behaviour... ok.
> Jun 10 14:21:54 [xinetd] xinetd Version 20030122 started with
> libwrap loadavg options compiled in.
> Jun 10 14:21:54 [xinetd] Started working: 2 available services
That's ok, assuming you verified that only two services should be serviced
by xinetd.
> > Last resort: pull out tcpdump or ethereal and see what's
> actually happening
> > on the wire.
>
> that's an idea.
here is another one (to take xinetd and networking out of the equation), use
netcat on the server system and connect via UDP to the Amanda port:
nc -u client.domain.com 10080
type
Amanda
that should give you an error like this
Amanda 2.4 NAK HANDLE SEQ 0
If you get this far, I doubt the problem is with xinetd or inetd.
Now check /tmp/amanda/amandad.<WhateverDateTimeYouDidThis>.debug on the
client and you should find your connection attempt there. If not, I suggest
recompiling with debugging turned on.
Bernhard
|
|
|