selfcheck request timed out problem !!
Hi,
I have this problem that's getting me mad!
Amanda used to work very fine between the backup server (gentoo/ Amanda
installed through emerge amanda), and my personal pc (ubuntu/ Amanda
installed through apt-get install amanda-client).
Now we have moved the backup server to a different network zone and now the
Amanda client is installed on a server on the same zone (no firewall). The
client has gentoo installed, and since there's no amanda-client in gentoo
portage amanda is installed (client with server) emerge amanda I'm not
sure if this can cause problems .
The situation right know is as the following:
The backup server:
-
$ hostname -f
backup..com
/etc/amanda/amandahosts:
auth02..com root
/etc/amanda/daily/disklist:
auth02 /etc comp-user-tar
/etc/xinetd.d/amanda:
service amanda
{
disable = no
socket_type = stream
protocol= tcp
wait= no
user= amanda
group = amanda
groups = yes
server = /usr/local/libexec/amandad
server_args = -auth=bsdtcp amdump amindexd amidxtaped
}
cat /etc/services | grep amanda
amanda 10080/tcp # amanda backup services
amanda 10080/udp
kamanda 10081/tcp # amanda backup services
(Kerberos)
kamanda 10081/udp
amandaidx 10082/tcp # amanda backup services
amidxtape 10083/tcp # amanda backup services
The client:
hostname -f
auth02..com
/etc/amanda/amandahosts:
backup..com amanda
/etc/xinetd.d/amanda:
service amanda
{
socket_type = dgram
protocol= udp
wait= yes
user= amanda
group = amanda
groups = yes
server = /usr/libexec/amandad
server_args = -auth=bsd amdump amindexd amidxtaped
disable = no
}
cat /etc/services | grep amanda
amanda 10080/tcp # amanda backup services
amanda 10080/udp
kamanda 10081/tcp # amanda backup services
(Kerberos)
kamanda 10081/udp
amandaidx 10082/tcp # amanda backup services
amidxtape 10083/tcp # amanda backup services
Now when:
backup ~ # su - amanda -c /usr/sbin/amcheck daily:
WARNING: auth02..com: selfcheck request timed out. Host down?
Client check: 1 host checked in 29.999 seconds, 1 problem found
What do you suggest? I tried a lot but couldn't get it to work, is there
something missing on the client? Something wrong? Is it a problem with
amanda service? Maybe a permissions problem?
Thanks in advance
--
Anas Marrawi
Visit me at: www.anasonline.net
Re: selfcheck request timed out problem !!
[EMAIL PROTECTED] schrieb: What do you suggest? Take a look at the wiki and check possible problems/solutions: http://wiki.zmanda.com/index.php/Selfcheck_request_failed -- Marc Muehlfeld (Leitung Systemadministration) Zentrum fuer Humangenetik und Laboratoriumsmedizin Dr. Klein und Dr. Rost Lochhamer Str. 29 - D-82152 Martinsried Telefon: +49(0)89/895578-0 - Fax: +49(0)89/895578-78 http://www.medizinische-genetik.de
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 [EMAIL PROTECTED] wrote: On Wed, 13 Sep 2006, Toomas Aas wrote: [EMAIL PROTECTED] 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 [EMAIL PROTECTED] http://3.am = James Smallacombe PlantageNet, Inc. CEO and Janitor [EMAIL PROTECTED] http://3.am =
Re: selfcheck request timed out WAS Re: Running amanda client only
[EMAIL PROTECTED] wrote: 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? No, amandad should not be running except during a backup. When the server connects to the amanda port on the client inetd starts amandad. 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? Have you tried running /usr/local/libexec/amandad from the command line on the client (it should just sit there and eventually time out and return your prompt, or immediately exit if you hit a key)? Perhaps you're missing a library (or need to run ldconfig or whatever is needed to update the dynamic library cache on your platform). Does the system log inetd even running amandad? Does amandad run and create anything in /tmp/amanda? Frank On Wed, 13 Sep 2006 [EMAIL PROTECTED] wrote: On Wed, 13 Sep 2006, Toomas Aas wrote: [EMAIL PROTECTED] 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 [EMAIL PROTECTED] http://3.am = James Smallacombe PlantageNet, Inc. CEO and Janitor [EMAIL PROTECTED] http://3.am = -- Frank Smith [EMAIL PROTECTED] Sr. Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
Re: selfcheck request timed out WAS Re: Running amanda client only
On Wed, 13 Sep 2006, Frank Smith wrote: [EMAIL PROTECTED] wrote: 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? No, amandad should not be running except during a backup. When the server connects to the amanda port on the client inetd starts amandad. 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? Have you tried running /usr/local/libexec/amandad from the command line on the client (it should just sit there and eventually time out and return your prompt, or immediately exit if you hit a key)? Perhaps you're missing a library (or need to run ldconfig or whatever is needed to update the dynamic library cache on your platform). Does the system log inetd even running amandad? Does amandad run and create anything in /tmp/amanda? Thanks for your reply. I did run it from the command line and it eventually times out, although it does not exit immediately if I type something. debug files are created in /tmp/amanda, but not with any useful info...just how it was compiled. There is absolutely nothing in /var/log/messages about amanda(d). I thought ldconfig was run upon boot...in any case, if I'm missing some kind of lib, wouldn't amanda complain about it when trying to build it? Thanks again for any help... James Smallacombe PlantageNet, Inc. CEO and Janitor [EMAIL PROTECTED] http://3.am =
Re: selfcheck request timed out WAS Re: Running amanda client only
[EMAIL PROTECTED] wrote: On Wed, 13 Sep 2006, Frank Smith wrote: [EMAIL PROTECTED] wrote: 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? No, amandad should not be running except during a backup. When the server connects to the amanda port on the client inetd starts amandad. 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? Have you tried running /usr/local/libexec/amandad from the command line on the client (it should just sit there and eventually time out and return your prompt, or immediately exit if you hit a key)? Perhaps you're missing a library (or need to run ldconfig or whatever is needed to update the dynamic library cache on your platform). Does the system log inetd even running amandad? Does amandad run and create anything in /tmp/amanda? Thanks for your reply. I did run it from the command line and it eventually times out, although it does not exit immediately if I type something. 2.4.5 will exit if you hit enter, 2.5 doesn't. debug files are created in /tmp/amanda, but not with any useful info...just how it was compiled. There is absolutely nothing in /var/log/messages about amanda(d). Inetd doesn't normally log unless you start it with a debug option. In your case, since a debug file is created then inetd is working so you may not need to check further on that. Post the debug file on the client and maybe we can see at what stage of the connection it stops. Are you running a firewall on or between the client? I thought ldconfig was run upon boot...in any case, if I'm missing some kind of lib, wouldn't amanda complain about it when trying to build it? The ldconfig suggestion is only relevant if running amandad from the command line returns a missing library error, sorry I wasn't clear about that. And yes it would complain on build, I was thinking more of cases where amanda lives on a shared filesystem or are copied to multiple machines. Frank Thanks again for any help... James Smallacombe PlantageNet, Inc. CEO and Janitor [EMAIL PROTECTED] http://3.am = -- Frank Smith [EMAIL PROTECTED] Sr. Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
Re: selfcheck request timed out WAS Re: Running amanda client only
On Wed, 13 Sep 2006, Frank Smith wrote: [EMAIL PROTECTED] wrote: On Wed, 13 Sep 2006, Frank Smith wrote: [EMAIL PROTECTED] wrote: 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? No, amandad should not be running except during a backup. When the server connects to the amanda port on the client inetd starts amandad. 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? Have you tried running /usr/local/libexec/amandad from the command line on the client (it should just sit there and eventually time out and return your prompt, or immediately exit if you hit a key)? Perhaps you're missing a library (or need to run ldconfig or whatever is needed to update the dynamic library cache on your platform). Does the system log inetd even running amandad? Does amandad run and create anything in /tmp/amanda? Thanks for your reply. I did run it from the command line and it eventually times out, although it does not exit immediately if I type something. 2.4.5 will exit if you hit enter, 2.5 doesn't. The client is 2.5.0p2, the server is 2.4.5. Could that be an issue? If so, which one do you recommend? debug files are created in /tmp/amanda, but not with any useful info...just how it was compiled. There is absolutely nothing in /var/log/messages about amanda(d). Inetd doesn't normally log unless you start it with a debug option. In your case, since a debug file is created then inetd is working so you may not need to check further on that. Post the debug file on the client and maybe we can see at what stage of the connection it stops. Are you running a firewall on or between the client? No firewall that I've configured...I did just hook up via comcast business though...nmap from the client back to the server looks ok...I can ssh back, as well. the debug files had what looked like nothing but a config.log, until I just looked now and noticed this huge (48MB) debug file with 670 thousand lines of this: amandad: dgram_recv: recvfrom() failed: Socket operation on non-socket amandad: dgram_recv: recvfrom() failed: Socket operation on non-socket amandad: dgram_recv: recvfrom() failed: Socket operation on non-socket James Smallacombe PlantageNet, Inc. CEO and Janitor [EMAIL PROTECTED] http://3.am =
Re: selfcheck request timed out. Host down?
On Monday 14 August 2006 00:52, Lengyel, Florian wrote: Pardon me: identd, not inetd. It wasn't a typo. I know about inetd and xinetd. I was disappointed to see that the debian hosts use inetd instead of xinetd. My bad, I actually missread it. Sorry. So was I, even more disappointed to see that ubuntu apparently isn't using either, virtually everything is controlled from /etc/init.d in a kubuntu install I just did on my cnc machine. On that box the only line in inetd.conf starts with disabled, and only 4 files live in the /etc/xinetd.d directory. identd could have some bearing on it I suppose, but having an identd, given that its used rather extensively as a verfication mechanism by using it as proof there is a machine at that address even if the port response indicates its closed is pretty universal. Here, I've got a pretty tight router and firewall setup, and the only response from my outside address when being scanned with nmap, is from a closed identd port thats actually located in the router. If I actually shut that response off, then I can't access half the web sites on the net. I think I'd start an identd daemon just for effects on that machine. It might not help, but it might not hurt either. [...] -- Cheers, Gene There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order. -Ed Howdershelt (Author) Yahoo.com and AOL/TW attorneys please note, additions to the above message by Gene Heskett are: Copyright 2006 by Maurice Eugene Heskett, all rights reserved.
RE: selfcheck request timed out. Host down?
Title: RE: selfcheck request timed out. Host down?
Pardon me: identd, not inetd. It wasn't a typo.
I know about inetd and xinetd. I was disappointed to see
that the debian hosts use inetd instead of xinetd.
-FL
-Original Message-
From: [EMAIL PROTECTED] on behalf of Gene Heskett
Sent: Mon 8/14/2006 12:03 AM
To: amanda-users@amanda.org
Subject: Re:
On Sunday 13 August 2006 23:20, Lengyel, Florian wrote:
Identical, except for identd on one client (the client that
doesn't work doesn't have identd).
Permissions and all? In some cases thats all important.
OTOH, the client that doesn't have inetd SHOULD have xinetd, and a
directory of control files in /etc/xinetd.d, and the one for the amanda
daemons should look something like this, noting that this file can be
named anything because its the contents that count:
=
# default = off
#
# description: Part of the Amanda server package
# This is the list of daemons such it needs
service amanda
{
disable = no
socket_type = dgram
protocol = udp
wait = yes
user = amanda
group = disk
groups = yes
server = /usr/local/libexec/amandad
}
service amandaidx
{
disable = no
socket_type = stream
protocol = tcp
wait = no
user = amanda
group = disk
groups = yes
server = /usr/local/libexec/amindexd
}
service amidxtape
{
disable = no
socket_type = stream
protocol = tcp
wait = no
user = amanda
group = disk
groups = yes
server = /usr/local/libexec/amidxtaped
}
==
Those paths are as installed by the tarball build, rpms will probably not
have the 'local' in the path. The user is whoever will be the one to
invoke amdump etc. The 'group' must have write perms to the disks.
If you edit this file, then do a 'service xinetd restart' from the command
line as root to make the edits effective w/o a reboot.
I hope this helps.
-Original Message-
From: [EMAIL PROTECTED] on behalf of Gene Heskett
Sent: Sun 8/13/2006 7:06 PM
To: amanda-users@amanda.org
Subject: Re:
On Sunday 13 August 2006 18:07, Lengyel, Florian wrote:
I'm using Amanda 2.4.4p3 on a Debian system (stable release)
I have one client that times out during the self-check--I'm mystified.
What do I do to debug this? There are no firewalls--everything is
on the same subnet.
[EMAIL PROTECTED] ~]$ amcheck Daily
Amanda Tape Server Host Check
-
WARNING: holding disk /var/tmp/amanda: only 9477560 KB free (10485760 KB
requested) amcheck-server: slot 2: date 20060713 label Daily002 (exact
label match) NOTE: skipping tape-writable test
Tape Daily002 label ok
Server check took 34.036 seconds
Amanda Backup Client Hosts Check
WARNING: rt: selfcheck request timed out. Host down?
Client check: 8 hosts checked in 30.485 seconds, 1 problem found
(brought to you by Amanda 2.4.4p3)
[EMAIL PROTECTED] ~]$
Double check the install on the client, everything. Compare to identical
files on another client, or even the server.
--
Cheers, Gene
There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order.
-Ed Howdershelt (Author)
Yahoo.com and AOL/TW attorneys please note, additions to the above
message by Gene Heskett are:
Copyright 2006 by Maurice Eugene Heskett, all rights reserved.
Re: WARNING: server.my.co.uk: selfcheck request timed out. Host down? this is a private IP address.
On 02/14/2006 02:25 AM, Kevin Till wrote: *Assume all outgoing packets are accepted/allowed.* For amdump to work, you need to open up: backup client : 10080(udp), a small range of tcp ports for data transfer e.g. 11000:11030 (recompile amanda with --with-tcpportrange=11000,11030) For amrecover to work, you need to open up: backup server: 10082(udp), 10083(udp), a small range of tcp ports for data transfer e.g. 11000:11030 (recompile amanda with --with-tcpportrange=11000,11030) I believe 10082 and 10083 are tcp, not udp. -- Paul Bijnens, xplanation Technology ServicesTel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 http://www.xplanation.com/ email: [EMAIL PROTECTED] *** * I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, ^^, * * F6, quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, * * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, * * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, * * init 0, kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ... * * ... Are you sure? ... YES ... Phew ... I'm out * ***
Re: [Fwd: Re: WARNING: server.my.co.uk: selfcheck request timed out. Host down? this is a private IP address.]
Hi Paul Bijnes Was the UDP also to be recompiled --with-udpportrange=11000,11030 thus the same port range as tcp. Cheers On Tue, 2006-02-14 at 08:19 +, chuck.amadi wrote: email message attachment (Re: WARNING: server.my.co.uk: selfcheck request timed out. Host down? thisis a private IP address.) On Tue, 2006-02-14 at 08:19 +, chuck.amadi wrote: -- Unix/ Linux Systems Administrator Chuck Amadi The Surgical Material Testing Laboratory (SMTL), Princess of Wales Hospital Coity Road Bridgend, United Kingdom, CF31 1RQ. Email chuck.smtl.co.uk Tel: +44 1656 752820 Fax: +44 1656 752830
Re: [Fwd: Re: WARNING: server.my.co.uk: selfcheck request timed out. Host down? this is a private IP address.]
On 02/14/2006 10:11 AM, Chuck Amadi Systems Administrator wrote: Hi Paul Bijnes Was the UDP also to be recompiled --with-udpportrange=11000,11030 thus the same port range as tcp. no, the only UDP connection is the one to 10080. But do allow the reply packet: in iptables, this is automatically, in ipchains this is not automatically (-- I believe -- it has been years since I used ipchains...). The server binds to a local port in the UDP-portrange, sends a packet to the client at port 10080, and must be able get the reply from client to server: you have to open the UDP-portrange on the firewall to allow the reply packet. The UDP-portrange must be 1024, otherwise, the client will complain about port not secure, and it will not work. The tcpportrange is used to send the data/mesg/index stream from client to server. You need 3 tcp connections for each host that is doing a backup in parallel. -- Paul Bijnens, xplanation Technology ServicesTel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 http://www.xplanation.com/ email: [EMAIL PROTECTED] *** * I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, ^^, * * F6, quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, * * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, * * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, * * init 0, kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ... * * ... Are you sure? ... YES ... Phew ... I'm out * ***
Re: WARNING: server.my.co.uk: selfcheck request timed out. Host down? this is a private IP address.
Hi I have re compiled amanda client on the server that sits outside of
my LAN with the following port range. --with-udpportrange=1100,11030
Thus you stating that it must be a system udp port range i.e 1023
If So I have Unassigned range -f 1001-1009 So I would use this when I re
compile a udp system port range --with-udpportrange=1001,1009 Does the
tcp port range stay the same. --with-tcpportrange=1100,11030 .
My IPChain example.
ipchains -A input -p udp -i -s $193.XXX.XXX.XXX{AMANDA_CLIENT} 1001:1009
--dport $192.168.1.XXX{AMANDA_SERVER} -j ACCEPT
ipchains -A input -p tcp -i -s $193.XXX.XXX.XXX {AMANDA_CLIENT}
10080:10083 --dport $192.168.1.XXX{AMANDA_SERVER} -j ACCEPT
CheersOn Tue, 2006-02-14 at 10:44 +0100, Paul Bijnens wrote:
On 02/14/2006 10:25 AM, Chuck Amadi Systems Administrator wrote:
Hi Agian
I am re compiling my amanda client thus after running the switch
--with-udpportrange=11000,110030 and --with-tcpportrange=11000,110030
I edit the /etc/services on the amanda client and add the following:
# Leave this lot intact:
amanda 10080/tcp # Amanda
the 10080/tcp is not used.
amanda 10080/udp # Amanda
amandaidx 10082/tcp
amidxtape 10083/tcp
# Check that these port ranges are Unassigned.
amanda 11000-11030/tcp # Amanda
(--with-tcpportrange=11000,110030)
amanda 11000-11030/udp # Amanda
(--with-udpportrange=11000,110030)
I think these two will give a syntax error in /etc/services :-)
You cannot give a name to a range (and the name amanda must
be for the 10080/udp port!)
Moreover, it is not strictly needed that the range is unassigned.
When Amanda wants to use a port in the range that is already in
use by something else, it will simply skip that port.
But because you need 3 tcp connections for each dump in parallel,
(inparallel in amanda.conf) you must add some extra ports in
the range to take into account the ports that are already in use.
--
Unix/ Linux Systems Administrator
Chuck Amadi
The Surgical Material Testing Laboratory (SMTL),
Princess of Wales Hospital
Coity Road
Bridgend,
United Kingdom, CF31 1RQ.
Email chuck.smtl.co.uk
Tel: +44 1656 752820
Fax: +44 1656 752830
WARNING: server.my.co.uk: selfcheck request timed out. Host down? this is a private IP address.
Hi List I have added a new Amanda client that doesn't belong to my LAN it's our zope/web server that has a public address and is on another network it's entry is in my dns server and in the /etc/hosts file which I thought would be it's first port of call before asking the ns server. Both LAN and zope/web server sit behind our firewall. Could be that because it's on another network LAN's 192.168.1.xx broadcast 255.255.255.0 and 123.345.567.89 225.225.225.224 or can I possible use the public IPA instead of server.my.co.uk in the DLE on the tape server. I am assuming this is something to do with my firewall. I have amandad running on the new amanda client. but I get the following error when amcheck runs fron the cron. I have created /var/lib/amanda/DailySet1/curinfo/server.my.co.uk/_ directory and chown amanda.disk. Also when I run the following commands server:/etc/xinetd.d # netstat -a | grep -i amanda tcp0 0 *:amandaidx *:* LISTEN udp0 0 *:amanda *:* server:/etc/xinetd.d # server:/etc/xinetd.d # ps auxxx|egrep amanda amanda 14847 0.0 0.3 4160 872 pts/3S12:30 0:00 [su] amanda 14848 0.0 0.6 4620 1584 pts/3S12:30 0:00 bash root 18452 0.0 0.1 3540 500 pts/3S15:51 0:00 /bin/grep -E amanda server:/etc/xinetd.d # Error Message below: WARNING: info file /var/lib/amanda/DailySet1/curinfo/server.my.co.uk/_/info: does not exist Server check took 10.788 seconds Amanda Backup Client Hosts Check WARNING: server.my.co.uk: selfcheck request timed out. Host down? Client check: 4 hosts checked in 29.328 seconds, 1 problem found -- Unix/ Linux Systems Administrator Chuck Amadi The Surgical Material Testing Laboratory (SMTL), Princess of Wales Hospital Coity Road Bridgend, United Kingdom, CF31 1RQ. Email chuck.smtl.co.uk Tel: +44 1656 752820 Fax: +44 1656 752830
Re: WARNING: server.my.co.uk: selfcheck request timed out. Host down? this is a private IP address.
Hi List I had a look on the amanda client less /tmp/amanda less amandad.20060213153537.debug Here is the debug report: Amanda 2.4 REQ HANDLE 003-E0990808 SEQ 1139841004 SECURITY USER amanda SERVICE noop OPTIONS features=feff9ffe0f; amandad: time 9.815: it is not an ack amandad: time 9.815: sending REP packet: Amanda 2.4 REP HANDLE 003-E0990808 SEQ 1139841004 ERROR [host fw.my.co.uk: port * not secure] amandad: time 18.975: got packet: Amanda 2.4 REQ HANDLE 003-E0990808 SEQ 1139841004 SECURITY USER amanda SERVICE noop OPTIONS features=feff9ffe0f; amandad: time 18.975: it is not an ack amandad: time 18.975: sending REP packet: Thus I assume I need to add rules for the Firewall server: Any examples or notes Cheers On Mon, 2006-02-13 at 14:51 +, Chuck Amadi Systems Administrator wrote: Hi List I have added a new Amanda client that doesn't belong to my LAN it's our zope/web server that has a public address and is on another network it's entry is in my dns server and in the /etc/hosts file which I thought would be it's first port of call before asking the ns server. Both LAN and zope/web server sit behind our firewall. Could be that because it's on another network LAN's 192.168.1.xx broadcast 255.255.255.0 and 123.345.567.89 225.225.225.224 or can I possible use the public IPA instead of server.my.co.uk in the DLE on the tape server. I am assuming this is something to do with my firewall. I have amandad running on the new amanda client. but I get the following error when amcheck runs fron the cron. I have created /var/lib/amanda/DailySet1/curinfo/server.my.co.uk/_ directory and chown amanda.disk. Also when I run the following commands server:/etc/xinetd.d # netstat -a | grep -i amanda tcp0 0 *:amandaidx *:* LISTEN udp0 0 *:amanda *:* server:/etc/xinetd.d # server:/etc/xinetd.d # ps auxxx|egrep amanda amanda 14847 0.0 0.3 4160 872 pts/3S12:30 0:00 [su] amanda 14848 0.0 0.6 4620 1584 pts/3S12:30 0:00 bash root 18452 0.0 0.1 3540 500 pts/3S15:51 0:00 /bin/grep -E amanda server:/etc/xinetd.d # Error Message below: WARNING: info file /var/lib/amanda/DailySet1/curinfo/server.my.co.uk/_/info: does not exist Server check took 10.788 seconds Amanda Backup Client Hosts Check WARNING: server.my.co.uk: selfcheck request timed out. Host down? Client check: 4 hosts checked in 29.328 seconds, 1 problem found -- Unix/ Linux Systems Administrator Chuck Amadi The Surgical Material Testing Laboratory (SMTL), Princess of Wales Hospital Coity Road Bridgend, United Kingdom, CF31 1RQ. Email chuck.smtl.co.uk Tel: +44 1656 752820 Fax: +44 1656 752830
Re: WARNING: server.my.co.uk: selfcheck request timed out. Host down? this is a private IP address.
Chuck Amadi Systems Administrator wrote: Hi List I had a look on the amanda client less /tmp/amanda less amandad.20060213153537.debug Here is the debug report: Amanda 2.4 REQ HANDLE 003-E0990808 SEQ 1139841004 SECURITY USER amanda SERVICE noop OPTIONS features=feff9ffe0f; amandad: time 9.815: it is not an ack amandad: time 9.815: sending REP packet: Amanda 2.4 REP HANDLE 003-E0990808 SEQ 1139841004 ERROR [host fw.my.co.uk: port * not secure] amandad: time 18.975: got packet: Amanda 2.4 REQ HANDLE 003-E0990808 SEQ 1139841004 SECURITY USER amanda SERVICE noop OPTIONS features=feff9ffe0f; amandad: time 18.975: it is not an ack amandad: time 18.975: sending REP packet: Thus I assume I need to add rules for the Firewall server: Any examples or notes Hi Chuck, there is some info about iptables firewall setup at http://wiki.zmanda.com/index.php/Configuration_with_iptables -- Thank you! Kevin Till Amanda documentation: http://wiki.zmanda.com Amanda forums:http://forums.zmanda.com
Re: WARNING: server.my.co.uk: selfcheck request timed out. Host down? this is a private IP address.
Chuck Amadi Systems Administrator wrote:
Hi List
I had a look on the amanda client less /tmp/amanda
less amandad.20060213153537.debug
Here is the debug report:
Amanda 2.4 REQ HANDLE 003-E0990808 SEQ 1139841004
SECURITY USER amanda
SERVICE noop
OPTIONS features=feff9ffe0f;
amandad: time 9.815: it is not an ack
amandad: time 9.815: sending REP packet:
Amanda 2.4 REP HANDLE 003-E0990808 SEQ 1139841004
ERROR [host fw.my.co.uk: port * not secure]
amandad: time 18.975: got packet:
Amanda 2.4 REQ HANDLE 003-E0990808 SEQ 1139841004
SECURITY USER amanda
SERVICE noop
OPTIONS features=feff9ffe0f;
amandad: time 18.975: it is not an ack
amandad: time 18.975: sending REP packet:
Thus I assume I need to add rules for the Firewall server:
Any examples or notes
Cheers
On Mon, 2006-02-13 at 14:51 +, Chuck Amadi Systems Administrator
wrote:
Hi List
I have added a new Amanda client that doesn't belong to my LAN it's our
zope/web server that has a public address and is on another network it's
entry is in my dns server and in the /etc/hosts file which I thought
would be it's first port of call before asking the ns server. Both LAN
and zope/web server sit behind our firewall. Could be that because it's
on another network LAN's 192.168.1.xx broadcast 255.255.255.0 and
123.345.567.89 225.225.225.224 or can I possible use the public IPA
instead of server.my.co.uk in the DLE on the tape server. I am assuming
this is something to do with my firewall.
I have amandad running on the new amanda client. but I get the following
error when amcheck runs fron the cron.
I have created /var/lib/amanda/DailySet1/curinfo/server.my.co.uk/_
directory and chown amanda.disk. Also when I run the following commands
server:/etc/xinetd.d # netstat -a | grep -i amanda
tcp0 0 *:amandaidx *:*
LISTEN
udp0 0 *:amanda
*:*
server:/etc/xinetd.d #
server:/etc/xinetd.d # ps auxxx|egrep amanda
amanda 14847 0.0 0.3 4160 872 pts/3S12:30 0:00 [su]
amanda 14848 0.0 0.6 4620 1584 pts/3S12:30 0:00 bash
root 18452 0.0 0.1 3540 500 pts/3S15:51 0:00 /bin/grep
-E amanda
server:/etc/xinetd.d #
Error Message below:
WARNING: info
file /var/lib/amanda/DailySet1/curinfo/server.my.co.uk/_/info: does not
exist
Server check took 10.788 seconds
Amanda Backup Client Hosts Check
WARNING: server.my.co.uk: selfcheck request timed out. Host down?
Client check: 4 hosts checked in 29.328 seconds, 1 problem found
Hi List I have had a read and digest of the following.
Chapter 22. How /Amanda/ uses UDP and TCP ports
Here is my possible ipchain rule.
Please can someone confirm that the udp should be privelage and tcp
non-privelaged and If udp is to be priveledge
have I got to re compile my amanda client
--with-tcpportrange=10082,10083 and --with-udpportrange=1023.
My IPChain example.
ipchains -A input -p udp -i -s $193.XXX.XXX.XXX{AMANDA_CLIENT} 10080 -d
$192.168.1.XXX{AMANDA_SERVER} -j ACCEPT
ipchains -A input -p tcp -i -s $193.XXX.XXX.XXX{AMANDA_CLIENT}
10082:10083 -d $192.168.1.XXX{AMANDA_SERVER} -j ACCEPT
Re: WARNING: server.my.co.uk: selfcheck request timed out. Host down? this is a private IP address.
Kevin Till wrote: Chuck Amadi Systems Administrator wrote: Hi List I had a look on the amanda client less /tmp/amanda less amandad.20060213153537.debug Here is the debug report: Amanda 2.4 REQ HANDLE 003-E0990808 SEQ 1139841004 SECURITY USER amanda SERVICE noop OPTIONS features=feff9ffe0f; amandad: time 9.815: it is not an ack amandad: time 9.815: sending REP packet: Amanda 2.4 REP HANDLE 003-E0990808 SEQ 1139841004 ERROR [host fw.my.co.uk: port * not secure] amandad: time 18.975: got packet: Amanda 2.4 REQ HANDLE 003-E0990808 SEQ 1139841004 SECURITY USER amanda SERVICE noop OPTIONS features=feff9ffe0f; amandad: time 18.975: it is not an ack amandad: time 18.975: sending REP packet: Thus I assume I need to add rules for the Firewall server: Any examples or notes Hi Chuck, there is some info about iptables firewall setup at http://wiki.zmanda.com/index.php/Configuration_with_iptables Cheers I did google this But I am using ipchains. Are there any examples for me to look at.
Re: WARNING: server.my.co.uk: selfcheck request timed out. Host down? this is a private IP address.
chuck.amadi wrote: Cheers I did google this But I am using ipchains. iptables replaces ipchains. ipchains is pretty much obsolete now, I would upgrade to iptables. Are there any examples for me to look at. the basic idea should be the same. *Assume all outgoing packets are accepted/allowed.* For amdump to work, you need to open up: backup client : 10080(udp), a small range of tcp ports for data transfer e.g. 11000:11030 (recompile amanda with --with-tcpportrange=11000,11030) For amrecover to work, you need to open up: backup server: 10082(udp), 10083(udp), a small range of tcp ports for data transfer e.g. 11000:11030 (recompile amanda with --with-tcpportrange=11000,11030) -- Thank you! Kevin Till Amanda documentation: http://wiki.zmanda.com Amanda forums:http://forums.zmanda.com
Re: WARNING: server.my.co.uk: selfcheck request timed out. Host down? this is a private IP address.
On Monday 13 February 2006 20:10, chuck.amadi wrote: Kevin Till wrote: Chuck Amadi Systems Administrator wrote: Hi List I had a look on the amanda client less /tmp/amanda less amandad.20060213153537.debug Here is the debug report: Amanda 2.4 REQ HANDLE 003-E0990808 SEQ 1139841004 SECURITY USER amanda SERVICE noop OPTIONS features=feff9ffe0f; amandad: time 9.815: it is not an ack amandad: time 9.815: sending REP packet: Amanda 2.4 REP HANDLE 003-E0990808 SEQ 1139841004 ERROR [host fw.my.co.uk: port * not secure] amandad: time 18.975: got packet: Amanda 2.4 REQ HANDLE 003-E0990808 SEQ 1139841004 SECURITY USER amanda SERVICE noop OPTIONS features=feff9ffe0f; amandad: time 18.975: it is not an ack amandad: time 18.975: sending REP packet: Thus I assume I need to add rules for the Firewall server: Any examples or notes Hi Chuck, there is some info about iptables firewall setup at http://wiki.zmanda.com/index.php/Configuration_with_iptables Cheers I did google this But I am using ipchains. Are there any examples for me to look at. I'd assume you will need to google for those, Chuck. ipchains isn't exactly jurassic you know, more probably pre-cambrian in computer time. Not many fossils still exist from that era. Any good reason why you don't switch to iptables? -- Cheers, Gene People having trouble with vz bouncing email to me should add the word 'online' between the 'verizon', and the dot which bypasses vz's stupid bounce rules. I do use spamassassin too. :-) Yahoo.com and AOL/TW attorneys please note, additions to the above message by Gene Heskett are: Copyright 2006 by Maurice Eugene Heskett, all rights reserved.
Re: selfcheck request timed out
Ram "TK" Krishnamurthy wrote: Did you install these software on the PC that works as well? The one where you changed your timeout? Was there any change on the network? Firewall configuration changes? Of the software installed, only samba seems to have any relevance. I found solution for 2 Debian PC's(clients), I changed inetd.conf: #amanda dgram udp wait backup /usr/sbin/tcpd /usr/lib/amanda/amandad amanda dgram udp wait backup /usr/lib/amanda/amandad amandad But for Suse PC until found any thing. Leonid
Re: selfcheck request timed out
Leonid Shulov schrieb: I found solution for 2 Debian PC's(clients), I changed inetd.conf: #amanda dgram udp wait backup /usr/sbin/tcpd/usr/lib/amanda/amandad amandadgram udp wait backup /usr/lib/amanda/amandadamandad But for _*Suse*_ PC until found any thing. Show configs and logs for the Suse again. I have many Suse-clients so we should find that ... Stefan
Re: selfcheck request timed out
Stefan G. Weichinger wrote:
Leonid Shulov schrieb:
I found solution for 2 Debian PC's(clients), I changed inetd.conf:
#amanda dgram udp wait backup /usr/sbin/tcpd
/usr/lib/amanda/amandad
amandadgram udp wait backup /usr/lib/amanda/amandadamandad
But for _*Suse*_ PC until found any thing.
Show configs and logs for the Suse again. I have many Suse-clients so
we should find that ...
Stefan
/tmp
drwxrwxrwt 494 root root 16384 Jan 25 13:45 tmp
/tmp/amanda
drwx--S---2 amanda disk 4096 Jan 24 16:35 amanda
/etc/services:
amanda 10080/tcp # amanda backup services
amanda 10080/udp
amandaidx 10082/tcp # amanda backup services
amidxtape 10083/tcp # amanda backup services
/etc/xinetd.d/amanda:
# default: off
# description: Amanda backup client
#
service amanda
{
socket_type = dgram
protocol= udp
wait= yes
user= amanda
group = disk
server = /usr/lib/amanda/amandad
disable = no
}
/erc/passwd:
amanda:x:37:6:Amanda admin:/var/lib/amanda:/bin/bash
/etc/group:
disk:*:6:
/var/lib/amanda:
-rw-r--r-- 1 amanda disk 28 Jan 19 15:02 .amandahosts
-rw-r--r-- 1 amanda disk 21 Jan 5 2001 .bashrc
-rw-r--r-- 1 amanda disk 10 Jan 5 2001 .profile
drwxr-xr-x 2 amanda disk 4096 Mar 22 2005 DailySet1
drwxr-xr-x 2 amanda disk 4096 Mar 22 2005 disklist
drwxr-xr-x 2 amanda disk 4096 Mar 22 2005 gnutar-lists
drwxr-xr-x 2 amanda disk 4096 Mar 22 2005 index
drwxr-xr-x 2 amanda disk 4096 Jan 19 14:55 lbl-templ
/var/lib/amanda/.amandahosts:
asraid01.localdomain amanda
#asraid01.localdomain - amanda server
/usr/lib/amanda:
-rwxr-xr-x1 root disk 44204 Mar 22 2005 amandad
-rw-r--r--1 amanda disk139 Mar 22 2005 amcat.awk
-rwxr-xr-x1 amanda disk 109640 Mar 22 2005 amcleanupdisk
-rwxr-xr-x1 amanda disk 94540 Mar 22 2005 amidxtaped
-rwxr-xr-x1 amanda disk 131748 Mar 22 2005 amindexd
-rwxr-xr-x1 amanda disk 48896 Mar 22 2005 amlogroll
-rw-r--r--1 amanda disk 17439 Mar 22 2005 amplot.awk
-rw-r--r--1 amanda disk 3283 Mar 22 2005 amplot.g
-rw-r--r--1 amanda disk 3293 Mar 22 2005 amplot.gp
-rwxr-x---1 root disk 19520 Mar 22 2005 amqde
-rwxr-xr-x1 amanda disk 115536 Mar 22 2005 amtrmidx
-rwxr-xr-x1 amanda disk 114992 Mar 22 2005 amtrmlog
-rwsr-x---1 root disk 23212 Mar 22 2005 calcsize
-rwxr-xr-x1 amanda disk 11178 Mar 22 2005 chg-chio
-rwxr-xr-x1 amanda disk 10042 Mar 22 2005 chg-chs
-rwxr-xr-x1 amanda disk 5885 Mar 22 2005 chg-disk
-rwxr-xr-x1 amanda disk 7211 Mar 22 2005 chg-iomega
-rwxr-xr-x1 amanda disk 5128 Mar 22 2005 chg-juke
-rwxr-xr-x1 amanda disk 6752 Mar 22 2005 chg-manual
-rwxr-xr-x1 amanda disk 13074 Mar 22 2005 chg-mcutil
-rwxr-xr-x1 amanda disk 5572 Mar 22 2005 chg-mtx
-rwxr-xr-x1 amanda disk 11938 Mar 22 2005 chg-multi
-rwxr-xr-x1 amanda disk 1688 Mar 22 2005 chg-null
-rwxr-xr-x1 amanda disk 3964 Mar 22 2005 chg-rait
-rwxr-xr-x1 amanda disk 6677 Mar 22 2005 chg-rth
-rwxr-xr-x1 amanda disk 207356 Mar 22 2005 chg-scsi
-rwxr-xr-x1 amanda disk 38002 Mar 22 2005 chg-zd-mtx
-rwxr-xr-x1 amanda disk 143000 Mar 22 2005 driver
-rwsr-x---1 root disk 146848 Mar 22 2005 dumper
-rwsr-x---1 root disk 19980 Mar 22 2005 killpgrp
-rwxr-xr-x1 amanda disk 4810 Mar 22 2005 patch-system
-rwsr-x---1 root disk 148308 Mar 22 2005 planner
-rwsr-x---1 root disk 19036 Mar 22 2005 rundump
-rwsr-x---1 root disk 19184 Mar 22 2005 runtar
-rwxr-xr-x1 root root 78416 Mar 22 2005 selfcheck
-rwxr-xr-x1 amanda disk 97692 Mar 22 2005 sendbackup
-rwxr-xr-x1 amanda disk 90972 Mar 22 2005 sendsize
-rwxr-xr-x1 amanda disk184 Mar 22 2005 suidlist
-rwxr-xr-x1 amanda disk 147144 Mar 22 2005 taper
-rwxr-xr-x1 amanda disk 19044 Mar 22 2005 versionsuffix
What else ?
Leonid
Re: selfcheck request timed out
Leonid Shulov schrieb: /erc/passwd: amanda:x:37:6:Amanda admin:/var/lib/amanda:/bin/bash I assume it's /etc not /erc /var/lib/amanda: -rw-r--r-- 1 amanda disk 28 Jan 19 15:02 .amandahosts -rw-r--r-- 1 amanda disk 21 Jan 5 2001 .bashrc -rw-r--r-- 1 amanda disk 10 Jan 5 2001 .profile drwxr-xr-x 2 amanda disk 4096 Mar 22 2005 DailySet1 drwxr-xr-x 2 amanda disk 4096 Mar 22 2005 disklist drwxr-xr-x 2 amanda disk 4096 Mar 22 2005 gnutar-lists drwxr-xr-x 2 amanda disk 4096 Mar 22 2005 index drwxr-xr-x 2 amanda disk 4096 Jan 19 14:55 lbl-templ So you use /var/lib/amanda both as ~amanda and config-dir? This looks like a AMANDA-server, I assumed it was one client of your installation. Is this planned as a singlehost-installation? Any particular reasons to NOT use the default directories? /var/lib/amanda/.amandahosts: asraid01.localdomain amanda #asraid01.localdomain - amanda server /usr/lib/amanda: -rwxr-xr-x1 root disk 44204 Mar 22 2005 amandad Mine is -rwxr-xr-x 1 amanda disk 36K Jan 20 12:52 /usr/local/libexec/amandad* You have followed the rule : configure and make as amanda-user, install as root? If not, do a make uninstall as root, make clean, reconfigure and make as amanda, make install as root. This is VERY important to get all the permissions right. --- Although: I have seen the configuration, but I still don't know about THE PROBLEM ... Stefan
Re: selfcheck request timed out
I fogot logs files: /tmp/amanda: -rw--- 1 amanda disk 2284 Jan 24 10:11 amandad.20060124101041.debug amandad.20060124101041.debug: amandad: build: VERSION="Amanda-2.4.4p3" amandad: BUILT_DATE="Tue Mar 22 19:23:34 UTC 2005" amandad: BUILT_MACH="Linux c001n13 2.6.9 #1 Thu Jan 27 09:19:29 UTC 2005 i686 i686 i386 GNU/Linux" amandad: CC="gcc" amandad: CONFIGURE_COMMAND="'./configure' '--mandir=/usr/share/man' '--prefix=/usr' '--infodir=/usr/share/info' '--sysconfdir=/etc' '--libdir=/usr/lib' '--libexecdir=/usr/lib/amanda' '--localstatedir=/var/lib' '--with-index-server=localhost' '--with-gnutar-listdir=/var/lib/amanda/gnutar-lists' '--with-smbclient=/usr/bin/smbclient' '--with-amandahosts' '--with-user=amanda' '--with-group=disk' '--with-gnutar=/bin/tar' '--disable-libtool' '--disable-shared' '--disable-static'" amandad: paths: bindir="/usr/bin" sbindir="/usr/sbin" amandad: libexecdir="/usr/lib/amanda" mandir="/usr/share/man" amandad: AMANDA_TMPDIR="/tmp/amanda" AMANDA_DBGDIR="/tmp/amanda" amandad: CONFIG_DIR="/etc/amanda" DEV_PREFIX="/dev/" amandad: RDEV_PREFIX="/dev/" DUMP="/sbin/dump" amandad: RESTORE="/sbin/restore" VDUMP=UNDEF VRESTORE=UNDEF amandad: XFSDUMP=UNDEF XFSRESTORE=UNDEF VXDUMP=UNDEF VXRESTORE=UNDEF amandad: SAMBA_CLIENT="/usr/bin/smbclient" GNUTAR="/bin/tar" amandad: COMPRESS_PATH="/usr/bin/gzip" amandad: UNCOMPRESS_PATH="/usr/bin/gzip" LPRCMD="/usr/bin/lpr" amandad: MAILER="/usr/bin/Mail" amandad: listed_incr_dir="/var/lib/amanda/gnutar-lists" amandad: defs: DEFAULT_SERVER="localhost" DEFAULT_CONFIG="DailySet1" amandad: DEFAULT_TAPE_SERVER="localhost" amandad: DEFAULT_TAPE_DEVICE="/dev/null" HAVE_MMAP HAVE_SYSVSHM amandad: LOCKING=POSIX_FCNTL SETPGRP_VOID DEBUG_CODE amandad: AMANDA_DEBUG_DAYS=4 BSD_SECURITY USE_AMANDAHOSTS amandad: CLIENT_LOGIN="amanda" FORCE_USERID HAVE_GZIP amandad: COMPRESS_SUFFIX=".gz" COMPRESS_FAST_OPT="--fast" amandad: COMPRESS_BEST_OPT="--best" UNCOMPRESS_OPT="-dc" amandad: time 29.994: dgram_recv: timeout after 30 seconds amandad: error receiving message: timeout amandad: time 29.994: error receiving message: timeout amandad: time 29.995: pid 3201 finish time Tue Jan 24 10:11:11 2006 /var/log/messages: Jan 24 16:35:59 ellas amandad[13633]: error receiving message: timeout Jan 24 16:59:53 ellas xinetd[6618]: Exiting...
Re: selfcheck request timed out
Stefan G. Weichinger wrote: Leonid Shulov schrieb: /erc/passwd: amanda:x:37:6:Amanda admin:/var/lib/amanda:/bin/bash It is my error in E-mail I assume it's /etc not /erc /var/lib/amanda: -rw-r--r-- 1 amanda disk 28 Jan 19 15:02 .amandahosts -rw-r--r-- 1 amanda disk 21 Jan 5 2001 .bashrc -rw-r--r-- 1 amanda disk 10 Jan 5 2001 .profile drwxr-xr-x 2 amanda disk 4096 Mar 22 2005 DailySet1 drwxr-xr-x 2 amanda disk 4096 Mar 22 2005 disklist drwxr-xr-x 2 amanda disk 4096 Mar 22 2005 gnutar-lists drwxr-xr-x 2 amanda disk 4096 Mar 22 2005 index drwxr-xr-x 2 amanda disk 4096 Jan 19 14:55 lbl-templ So you use /var/lib/amanda both as ~amanda and config-dir? This looks like a AMANDA-server, I assumed it was one client of your installation. Is this planned as a singlehost-installation? Any particular reasons to NOT use the default directories? I don't compiled from source, I installed amanda from SuSe 9.3 amanda package /var/lib/amanda/.amandahosts: asraid01.localdomain amanda #asraid01.localdomain - amanda server /usr/lib/amanda: -rwxr-xr-x1 root disk 44204 Mar 22 2005 amandad Mine is -rwxr-xr-x 1 amanda disk 36K Jan 20 12:52 /usr/local/libexec/amandad* You have followed the rule : configure and make as amanda-user, install as root? If not, do a make uninstall as root, make clean, reconfigure and make as amanda, make install as root. This is VERY important to get all the permissions right. --- Although: I have seen the configuration, but I still don't know about THE PROBLEM ... Leonid
Re: selfcheck request timed out
Leonid Shulov wrote: I fogot logs files: /tmp/amanda: -rw---1 amanda disk 2284 Jan 24 10:11 amandad.20060124101041.debug amandad.20060124101041.debug: amandad: build: VERSION=Amanda-2.4.4p3 amandad:BUILT_DATE=Tue Mar 22 19:23:34 UTC 2005 amandad:BUILT_MACH=Linux c001n13 2.6.9 #1 Thu Jan 27 09:19:29 UTC 2005 i686 i686 i386 GNU/Linux amandad:CC=gcc amandad:CONFIGURE_COMMAND='./configure' '--mandir=/usr/share/man' '--prefix=/usr' '--infodir=/usr/share/info' '--sysconfdir=/etc' '--libdir=/usr/lib' '--libexecdir=/usr/lib/amanda' '--localstatedir=/var/lib' '--with-index-server=localhost' '--with-gnutar-listdir=/var/lib/amanda/gnutar-lists' '--with-smbclient=/usr/bin/smbclient' '--with-amandahosts' '--with-user=amanda' '--with-group=disk' '--with-gnutar=/bin/tar' '--disable-libtool' '--disable-shared' '--disable-static' amandad: paths: bindir=/usr/bin sbindir=/usr/sbin amandad:libexecdir=/usr/lib/amanda mandir=/usr/share/man amandad:AMANDA_TMPDIR=/tmp/amanda AMANDA_DBGDIR=/tmp/amanda amandad:CONFIG_DIR=/etc/amanda DEV_PREFIX=/dev/ amandad:RDEV_PREFIX=/dev/ DUMP=/sbin/dump amandad:RESTORE=/sbin/restore VDUMP=UNDEF VRESTORE=UNDEF amandad:XFSDUMP=UNDEF XFSRESTORE=UNDEF VXDUMP=UNDEF VXRESTORE=UNDEF amandad:SAMBA_CLIENT=/usr/bin/smbclient GNUTAR=/bin/tar amandad:COMPRESS_PATH=/usr/bin/gzip amandad:UNCOMPRESS_PATH=/usr/bin/gzip LPRCMD=/usr/bin/lpr amandad:MAILER=/usr/bin/Mail amandad:listed_incr_dir=/var/lib/amanda/gnutar-lists amandad: defs: DEFAULT_SERVER=localhost DEFAULT_CONFIG=DailySet1 amandad:DEFAULT_TAPE_SERVER=localhost amandad:DEFAULT_TAPE_DEVICE=/dev/null HAVE_MMAP HAVE_SYSVSHM amandad:LOCKING=POSIX_FCNTL SETPGRP_VOID DEBUG_CODE amandad:AMANDA_DEBUG_DAYS=4 BSD_SECURITY USE_AMANDAHOSTS amandad:CLIENT_LOGIN=amanda FORCE_USERID HAVE_GZIP amandad:COMPRESS_SUFFIX=.gz COMPRESS_FAST_OPT=--fast amandad:COMPRESS_BEST_OPT=--best UNCOMPRESS_OPT=-dc *amandad: time 29.994: dgram_recv: timeout after 30 seconds amandad: error receiving message: timeout amandad: time 29.994: error receiving message: timeout amandad: time 29.995: pid 3201 finish time Tue Jan 24 10:11:11 2006 */var/log/messages: Jan 24 16:35:59 ellas amandad[13633]: error receiving message: timeout Jan 24 16:59:53 ellas xinetd[6618]: Exiting... This is strange: xinetd invokes amandad because there is some traffic received on port 10080/udp. But when amandad tries to receive a dgram, it receives nothing, and thus times out after 30 seconds. Very strange... -- Paul Bijnens, XplanationTel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 http://www.xplanation.com/ email: [EMAIL PROTECTED] *** * I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, ^^, * * F6, quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, * * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, * * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, * * init 0, kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ... * * ... Are you sure? ... YES ... Phew ... I'm out * ***
Re: selfcheck request timed out
As usual, a followup on myself :-) Paul Bijnens wrote: Leonid Shulov wrote: I fogot logs files: /tmp/amanda: -rw---1 amanda disk 2284 Jan 24 10:11 amandad.20060124101041.debug ... amandad: error receiving message: timeout amandad: time 29.994: error receiving message: timeout amandad: time 29.995: pid 3201 finish time Tue Jan 24 10:11:11 2006 */var/log/messages: Jan 24 16:35:59 ellas amandad[13633]: error receiving message: timeout Jan 24 16:59:53 ellas xinetd[6618]: Exiting... This is strange: xinetd invokes amandad because there is some traffic received on port 10080/udp. But when amandad tries to receive a dgram, it receives nothing, and thus times out after 30 seconds. Very strange... But this log file dates from yesterday. What that the logfile that is created when you started amandad manually. Then yes indeed, it should time out after 30 seconds. Perfect. Note that the timestamps in /var/log/messages are 6 hours later :-) Please try to simulate one problem at a time. -- Paul Bijnens, XplanationTel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 http://www.xplanation.com/ email: [EMAIL PROTECTED] *** * I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, ^^, * * F6, quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, * * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, * * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, * * init 0, kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ... * * ... Are you sure? ... YES ... Phew ... I'm out * ***
Re: selfcheck request timed out
I don't way, but sudenly amanda with Suse work perfectly: asraid01:/etc/amanda# sudo -u amanda amcheck DailySetE Amanda Tape Server Host Check - Holding disk /home/amanda/tmp: 173619800 kB disk space available, using 152648280 kB ERROR: /dev/nst0: Permission denied (expecting tape DailySet106 or a new tape) NOTE: skipping tape-writable test Server check took 0.001 seconds Amanda Backup Client Hosts Check Client check: 1 host checked in 0.245 seconds, 0 problems found Thanks to Stefan G. Weichinger and Paul Bijnens Leonid
Re: selfcheck request timed out
Leonid Shulov schrieb: I don't way, but sudenly amanda with Suse work perfectly: Often it is enough to enter the room ;-) asraid01:/etc/amanda# sudo -u amanda amcheck DailySetE Amanda Tape Server Host Check - Holding disk /home/amanda/tmp: 173619800 kB disk space available, using 152648280 kB ERROR: /dev/nst0: Permission denied (expecting tape DailySet106 or a new tape) Get that permission right ... NOTE: skipping tape-writable test Server check took 0.001 seconds Amanda Backup Client Hosts Check Client check: 1 host checked in 0.245 seconds, 0 problems found Thanks to Stefan G. Weichinger and Paul Bijnens Greets, Stefan.
Re: selfcheck request timed out
Stefan G. Weichinger wrote: asraid01:/etc/amanda# sudo -u amanda amcheck DailySetE Amanda Tape Server Host Check - Holding disk /home/amanda/tmp: 173619800 kB disk space available, using 152648280 kB ERROR: /dev/nst0: Permission denied (expecting tape DailySet106 or a new tape) Get that permission right ... Its happens when cartridge is not in tape. Leonid
Re: selfcheck request timed out
Leonid Shulov schrieb: ERROR: /dev/nst0: Permission denied (expecting tape DailySet106 or a new tape) Get that permission right ... Its happens when cartridge is not in tape. I get Input/output error then, but OK. Stefan
Re: selfcheck request timed out
Stefan G. Weichinger wrote: Leonid Shulov schrieb: ERROR: /dev/nst0: Permission denied (expecting tape DailySet106 or a new tape) Get that permission right ... Its happens when cartridge is not in tape. I get Input/output error then, but OK. When you get a Permission denied instead of Input/output error, then maybe the error for create directory /var/log/amanda: Permission denied is also bogus, and actually means success? :-) -- Paul Bijnens, XplanationTel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 http://www.xplanation.com/ email: [EMAIL PROTECTED] *** * I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, ^^, * * F6, quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, * * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, * * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, * * init 0, kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ... * * ... Are you sure? ... YES ... Phew ... I'm out * ***
Re: selfcheck request timed out
Paul Bijnens wrote: Leonid Shulov wrote: Now /var/log/amanda: drwx--S--- 2 backup backup1024 2006-01-23 12:50 amanda/ It is still confusing what you write: Is that the contents of /var/log/amanda or the directory itself? I.e is there a directory /var/log/amanda/amanda that has those permissions? or is it /var/log/amanda itself? but: astp0002:/var/log# sudo -u backup /usr/lib/amanda/amandad amandad: create debug directory /var/log/amanda: Permission denied Or do you have SElinux enabled with some very strict setting? Now (24.01.2005) I have 3 PC with same problem, 2 - Debian, 1 - SuSe - amanda timed down: amandad: time 29.994: dgram_recv: timeout after 30 seconds amandad: error receiving message: timeout amandad: time 29.994: error receiving message: timeout amandad: time 29.995: pid 3201 finish time Tue Jan 24 10:11:11 2006 I attach 2 *.debug files Leonid amandad: debug 1 pid 25096 ruid 34 euid 34: start at Tue Jan 24 10:08:25 2006 amandad: version 2.4.5p1 amandad: build: VERSION=Amanda-2.4.5p1 amandad:BUILT_DATE=Thu Dec 29 11:59:13 MST 2005 amandad:BUILT_MACH=Linux rover 2.6.12-9-686 #1 Mon Oct 10 13:25:32 BST 2005 i686 GNU/Linux amandad:CC=gcc amandad:CONFIGURE_COMMAND='./configure' '--prefix=/usr' '--bindir=/usr/sbin' '--mandir=/usr/share/man' '--libexecdir=/usr/lib/amanda' '--enable-shared' '--sysconfdir=/etc' '--localstatedir=/var/lib' '--with-gnutar-listdir=/var/lib/amanda/gnutar-lists' '--with-index-server=localhost' '--with-user=backup' '--with-group=backup' '--with-bsd-security' '--with-amandahosts' '--with-smbclient=/usr/bin/smbclient' '--with-debugging=/var/log/amanda' '--with-tcpportrange=5,50100' '--with-udpportrange=840,860' amandad: paths: bindir=/usr/sbin sbindir=/usr/sbin amandad:libexecdir=/usr/lib/amanda mandir=/usr/share/man amandad:AMANDA_TMPDIR=/tmp/amanda amandad:AMANDA_DBGDIR=/var/log/amanda CONFIG_DIR=/etc/amanda amandad:DEV_PREFIX=/dev/ RDEV_PREFIX=/dev/ DUMP=/sbin/dump amandad:RESTORE=/sbin/restore VDUMP=UNDEF VRESTORE=UNDEF amandad:XFSDUMP=/sbin/xfsdump XFSRESTORE=/sbin/xfsrestore amandad:VXDUMP=UNDEF VXRESTORE=UNDEF amandad:SAMBA_CLIENT=/usr/bin/smbclient GNUTAR=/bin/tar amandad:COMPRESS_PATH=/bin/gzip UNCOMPRESS_PATH=/bin/gzip amandad:LPRCMD=/usr/bin/lpr MAILER=/usr/bin/mail amandad:listed_incr_dir=/var/lib/amanda/gnutar-lists amandad: defs: DEFAULT_SERVER=localhost DEFAULT_CONFIG=DailySet1 amandad:DEFAULT_TAPE_SERVER=localhost amandad:DEFAULT_TAPE_DEVICE=/dev/null HAVE_MMAP HAVE_SYSVSHM amandad:LOCKING=POSIX_FCNTL SETPGRP_VOID DEBUG_CODE amandad:AMANDA_DEBUG_DAYS=4 BSD_SECURITY USE_AMANDAHOSTS amandad:CLIENT_LOGIN=backup FORCE_USERID HAVE_GZIP amandad:COMPRESS_SUFFIX=.gz COMPRESS_FAST_OPT=--fast amandad:COMPRESS_BEST_OPT=--best UNCOMPRESS_OPT=-dc amandad: time 30.009: dgram_recv: timeout after 30 seconds amandad: error receiving message: timeout amandad: time 30.010: error receiving message: timeout amandad: time 30.010: pid 25096 finish time Tue Jan 24 10:08:56 2006 amandad: debug 1 pid 3201 ruid 37 euid 37: start at Tue Jan 24 10:10:41 2006 amandad: version 2.4.4p3 amandad: build: VERSION=Amanda-2.4.4p3 amandad:BUILT_DATE=Tue Mar 22 19:23:34 UTC 2005 amandad:BUILT_MACH=Linux c001n13 2.6.9 #1 Thu Jan 27 09:19:29 UTC 2005 i686 i686 i386 GNU/Linux amandad:CC=gcc amandad:CONFIGURE_COMMAND='./configure' '--mandir=/usr/share/man' '--prefix=/usr' '--infodir=/usr/share/info' '--sysconfdir=/etc' '--libdir=/usr/lib' '--libexecdir=/usr/lib/amanda' '--localstatedir=/var/lib' '--with-index-server=localhost' '--with-gnutar-listdir=/var/lib/amanda/gnutar-lists' '--with-smbclient=/usr/bin/smbclient' '--with-amandahosts' '--with-user=amanda' '--with-group=disk' '--with-gnutar=/bin/tar' '--disable-libtool' '--disable-shared' '--disable-static' amandad: paths: bindir=/usr/bin sbindir=/usr/sbin amandad:libexecdir=/usr/lib/amanda mandir=/usr/share/man amandad:AMANDA_TMPDIR=/tmp/amanda AMANDA_DBGDIR=/tmp/amanda amandad:CONFIG_DIR=/etc/amanda DEV_PREFIX=/dev/ amandad:RDEV_PREFIX=/dev/ DUMP=/sbin/dump amandad:RESTORE=/sbin/restore VDUMP=UNDEF VRESTORE=UNDEF amandad:XFSDUMP=UNDEF XFSRESTORE=UNDEF VXDUMP=UNDEF VXRESTORE=UNDEF amandad:SAMBA_CLIENT=/usr/bin/smbclient GNUTAR=/bin/tar amandad:COMPRESS_PATH=/usr/bin/gzip amandad:UNCOMPRESS_PATH=/usr/bin/gzip LPRCMD=/usr/bin/lpr amandad:MAILER=/usr/bin/Mail amandad:listed_incr_dir=/var/lib/amanda/gnutar-lists amandad: defs: DEFAULT_SERVER=localhost DEFAULT_CONFIG=DailySet1 amandad:DEFAULT_TAPE_SERVER=localhost amandad:DEFAULT_TAPE_DEVICE=/dev/null HAVE_MMAP HAVE_SYSVSHM amandad:LOCKING=POSIX_FCNTL SETPGRP_VOID DEBUG_CODE amandad:AMANDA_DEBUG_DAYS=4 BSD_SECURITY USE_AMANDAHOSTS
Re: selfcheck request timed out
Now (24.01.2005) I have 3 PC with same problem, 2 - Debian, 1 - SuSe - amanda timed down: amandad: time 29.994: dgram_recv: timeout after 30 seconds amandad: error receiving message: timeout amandad: time 29.994: error receiving message: timeout amandad: time 29.995: pid 3201 finish time Tue Jan 24 10:11:11 2006 In all my amanda.conf I wrote: etimeout 300# number of seconds per filesystem for estimates. Every day I amdump 15 servers and PC's Leonid
Re: selfcheck request timed out
Leonid Shulov wrote: Now (24.01.2005) I have 3 PC with same problem, 2 - Debian, 1 - SuSe - amanda timed down: amandad: time 29.994: dgram_recv: timeout after 30 seconds amandad: error receiving message: timeout amandad: time 29.994: error receiving message: timeout amandad: time 29.995: pid 3201 finish time Tue Jan 24 10:11:11 2006 In all my amanda.conf I wrote: etimeout 300# number of seconds per filesystem for estimates. I changed etimeout from 300 to 600 and after than amanda work. Thanks to Paul Bijnens for help and time for me. Leonid
Re: selfcheck request timed out
Leonid Shulov wrote: Leonid Shulov wrote: Now (24.01.2005) I have 3 PC with same problem, 2 - Debian, 1 - SuSe - amanda timed down: amandad: time 29.994: dgram_recv: timeout after 30 seconds amandad: error receiving message: timeout amandad: time 29.994: error receiving message: timeout amandad: time 29.995: pid 3201 finish time Tue Jan 24 10:11:11 2006 In all my amanda.conf I wrote: etimeout 300# number of seconds per filesystem for estimates. I changed etimeout from 300 to 600 and after than amanda work. Good for you. But I do not understand how changing the timeout helps in this case... :-) -- Paul Bijnens, XplanationTel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 http://www.xplanation.com/ email: [EMAIL PROTECTED] *** * I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, ^^, * * F6, quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, * * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, * * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, * * init 0, kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ... * * ... Are you sure? ... YES ... Phew ... I'm out * ***
Re: selfcheck request timed out
Paul Bijnens wrote: Leonid Shulov wrote: Leonid Shulov wrote: I changed etimeout from 300 to 600 and after than amanda work. Good for you. But I do not understand how changing the timeout helps in this case... I are right, its help me only on 1 PC and I thought that all right. Now I checked another PC and : Server check took 120.707 seconds Amanda Backup Client Hosts Check WARNING: nicks: selfcheck request timed out. Host down? Client check: 1 host checked in 29.998 seconds, 1 problem found
Re: selfcheck request timed out
Leonid Shulov wrote: Now I checked another PC and : Server check took 120.707 seconds Amanda Backup Client Hosts Check WARNING: nicks: selfcheck request timed out. Host down? Client check: 1 host checked in 29.998 seconds, 1 problem found I'm still curious about the results of the executing this command on the failing clients (not on the server!): $ sudo -u backup mkdir -p /var/log/amanda Do you get an error (which?), or does it succeed (no output)? -- Paul Bijnens, XplanationTel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 http://www.xplanation.com/ email: [EMAIL PROTECTED] *** * I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, ^^, * * F6, quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, * * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, * * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, * * init 0, kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ... * * ... Are you sure? ... YES ... Phew ... I'm out * ***
Re: selfcheck request timed out
Paul Bijnens wrote: Leonid Shulov wrote: Now I checked another PC and : Server check took 120.707 seconds Amanda Backup Client Hosts Check WARNING: nicks: selfcheck request timed out. Host down? Client check: 1 host checked in 29.998 seconds, 1 problem found I'm still curious about the results of the executing this command on the failing clients (not on the server!): $ sudo -u backup mkdir -p /var/log/amanda Do you get an error (which?), or does it succeed (no output)? With this all is OK and amndad run with this log file in /var/log/amanda/amandad.20060124131203.debug: amandad: time 30.002: dgram_recv: timeout after 30 seconds amandad: error receiving message: timeout amandad: time 30.002: error receiving message: timeout amandad: time 30.002: pid 24491 finish time Tue Jan 24 13:12:33 2006 Yesterday nigth amanda has made backup, after that client upgraded system with packages: Setting up libusb-0.1-4 (0.1.11-3) ... Setting up patch (2.5.9-3) ... Setting up libktnef1 (3.5.0-5) ... Setting up dvd+rw-tools (6.0-1) ... Setting up enscript (1.6.4-8) ... Setting up gnome-session (2.12.0-4) ... Setting up libkleopatra1 (3.5.0-5) ... Setting up kde-style-lipstik (2.1-2) ... Setting up libbonoboui2-common (2.10.1-2) ... Setting up libeel2-data (2.12.2-3) ... Setting up libicu34 (3.4-4) ... Setting up libmysqlclient12 (4.0.24-10sarge1) ... Setting up libsmbclient (3.0.21a-3) ... Setting up libungif4g (4.1.4-2) ... Setting up pppoeconf (1.9) ... Setting up realpath (1.9.28) ... Setting up samba-common (3.0.21a-3) ... Setting up smbclient (3.0.21a-3) ... Setting up smbfs (3.0.21a-3) ... Setting up samba (3.0.21a-3) ... Starting Samba daemons: nmbd smbd. Setting up showimg (0.9.5-1) ... Setting up ttf-bitstream-vera (1.10-4) ... Regenerating fonts cache... done. Setting up libmotif3 (2.2.3-1.3) ... Setting up libbonoboui2-0 (2.10.1-2) ... Setting up libeel2-2 (2.12.2-3) ... Setting up libkdepim1a (3.5.0-5) ... Setting up libkcal2b (3.5.0-5) ... Setting up akregator (3.5.0-5) ... Setting up kaddressbook (3.5.0-5) ... Setting up knotes (3.5.0-5) ... I dont know how it affect to amanda, but fact, after that it finished work with this PC. Leonid
Re: selfcheck request timed out
Did you install these software on the PC that works as well? The one where you changed your timeout? Was there any change on the network? Firewall configuration changes? Of the software installed, only samba seems to have any relevance. Thanks tk Leonid Shulov wrote: Paul Bijnens wrote: Leonid Shulov wrote: Now I checked another PC and : Server check took 120.707 seconds Amanda Backup Client Hosts Check WARNING: nicks: selfcheck request timed out. Host down? Client check: 1 host checked in 29.998 seconds, 1 problem found I'm still curious about the results of the executing this command on the failing clients (not on the server!): $ sudo -u backup mkdir -p /var/log/amanda Do you get an error (which?), or does it succeed (no output)? With this all is OK and amndad run with this log file in /var/log/amanda/amandad.20060124131203.debug: amandad: time 30.002: dgram_recv: timeout after 30 seconds amandad: error receiving message: timeout amandad: time 30.002: error receiving message: timeout amandad: time 30.002: pid 24491 finish time Tue Jan 24 13:12:33 2006 Yesterday nigth amanda has made backup, after that client upgraded system with packages: Setting up libusb-0.1-4 (0.1.11-3) ... Setting up patch (2.5.9-3) ... Setting up libktnef1 (3.5.0-5) ... Setting up dvd+rw-tools (6.0-1) ... Setting up enscript (1.6.4-8) ... Setting up gnome-session (2.12.0-4) ... Setting up libkleopatra1 (3.5.0-5) ... Setting up kde-style-lipstik (2.1-2) ... Setting up libbonoboui2-common (2.10.1-2) ... Setting up libeel2-data (2.12.2-3) ... Setting up libicu34 (3.4-4) ... Setting up libmysqlclient12 (4.0.24-10sarge1) ... Setting up libsmbclient (3.0.21a-3) ... Setting up libungif4g (4.1.4-2) ... Setting up pppoeconf (1.9) ... Setting up realpath (1.9.28) ... Setting up samba-common (3.0.21a-3) ... Setting up smbclient (3.0.21a-3) ... Setting up smbfs (3.0.21a-3) ... Setting up samba (3.0.21a-3) ... Starting Samba daemons: nmbd smbd. Setting up showimg (0.9.5-1) ... Setting up ttf-bitstream-vera (1.10-4) ... Regenerating fonts cache... done. Setting up libmotif3 (2.2.3-1.3) ... Setting up libbonoboui2-0 (2.10.1-2) ... Setting up libeel2-2 (2.12.2-3) ... Setting up libkdepim1a (3.5.0-5) ... Setting up libkcal2b (3.5.0-5) ... Setting up akregator (3.5.0-5) ... Setting up kaddressbook (3.5.0-5) ... Setting up knotes (3.5.0-5) ... I dont know how it affect to amanda, but fact, after that it finished work with this PC. Leonid -- Ram TK Krishnamurthy http://www.zmanda.com
selfcheck request timed out
Suddenly my amanda stoped backup one of my users PC and I don't found why. amcheck report: WARNING: astp0002: selfcheck request timed out. Host down? /tmp drwx--S--- 2 backup backup 1024 2006-01-23 12:53 amanda/ /etc/services amanda 10080/tcp # amanda backup services amanda 10080/udp amandaidx 10082/tcp # amanda backup services amidxtape 10083/tcp # amanda backup services /etc/inetd.conf amanda dgram udp waitbackup /usr/sbin/tcpd /usr/lib/amanda/amandad amanda.conf disklist for this PC I don't changed. Thanks for help Leonid
Re: selfcheck request timed out
Leonid Shulov wrote: Suddenly my amanda stoped backup one of my users PC and I don't found why. amcheck report: WARNING: astp0002: selfcheck request timed out. Host down? Did you check all the items in: http://wiki.zmanda.com/index.php/Amcheck:_selfcheck_request_timed_out /tmp drwx--S--- 2 backup backup 1024 2006-01-23 12:53 amanda/ Look in the amandad.DATETIME.debug file inside that directory for clues. /etc/inetd.conf amanda dgram udp waitbackup /usr/sbin/tcpd /usr/lib/amanda/amandad You are running with tcpd. Are the entries in /etc/hosts.allow or /etc/hosts.deny ok? -- Paul Bijnens, XplanationTel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 http://www.xplanation.com/ email: [EMAIL PROTECTED] *** * I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, ^^, * * F6, quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, * * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, * * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, * * init 0, kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ... * * ... Are you sure? ... YES ... Phew ... I'm out * ***
Re: selfcheck request timed out
Paul Bijnens wrote: Leonid Shulov wrote: Suddenly my amanda stoped backup one of my users PC and I don't found why. amcheck report: WARNING: astp0002: selfcheck request timed out. Host down? Did you check all the items in: http://wiki.zmanda.com/index.php/Amcheck:_selfcheck_request_timed_out Yes. /tmp drwx--S--- 2 backup backup 1024 2006-01-23 12:53 amanda/ Look in the amandad.DATETIME.debug file inside that directory for clues. In /tmp/amanda I don't have any amandad.DATETIME.debug file /etc/inetd.conf amanda dgram udp waitbackup /usr/sbin/tcpd /usr/lib/amanda/amandad You are running with tcpd. Are the entries in /etc/hosts.allow or /etc/hosts.deny ok? Both files is empty
Re: selfcheck request timed out
Leonid Shulov wrote: Paul Bijnens wrote: Leonid Shulov wrote: Suddenly my amanda stoped backup one of my users PC and I don't found why. amcheck report: WARNING: astp0002: selfcheck request timed out. Host down? Did you check all the items in: http://wiki.zmanda.com/index.php/Amcheck:_selfcheck_request_timed_out Yes. Fine! /tmp drwx--S--- 2 backup backup 1024 2006-01-23 12:53 amanda/ Look in the amandad.DATETIME.debug file inside that directory for clues. In /tmp/amanda I don't have any amandad.DATETIME.debug file any other files? If there is no such file at all, then it means that amandad isn't even starting. When you start as user amanda /usr/lib/amanda/amandad manually from a shell, it should sit there for about 30 seconds and then time out. Or do you get any errors about libraries not being found etc.? (One remarkable about your setup is that in a normal setup, you the amandad binary is inside the libexec directory.) /etc/inetd.conf amanda dgram udp waitbackup /usr/sbin/tcpd /usr/lib/amanda/amandad You are running with tcpd. Are the entries in /etc/hosts.allow or /etc/hosts.deny ok? Both files is empty Do you find any traces that tcpd logged about invoking the program or denying access (maybe you have to increase the verbosity of syslogd). Or just run without tcpd, to assure that is not the problem. -- Paul Bijnens, XplanationTel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 http://www.xplanation.com/ email: [EMAIL PROTECTED] *** * I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, ^^, * * F6, quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, * * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, * * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, * * init 0, kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ... * * ... Are you sure? ... YES ... Phew ... I'm out * ***
Re: selfcheck request timed out
Paul Bijnens wrote: Leonid Shulov wrote: Paul Bijnens wrote: Leonid Shulov wrote: Suddenly my amanda stoped backup one of my users PC and I don't found why. amcheck report: WARNING: astp0002: selfcheck request timed out. Host down? Did you check all the items in: http://wiki.zmanda.com/index.php/Amcheck:_selfcheck_request_timed_out Yes. Fine! /tmp drwx--S--- 2 backup backup 1024 2006-01-23 12:53 amanda/ Look in the amandad.DATETIME.debug file inside that directory for clues. In /tmp/amanda I don't have any amandad.DATETIME.debug file any other files? If there is no such file at all, then it means that amandad isn't even starting. No files complitely When you start as user amanda /usr/lib/amanda/amandad manually from a shell, it should sit there for about 30 seconds and then time out. Or do you get any errors about libraries not being found etc.? astp0002:/var/log# /usr/lib/amanda/amandad amandad: create debug directory /var/log/amanda: Permission denied astp0002:/var/log# sudo -u backup /usr/lib/amanda/amandad amandad: create debug directory /var/log/amanda: Permission denied I changed permission to 777 - but without any changing (One remarkable about your setup is that in a normal setup, you the amandad binary is inside the libexec directory.) normal amanda dgram udp waitbackup /usr/sbin/tcpd /usr/lib/amanda/amandad You are running with tcpd. Are the entries in /etc/hosts.allow or /etc/hosts.deny ok? Both files is empty /etc/inetd.conf Do you find any traces that tcpd logged about invoking the program or denying access (maybe you have to increase the verbosity of syslogd). Or just run without tcpd, to assure that is not the problem. I changed inetd.conf: #amanda dgram udp waitbackup /usr/sbin/tcpd /usr/lib/amanda/amandad amanda dgram udp waitbackup /usr/lib/amanda/amandad amandad and after that /etc/init.d/inetd restart After amcheck in syslog I see: Jan 23 17:11:12 astp0002 inetd[30734]: /usr/lib/amanda/amandad: exit status 0x1 Jan 23 17:11:12 astp0002 last message repeated 38 times Jan 23 17:11:12 astp0002 inetd[30734]: amanda/udp server failing (looping), service terminated
Re: selfcheck request timed out
Leonid Shulov wrote: Paul Bijnens wrote: Leonid Shulov wrote: Paul Bijnens wrote: Leonid Shulov wrote: Suddenly my amanda stoped backup one of my users PC and I don't found why. amcheck report: WARNING: astp0002: selfcheck request timed out. Host down? Did you check all the items in: http://wiki.zmanda.com/index.php/Amcheck:_selfcheck_request_timed_out Yes. Apparently you missed the first sentence: Locate the AMANDA_DBGDIR directory :-) Because /tmp/amanda is not your debug directory. See below... Fine! /tmp drwx--S--- 2 backup backup 1024 2006-01-23 12:53 amanda/ Look in the amandad.DATETIME.debug file inside that directory for clues. In /tmp/amanda I don't have any amandad.DATETIME.debug file any other files? If there is no such file at all, then it means that amandad isn't even starting. No files complitely When you start as user amanda /usr/lib/amanda/amandad manually from a shell, it should sit there for about 30 seconds and then time out. Or do you get any errors about libraries not being found etc.? astp0002:/var/log# /usr/lib/amanda/amandad amandad: create debug directory /var/log/amanda: Permission denied astp0002:/var/log# sudo -u backup /usr/lib/amanda/amandad amandad: create debug directory /var/log/amanda: Permission denied I changed permission to 777 - but without any changing OK, so your debug directory seems to be /var/log/amanda. Is that a directory? Or did you create a file instead? The permissions of the debug directory should not be 777, but 700 or 2700. -- Paul Bijnens, XplanationTel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 http://www.xplanation.com/ email: [EMAIL PROTECTED] *** * I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, ^^, * * F6, quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, * * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, * * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, * * init 0, kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ... * * ... Are you sure? ... YES ... Phew ... I'm out * ***
Re: selfcheck request timed out
Paul Bijnens wrote: Leonid Shulov wrote: Paul Bijnens wrote: Leonid Shulov wrote: Paul Bijnens wrote: Leonid Shulov wrote: Suddenly my amanda stoped backup one of my users PC and I don't found why. amcheck report: WARNING: astp0002: selfcheck request timed out. Host down? Did you check all the items in: http://wiki.zmanda.com/index.php/Amcheck:_selfcheck_request_timed_out Yes. Apparently you missed the first sentence: Locate the AMANDA_DBGDIR directory :-) Because /tmp/amanda is not your debug directory. See below... Fine! /tmp drwx--S--- 2 backup backup 1024 2006-01-23 12:53 amanda/ Look in the amandad.DATETIME.debug file inside that directory for clues. In /tmp/amanda I don't have any amandad.DATETIME.debug file any other files? If there is no such file at all, then it means that amandad isn't even starting. No files complitely When you start as user amanda /usr/lib/amanda/amandad manually from a shell, it should sit there for about 30 seconds and then time out. Or do you get any errors about libraries not being found etc.? astp0002:/var/log# /usr/lib/amanda/amandad amandad: create debug directory /var/log/amanda: Permission denied astp0002:/var/log# sudo -u backup /usr/lib/amanda/amandad amandad: create debug directory /var/log/amanda: Permission denied I changed permission to 777 - but without any changing OK, so your debug directory seems to be /var/log/amanda. Is that a directory? Or did you create a file instead? The permissions of the debug directory should not be 777, but 700 or 2700. Now /var/log/amanda: drwx--S--- 2 backup backup1024 2006-01-23 12:50 amanda/ but: astp0002:/var/log# sudo -u backup /usr/lib/amanda/amandad amandad: create debug directory /var/log/amanda: Permission denied and /var/log/syslog: Jan 23 17:11:12 astp0002 inetd[30734]: /usr/lib/amanda/amandad: exit status 0x1 Jan 23 17:11:12 astp0002 last message repeated 38 times Jan 23 17:11:12 astp0002 inetd[30734]: amanda/udp server failing (looping), service terminated
Re: selfcheck request timed out
Paul Bijnens wrote: Leonid Shulov wrote: Now /var/log/amanda: drwx--S--- 2 backup backup1024 2006-01-23 12:50 amanda/ It is still confusing what you write: Is that the contents of /var/log/amanda or the directory itself? I.e is there a directory /var/log/amanda/amanda that has those permissions? or is it /var/log/amanda itself? it is /var/log/amanda but: astp0002:/var/log# sudo -u backup /usr/lib/amanda/amandad amandad: create debug directory /var/log/amanda: Permission denied Or do you have SElinux enabled with some very strict setting? No, simple Debian Linux with kernel 2.6.15-1-686
Re: selfcheck request timed out. Host down?
Hello, Joshua Baker-LePain wrote: My /tmp/amcheck.20051121214741.debug file has: There's no /tmp/amanda*debug (or /tmp/amanda/amanda*debug)? In that case, it can't even talk to the server. Are you using TCP wrappers? Any firewall issues? Sorry, the file is actually /tmp/amanda/amcheck.20051121214741.debug. No TCP wrappers, no firewall. -- ### Nader Amadeu### ### Institut fuer Chemie### ### Freie Universitaet Berlin ### ### D - 14195 Berlin / Germany ### ### www.chemie.fu-berlin.de/~nader ###
Re: selfcheck request timed out. Host down?
On Mon, 21 Nov 2005 at 11:08pm, Nader Amadeu wrote this error was already extensively reported, but i have to do it again :-) I installed amanda 2.4.5 on FreeBSD 5.3 to backup the main HD to a second HD of my machine (so both amanda server and client where installed). I created a configuration called kenai and typed: SHELL: amcheck kenai . . (server check ok) . Amanda Backup Client Hosts Check WARNING: kenai.chemie.fu-berlin.de: selfcheck request timed out. Host down? *snip* I overchecked the files .../config/kenai/disklist (this uses the full qualified hostname), /etc/inetd.conf (inetd restarted), FreeBSD still uses inetd rather than xinetd? Wow. /etc/services, /etc/amandahosts, ~/.rhosts (from proper user). My /tmp/amcheck.20051121214741.debug file has: *snip* As the error is on the client side, i think the changer problems shouldnt be important. But are the only error message i have. There's no /tmp/amanda*debug (or /tmp/amanda/amanda*debug)? In that case, it can't even talk to the server. Are you using TCP wrappers? Any firewall issues? -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
selfcheck request timed out. Host down?
Hi all,
this error was already extensively reported, but i have to do it again :-)
I installed amanda 2.4.5 on FreeBSD 5.3 to backup the main HD to a second
HD of my machine (so both amanda server and client where installed).
I created a configuration called kenai and typed:
SHELL: amcheck kenai
.
. (server check ok)
.
Amanda Backup Client Hosts Check
WARNING: kenai.chemie.fu-berlin.de: selfcheck request timed out. Host down?
Relevant parts of my .../kenai/amanda.conf file are:
--
tpchanger chg-disk
tapedev file:/d1/amanda/bkups/kenai
changerfile /d1/amanda/config/kenai/chg-multi.conf
define tapetype HARD-DISK {
length 600 mbytes # there will be many 600MB slots, CDs will be burnd ...
}
define dumptype tar-to-hd-kenai {
holdingdisk no
index yes
program GNUTAR
}
tapetype HARD-DISK
amrecover_changer chg-multi
--
I overchecked the files
.../config/kenai/disklist (this uses the full qualified hostname),
/etc/inetd.conf (inetd restarted),
/etc/services, /etc/amandahosts, ~/.rhosts (from proper user).
My /tmp/amcheck.20051121214741.debug file has:
amcheck: debug 1 pid 76162 ruid 1003 euid 0: start at Mon Nov 21 21:47:41 2005
amcheck: dgram_bind: socket bound to 0.0.0.0.1007
changer: got exit: 0 str: 1 30 1
changer_query: changer return was 30 1
changer_query: searchable = 0
changer_find: looking for NULL changer is searchable = 0
changer: got exit: 0 str: 1 file:/d1/amanda/bkups/kenai
amcheck: pid 76162 finish time Mon Nov 21 21:48:11 2005
As the error is on the client side, i think the changer
problems shouldnt be important. But are the only error message i have.
Does anyone have any idea where is the problem?
I thank you all in advance.
Nader
--
### Nader Amadeu###
### Institut fuer Chemie###
### Freie Universitaet Berlin ###
### D - 14195 Berlin / Germany ###
### www.chemie.fu-berlin.de/~nader ###
Re: Fwd: Re: WARNING: hostxxx: selfcheck request timed out. Host down?
Yes this was the debug file resulting from the "start manually and wait30 seconds" . As yet I have no debug file produced from inetd.Paul Bijnens [EMAIL PROTECTED] wrote: shoaib r wrote: This is the /tmp/amanda/amandad.20051005130850.debug file on the CLIENT server (bkpclient): amandad: debug 1 pid 7021 ruid 198 euid 198: start at Wed Oct 5 13:08:50 2005 amandad: version 2.4.5... amandad: time 30.005: dgram_recv: timeout after 30 secondsWas this the debug file resulting from the "start manually and wait30 seconds" test? Or was it the result of amandad invoked by inetd?-- Paul Bijnens, Xplanation Tel +32 16 397.511Technologielaan 21 bus 2, B-3001 Leuven, BELGIUM Fax +32 16 397.512http://www.xplanation.com/ email: [EMAIL PROTECTED] I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, F6, ** quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, cl! ose, bye, /bye, ** stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, ** PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, ** kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ... ** ... "Are you sure?" ... YES ... Phew ... I'm out Yahoo! Messenger NEW - crystal clear PC to PC calling worldwide with voicemail
Re: Fwd: Re: WARNING: hostxxx: selfcheck request timed out. Host down?
shoaib r wrote: Yes this was the debug file resulting from the start manually and wait 30 seconds . As yet I have no debug file produced from inetd. Then I would conclude that you have a problem with your inetd configuration. -- Paul Bijnens, XplanationTel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 http://www.xplanation.com/ email: [EMAIL PROTECTED] *** * I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, ^^, * * F6, quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, * * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, * * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, * * init 0, kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ... * * ... Are you sure? ... YES ... Phew ... I'm out * ***
Re: Fwd: Re: WARNING: hostxxx: selfcheck request timed out. Host down?
Fair enough, I'll check again. f.y.i I ran a snoop from the client (bkpclient) whilst running an "amcheck -c daily" on the server (tapesvr) and this is what I got: tapesvr - bkpclient UDP D=10080 S=980 LEN=125bkpclient - tapesvr ICMP Destination unreachable (UDP port 10080 unreachable)tapesvr - bkpclient UDP D=10080 S=980 LEN=125bkpclient - tapesvr ICMP Destination unreachable (UDP port 10080 unreachable)tapesvr - bkpclient UDP D=10080 S=980 LEN=125bkpclient - tapesvr ICMP Destination unreachable (UDP port 10080 unreachable)Paul Bijnens [EMAIL PROTECTED] wrote: shoaib r wrote: Yes this was the debug file resulting from the "start manually and wait 30 seconds" . As yet I have no debug file produced from inetd.Then I would conclude that you have a problem with your inetd configuration.-- Paul Bijnens, Xplanation Tel +32 16 397.511Technologielaan 21 bus 2, B-3001 Leuven, BELGIUM Fax +32 16 397.512http://www.xplanation.com/ email: [EMAIL PROTECTED] I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, ^^, ** F6, quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, ** stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, ** PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, ** init 0, kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ! ... ** ... "Are you sure?" ... YES ... Phew ... I'm out To help you stay safe and secure online, we've developed the all new Yahoo! Security Centre.
WARNING: hostxxx: selfcheck request timed out. Host down?
Hi folks I've been trying to get Amanda to be able to query the one backup client host that I have with no luck. I've been thru all the tech pages with no progress yet. Am I missing something? My .amandahosts file has the FQDN and I've only got one line specified for the client as a test in the disklist file. I've checked inetd.conf and /etc/services according to advice and they seem fine: Any help would be appreciated. Thanks Shabs Yahoo! Messenger NEW - crystal clear PC to PC calling worldwide with voicemail
Re: WARNING: hostxxx: selfcheck request timed out. Host down?
On Wed, Oct 05, 2005 at 07:53:26AM -0400, Scott R. Burns enlightened us: Is the error report reporting the FQDN or a shorter name. Try putting the name it is reporting in the .amandahosts. If it was a problem with .amandahosts, it would most likely be returning a Permission Denied from Host error, not a timeout. Are there any firewalls in between or on either the client or server? Can you watch a tcpdump of the traffic to see what is being exchanged? -- Matt Hyclak Department of Mathematics Department of Social Work Ohio University (740) 593-1263
Re: WARNING: hostxxx: selfcheck request timed out. Host down?
shoaib r wrote: I've been trying to get Amanda to be able to query the one backup client host that I have with no luck. I've been thru all the tech pages with no progress yet. Am I missing something? We miss the exact error messages. :-) My .amandahosts file has the FQDN and I've only got one line specified for the client as a test in the disklist file. I've checked inetd.conf and /etc/services according to advice and they seem fine: Is the amandad client started and gives an error or isn't it started at all? What happens when you start the amandad client from a command line? It should sit there for 30 seconds and than terminate. Or do you get any error message there. Verify that the amandad program is indeed started by inetd. Any output in /tmp/amanda/*.debug on the client? -- Paul Bijnens, XplanationTel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 http://www.xplanation.com/ email: [EMAIL PROTECTED] *** * I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, ^^, * * F6, quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, * * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, * * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, * * init 0, kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ... * * ... Are you sure? ... YES ... Phew ... I'm out * ***
Re: WARNING: hostxxx: selfcheck request timed out. Host down?
Thanks for the responses so far folks Ok. I have 2 hosts tapesrv and bkpclient The error message is: + running on tapesvr + $ amcheck -c daily Amanda Backup Client Hosts CheckWARNING: tapesvr.b.c.uk: selfcheck request timed out. Host down?Client check: 2 hosts checked in 30.072 seconds, 1 problem found (brought to you by Amanda 2.4.5) There is no firewall between tapesvr and bkpclient. When I start amandad from the bkpclient as user amanda it does indeed sit there for 30secs and then terminates. I get nothing useful or conspicuous lets say from /tmp/amanda/*.debug My .amandahosts file goes like this on "tapesvr" : tapesvramandatapesvrrootbkpclient.b.c.uk amandabkpclient.b.c.uk root I'm not sure about the commands in solaris of how to check if the connections are comming in. Thx Shabs Paul Bijnens [EMAIL PROTECTED] wrote: shoaib r wrote: I've been trying to get Amanda to be able to query the one backup client host that I have with no luck. I've been thru all the tech pages with no progress yet. Am I missing something?We miss the exact error messages. :-) My .amandahosts file has the FQDN and I've only got one line specified for the client as a test in the disklist file. I've checked inetd.conf and /etc/services according to advice and they seem fine:Is the amandad client started and gives an error or isn't it startedat all?What happens when you start the amandad client from a command line?It should sit there for 30 seconds and than terminate. Or do you getany error message there.Verify that the amandad program is indeed started by inetd.<BR! >Any output in /tmp/amanda/*.debug on the client?-- Paul Bijnens, Xplanation Tel +32 16 397.511Technologielaan 21 bus 2, B-3001 Leuven, BELGIUM Fax +32 16 397.512http://www.xplanation.com/ email: [EMAIL PROTECTED] I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, ^^, ** F6, quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, ** stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, ** PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, ** init 0, kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ... ** ... "Are you sure?" ... YES ... Phew ... I'm out How much free photo storage do you get? Store your holiday snaps for FREE with Yahoo! Photos. Get Yahoo! Photos
Re: WARNING: hostxxx: selfcheck request timed out. Host down?
shoaib r wrote: Thanks for the responses so far folks Ok. I have 2 hosts tapesrv and bkpclient The error message is: + running on tapesvr + $ amcheck -c daily Amanda Backup Client Hosts Check WARNING: tapesvr.b.c.uk: selfcheck request timed out. Host down? Client check: 2 hosts checked in 30.072 seconds, 1 problem found (brought to you by Amanda 2.4.5) Actually, it is tapesrv.bc.uk that's timing out and not bkpclient. Forget about bkpclient, it seems to work just fine; look into /tmp/amanda/ on tapesrv, that's where your problem is. And yes, even local backup (from a disk on tapesrv to a tape on tapesrv) go over a net connection, so check inetd, xinetd, services etc. *on tapesrv*. Alex -- Alexander Jolk / BUF Compagnie tel +33-1 42 68 18 28 / fax +33-1 42 68 18 29
Re: WARNING: hostxxx: selfcheck request timed out. Host down?
Just in case it makes any difference to what you know already, the backups for tapesrv are working just fine. I've checked inetd.conf, services, .amandahosts etc and their permissions and ownerships against a completey separate configuration that works. All seems to be fine: --- On tapesrv --- /etc/services: amanda 10080/udp # Amanda backupamandaidx 10082/tcp # Amanda backup index /etc/inetd.conf: amandaidx stream tcp nowait amanda /usr/local/amanda/libexec/amindexd \amindexdamidxtape stream tcp nowait amanda /usr/local/amanda/libexec/amidxtaped \amidxtapedamanda dgram udp wait amanda /usr/local/amanda/libexec/amandad \amandad Does the interface column in disklist make any difference? Have I missed anything out? Appreciate you help so far. ShabsAlexander Jolk [EMAIL PROTECTED] wrote: shoaib r wrote: Thanks for the responses so far folks Ok. I have 2 hosts tapesrv and bkpclient The error message is: + running on tapesvr + $ amcheck -c daily Amanda Backup Client Hosts Check WARNING: tapesvr.b.c.uk: selfcheck request timed out. Host down? Client check: 2 hosts checked in 30.072 seconds, 1 problem found (brought to you by Amanda 2.4.5) Actually, it is tapesrv.bc.uk that's timing out and not bkpclient. Forget about bkpclient, it seems to work just fine; look into /tmp/amanda/ on tapesrv, that's where your problem is. And yes, even local backup (from a disk on tapesrv to a tape on tapesrv) go over a net connection, so check inetd, xinetd, services etc. *on tapesrv*.Alex-- Alexander Jolk / BUF Compagnietel +33-1 42 68 18 28 / fax +33-1 42 68 18 29 Yahoo! Messenger NEW - crystal clear PC to PC calling worldwide with voicemail
Re: WARNING: hostxxx: selfcheck request timed out. Host down?
shoaib r wrote: + running on tapesvr + $ amcheck -c daily Amanda Backup Client Hosts Check WARNING: tapesvr.b.c.uk: selfcheck request timed out. Host down? Client check: 2 hosts checked in 30.072 seconds, 1 problem found (brought to you by Amanda 2.4.5) Just in case it makes any difference to what you know already, the backups for tapesrv are working just fine. Then why do you get a timeout message? Unless you mixed up both machines when you edited the hostnames in your example. Please confirm the exact error message that you are getting; if you think you need to edit the hostnames, triple-check what you are doing; and please give us the debug files in /tmp/amanda/ from the machine that is failing. Alex -- Alexander Jolk / BUF Compagnie tel +33-1 42 68 18 28 / fax +33-1 42 68 18 29
Fwd: Re: WARNING: hostxxx: selfcheck request timed out. Host down?
Note: forwarded message attached. How much free photo storage do you get? Store your holiday snaps for FREE with Yahoo! Photos. Get Yahoo! Photos---BeginMessage--- This is the /tmp/amanda/amandad.20051005130850.debug file on the CLIENT server (bkpclient): amandad: debug 1 pid 7021 ruid 198 euid 198: start at Wed Oct 5 13:08:50 2005amandad: version 2.4.5amandad: build: VERSION="Amanda-2.4.5"amandad: BUILT_DATE="Wed Aug 17 17:42:57 BST 2005"amandad: BUILT_MACH="SunOS dptsdsda02 5.9 Generic_117171-02 sun4u sparc SUNW,Sun-Fire-480R"amandad: CC="gcc"amandad: CONFIGURE_COMMAND="'./configure' '--prefix=/usr/local/amanda' '--with-user=amanda' '--with-group=amanda'"amandad: paths: bindir="/usr/local/amanda/bin"amandad: sbindir="/usr/local/amanda/sbin"amandad: libexecdir="/usr/local/amanda/libexec"amandad: mandir="/usr/local/amanda/man" AMANDA_TMPDIR="/tmp/amanda"amandad: AMANDA_DBGDIR="/tmp/amanda"amandad: CONFIG_DIR="/usr/local/amanda/etc/amanda"amandad: DEV_PREFIX="/dev/dsk/" RDEV_PREFIX="/dev/rdsk/"amandad: DUMP="/usr/sbin/ufsdump" RESTORE="/usr/sbin/ufsrestore"amandad: VDUMP=UNDEF VRESTORE=UNDEF XFSDUMP=UNDEF XFSRESTORE=UNDEFamandad: VXDUMP=UNDEF VXRESTORE=UNDEFamandad: SAMBA_CLIENT="/usr/local/samba/bin/smbclient"amandad: GNUTAR="/usr/local/bin/tar" COMPRESS_PATH="/usr/bin/gzip"amandad: UNCOMPRESS_PATH="/usr/bin/gzip" LPRCMD="/usr/bin/lp"amandad: MAILER="/usr/bin/mailx"amandad: listed_incr_dir="/usr/local/amanda/var/amanda/gnutar-lists"amandad: defs: DEFAULT_SERVER="dptsdsda02" DEFAULT_CONFIG="DailySet1"amandad: DEFAULT_TAPE_SERVER="dptsdsda02"amandad: DEFAULT_TAPE_DEVICE="/dev/null" HAVE_MMAP HAVE_SYSVSHMamandad: LOCKING=POSIX_FCNTL SETPGRP_VOID DEBUG_CODEamandad: AMANDA_DEBUG_DAYS=4 BSD_SECURITY USE_AMANDAHOSTSamandad: CLIENT_LOGIN="amanda" FORCE_USERID HAVE_GZIPamandad: COMPRESS_SUFFIX=".gz" COMPRESS_FAST_OPT="--fast"amandad: COMPRESS_BEST_OPT="--best" UNCOMPRESS_OPT="-dc"amandad: time 30.005: dgram_recv: timeout after 30 secondsamand! ad: error receiving message: timeoutamandad: time 30.006: error receiving message: timeoutamandad: time 30.006: pid 7021 finish time Wed Oct 5 13:09:20 2005Alexander Jolk [EMAIL PROTECTED] wrote: shoaib r wrote: sorry Alexander My mistake. As I'm working on a gov't project, I had to change the hostnames for aliases for the amanda mailing list. I basically vut and paste the wrong alias. Here is the actual error mesage: $ amcheck -c daily Amanda Backup Client Hosts Check WARNING: bkupclient.b.c.uk: selfcheck request timed out. Host down? Client check: 2 hosts checked in 30.072 seconds, 1 problem found (brought to you by Amanda 2.4.5)OK, so let's get back to the mailing list. Please do look into /tmp/amanda/ on the failing client, and send any information therein to the list.Alex-- Alexander Jolk / BUF Compagnietel +33-1 42 68 18 28 / fax +33-1 42 68 18 29 To help you stay safe and secure online, we've developed the all new Yahoo! Security Centre.---End Message---
Re: WARNING: hostxxx: selfcheck request timed out. Host down?
I've checked there are definately no firewalls between. Also both servers are connected to the same switch.Alexander Jolk [EMAIL PROTECTED] wrote: shoaib r wrote: This is the /tmp/amanda/amandad.20051005130850.debug file on the CLIENT server (bkpclient):[...] amandad: time 30.005: dgram_recv: timeout after 30 seconds amandad: error receiving message: timeout amandad: time 30.006: error receiving message: timeout amandad: time 30.006: pid 7021 finish time Wed Oct 5 13:09:20 2005Please keep this thread on the list. Really.You get a timeout after 30s. That means that the first packet arrives but subsequent ones don't seem to get through. Sounds like a firewall problem to me; please double-check that none of the two machines has a local firewall configured and that there's no other firewall between them.Alex-- Alexander Jolk / BUF Compagnietel +33-1 42 68 18 28 / fax +33-1 42 68 18 29 Yahoo! Messenger NEW - crystal clear PC to PC calling worldwide with voicemail
Re: Fwd: Re: WARNING: hostxxx: selfcheck request timed out. Host down?
shoaib r wrote: This is the /tmp/amanda/amandad.20051005130850.debug file on the CLIENT server (bkpclient): amandad: debug 1 pid 7021 ruid 198 euid 198: start at Wed Oct 5 13:08:50 2005 amandad: version 2.4.5 ... amandad: time 30.005: dgram_recv: timeout after 30 seconds Was this the debug file resulting from the start manually and wait 30 seconds test? Or was it the result of amandad invoked by inetd? -- Paul Bijnens, XplanationTel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 http://www.xplanation.com/ email: [EMAIL PROTECTED] *** * I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, F6, * * quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, * * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, * * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, * * kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ...* * ... Are you sure? ... YES ... Phew ... I'm out * ***
WARNING: server.domian.co.uk: selfcheck request timed out. Host down?
I have nuked the source version of amanda and installed amanada version rpm's 2.4.4 using Yast2 on SuSE Linux Enterprise server. I have used chkconfig --list' to see if amanda service is up or not and it is there and also when I use Yast2 xinetd services if not and then I run # /etc/xinetd.d restart I stopped SuSE internal firewall. I've ensured and checked that the appropriate lines are in /etc/services: amanda 10080/tcp # Amanda amanda 10080/udp # Amanda amandaidx 10082/tcp amidxtape 10083/tcp I've made sure that the amanda user does have permissions to run amandad by running /usr/sbin as amanda user this generated the /tmp/amanda directory as I was getting Permissions Denied So rm -rf and restarted amcheck as amanda to re produce the /tmp/amanda dir , and write to /tmp/amanda. Details below: drwx--S--- 2 amanda users 576 May 17 13:28 amanda -rwxr-xr-x 1 amanda disk 52631 Jul 1 2004 amandad The FQDN is listed in /var/lib/amanda/.amandahosts and in the disklist, and in /etc/hosts as follows server.domain.smtl.co.uk. I suppose I should mention that the server and client are the same machine, server.domain.co.uk. Does anyone have any ideas? When I run the following server:/usr/lib/amanda # su amanda -c /usr/sbin/amcheck -c DailySet1 Amanda Backup Client Hosts Check WARNING: server.domain.co.uk: selfcheck request timed out. Host down? Client check: 1 host checked in 30.003 seconds, 1 problem found As I am back to this - going backwards. I have read and digested the doc's but this is now getting frustrating . My /var/log/messages info as below server su: pam_unix2: session started for user amanda, service su May 17 13:51:46 server su: pam_unix2: session finished for user amanda, service su Cheers Chuck -- Unix/ Linux Systems Administrator The Surgical Material Testing Laboratory (SMTL), Princess of Wales Hospital Coity Road Bridgend, United Kingdom, CF31 1RQ. Tel: +44 1656 752820 Fax: +44 1656 752830
Re: WARNING: server.domian.co.uk: selfcheck request timed out. Host down?
Chuck so nothing in /tmp/amanda -- Martin Hepworth Snr Systems Administrator Solid State Logic Tel: +44 (0)1865 842300 Chuck Amadi wrote: I have nuked the source version of amanda and installed amanada version rpm's 2.4.4 using Yast2 on SuSE Linux Enterprise server. I have used chkconfig --list' to see if amanda service is up or not and it is there and also when I use Yast2 xinetd services if not and then I run # /etc/xinetd.d restart I stopped SuSE internal firewall. I've ensured and checked that the appropriate lines are in /etc/services: amanda 10080/tcp # Amanda amanda 10080/udp # Amanda amandaidx 10082/tcp amidxtape 10083/tcp I've made sure that the amanda user does have permissions to run amandad by running /usr/sbin as amanda user this generated the /tmp/amanda directory as I was getting Permissions Denied So rm -rf and restarted amcheck as amanda to re produce the /tmp/amanda dir , and write to /tmp/amanda. Details below: drwx--S--- 2 amanda users 576 May 17 13:28 amanda -rwxr-xr-x 1 amanda disk 52631 Jul 1 2004 amandad The FQDN is listed in /var/lib/amanda/.amandahosts and in the disklist, and in /etc/hosts as follows server.domain.smtl.co.uk. I suppose I should mention that the server and client are the same machine, server.domain.co.uk. Does anyone have any ideas? When I run the following server:/usr/lib/amanda # su amanda -c /usr/sbin/amcheck -c DailySet1 Amanda Backup Client Hosts Check WARNING: server.domain.co.uk: selfcheck request timed out. Host down? Client check: 1 host checked in 30.003 seconds, 1 problem found As I am back to this - going backwards. I have read and digested the doc's but this is now getting frustrating . My /var/log/messages info as below server su: pam_unix2: session started for user amanda, service su May 17 13:51:46 server su: pam_unix2: session finished for user amanda, service su Cheers Chuck ** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This footnote confirms that this email message has been swept for the presence of computer viruses and is believed to be clean. **
Re: WARNING: server.domian.co.uk: selfcheck request timed out. Host down?
Chuck Amadi wrote: server:/usr/lib/amanda # su amanda -c /usr/sbin/amcheck -c DailySet1 Amanda Backup Client Hosts Check WARNING: server.domain.co.uk: selfcheck request timed out. Host down? Client check: 1 host checked in 30.003 seconds, 1 problem found And now do you have messages in /tmp/amanda? Could you cite them? Alex -- Alexander Jolk / BUF Compagnie tel +33-1 42 68 18 28 / fax +33-1 42 68 18 29
Re: WARNING: server.domian.co.uk: selfcheck request timed out. Host down?
Yes I could here's the less output: amandad: debug 1 pid 26781 ruid 150 euid 150: start at Tue May 17 13:19:43 2005 amandad: version 2.4.4p2 amandad: build: VERSION=Amanda-2.4.4p2 amandad:BUILT_DATE=Wed Jun 30 23:45:53 UTC 2004 amandad:BUILT_MACH=Linux eisenstein 2.6.5 #1 Thu Nov 14 12:14:04 UTC 2002 i686 i686 i386 GNU/Linux amandad:CC=gcc amandad:CONFIGURE_COMMAND='./configure' '--mandir=/usr/share/man' '--prefix=/usr' '--infodir=/usr/share/info' '--sysconfdir=/etc' '--libdir=/usr/lib' '--libexecdir=/usr/lib/amanda' '--localstatedir=/var/lib' '--with-index-server=localhost' '--with-gnutar-listdir=/var/lib/amanda/gnutar-lists' '--with-smbclient=/usr/bin/smbclient' '--with-amandahosts' '--with-user=amanda' '--with-group=disk' '--with-gnutar=/bin/tar' '--disable-libtool' '--disable-shared' '--disable-static' amandad: paths: bindir=/usr/bin sbindir=/usr/sbin amandad:libexecdir=/usr/lib/amanda mandir=/usr/share/man amandad:AMANDA_TMPDIR=/tmp/amanda AMANDA_DBGDIR=/tmp/amanda amandad:CONFIG_DIR=/etc/amanda DEV_PREFIX=/dev/ amandad:RDEV_PREFIX=/dev/r DUMP=/sbin/dump amandad:RESTORE=/sbin/restore VDUMP=UNDEF VRESTORE=UNDEF amandad:XFSDUMP=UNDEF XFSRESTORE=UNDEF VXDUMP=UNDEF VXRESTORE=UNDEF amandad:SAMBA_CLIENT=/usr/bin/smbclient GNUTAR=/bin/tar amandad:COMPRESS_PATH=/usr/bin/gzip amandad:UNCOMPRESS_PATH=/usr/bin/gzip LPRCMD=/usr/bin/lpr amandad:MAILER=/usr/bin/Mail amandad:listed_incr_dir=/var/lib/amanda/gnutar-lists amandad: defs: DEFAULT_SERVER=localhost DEFAULT_CONFIG=DailySet1 amandad:DEFAULT_TAPE_SERVER=localhost amandad:DEFAULT_TAPE_DEVICE=/dev/null HAVE_MMAP HAVE_SYSVSHM amandad:LOCKING=POSIX_FCNTL SETPGRP_VOID DEBUG_CODE amandad:AMANDA_DEBUG_DAYS=4 BSD_SECURITY USE_AMANDAHOSTS amandad:CLIENT_LOGIN=amanda FORCE_USERID HAVE_GZIP amandad:COMPRESS_SUFFIX=.gz COMPRESS_FAST_OPT=--fast amandad:COMPRESS_BEST_OPT=--best UNCOMPRESS_OPT=-dc amandad: time 29.996: dgram_recv: timeout after 30 seconds amandad: error receiving message: timeout amandad: time 29.996: error receiving message: timeout amandad: time 29.996: pid 26781 finish time Tue May 17 13:20:13 2005 On Tue, 2005-05-17 at 15:02 +0200, Alexander Jolk wrote: Chuck Amadi wrote: server:/usr/lib/amanda # su amanda -c /usr/sbin/amcheck -c DailySet1 Amanda Backup Client Hosts Check WARNING: server.domain.co.uk: selfcheck request timed out. Host down? Client check: 1 host checked in 30.003 seconds, 1 problem found And now do you have messages in /tmp/amanda? Could you cite them? Alex -- Unix/ Linux Systems Administrator The Surgical Material Testing Laboratory (SMTL), Princess of Wales Hospital Coity Road Bridgend, United Kingdom, CF31 1RQ. Tel: +44 1656 752820 Fax: +44 1656 752830
Re: WARNING: server.domian.co.uk: selfcheck request timed out. Host down?
Chuck Amadi wrote: amandad: time 29.996: dgram_recv: timeout after 30 seconds amandad: error receiving message: timeout amandad: time 29.996: error receiving message: timeout amandad: time 29.996: pid 26781 finish time Tue May 17 13:20:13 2005 It would appear that the UDP packets for communication between the server and client parts don't get received. Can you double check whether your Firewall is switched off? Note that there has been a hint on firewall configuration yesterday on the list. Alex -- Alexander Jolk / BUF Compagnie tel +33-1 42 68 18 28 / fax +33-1 42 68 18 29
Re: WARNING: server.domain.co.uk: selfcheck request timed out. Host down? -Fixed!
Hi I did and it's working I had used the wrong path where my tar was located. Cheers Chuck On Tue, 2005-05-10 at 17:42 +0200, Stefan G. Weichinger wrote: Hi, Chuck, on Dienstag, 10. Mai 2005 at 15:57 you wrote to amanda-users: CA Here's my advance I will sort this alot out as it's self explanatory. and CA Amanda Backup Client Hosts Check CA CA ERROR: server.domain.co.uk: [GNUTAR program not available] Install gnutar. Re-run configure as amanda, make and make install as root so you get fresh new binaries that know about the location of your new gnutar-binary. Watch out for WARNINGs at the configure-step, there should be no warnings requesting gnutar ... -- Unix/ Linux Systems Administrator The Surgical Material Testing Laboratory (SMTL), Princess of Wales Hospital Coity Road Bridgend, United Kingdom, CF31 1RQ. Tel: +44 1656 752820 Fax: +44 1656 752830
WARNING: server.domain.co.uk: selfcheck request timed out. Host down?
Hi I added the files amanda and amandaix to /etc/xinetd.d enable running chkconfig -s xinetd 345 and run /etc/init/xinet.d restart shutdown SuSE internal firewall. server:~ # netstat -a | grep -i amanda tcp0 0 *:amandaidx *:* LISTEN udp0 0 *:amanda*:* server:~ # lsof | grep amanda xinetd5774 root5u IPv4 8186UDP *:amanda xinetd5774 root8u IPv4 8188TCP *:amandaidx (LISTEN) server:~ # Also in /var/lib/amanda/.amandahosts I have my client setup as below #localhost amanda server.domain.co.uk /etc comp-root-tar I have had a look at by amanda logs /tmp/dbglogs but I haven't anything for that is meaning full. My /var.log/messages ay 10 12:38:16 server xinetd[5118]: removing chargen May 10 12:38:16 server xinetd[5118]: removing chargen May 10 12:38:16 server xinetd[5118]: removing printer May 10 12:38:16 server xinetd[5118]: removing daytime May 10 12:38:16 server xinetd[5118]: removing daytime May 10 12:38:16 server xinetd[5118]: removing echo May 10 12:38:16 server xinetd[5118]: removing echo May 10 12:38:16 server xinetd[5118]: removing netstat May 10 12:38:16 server xinetd[5118]: removing rsync May 10 12:38:16 server xinetd[5118]: removing servers May 10 12:38:16 server xinetd[5118]: removing services May 10 12:38:16 server xinetd[5118]: removing systat May 10 12:38:16 server xinetd[5118]: removing time May 10 12:38:16 server xinetd[5118]: removing time May 10 12:38:16 server xinetd[5118]: removing vnc1 May 10 12:38:16 server xinetd[5118]: removing vnc2 May 10 12:38:16 server xinetd[5118]: removing vnc3 May 10 12:38:16 server xinetd[5118]: removing vnchttpd1 May 10 12:38:16 server xinetd[5118]: removing vnchttpd2 May 10 12:38:16 server xinetd[5118]: removing vnchttpd3 May 10 12:38:16 server xinetd[5118]: removing ftp Run socklist and amanda isnt using any ports server:/tmp/amanda-dbg # socklist type port inode uidpid fd name tcp 10082 10472 0 51188 xinetd tcp803 5303 0 31665 ypbind tcp111 4749 0 28804 portmap tcp631 8470 0 31420 cupsd udp 32768 8060 26 38244 postmaster udp800 5298 0 31664 ypbind udp827 10158 0 31666 ypbind udp 10080 10471 0 51185 xinetd udp111 4748 0 28803 portmap udp631 8471 0 31422 cupsd cd /tmp/amanda-debug less amcheck.20050509150302.debug amcheck: debug 1 pid 6923 ruid 150 euid 0: start at Mon May 9 15:03:02 2005 amcheck: dgram_bind: socket bound to 0.0.0.0.673 amcheck: pid 6923 finish time Mon May 9 15:03:32 2005 My /etc/services file # 10009-10079 Unassigned amanda 10080/tcp # Amanda amanda 10080/udp # Amanda amandaidx 10082/tcp amidxtape 10083/tcp But I still get WARNING: server.domain.co.uk: selfcheck request timed out. Host down? Any other areas to checkover I have gone through this with a fine tooth comb. Cheers -- Unix/ Linux Systems Administrator The Surgical Material Testing Laboratory (SMTL), Princess of Wales Hospital Coity Road Bridgend, United Kingdom, CF31 1RQ. Tel: +44 1656 752820 Fax: +44 1656 752830
Re: WARNING: server.domain.co.uk: selfcheck request timed out. Host down?
On Tue, May 10, 2005 at 12:52:32PM +0100, Chuck Amadi enlightened us: Also in /var/lib/amanda/.amandahosts I have my client setup as below #localhost amanda server.domain.co.uk /etc comp-root-tar This is wrong. you've put a disklist entry in amandahosts. amandahosts should contain host username pairs, one per line. Run socklist and amanda isnt using any ports It shouldn't be until a client connects. Matt -- Matt Hyclak Department of Mathematics Department of Social Work Ohio University (740) 593-1263 pgpXzTuId8H81.pgp Description: PGP signature
Re: WARNING: server.domain.co.uk: selfcheck request timed out. Host down?
Hi, Chuck, on Dienstag, 10. Mai 2005 at 13:52 you wrote to amanda-users: CA Hi I added the files amanda and amandaix to /etc/xinetd.d CA enable running chkconfig -s xinetd 345 and run /etc/init/xinet.d restart CA shutdown SuSE internal firewall. CA server:~ # netstat -a | grep -i amanda CA tcp0 0 *:amandaidx *:* CA LISTEN CA udp0 0 *:amanda*:* CA server:~ # lsof | grep amanda CA xinetd5774 root5u IPv4 8186UDP CA *:amanda CA xinetd5774 root8u IPv4 8188TCP CA *:amandaidx (LISTEN) CA server:~ # Ok. CA Also in /var/lib/amanda/.amandahosts I have my client CA setup as below CA #localhost amanda CA server.domain.co.uk /etc comp-root-tar Not OK. Should contain: server.domain.co.uk root server.domain.co.uk amanda CA I have had a look at by amanda logs /tmp/dbglogs CA but I haven't anything for that is meaning full. CA My /var.log/messages CA ay 10 12:38:16 server xinetd[5118]: removing chargen CA May 10 12:38:16 server xinetd[5118]: removing chargen Is xinetd running? Should be concerning the netstat-output. CA Run socklist and amanda isnt using any ports AMANDA isn't running now. This is OK. CA cd /tmp/amanda-debug CA less amcheck.20050509150302.debug CA amcheck: debug 1 pid 6923 ruid 150 euid 0: start at Mon May 9 15:03:02 CA 2005 CA amcheck: dgram_bind: socket bound to 0.0.0.0.673 CA amcheck: pid 6923 finish time Mon May 9 15:03:32 2005 CA My /etc/services file CA # 10009-10079 Unassigned CA amanda 10080/tcp # Amanda CA amanda 10080/udp # Amanda CA amandaidx 10082/tcp CA amidxtape 10083/tcp Fine so far. CA But I still get WARNING: server.domain.co.uk: selfcheck request timed CA out. Host down? CA Any other areas to checkover I have gone through this with a fine tooth CA comb. Correct your .amandahosts first. -- best regards, Stefan Stefan G. Weichinger mailto:[EMAIL PROTECTED]
Re: WARNING: server.domain.co.uk: selfcheck request timed out. Host down? -Fixed!
I got a bit further I had forgot to add - server.domain.co.uk root as well as server.domain.co.uk amanda. Here's my advance I will sort this alot out as it's self explanatory. Amanda Tape Server Host Check - Holding disk /dumps/amanda: 137244996 KB disk space available, that's plenty ERROR: /dev/nst0: tape_rdlabel: tape open: /dev/nst0: Input/output error (expecting a new tape) NOTE: skipping tape-writable test Server check took 120.453 seconds Amanda Backup Client Hosts Check ERROR: server.domain.co.uk: [GNUTAR program not available] Client check: 1 host checked in 10.140 seconds, 1 problem found So I am slowly getting there!. I hope Cheers Chuck On Tue, 2005-05-10 at 15:25 +0200, Stefan G. Weichinger wrote: server.domain.co.uk root -- Unix/ Linux Systems Administrator The Surgical Material Testing Laboratory (SMTL), Princess of Wales Hospital Coity Road Bridgend, United Kingdom, CF31 1RQ. Tel: +44 1656 752820 Fax: +44 1656 752830
Re: WARNING: server.domain.co.uk: selfcheck request timed out. Host down? -Fixed!
Hi, Chuck, on Dienstag, 10. Mai 2005 at 15:57 you wrote to amanda-users: CA Here's my advance I will sort this alot out as it's self explanatory. and CA Amanda Backup Client Hosts Check CA CA ERROR: server.domain.co.uk: [GNUTAR program not available] Install gnutar. Re-run configure as amanda, make and make install as root so you get fresh new binaries that know about the location of your new gnutar-binary. Watch out for WARNINGs at the configure-step, there should be no warnings requesting gnutar ... -- best regards, Stefan Stefan G. Weichinger mailto:[EMAIL PROTECTED]
WARNING: server.domain.co.uk: selfcheck request timed out. Host down?
Hi I have a standalone tape server And I haven't and not running xinet.d services when I built amanda it did not build a /honme/amanda directory thus I haven't got a .amandahost file but one does have such a file in /var/lib/amanda/.amandahosts.rpmsave I get this warning Amanda Backup Client Hosts Check WARNING: server.domain.co.uk: selfcheck request timed out. Host down? Client check: 1 host checked in 30.002 seconds, 1 problem found I assume that I my tape server cant see the client which is the same machine. I have checked and I have got in the /etc/services and I still get host is down!. Cheers Chuck -- Unix/ Linux Systems Administrator The Surgical Material Testing Laboratory (SMTL), Princess of Wales Hospital Coity Road Bridgend, United Kingdom, CF31 1RQ. Tel: +44 1656 752820 Fax: +44 1656 752830
WARNING: server.domain.co.uk: selfcheck request timed out. Host down?
Hi I added the files amanda and amandaix to /etc/xinetd.d enable running chkconfig -s xinetd 345 and rebooted. server:~ # netstat -a | grep -i amanda tcp0 0 *:amandaidx *:* LISTEN udp0 0 *:amanda*:* server:~ # lsof | grep amanda xinetd5774 root5u IPv4 8186UDP *:amanda xinetd5774 root8u IPv4 8188TCP *:amandaidx (LISTEN) server:~ # Also in /var/lib/amanda/.amandahosts I have my client #localhost amanda server.domain.co.uk /etc comp-root-tar But I still get WARNING: server.domain.co.uk: selfcheck request timed out. Host down? Any Ideas relating to my Client being down. -- Unix/ Linux Systems Administrator The Surgical Material Testing Laboratory (SMTL), Princess of Wales Hospital Coity Road Bridgend, United Kingdom, CF31 1RQ. Tel: +44 1656 752820 Fax: +44 1656 752830
Re: WARNING: server.domain.co.uk: selfcheck request timed out. Host down?
Chuck the .amandahosts should be something like server.domain.co.uk root server.domain.co.uk amanda odd output from netstat -a, this shouldn't respond until you 'ping' the appropriate port.. also check the logs (usually /tmp/amanda for any clues, as well as making sure the amanda in /etc/xinet.d is properly configured to allow the local host access to itself. -- Martin Hepworth Snr Systems Administrator Solid State Logic Tel: +44 (0)1865 842300 Chuck Amadi wrote: Hi I added the files amanda and amandaix to /etc/xinetd.d enable running chkconfig -s xinetd 345 and rebooted. server:~ # netstat -a | grep -i amanda tcp0 0 *:amandaidx *:* LISTEN udp0 0 *:amanda*:* server:~ # lsof | grep amanda xinetd5774 root5u IPv4 8186UDP *:amanda xinetd5774 root8u IPv4 8188TCP *:amandaidx (LISTEN) server:~ # Also in /var/lib/amanda/.amandahosts I have my client #localhost amanda server.domain.co.uk /etc comp-root-tar But I still get WARNING: server.domain.co.uk: selfcheck request timed out. Host down? Any Ideas relating to my Client being down. ** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This footnote confirms that this email message has been swept for the presence of computer viruses and is believed to be clean. **
Re: WARNING: server.domain.co.uk: selfcheck request timed out. Hostdown?
I'm not sure, but you might need to add user 'amanda' to your server and/or client. And check permissions. Just my 2 cents... -steve - Original Message - From: Chuck Amadi [EMAIL PROTECTED] To: Amanda List amanda-users@amanda.org Sent: Monday, May 09, 2005 8:41 AM Subject: WARNING: server.domain.co.uk: selfcheck request timed out. Hostdown? Hi I added the files amanda and amandaix to /etc/xinetd.d enable running chkconfig -s xinetd 345 and rebooted. server:~ # netstat -a | grep -i amanda tcp0 0 *:amandaidx *:* LISTEN udp0 0 *:amanda*:* server:~ # lsof | grep amanda xinetd5774 root5u IPv4 8186UDP *:amanda xinetd5774 root8u IPv4 8188TCP *:amandaidx (LISTEN) server:~ # Also in /var/lib/amanda/.amandahosts I have my client #localhost amanda server.domain.co.uk /etc comp-root-tar But I still get WARNING: server.domain.co.uk: selfcheck request timed out. Host down? Any Ideas relating to my Client being down. -- Unix/ Linux Systems Administrator The Surgical Material Testing Laboratory (SMTL), Princess of Wales Hospital Coity Road Bridgend, United Kingdom, CF31 1RQ. Tel: +44 1656 752820 Fax: +44 1656 752830
WARNING: server.domain.co.uk: selfcheck request timed out. Host down?
Hi I get this error when I run amcheck. Amanda Tape Server Host Check - Holding disk /dumps/amanda: 137245600 KB disk space available, that's plenty ERROR: cannot overwrite active tape DailySet101 (expecting a new tape) NOTE: skipping tape-writable test Server check took 0.013 seconds Amanda Backup Client Hosts Check WARNING: server.domain.co.uk: selfcheck request timed out. Host down? Client check: 1 host checked in 30.002 seconds, 1 problem found Have I got to create a file in /etc/xinit.d/amidxtape As I haven't got this file or any other relating to amanda in xinit.d . Cheers Chuck -- Unix/ Linux Systems Administrator The Surgical Material Testing Laboratory (SMTL), Princess of Wales Hospital Coity Road Bridgend, United Kingdom, CF31 1RQ. Tel: +44 1656 752820 Fax: +44 1656 752830
Re: WARNING: server.domain.co.uk: selfcheck request timed out. Host down?
--On Sunday, May 08, 2005 16:23:44 +0100 Chuck Amadi [EMAIL PROTECTED] wrote: Hi I get this error when I run amcheck. Amanda Tape Server Host Check - Holding disk /dumps/amanda: 137245600 KB disk space available, that's plenty ERROR: cannot overwrite active tape DailySet101 (expecting a new tape) This tells you that the tape currently in the drive won't be used since it contains recent data (within tapecycle-1 tapes I believe), and because it is also asking for a new tape instead of a labeled tape, you haven't yet labeled tapecycle number of tapes. If this is a new setup and you're stll just testing, you could amrmtape that tape and relabel it until you're ready to go into production, but this is a separate issue from your current problem below. NOTE: skipping tape-writable test Server check took 0.013 seconds Amanda Backup Client Hosts Check WARNING: server.domain.co.uk: selfcheck request timed out. Host down? Client check: 1 host checked in 30.002 seconds, 1 problem found Have I got to create a file in /etc/xinit.d/amidxtape Only on the server, not on all the clients. As I haven't got this file or any other relating to amanda in xinit.d . That's why you're getting the 'selfcheck timeout' error. You need one for amanda on each client (and on the server in the usual case of it also being a client), and one for amandaidx and amidxtape on the server. Frank Cheers Chuck -- Unix/ Linux Systems Administrator The Surgical Material Testing Laboratory (SMTL), Princess of Wales Hospital Coity Road Bridgend, United Kingdom, CF31 1RQ. Tel: +44 1656 752820 Fax: +44 1656 752830 -- Frank Smith[EMAIL PROTECTED] Sr. Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
SAMBA: selfcheck request timed out. Host down?
Hi
I am trying to get amanda backup from windows machines up and running,
currently without any success:
I have tried three hosts two windows machines and one unix box and both
windows boxes fail.
The log of amcheck -c looks like this:
Amanda Backup Client Hosts Check
WARNING: snap1: selfcheck request timed out. Host down?
WARNING: wins4: selfcheck request timed out. Host down?
Client check: 3 hosts checked in 29.156 seconds, 2 problems found
The disklist:
snap1 //snap1/iss/ samba
wins4 //wins4/software/ samba
sun10 /var/www/ comp-user-tar
amandapass:
//snap1/iss/user%password TUD_FB20_ISS
//wins4/software/ user%password TUD_FB20_ISS
the dumptype samba of amanda.conf
define dumptype samba {
program GNUTAR
comment partitions dumped with tar
options compress-fast
priority low
}
The system itself is a 2.4.2x linux box with debian woody and a
backported amanda from debian sid:
ii amanda-server 2.4.4p2-1 Advanced Maryland Automatic Network Disk Archiver
(Server)
The most unusual ist the backported smbclient:
ii smbclient3.0.2a-0.backports.org.2 a
LanManager-like simple client for Unix
But since there is an entry in the changelog about fixing a bug with
samba 3.0 i suppose it should work. The unix backup is working. There's
no firewall, and amanda is listed in the inetd.conf:
amanda dgram udp wait backup /usr/sbin/tcpd /usr/lib/amanda/amandad
amandaidx stream tcp nowait backup /usr/sbin/tcpd /usr/lib/amanda/amindexd
amidxtape stream tcp nowait backup /usr/sbin/tcpd /usr/lib/amanda/amidxtaped
host.deny is empty and host.allow has:
amanda: snap1.vlsi.informatik.tu-darmstadt.de
It seems to me that amcheck tries to initiate a amanda connection via
udp. Which doesn't work with windows machines? I would apreciate any
hints.
Thanks
Tim
Re: SAMBA: selfcheck request timed out. Host down?
On Thu, 11 Mar 2004 at 1:40pm, Tim Krieglstein wrote The log of amcheck -c looks like this: Amanda Backup Client Hosts Check WARNING: snap1: selfcheck request timed out. Host down? WARNING: wins4: selfcheck request timed out. Host down? Client check: 3 hosts checked in 29.156 seconds, 2 problems found The disklist: snap1 //snap1/iss/ samba wins4 //wins4/software/ samba sun10 /var/www/ comp-user-tar *snip* It seems to me that amcheck tries to initiate a amanda connection via udp. Which doesn't work with windows machines? I would apreciate any hints. The client in your disklist (the first column) for 'doze boxes backed up via samba needs to be a *nix box with smbclient installed. When amanda contacts the *nix box, that box will then initiate the smbclient connection to the 'doze box. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: SAMBA: selfcheck request timed out. Host down?
Hi Joshua The client in your disklist (the first column) for 'doze boxes backed up via samba needs to be a *nix box with smbclient installed. When amanda contacts the *nix box, that box will then initiate the smbclient connection to the 'doze box. Thanks for the hint. It did the trick. Thats why is was staring at the man page and couldn't understand the wording. 8) Tim
Re: selfcheck request timed out error
This is a tuff one. I really can't figure out what is going on.
Joshua Baker-LePain wrote:
On Wed, 25 Feb 2004 at 3:06pm, jlm17 wrote
I commented out the only_from line from all three amanda services but it
does not work.
The other thing to check is /etc/hosts.{allow,deny}. I don't know Gentoo,
but on RedHat xinetd uses them. Accepts or denies based on those files
should be logged in /var/log/secure.
I didn't have either a /etc/hosts.allow or /etc/hosts.deny. I created an
/etc/hosts.allow with the one line: ALL: LOCAL No change in behavior.
Note that I do not get any lines about removing amanda services.
Yes, but...
If you're not getting anything in /tmp/amanda, then amandad isn't even
starting up. Is ipchains/iptables getting in the way? What's the output
of 'netstat -ln | grep 10080'?
netstat -ln | grep 10080
udp0 0 0.0.0.0:10080 0.0.0.0:*
That means amanda is listening, so that part of xinetd is working right.
As far as I know I do not have any iptables stuff turned on. I don't
even have the iptables userland tools installed. I have turned it on in
the kernel, though.
iptables looks empty:
Chain INPUT (policy ACCEPT)
target prot opt source destination
Chain FORWARD (policy ACCEPT)
target prot opt source destination
Chain OUTPUT (policy ACCEPT)
target prot opt source destination
You can check what rules are set up with 'iptables -nL'. I'd say the next
thing to do would be to look at the traffic. Do 'tcpdump -i lo' and then
run amcheck and see what happens.
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
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
Feb 26 10:08:37 royal xinetd[5766]: START: amanda pid=5942
from=152.148.113.221
Feb 26 10:08:37 royal xinetd[5942]: FAIL: amanda address
from=152.148.113.221
Feb 26 10:08:47 royal xinetd[5766]: START: amanda pid=5943
from=152.148.113.221
Feb 26 10:08:47 royal xinetd[5943]: FAIL: amanda address
from=152.148.113.221
Still not very useful though. I have changed the amandad config in xinetd:
service amanda
{
socket_type = dgram
protocol= udp
wait= yes
user= amanda
group = amanda
groups = yes
server = /usr/libexec/amandad
# You need to ensure this points to your Amanda server!
# Don't just remove it!
only_from = royal
disable = no
}
so that wait = no. That just made things worse. Running amandad by hand
seems to do the right thing:
sudo -u amanda /usr/libexec/amandad
amandad: error receiving message: timeout
The next thing I will be trying is to run strace on xinetd and see if I
can glean any information that way.
Thanks again for all of your help.
Re: selfcheck request timed out error
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: . . addressthe 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
Re: selfcheck request timed out error
Thanks for the help. Turns out it was xinetd. There was an only_from in both /etc/xinetd.conf and in /etc/xinetd.d/amanda. By commenting out all of those amcheck returned with no errors. Joshua Baker-LePain wrote: 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: . . addressthe 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.
selfcheck request timed out error
I am having problems getting amcheck to return happy:
sudo -u amanda amcheck -c fullbackup
Amanda Backup Client Hosts Check
WARNING: royal.inse.lucent.com: selfcheck request timed out. Host down?
Client check: 1 host checked in 30.011 seconds, 1 problem found
(brought to you by Amanda 2.4.4)
royal is also the server.
I am following along with the tutorial at
http://www.backupcentral.com/amanda-14.html
Here are the relevant lines from /etc/services:
amanda 10080/udp# amanda backup services
kamanda 10081/tcp# amanda backup services (Kerberos)
kamanda 10081/udp# amanda backup services (Kerberos)
amandaidx 10082/tcp# amanda backup services
amidxtape 10083/tcp# amanda backup services
I ran the c program and obtained this output:
jlm17:royal:/tuxhome/jlm17 2309 ./a.out amanda udp
amanda/udp: 10080
jlm17:royal:/tuxhome/jlm17 2310 ./a.out amandaidx
amandaidx/tcp: 10082
jlm17:royal:/tuxhome/jlm17 2311 ./a.out amidxtape
amidxtape/tcp: 10083
Here is the /etc/xinetd.d/amanda file:
service amanda
{
socket_type = dgram
protocol= udp
wait= yes
user= amanda
group = amanda
groups = yes
server = /usr/libexec/amandad
# You need to ensure this points to your Amanda server!
# Don't just remove it!
only_from = royal
disable = no
}
service amandaidx
{
socket_type = stream
protocol= tcp
wait= no
user= amanda
group = amanda
groups = yes
server = /usr/libexec/amindexd
# You need to ensure this points to your Amanda server!
# Don't just remove it!
only_from = royal
disable = no
}
service amidxtape
{
socket_type = stream
protocol= tcp
wait= no
user= amanda
group = amanda
groups = yes
server = /usr/libexec/amidxtaped
# You need to ensure this points to your Amanda server!
# Don't just remove it!
only_from = royal
disable = no
}
There are no error messages from xinetd regarding amanda in /var/log/syslog.
There is nothing in /tmp. I'm not sure if my amanda configuration would
use /tmp for anything. There is no amandad*debug file anywhere on the
computer.
The access time on /usr/libexec/amandad is not being updated, but it
doesn't change even when I run amandad by hand:
ls -lu /usr/libexec/amandad
-rwxr-xr-x1 amanda amanda 12808 Feb 12 12:21
/usr/libexec/amandad*
Beyond what the document says to check, I have run smbclient
//dd439/jlm17_westford password -U amanda and it connected just fine.
Here is my disklist file:
royal.inse.lucent.com jlm17_westford //dd439/jlm17_westford fulldump
I have double checked my /etc/amandapass and it looks fine.
I am running Gentoo Linux 1.4rc4 on a Sun Ultra 2. Amanda version is
2.4.4. What should I check next?
Thanks.
Re: selfcheck request timed out error
On Wed, 25 Feb 2004 at 8:57am, jlm17 wrote
I am having problems getting amcheck to return happy:
sudo -u amanda amcheck -c fullbackup
Amanda Backup Client Hosts Check
WARNING: royal.inse.lucent.com: selfcheck request timed out. Host down?
Client check: 1 host checked in 30.011 seconds, 1 problem found
Here is the /etc/xinetd.d/amanda file:
service amanda
{
socket_type = dgram
protocol= udp
wait= yes
user= amanda
group = amanda
groups = yes
server = /usr/libexec/amandad
# You need to ensure this points to your Amanda server!
# Don't just remove it!
only_from = royal
disable = no
}
Just to check, if you remove the only_from line, does it work?
There are no error messages from xinetd regarding amanda in /var/log/syslog.
What does it way when you start it up? On RedHat it'll tell you how many
services are available...
There is nothing in /tmp. I'm not sure if my amanda configuration would
use /tmp for anything. There is no amandad*debug file anywhere on the
computer.
If you're not getting anything in /tmp/amanda, then amandad isn't even
starting up. Is ipchains/iptables getting in the way? What's the output
of 'netstat -ln | grep 10080'?
--
Joshua Baker-LePain
Department of Biomedical Engineering
Duke University
Re: selfcheck request timed out error
Thanks for the help. Responses to your questions are below:
Joshua Baker-LePain wrote:
On Wed, 25 Feb 2004 at 8:57am, jlm17 wrote
I am having problems getting amcheck to return happy:
sudo -u amanda amcheck -c fullbackup
Amanda Backup Client Hosts Check
WARNING: royal.inse.lucent.com: selfcheck request timed out. Host down?
Client check: 1 host checked in 30.011 seconds, 1 problem found
Here is the /etc/xinetd.d/amanda file:
service amanda
{
socket_type = dgram
protocol= udp
wait= yes
user= amanda
group = amanda
groups = yes
server = /usr/libexec/amandad
# You need to ensure this points to your Amanda server!
# Don't just remove it!
only_from = royal
disable = no
}
Just to check, if you remove the only_from line, does it work?
I commented out the only_from line from all three amanda services but it
does not work.
There are no error messages from xinetd regarding amanda in /var/log/syslog.
When I restart xinetd I only get the [OK],but I get these lines in
/var/log/syslog:
Feb 25 07:30:06 royal xinetd[28751]: Reading included configuration
file: /etc/xinetd.d/amanda [file=/etc/xinetd.conf] [line=13]
Feb 25 07:30:06 royal xinetd[28751]: Reading included configuration
file: /etc/xinetd.d/chargen-tcp [file=/etc/xinetd.d/chargen-tcp] [line=48]
Feb 25 07:30:06 royal xinetd[28751]: Reading included configuration
file: /etc/xinetd.d/chargen-udp [file=/etc/xinetd.d/chargen-udp] [line=13]
Feb 25 07:30:06 royal xinetd[28751]: Reading included configuration
file: /etc/xinetd.d/cups-lpd [file=/etc/xinetd.d/cups-lpd] [line=14]
Feb 25 07:30:06 royal xinetd[28751]: Reading included configuration
file: /etc/xinetd.d/daytime-tcp [file=/etc/xinetd.d/daytime-tcp] [line=13]
Feb 25 07:30:06 royal xinetd[28751]: Reading included configuration
file: /etc/xinetd.d/daytime-udp [file=/etc/xinetd.d/daytime-udp] [line=13]
Feb 25 07:30:06 royal xinetd[28751]: Reading included configuration
file: /etc/xinetd.d/echo-tcp [file=/etc/xinetd.d/echo-tcp] [line=14]
Feb 25 07:30:06 royal xinetd[28751]: Reading included configuration
file: /etc/xinetd.d/echo-udp [file=/etc/xinetd.d/echo-udp] [line=13]
Feb 25 07:30:06 royal xinetd[28751]: Reading included configuration
file: /etc/xinetd.d/swat [file=/etc/xinetd.d/swat] [line=14]
Feb 25 07:30:06 royal xinetd[28751]: Reading included configuration
file: /etc/xinetd.d/time-tcp [file=/etc/xinetd.d/time-tcp] [line=17]
Feb 25 07:30:06 royal xinetd[28751]: Reading included configuration
file: /etc/xinetd.d/time-udp [file=/etc/xinetd.d/time-udp] [line=13]
Feb 25 07:30:06 royal xinetd[28751]: removing chargen
Feb 25 07:30:06 royal xinetd[28751]: removing chargen
Feb 25 07:30:06 royal xinetd[28751]: removing printer
Feb 25 07:30:06 royal xinetd[28751]: removing daytime
Feb 25 07:30:06 royal xinetd[28751]: removing daytime
Feb 25 07:30:06 royal xinetd[28751]: removing echo
Feb 25 07:30:06 royal xinetd[28751]: removing echo
Feb 25 07:30:06 royal xinetd[28751]: removing swat
Feb 25 07:30:06 royal xinetd[28751]: removing time
Note that I do not get any lines about removing amanda services.
What does it way when you start it up? On RedHat it'll tell you how many
services are available...
There is nothing in /tmp. I'm not sure if my amanda configuration would
use /tmp for anything. There is no amandad*debug file anywhere on the
computer.
If you're not getting anything in /tmp/amanda, then amandad isn't even
starting up. Is ipchains/iptables getting in the way? What's the output
of 'netstat -ln | grep 10080'?
netstat -ln | grep 10080
udp0 0 0.0.0.0:10080 0.0.0.0:*
As far as I know I do not have any iptables stuff turned on. I don't
even have the iptables userland tools installed. I have turned it on in
the kernel, though.
--
Jason M'Sadoques
(978)392-6417 Phone
(888)422-3597 Pager
[EMAIL PROTECTED]
A146B
Re: selfcheck request timed out error
On Wed, 25 Feb 2004 at 3:06pm, jlm17 wrote
I commented out the only_from line from all three amanda services but it
does not work.
The other thing to check is /etc/hosts.{allow,deny}. I don't know Gentoo,
but on RedHat xinetd uses them. Accepts or denies based on those files
should be logged in /var/log/secure.
Note that I do not get any lines about removing amanda services.
Yes, but...
If you're not getting anything in /tmp/amanda, then amandad isn't even
starting up. Is ipchains/iptables getting in the way? What's the output
of 'netstat -ln | grep 10080'?
netstat -ln | grep 10080
udp0 0 0.0.0.0:10080 0.0.0.0:*
That means amanda is listening, so that part of xinetd is working right.
As far as I know I do not have any iptables stuff turned on. I don't
even have the iptables userland tools installed. I have turned it on in
the kernel, though.
You can check what rules are set up with 'iptables -nL'. I'd say the next
thing to do would be to look at the traffic. Do 'tcpdump -i lo' and then
run amcheck and see what happens.
--
Joshua Baker-LePain
Department of Biomedical Engineering
Duke University
Re: WARNING: database01: selfcheck request timed out. Host down?
On Sun, Dec 21, 2003 at 12:47:24PM -, Dean Pullen wrote:
Thanks for your interest and replys guys, I think we're getting closer to a solution
[I hope].
I'm using SuSE 8.2 (but using the amanda rpm from SuSE 9.0) - which I believe uses
xinetd.
Not that I know the difference. I'm afraid I'm a bit of a newbie in all areas, so
please bare with me.
Presumably this is a problem seeing as I have edited the inetd.conf instead of a
xinetd.conf? Why would there be a inetd.conf if SuSE is using xinetd?
Forgive me for jumping in late and to a discussion I know little about.
But these lines give me pause.
Your {x}inet daemon does not seem to be starting amandad (no /tmp/amanda/debug file).
You are using (I presume this is both server and client) SuSE 8.2.
You mention your amanda is from an SuSE 9 system and that SuSE 9 uses xinetd.
From that I take it SuSE 8.X may not.
I don't see why it matters a bit which, inet daemon SuSE 9 uses.
Which inet daemon are your systems set up to run at boot time.
That is the type of config files you should be editing.
Do you know your editing has had 'any' effect? ISTR that a command
like netstat (may be some other one) can be used to list the ports
that are being listened to by the internet daemon. Maybe someone
could correct or complete that thought.
jl
--
Jon H. LaBadie [EMAIL PROTECTED]
JG Computing
4455 Province Line Road(609) 252-0159
Princeton, NJ 08540-4322 (609) 683-7220 (fax)
RE: WARNING: database01: selfcheck request timed out. Host down?
Ok back at work... There seems to be no xinetd or inetd messages during startup (I performed a dmesg dmesg.txt and searched for xinetd/inetd). Is it worth trying to install xinetd from the supplied SuSE rpms? Note: The guy who first configured these machines has put various networking scripts in /etc/init.d/ is this similar to inetd etc? Dean.
RE: WARNING: database01: selfcheck request timed out. Host down?
Just a quick note. Looking at the SuSE manuals, it appears SuSE 8.2 uses xinetd (whereas 8.1 uses inetd). Which makes me wonder why it doesn't appear in the start up log. Dean.
Re: WARNING: database01: selfcheck request timed out. Host down?
On Monday 22 December 2003 05:01, Dean Pullen wrote: Ok back at work... There seems to be no xinetd or inetd messages during startup (I performed a dmesg dmesg.txt and searched for xinetd/inetd). Is it worth trying to install xinetd from the supplied SuSE rpms? Note: The guy who first configured these machines has put various networking scripts in /etc/init.d/ is this similar to inetd etc? Dean. I would say to do that only if inetd isn't being used on that system. And I've no idea how hard it would be to convert an inetd using installation into an xinetd using installation short of putting the newer versions cd in the drive and rebooting. Most installers will let you update a system, usually without losing any data. But I've not had 100% success doing that, more like 90% I think. To answer the last question, no, there is a dividing line there as the startup scripts for this and that get put into /etc/init.d, and are linked to various names starting with S99 or K43 in the various rcx.d dirs, where x is a number. What those do is setup the sequenceing of the machines personality, so the S99local is the last thing started, and K01local would be the first thing shut down when you do a reboot, or an init to a different runlevel than you are running at the moment. Xinetd.d's stuff isn't related to that. The basic diff between inetd and xinetd is that xinetd starts things on demand, whereas inetd started them and left them sleeping, using a bit more memory, and far less security. -- Cheers, Gene AMD [EMAIL PROTECTED] 320M [EMAIL PROTECTED] 512M 99.22% setiathome rank, not too shabby for a WV hillbilly Yahoo.com attornies please note, additions to this message by Gene Heskett are: Copyright 2003 by Maurice Eugene Heskett, all rights reserved.
Re: WARNING: database01: selfcheck request timed out. Host down?
On Monday 22 December 2003 05:36, Dean Pullen wrote: Just a quick note. Looking at the SuSE manuals, it appears SuSE 8.2 uses xinetd (whereas 8.1 uses inetd). Which makes me wonder why it doesn't appear in the start up log. Dean. Humm, it sure should. Do you have, in /etc/rc(your runlevel as a number).d, an SXXxinetd, where it is a link to ../init.d/xinetd? Since I boot to level 3, and then run startx for my eye candy, its /etc/rc3.d/S56xinetd on this RH8.0 system. Like this: [EMAIL PROTECTED] root]# ls -l /etc/rc3.d/S56xinetd lrwxrwxrwx1 root root 16 Nov 12 00:23 /etc/rc3.d/S56xinetd - ../init.d/xinetd -- Cheers, Gene AMD [EMAIL PROTECTED] 320M [EMAIL PROTECTED] 512M 99.22% setiathome rank, not too shabby for a WV hillbilly Yahoo.com attornies please note, additions to this message by Gene Heskett are: Copyright 2003 by Maurice Eugene Heskett, all rights reserved.
RE: WARNING: database01: selfcheck request timed out. Host down?
-Original Message- From: Gene Heskett [mailto:[EMAIL PROTECTED] Sent: 22 December 2003 11:03 To: Dean Pullen; [EMAIL PROTECTED] Subject: Re: WARNING: database01: selfcheck request timed out. Host down? On Monday 22 December 2003 05:36, Dean Pullen wrote: Just a quick note. Looking at the SuSE manuals, it appears SuSE 8.2 uses xinetd (whereas 8.1 uses inetd). Which makes me wonder why it doesn't appear in the start up log. Dean. Humm, it sure should. Do you have, in /etc/rc(your runlevel as a number).d, an SXXxinetd, where it is a link to ../init.d/xinetd? Since I boot to level 3, and then run startx for my eye candy, its /etc/rc3.d/S56xinetd on this RH8.0 system. Like this: [EMAIL PROTECTED] root]# ls -l /etc/rc3.d/S56xinetd lrwxrwxrwx1 root root 16 Nov 12 00:23 /etc/rc3.d/S56xinetd - ../init.d/xinetd -- Cheers, Gene AMD [EMAIL PROTECTED] 320M [EMAIL PROTECTED] 512M 99.22% setiathome rank, not too shabby for a WV hillbilly Yahoo.com attornies please note, additions to this message by Gene Heskett are: Copyright 2003 by Maurice Eugene Heskett, all rights reserved. Gene, Well there was no link in any of the rcX.d directories. I tried adding one to rc3.d but xinetd still does not print anything on startup. Dean
RE: WARNING: database01: selfcheck request timed out. Host down?
Performing an xinted from command line gives me this in my /var/log/messages: Dec 22 13:20:14 database01 xinetd[1716]: Reading included configuration file: /etc/xinetd.d/amanda [line=26] Dec 22 13:20:14 database01 xinetd[1716]: Reading included configuration file: /etc/xinetd.d/amandaidx [line=14] Dec 22 13:20:14 database01 xinetd[1716]: Reading included configuration file: /etc/xinetd.d/amidxtape [line=14] -- cut -- Dec 22 13:20:14 database01 xinetd[1716]: removing amanda Dec 22 13:20:14 database01 xinetd[1716]: removing amandaidx Dec 22 13:20:14 database01 xinetd[1716]: removing amidxtape Does it look like its running the services the killing them? Dean.
RE: WARNING: database01: selfcheck request timed out. Host down?
Doing this:
# /etc/init.d/xinetd start
Produces this:
# Starting INET services. (xinetd) failed
And by the way the end of the log states:
Dec 22 13:39:38 database01 xinetd[1909]: 1909 {init_services} no services.
Exiting...
