On 07/18/2014 11:43 AM, Gene Heskett wrote:
On Friday 18 July 2014 11:34:16 Olivier Nicole did opine
And Gene did reply:
Gene,
On Fri, Jul 18, 2014 at 9:26 PM, Gene Heskett <ghesk...@wdtv.com> wrote:
Greeting Jean-Louis;
Trying to figure out why amanda can't backup this machine, one of the
things I noticed in /etc, is that on the shop box, which works, there
is not an /etc/xinetd.d but it has an old-xinetd.d with a single
stanza amanda file in it.
An ls -lau shows that file, /etc/old-xinetd.d/amanda was apparently
accessed a few minutes ago by my amcheck from the server.
However, on the new install on the machine that is failing to allow
the connection, there is an /etc/xinet.d, with an amanda file in it
with an old last access date/time, was not 'touched' when I ran the
amcheck. Its last access date/time is I believe, the date/time of
the installation itself.
That amanda-common is 2.6.1p1 IIRC.
amcheck says:
WARNING: lathe: selfcheck request failed: Connection refused
There has been enough configuration done that amrecover on this
machine works.
There is a /var/backups/.amandahosts file, its a link to
/etc/amandahosts BUT, in /etc/.amandahosts. I'll mv it to
/etc/amandahosts. Ran amcheck, no change and that file was not
accessed.
What do I check next?
netstat -na |grep 10080
You should see an UDP open on that port, else it means xinetd is not
running/not listening for amanda.
Olivier
gene@lathe:/etc/xinetd.d$ netstat -na |grep 10080
udp 0 0 0.0.0.0:10080 0.0.0.0:*
udp 0 0 0.0.0.0:10080 0.0.0.0:*
IIRC thats good.
It's not good, this is for bsd auth, you want to use bsdtcp.
Next?
Thanks Olivier.
Cheers, Gene Heskett
