The command you should run is:
lsof -I :amanda
Which should show the inetd/xinetd process listening on the amanda port
(UDP port 10080). The output should look something like this:
ritcdx> lsof -i :amanda
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
inetd 1285913 root 28u IPv4 0x5fe888c0 0t0 UDP *:amanda
Unless you are very lucky during your testing, this is probably all you
will ever see on the port except when Amanda is actually performing a
backup.
Best wishes,
Donald L. (Don) Ritchey
Information Technology, Exelon Corporation
-----Original Message-----
From: owner-amanda-users AT amanda DOT org
[mailto:owner-amanda-users AT amanda DOT org] On Behalf Of up AT 3 DOT am
Sent: Wednesday, September 13, 2006 11:41 AM
To: amanda-users AT amanda DOT org
Subject: Re: "selfcheck request timed out" WAS Re: Running amanda client
only
Replying to my own post (sorry, but I'm getting desperate here), I took
the advice of the FAQ-O-Matic and installed lsof and ran this command:
su-2.05b# lsof -uamanda
There was no output. Should there have been? Does this mean that
amandad
is not running? This is what I have in my /etc/inetd.conf:
amanda dgram udp wait amanda /usr/local/libexec/amandad amandad
inetd.conf has beek killed and restarted, the client even
rebooted...anything?
On Wed, 13 Sep 2006 up AT 3 DOT am wrote:
> On Wed, 13 Sep 2006, Toomas Aas wrote:
>
> > up AT 3 DOT am wrote:
> >
> > > The server is reporting that client down, so I checked and noticed
that
> > > the FBSD port for the amanda-client did not install amindexd or
> > > amidxtaped, although it did install amandad. Are all 3 needed for
a
> > > client?
> >
> > No, for client only amandad is needed.
>
> Then I cannot figure out why I'm getting "selfcheck request timed out"
> from that client. The path in inetd.conf is correct, as is the user
> (amanda) and /tmp/amanda is owned by amanda and has debug files there
> (just config info). .amandaclients has localhost.fqdn as well as
> hostname.fqdn. That client IS running alot of IP addresses on it, but
> I've done that before with no trouble.
>
> Here is amcheck -c output:
>
> su-2.05b$ amcheck -c weekly
>
> Amanda Backup Client Hosts Check
> --------------------------------
> ERROR: old.amanda.client: [host someIP.comcastbiz.net: hostname lookup
> failed]
> WARNING: new.amanda.client: selfcheck request timed out. Host down?
> Client check: 2 hosts checked in 30.153 seconds, 2 problems found
>
> I understand the first error from the old client...there is no forward
DNS
> on that IP (BTW, is there a way around that? Just have it look at IP
> address?). I can't figure out the cause of the second one...I went
> through everything on the FAQ-O-Matic about it...
>
> James Smallacombe PlantageNet, Inc. CEO and Janitor
> up AT 3 DOT am
http://3.am
>
========================================================================
=
>
>
James Smallacombe PlantageNet, Inc. CEO and Janitor
up AT 3 DOT am http://3.am
========================================================================
=
-----------------------------------------
**************************************************
This e-mail and any of its attachments may contain Exelon
Corporation proprietary information, which is privileged,
confidential, or subject to copyright belonging to the Exelon
Corporation family of Companies.
This e-mail is intended solely for the use of the individual or
entity to which it is addressed. If you are not the intended
recipient of this e-mail, you are hereby notified that any
dissemination, distribution, copying, or action taken in relation
to the contents of and attachments to this e-mail is strictly
prohibited and may be unlawful. If you have received this e-mail
in error, please notify the sender immediately and permanently
delete the original and any copy of this e-mail and any printout.
Thank You.
**************************************************
|
