Amanda-Users

RE: amcheck error

2005-03-16 16:52:50
Subject: RE: amcheck error
From: "Kevin Chen" <kchen AT fre.devry DOT edu>
To: "Paul Bijnens" <paul.bijnens AT xplanation DOT com>
Date: Wed, 16 Mar 2005 13:37:32 -0800
Hi:

That's exactly what I have in inetd.conf, if I typed it from command
line, it would sit there for 30 seconds and stop and create a log file
at /tmp/amanda - amandad.20050316134621.debug.

Here are last few lines of this log file - 

time 30.007: dgram_recv: timeout after 30 seconds
amandad: error receiving message: timeout
amandad: time 30.008: error receiving message: timeout
amandad: time 30.008: pid 939 finish time Wed Mar 16 13:46:51 2005

Thanks.

Kevin

-----Original Message-----
From: Paul Bijnens [mailto:paul.bijnens AT xplanation DOT com] 
Sent: Wednesday, March 16, 2005 1:16 PM
To: Kevin Chen
Cc: amanda-users AT amanda DOT org
Subject: Re: amcheck error

Kevin Chen wrote:

> Greetings:
> 
>  
> 
> I am setting up Amanda 2.4.4p4 on a Sun Ultra30 machine which is
> running Solaris 8, configuration and make install went through all
> right, but when I run "amcheck Daily", it is keep on complaining
> about one of client host is down - "Warning: spain selfcheck request
> timed out, Host down?", spain is another ultra30 in the same subnet
> and I have ran "patch-system" on both server and client "spain"
> machine already. There are also some error messages in
/var/adm/messages 
> - "inetd[138]: [ID 858011 daemon.warning] /usr/local/libexec/amandad: 
> Killed" and " amanda/udp server failing (looping), service
terminated". 
> I have checked all the amanda documentation but no
> lucks so far to solve my problem.

Is the line /etc/inetd.conf correct?  Something like this:

amanda dgram udp wait amanda /usr/local/libexec/amandad amandad


What happens if you start /usr/local/libexec/amandad on the commandline?

It should sit there waiting for 30 seconds and stop.  It should also
create a debug file named /tmp/amanda/amanda.DATETIMESTAMP.debug.

If you typed something the command stops immediatly and logs something
about "socket operation on non-socket", otherwise it logs "timeout"
(Not sure about exact words).


-- 
Paul Bijnens, Xplanation                            Tel  +32 16 397.511
Technologielaan 21 bus 2, B-3001 Leuven, BELGIUM    Fax  +32 16 397.512
http://www.xplanation.com/          email:  Paul.Bijnens AT xplanation DOT com
***********************************************************************
* I think I've got the hang of it now:  exit, ^D, ^C, ^\, ^Z, ^Q, F6, *
* quit,  ZZ, :q, :q!,  M-Z, ^X^C,  logoff, logout, close, bye,  /bye, *
* stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt,  abort,  hangup, *
* PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e,  kill -1 $$,  shutdown, *
* kill -9 1,  Alt-F4,  Ctrl-Alt-Del,  AltGr-NumLock,  Stop-A,  ...    *
* ...  "Are you sure?"  ...   YES   ...   Phew ...   I'm out          *
***********************************************************************



<Prev in Thread] Current Thread [Next in Thread>