On Thu, 26 Feb 2004 at 10:16am, jlm17 wrote
> tcpdump gives me this:
> tcpdump -vv -i lo
> tcpdump: listening on lo, link-type EN10MB (Ethernet), capture size 68 bytes
> 10:08:27.706802 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF],
> length: 145) royal.inse.lucent.com.798 > royal.inse.lucent.com.amanda:
> UDP, length: 117
> 10:08:37.704970 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF],
> length: 145) royal.inse.lucent.com.798 > royal.inse.lucent.com.amanda:
> UDP, length: 117
> 10:08:47.706323 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF],
> length: 145) royal.inse.lucent.com.798 > royal.inse.lucent.com.amanda:
> UDP, length: 117
Those are the packets from amcheck. As you can see, there's no reply.
amandad isn't getting started.
> Additionally I figured out that xinetd logs some stuff in /var/log/auth.log:
>
> Feb 26 10:08:27 royal xinetd[5766]: START: amanda pid=5941
> from=152.148.113.221
> Feb 26 10:08:27 royal xinetd[5941]: FAIL: amanda address
> from=152.148.113.221
>
> Still not very useful though. I have changed the amandad config in xinetd:
Actually, that is pretty useful. From 'man xinetd.log':
A FAIL entry has the format:
FAIL: service-id reason [from=%d.%d.%d.%d]
Possible reasons are:
.
.
address the address check failed
I'd guess that reverse lookups aren't working? Are you sure you restarted
xinetd after removing the 'only_from' directive? Because that address
check is your problem.
--
Joshua Baker-LePain
Department of Biomedical Engineering
Duke University
