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
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" 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: > > 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
The command you should run is: lsof -I :amanda Which should show the inetd/xinetd process listening on the amanda port (UDP port 10080). The output should look something like this: ritcdx> lsof -i :amanda COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME inetd 1285913 root 28u IPv4 0x5fe888c0 0t0 UDP *:amanda Unless you are very lucky during your testing, this is probably all you will ever see on the port except when Amanda is actually performing a backup. Best wishes, Donald L. (Don) Ritchey Information Technology, Exelon Corporation -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Wednesday, September 13, 2006 11:41 AM To: [email protected] Subject: Re: "selfcheck request timed out" WAS Re: Running amanda client only Replying to my own post (sorry, but I'm getting desperate here), I took the advice of the FAQ-O-Matic and installed lsof and ran this command: su-2.05b# lsof -uamanda There was no output. Should there have been? Does this mean that amandad is not running? This is what I have in my /etc/inetd.conf: amanda dgram udp wait amanda /usr/local/libexec/amandad amandad inetd.conf has beek killed and restarted, the client even rebooted...anything? On Wed, 13 Sep 2006 [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 = - ** This e-mail and any of its attachments may contain Exelon Corporation proprietary information, which is privileged, confidential, or subject to copyright belonging to the Exelon Corporation family of Companies. This e-mail is intended solely for the use of the individual or entity to which it is addressed. If you are not the intended recipient of this e-mail, you are hereby notified that any dissemination, distribution, copying, or action taken in relation to the contents of and attachments to this e-mail is strictly prohibited and may be unlawful. If you have received this e-mail in error, please notify the sender immediately and permanently delete the original and any copy of this e-mail and any printout. Thank You. **
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
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. 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: [email protected] 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: [email protected] >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: 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
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: 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: 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
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
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
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
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
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
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
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: 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
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
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
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
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: 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: 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
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
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
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 amanda
Re: selfcheck request timed out
Leonid Shulov wrote: but: astp0002:/var/log# sudo -u backup /usr/lib/amanda/amandad amandad: create debug directory "/var/log/amanda": Permission denied What happens if you type: sudo -u backup mkdir -p /var/log/amanda Do you an error, or does it succeed silently? Or do you have SElinux enabled with some very strict setting? No, simple Debian Linux with kernel 2.6.15-1-686 I'm not that familiar with debian. (SELinux is a configuration not a packager, just in 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: 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
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? -- 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
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: 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: 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: 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: 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. Host down?
Nader Amadeu wrote: 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. That's the file on the server. On the client there needs to be a file named /tmp/amanda/amandad.*.debug Is it there? -- 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. 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
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.
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: 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 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.
On Mon, 13 May 2002, jmurray wrote: > Ok, I figured out the permissions problem that was preventing amcheck from > working, as per below. > amcheck now finishes with no errors. > > When I run amdump, "top" on the client shows gtar working away, so it data > compression seems to be happening. amdump finishes with no errors, but in > the report email, I get: > > > These dumps were to tape daily001. > > The next tape Amanda expects to use is: daily001. > > > > FAILURE AND STRANGE DUMP SUMMARY: > > client.agic. /usr lev 0 FAILED [Request to client.agic.ne.jp timed out.] > > ... > > Can anyone help me end this nightmare? > > Shawn Check the files in /tmp/amanda for the date in question. Better yet, remove /tmp/amanda, run a dump and scrutinize the files created. Could be the estimation timing out due to large partition, slow machine, short 'etimeout', low 'netusage', or a combination of these. Estimation timeout is one of the rare situations where, in my opinion, Amanda does not make the error visible. I notice that you use a single tape. It would make things easier for all of us if you use a somewhat more realistic setup. For example: dumpcycle 1 week# a full dump every week runspercycle 5 # backup weekdays only tapecycle 8 tapes # three extra tapes Or, if you're really short of tapes: dumpcycle 2 days# a full dump every other day runspercycle 2 # backup every day tapecycle 3 tapes # one extra tape -- Ulrik Sandberg
Re: selfcheck request timed out.
Ok, I figured out the permissions problem that was preventing amcheck from working, as per below. amcheck now finishes with no errors. When I run amdump, "top" on the client shows gtar working away, so it data compression seems to be happening. amdump finishes with no errors, but in the report email, I get: > These dumps were to tape daily001. > The next tape Amanda expects to use is: daily001. > > FAILURE AND STRANGE DUMP SUMMARY: > client.agic. /usr lev 0 FAILED [Request to client.agic.ne.jp timed out.] > > > STATISTICS: > Total Full Daily > > Estimate Time (hrs:min)0:15 > Run Time (hrs:min) 0:15 > Dump Time (hrs:min)0:00 0:00 0:00 > Output Size (meg) 0.00.00.0 > Original Size (meg) 0.00.00.0 > Avg Compressed Size (%) -- -- -- > Filesystems Dumped0 0 0 > Avg Dump Rate (k/s) -- -- -- > > Tape Time (hrs:min)0:00 0:00 0:00 > Tape Size (meg) 0.00.00.0 > Tape Used (%) 0.00.00.0 > Filesystems Taped 0 0 0 > Avg Tp Write Rate (k/s) -- -- -- > > > NOTES: > planner: Adding new disk client.agic.ne.jp:/usr. > driver: WARNING: got empty schedule from planner > taper: tape daily001 kb 0 fm 0 [OK] > > > DUMP SUMMARY: > DUMPER STATSTAPER STATS > HOSTNAME DISKL ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS KB/s > -- - > client.agic.ne /usr0 FAILED --- > > (brought to you by Amanda version 2.4.2p2) Can anyone help me end this nightmare? Shawn - Original Message - From: "Jonathan Murray" <[EMAIL PROTECTED]> To: "GIC MLs" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Saturday, May 11, 2002 1:55 AM Subject: Re: selfcheck request timed out. > check .amandahosts file. > also make sure that you don't use FQDN in .amandahosts. > > GIC MLs wrote: > > > Hi, > > > > I'm running Amanda 2.4.2p2, and when I run "amcheck daily", I get: > > > > Amanda Tape Server Host Check > > - > > NOTE: skipping tape-writable test > > Tape daily001 label ok > > NOTE: info dir /usr/local/etc/amanda/daily/curinfo: does not exist > > NOTE: it will be created on the next run > > Server check took 5.219 seconds > > > > Amanda Backup Client Hosts Check > > > > WARNING: client.agic.ne.jp: selfcheck request timed out. Host down? > > Client check: 1 host checked in 30.078 seconds, 1 problem found > > > > The client machine is pingable and configured with amandad running off of > > inetd. > > Can anyone tell me where I should start looking for the root of this > > problem? > > > > Thank you for any assistance. > > > > Shawn > > > > > > > > >
Re: selfcheck request timed out.
check .amandahosts file. also make sure that you don't use FQDN in .amandahosts. GIC MLs wrote: > Hi, > > I'm running Amanda 2.4.2p2, and when I run "amcheck daily", I get: > > Amanda Tape Server Host Check > - > NOTE: skipping tape-writable test > Tape daily001 label ok > NOTE: info dir /usr/local/etc/amanda/daily/curinfo: does not exist > NOTE: it will be created on the next run > Server check took 5.219 seconds > > Amanda Backup Client Hosts Check > > WARNING: client.agic.ne.jp: selfcheck request timed out. Host down? > Client check: 1 host checked in 30.078 seconds, 1 problem found > > The client machine is pingable and configured with amandad running off of > inetd. > Can anyone tell me where I should start looking for the root of this > problem? > > Thank you for any assistance. > > Shawn > >
Re: selfcheck request timed out.
On Fri, 10 May 2002 at 1:32pm, GIC MLs wrote > I'm running Amanda 2.4.2p2, and when I run "amcheck daily", I get: > Amanda Backup Client Hosts Check > > WARNING: client.agic.ne.jp: selfcheck request timed out. Host down? > Client check: 1 host checked in 30.078 seconds, 1 problem found > > The client machine is pingable and configured with amandad running off of > inetd. > Can anyone tell me where I should start looking for the root of this > problem? Have you gone through the steps in amcheck section of Faq-O-Matic? That's the place to start, then come back here if that doesn't work. http://amanda.sourceforge.net/fom-serve/cache/1.html -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: selfcheck request timed out. Host down?
On Wed, Jan 30, 2002 at 07:05:19AM +1100, Tim Tuck wrote: > Hi Don, > > I've been following this discussion and you might have what my Solaris boxs did > firts time I ran Amanda ; your /tmp is not writable by the user Amanda is > running as. > > Amanda needs to build an amanda dir inside /tmp - check the perms you might find > that /tmp has limited access. Or that the subdirectory, /tmp/amanda, has inappropriate ownership/permissions. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: selfcheck request timed out. Host down?
Hi Don, I've been following this discussion and you might have what my Solaris boxs did firts time I ran Amanda ; your /tmp is not writable by the user Amanda is running as. Amanda needs to build an amanda dir inside /tmp - check the perms you might find that /tmp has limited access. cheers Tim
Re: selfcheck request timed out. Host down?
Launching the daemon as root works just fine.I didn't even think about the library issue. the access time never changed on amandad until I changed the daemon owner...now comes the fun part ot figure out which library has a permission issue.. But I should be able to discern that by he truss..at least I believe that should work... Don John R. Jackson wrote: >>Jan 29 13:48:18 helix inetd[189]: [ID 858011 daemon.warning] >>/usr/bin/truss: Hangup >>... >>Jan 29 13:50:28 helix inetd[189]: [ID 858011 daemon.warning] >>/tmp/amanda_test: Hangup >> > >Something is seriously wonky about your system if you can't run these >things. Try one more test without Amanda in the loop at all: > > amandadgram udp wait amanda /bin/sleep sleep 4 > >If that also does the Hangup (amcheck will fail, but that's not important >at this point), then I have no clue. Well, maybe one ... > >>I can truss the amandad with no problem as well as determine what >>arguments and exit status by running from the command line >> > >When you run things by hand, they have a different environment (in many >ways) than when inetd runs them. It can be a real pain figuring out >what the difference is. > >When you ran things by hand, did you run them a "amanda"? In >particular, did you do something like this: > > su - amanda -c "/var/adm/amanda/libexec/amandad" > >The leading '-' tells "su" to set up the environment as though the >user had logged in (i.e. it does not inherit whatever you have). >And specifying the full path makes sure $PATH isn't getting you a >different version of the program. > >If that's not it, and the sleep also fails, try using sleep again but >change "amanda" to "root". > >If that also fails, there is something wrong with the way your system >is set up, but without looking at it myself I wouldn't have the faintest >idea where to start. > >If root works but amanda fails, you've may have some kind of permissions >problem. Since amandad (et al) are dieing right at the start, I'd guess >a shared library. > >One other thing you could try is truss (-f) inetd itself to watch >the amanda service (I'd still use sleep at this point) get started. >The problem could easily be that the forked inetd child is having the >problem and never even getting to the other program (sleep, amandad, >truss, etc). > >Speaking of which, did you check the access time on amandad after trying >amcheck? If it's not getting updated, that also means it's probably >the inetd child failing before it can exec the real program. > >John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED] >
Re: selfcheck request timed out. Host down?
>Jan 29 13:48:18 helix inetd[189]: [ID 858011 daemon.warning] >/usr/bin/truss: Hangup >... >Jan 29 13:50:28 helix inetd[189]: [ID 858011 daemon.warning] >/tmp/amanda_test: Hangup Something is seriously wonky about your system if you can't run these things. Try one more test without Amanda in the loop at all: amandadgram udp wait amanda /bin/sleep sleep 4 If that also does the Hangup (amcheck will fail, but that's not important at this point), then I have no clue. Well, maybe one ... >I can truss the amandad with no problem as well as determine what >arguments and exit status by running from the command line When you run things by hand, they have a different environment (in many ways) than when inetd runs them. It can be a real pain figuring out what the difference is. When you ran things by hand, did you run them a "amanda"? In particular, did you do something like this: su - amanda -c "/var/adm/amanda/libexec/amandad" The leading '-' tells "su" to set up the environment as though the user had logged in (i.e. it does not inherit whatever you have). And specifying the full path makes sure $PATH isn't getting you a different version of the program. If that's not it, and the sleep also fails, try using sleep again but change "amanda" to "root". If that also fails, there is something wrong with the way your system is set up, but without looking at it myself I wouldn't have the faintest idea where to start. If root works but amanda fails, you've may have some kind of permissions problem. Since amandad (et al) are dieing right at the start, I'd guess a shared library. One other thing you could try is truss (-f) inetd itself to watch the amanda service (I'd still use sleep at this point) get started. The problem could easily be that the forked inetd child is having the problem and never even getting to the other program (sleep, amandad, truss, etc). Speaking of which, did you check the access time on amandad after trying amcheck? If it's not getting updated, that also means it's probably the inetd child failing before it can exec the real program. John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: selfcheck request timed out. Host down?
dum fails as well (should of specified )..running the test that you specified I recieved the following in the /var/adm/messages: Jan 29 13:48:18 helix inetd[189]: [ID 858011 daemon.warning] /usr/bin/truss: Hangup Jan 29 13:48:26 helix last message repeated 38 times Jan 29 13:48:26 helix inetd[189]: [ID 667328 daemon.error] amanda/udp server failing (looping), service terminated Jan 29 13:50:28 helix inetd[189]: [ID 858011 daemon.warning] /tmp/amanda_test: Hangup I can truss the amandad with no problem as well as determine what arguments and exit status by running from the command line John R. Jackson wrote: >>it only croaks on the amcheck... >> > >Huh??? It **doesn't** fail for amdump? > >>the amandad will Hangup before providing any output.. >> > >Huh??? > >Did you try either of the other "debug tricks" I sent? > >John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED] >
Re: selfcheck request timed out. Host down?
>it only croaks on the amcheck... Huh??? It **doesn't** fail for amdump? >the amandad will Hangup before providing any output.. Huh??? Did you try either of the other "debug tricks" I sent? John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: selfcheck request timed out. Host down?
Cut and paste ...
it only croaks on the amcheck...
no security packs. at all:
the amandad will Hangup before providing any output..
John R. Jackson wrote:
>>amandadgram udp wait amanda /var/adm/amanda/libexec/amandad
>>amandad
>>amandaidx stream tcp nowait amanda /var/adm/amanda/libexec/amindexd
>>amindexd
>>amidxtape stream tcp nowait amanda /var/adm/amanda/libexec/amidxtaped
>>amidxtaped
>>
>
>The lines came across in the E-mail broken as shown above. Is that
>real or is it just a cut/paste artifact?
>
>The important part is that there be one, and only one, arg to each of
>the lines (after the path to the executable). If the arg (e.g. "amanda")
>is missing, the server will try to reference argv[0] and die.
>
>What you have above is OK if there are actually three lines and not six.
>
>Did inetd whine into /var/adm/messages when you HUP'd it?
>
>Do you have (I think it's called) BSM installed (some kind of enhanced
>security package)? I recall problems with it, but don't remember the
>details.
>
>If none of that helps, here are the next things I do (from my inetd.conf):
>
>#JJ First debug trick -- create this shell script (chmod +x /tmp/amandad.test):
>#JJ #!/bin/ksh
>#JJ exec > /tmp/amandad.out.$$ 2>&1
>#JJ echo "$(/bin/date): starting amandad ($#): " "$@"
>#JJ /opt/amanda/libexec/amandad "$@"
>#JJ status=$?
>#JJ echo "$(/bin/date): amandad done: status is $status"
>#JJ exit $status
>#JJ
>#JJ amanda dgram udp waitbackup /tmp/amandad.test amandad
>#JJ
>#JJ Next debug trick -- run amandad under truss:
>#JJ
>#JJ amanda dgram udp waitbackup /bin/truss amandad -fo
>/tmp/amandad.truss /opt/amanda/libexec/amandad
>
>Note that the user name ("backup" vs. "amanda") and paths to the binaries
>on your system will be different.
>
>John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
>
Re: selfcheck request timed out. Host down?
>amandadgram udp wait amanda /var/adm/amanda/libexec/amandad
>amandad
>amandaidx stream tcp nowait amanda /var/adm/amanda/libexec/amindexd
>amindexd
>amidxtape stream tcp nowait amanda /var/adm/amanda/libexec/amidxtaped
>amidxtaped
The lines came across in the E-mail broken as shown above. Is that
real or is it just a cut/paste artifact?
The important part is that there be one, and only one, arg to each of
the lines (after the path to the executable). If the arg (e.g. "amanda")
is missing, the server will try to reference argv[0] and die.
What you have above is OK if there are actually three lines and not six.
Did inetd whine into /var/adm/messages when you HUP'd it?
Do you have (I think it's called) BSM installed (some kind of enhanced
security package)? I recall problems with it, but don't remember the
details.
If none of that helps, here are the next things I do (from my inetd.conf):
#JJ First debug trick -- create this shell script (chmod +x /tmp/amandad.test):
#JJ #!/bin/ksh
#JJ exec > /tmp/amandad.out.$$ 2>&1
#JJ echo "$(/bin/date): starting amandad ($#): " "$@"
#JJ /opt/amanda/libexec/amandad "$@"
#JJ status=$?
#JJ echo "$(/bin/date): amandad done: status is $status"
#JJ exit $status
#JJ
#JJ amanda dgram udp waitbackup /tmp/amandad.test amandad
#JJ
#JJ Next debug trick -- run amandad under truss:
#JJ
#JJ amanda dgram udp waitbackup /bin/truss amandad -fo
/tmp/amandad.truss /opt/amanda/libexec/amandad
Note that the user name ("backup" vs. "amanda") and paths to the binaries
on your system will be different.
John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: selfcheck request timed out. Host down?
Here ya' go.basiclly the config appeneeded when you use patch-system /etc/services amanda 10080/udp amandaidx 10082/tcp amidxtape 10083/tcp /etc/inetd.conf amandadgram udp wait amanda /var/adm/amanda/libexec/amandad amandad amandaidx stream tcp nowait amanda /var/adm/amanda/libexec/amindexd amindexd amidxtape stream tcp nowait amanda /var/adm/amanda/libexec/amidxtaped amidxtaped John R. Jackson wrote: >>... Ran the amcheck again and the amanda ports would be shut >>down with the following message in the /var/adm/message file: >> >>Jan 29 10:50:54 svr1 inetd[189]: [ID 858011 daemon.warning] /var/adm/amanda/li >>bexec/amandad: Hangup >>... >> > >What's your inetd.conf line look like? > >>Don Potter >> > >John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED] >
Re: selfcheck request timed out. Host down?
>... Ran the amcheck again and the amanda ports would be shut >down with the following message in the /var/adm/message file: > >Jan 29 10:50:54 svr1 inetd[189]: [ID 858011 daemon.warning] /var/adm/amanda/li >bexec/amandad: Hangup >... What's your inetd.conf line look like? >Don Potter John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: Selfcheck request timed out, host down problem?
[EMAIL PROTECTED] wrote: > Hi, again > James thanks for your help. > > Well, > The server and the client are in the same machine (wendy), by the moment. > When I execute #su amanda -c "/software/amanda/libexec/amandad", the >amadad.xxx.debug is This is probably because you also have amandad being executed by inetd. What shows up in amanda.xxx.debug when you run amcheck and inetd starts amandad? > > > > amandad: debug 1 pid 4921 ruid 3001 euid 3001 start time Wed Jan 9 12:38:32 200 > 2 [...lots of path messages] > amandad: dgram_recv: timeout after 30 seconds > amandad: error receiving message: timeout > error receiving message: timeout > amandad: pid 4921 finish time Wed Jan 9 12:39:02 2002 > > > > > Also i have to say that i want to use AMANDA with a SUN STARAGE L20 > > Thanks for all. > --- > Javier Fernández Pérez > Servicio de Informática Corporativa > D.G. de Telecomunicaciones y Transportes > > Consejería de Fomento - Junta de Castilla y León > Rigoberto Cortejoso, 14. 47014 Valladolid (Spain) > > e-mail: [EMAIL PROTECTED] > --- > > -- David T. Smith PGP Fingerprint: 7B01 0086 BC4E C092 5348 B9AE E79A 07F2 9E59 29C2 ph: 1 203 364 1796 fax: 1 203 364 1795 cell: 1 203 770 1685 E-mail [EMAIL PROTECTED]
Re: selfcheck request timed out. Host down? error
> I am having a problem backing up one of my UNIX boxes with Amanda. When I > run AmCheck I get the error: > > WARNING: bill: selfcheck request timed out. Host down? > Client check: 7 hosts checked in 29.678 seconds, 1 problem found. > > As you can see the check runs successfully on 6 hosts but times out on 1. > The host is not down as I can ping and rlogin in to it without any problem. > It does also have the appropriate entries in the /etc/services and > /etc/inetd.conf What's in /tmp/amanda/*debug on this machine?
Re: selfcheck request timed out
sendoro wrote:
> Hi Folks,
>
>
> Pls help, I have spent a lot of time but I haven't yet succeded,
> I am getting this error "WARNING: xxx: selfcheck request timed out.
> Host down?"
> on amanda-2.4.2p2
> I trying to backup the client from the same machine which is tape
> server. so that I can backup its file system.
>
> 1.Here is my config. I configured the tape server as follows.
> ./configure --with-user=amanda --with-group=amanda
> --with-config=config --without-bsd-security --with-amandaho
> sts --with-index-server=xxx.domain.com
> --with-tape-server=.domain.com --with-tape-drive=/dev
> /nst0 --with-fqdn --with-gnutar=/usr/local/bin/tar
>
> 2. my xinted.conf has the following
> service amanda
> {
> socket_type dgram
> protocoludp
> waityes
> useramanda
> group amanda
> server /usr/local/libexec/amandad
> port10080
> }
> service amandaidx
> {
> socket_type stream
> protocoltcp
> waitno
> useramanda
> group amanda
> server /usr/local/libexec/amindexd
> port10082
> log_type= SYSLOG authpriv
> log_on_success = HOST PID
> log_on_failure = HOST RECORD
> }
> service amidxtape
> {
> socket_type stream
> protocoltcp
> waitno
> useramanda
> group amanda
> server /usr/local/libexec/amidxtaped
> port10083
> log_type= SYSLOG authpriv
> log_on_success = HOST PID
> log_on_failure = HOST RECORD
> }
> 3. I increased the ctimeout from 30secs to 60 secs in amanda.conf
> 4. I unistalled nfs
> 5. the /etc/services looks good.
> 6. Howerver when trying to rlogin -l amanda_user it is asking for
> password
>
> Kindly show me what to do. Thank you
> ^^^
> J. I. Sendoro
> IS Manager
> NewA.Net Ltd.
> Tel. +255 22 2700 962
> Mob. +255 744 279 721
> email [EMAIL PROTECTED]
> website http://www.newafrica.com
> Learning Linux From The Man Page is Like Learning French From A
> Dictionary
>
> ^^^
>
Hi, what you seem to be missing is the file ".amandahosts".
It must be in the home directory of the dump user (here "amanda") and
looks like the following:
host.to.give.access amanda
Where host.to.give.access would be your machine. However, amanda doesn't
seem to take ip adresses so give your machine name (try to ping yourself
with the name you give to see if the name is recognised by the system,
if not, add it to /etc/hosts).
That should be it, if you have more problem with this issue, i seggest
looking at the Faq-O-matic (there is a link on www.amanda.org) , it
saved me a great deal of time.
Re: selfcheck request timed out
>I am getting this error "WARNING: xxx: selfcheck request timed out. Host >down?" >on amanda-2.4.2p2 As a short guess, I's say you have to open the ports on tcp.wrapper. What do you use in disklist? localhost of the FDQN Olivier
Re: selfcheck request timed out.
>since a reboot of the firewall, amanda reports "selfcheck request timed >out." for some (up to four) servers. some servers are never reported (they >seem to repsond to the selfcheck request), the other servers change (i.e., >servers a,b,c,d are reported to time out, 1 hour later servers c,d,e,f are >reported to time out). I would suggest that the firewall had been reconfigured to allow amanda and the confg was not saved. When the firewall rebooted, the modifications were lost. Olivier
Re: selfcheck request timed out - redux
>... What I really was looking for was a more >efficient manner of diagnosing the problems in response to the error >message. Here's the order I would do things after adding the entry and HUP'ing inetd (or the equivalent for xinetd): * Look at whatever system log inetd writes to and make sure it didn't complain about anything. For instance, if you forgot to add the amandad service to /etc/services, inetd will whine to the log file about a bad service name. It might even be useful to deliberately put a bad entry in the file just to see where error messages get logged. * Run "netstat -a | grep amanda" and make sure someone (inetd) is listening on the amanda port(s). If not, you for certain have an inetd problem and there's no point going further. It might be as simple as having forgotten to do the HUP. Or it could be some typo in the line (which probably would have been logged). * Run "amcheck -cl " on the tape server (after updating disklist, etc). If it times out, the first thing to check is the files in /tmp/amanda on the client. If you don't see an amandad*debug file at all, inetd was not able to start it for some reason. Back to the log files, or try the "run it by hand" test. If the file is there, check it for errors and also look for the corresponding selfcheck*debug file, although things rarely get this far and still fail. At least part of the difficulty with all this is the differences between OS's. For instance, you mentioned setting the user and group in inetd.conf. None of my OS's support that, so I wouldn't have had any idea to advise you to look for that type of problem. >Josh Kuperman John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: selfcheck request timed out - redux
I think I should reply since I figured out I yet again had a typo in inetd.conf. Unless adding "don't make a typo in inetd.conf or if you do spot it" to the FAQ. What I really was looking for was a more efficient manner of diagnosing the problems in response to the error message. On Fri, Jun 22, 2001 at 09:33:54PM -0500, John R. Jackson wrote: > >When I run amcheck I get 'selfcheck request timed out' while trying to > >connect to localhost ... > > First, don't use "localhost". It will bite you eventually. Use the My best guess is it has bitten me many times. > fully qualified domain name of the host. Any modern network code will > notice they are the same thing and you won't lose any performance. > > >I remember getting this error on other installations. It seems to get > >me every time I do a new install or even an update on an old machine. > > It is, by far, the most common problem for new installations. There are > >... I > >have found that with a machine with two ethernet interfaces, each with > >its own IP and name, one will work and the other will fail. ... I have problems because I'm almost alway using dual homed hosts where I'll have one interface on the internet and typically a 192.168.1.x interface on my local net. The problems come from getting the reverse lookup to match the name look up. I'm not sure if this can actually cause the "selfcheck request timed out" message. > > If you get a case like this again, please post and maybe we can look > into what's going on and see if there is something Amanda could do to > make it better. I will the next time I set it another machine. > > >I have > >found cases where I need to put both the user and the operator in > >inetd.conf. I meant to say where I need both the user and the group, in my case operator.operator in inetd.conf. that was just typing too fast - which is probably what happens when I make entries in inetd.conf > > Not sure I understood this one. > > >Does anyone have a complete list of what causes this error message? ... > > That's what the FAQ at www.amanda.org is for. Here are the main URL's > about this particular topic: > > http://amanda.sourceforge.net/fom-serve/cache/16.html > http://amanda.sourceforge.net/fom-serve/cache/140.html > > I think some of this is also covered in "the book chapter" referenced > at www.amanda.org. > > >... I > >keep thinking about what it could be and then I try something. If it > >fixes it I stop (and forget exactly what I did to get it working). ... > > Instead of forgetting :-), how about adding an FAQ item yourself? > You'll not only help yourself next time you run into the same thing, > you'll also be helping other people. I would if they weren't already in the FAQ. My problem is not that I ever come up with a new problem but that it is hard to diagnose it. I did look at those pages. And I will look at them again and will readily acknowledge my need to go through more thoroughly. I downloaded and installed lsof. But I didn't know what files to look for when I ran lsof. I saw some of the pieces running, that is some files that were obviously part of amandam, and thought they all were. I also tried downloading the C programs, gethostbyname.c, gethostbyaddr.c, and getservbyname.c, to help figure what was happening. For some reasons I will examine later I was unable to get them to compile on the machine I am running amanda on. I also looked through the tmp directory, and probably should have figured out staight away that the amandad wasn't being started through inetd because the files were too short. But of course that's what I'd expect with the timeout message. It feel that I should have gotten the mechanics of testing down; but somehonw I haven't. I'm not sure what, if anything, I really should have asked. I suspect the answer was run top, i.e. "top -Uoperator" and watch to see that an amandad process and at least a second amcheck progress starts. Though even in this case I'm not really sure what I should see. -- Josh Kuperman [EMAIL PROTECTED]
Re: selfcheck request timed out - redux
>When I run amcheck I get 'selfcheck request timed out' while trying to >connect to localhost ... First, don't use "localhost". It will bite you eventually. Use the fully qualified domain name of the host. Any modern network code will notice they are the same thing and you won't lose any performance. >I remember getting this error on other installations. It seems to get >me every time I do a new install or even an update on an old machine. It is, by far, the most common problem for new installations. There are just so many OS's and possible ways for to screw up, that unless you practice all the time :-), it's probably going to keep showing up. >... I >have found that with a machine with two ethernet interfaces, each with >its own IP and name, one will work and the other will fail. ... If you get a case like this again, please post and maybe we can look into what's going on and see if there is something Amanda could do to make it better. >I have >found cases where I need to put both the user and the operator in >inetd.conf. Not sure I understood this one. >Does anyone have a complete list of what causes this error message? ... That's what the FAQ at www.amanda.org is for. Here are the main URL's about this particular topic: http://amanda.sourceforge.net/fom-serve/cache/16.html http://amanda.sourceforge.net/fom-serve/cache/140.html I think some of this is also covered in "the book chapter" referenced at www.amanda.org. >... I >keep thinking about what it could be and then I try something. If it >fixes it I stop (and forget exactly what I did to get it working). ... Instead of forgetting :-), how about adding an FAQ item yourself? You'll not only help yourself next time you run into the same thing, you'll also be helping other people. >Josh Kuperman John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: selfcheck request timed out
> Are there any clues in the /tmp/amanda directory on the server ? Nope. not a thing. When I run 'amcheck eagle' it doesn't write anything in the /tmp/amanda directory. I do see stuff in there from last night's successful backup of the two unix boxes though. That's the goofy part. The backups of the Unix boxes works fine, just I broke the PC shares when I replaced the old server with the new. FreeBSD 4.2 Release. The ports tree has Amanda 2.4.1p1 -Gerry
Re: selfcheck request timed out
> Are you able to communicate with the PC using the smbclient program ? > i.e. Can you interact with it by typing from the amanda server > smbclient file://mypcname/mysharename share-password Yep. ./smbclient file://ww2/d -U samba It then prompts me for the password, and I can list the files, etc. -Gerry
Re: Selfcheck request timed out
On Oct 28, 2000, Vijay Parthasarathy <[EMAIL PROTECTED]> wrote:
> WARNING: par: selfcheck request timed out. Host down?
Check the on-line FAQ at www.amanda.org.
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicampoliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist*Please* write to mailing lists, not to me
