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
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
On 02/14/2006 02:25 AM, Kevin Till wrote:
*Assume all outgoing packets are accepted/allowed.*
For amdump to work, you need to open up:
backup client : 10080(udp), a small range of tcp ports for data
transfer e.g. 11000:11030 (recompile amanda with
--with-tcpportrange=11000,11030)
For
Hi Paul Bijnes
Was the UDP also to be recompiled --with-udpportrange=11000,11030 thus
the same port range as tcp.
Cheers
On Tue, 2006-02-14 at 08:19 +, chuck.amadi wrote:
email message attachment (Re: WARNING: server.my.co.uk: selfcheck
request timed out. Host down? thisis a private IP
On 02/14/2006 10:11 AM, Chuck Amadi Systems Administrator wrote:
Hi Paul Bijnes
Was the UDP also to be recompiled --with-udpportrange=11000,11030 thus
the same port range as tcp.
no, the only UDP connection is the one to 10080. But do allow
the reply packet: in iptables, this is
Hi I have re compiled amanda client on the server that sits outside of
my LAN with the following port range. --with-udpportrange=1100,11030
Thus you stating that it must be a system udp port range i.e 1023
If So I have Unassigned range -f 1001-1009 So I would use this when I re
compile a udp
10.788 seconds
Amanda Backup Client Hosts Check
WARNING: server.my.co.uk: selfcheck request timed out. Host down?
Client check: 4 hosts checked in 29.328 seconds, 1 problem found
--
Unix/ Linux Systems Administrator
Chuck Amadi
The Surgical Material Testing
Amanda Backup Client Hosts Check
WARNING: server.my.co.uk: selfcheck request timed out. Host down?
Client check: 4 hosts checked in 29.328 seconds, 1 problem found
--
Unix/ Linux Systems Administrator
Chuck Amadi
The Surgical Material Testing Laboratory
Chuck Amadi Systems Administrator wrote:
Hi List
I had a look on the amanda client less /tmp/amanda
less amandad.20060213153537.debug
Here is the debug report:
Amanda 2.4 REQ HANDLE 003-E0990808 SEQ 1139841004
SECURITY USER amanda
SERVICE noop
OPTIONS features=feff9ffe0f;
10.788 seconds
Amanda Backup Client Hosts Check
WARNING: server.my.co.uk: selfcheck request timed out. Host down?
Client check: 4 hosts checked in 29.328 seconds, 1 problem found
Hi List I have had a read and digest of the following.
Chapter 22. How
Kevin Till wrote:
Chuck Amadi Systems Administrator wrote:
Hi List
I had a look on the amanda client less /tmp/amanda
less amandad.20060213153537.debug
Here is the debug report:
Amanda 2.4 REQ HANDLE 003-E0990808 SEQ 1139841004
SECURITY USER amanda
SERVICE noop
OPTIONS
chuck.amadi wrote:
Cheers I did google this But I am using ipchains.
iptables replaces ipchains. ipchains is pretty much obsolete now, I
would upgrade to iptables.
Are there any examples for me to look at.
the basic idea should be the same.
*Assume all outgoing packets are
On Monday 13 February 2006 20:10, chuck.amadi wrote:
Kevin Till wrote:
Chuck Amadi Systems Administrator wrote:
Hi List
I had a look on the amanda client less /tmp/amanda
less amandad.20060213153537.debug
Here is the debug report:
Amanda 2.4 REQ HANDLE 003-E0990808 SEQ 1139841004
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
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
kenai
.
. (server check ok)
.
Amanda Backup Client Hosts Check
WARNING: kenai.chemie.fu-berlin.de: selfcheck request timed out. Host down?
Relevant parts of my .../kenai/amanda.conf file are:
--
tpchanger chg-disk
tapedev
Yes this was the debug file resulting from the "start manually and wait30 seconds" . As yet I have no debug file produced from inetd.Paul Bijnens [EMAIL PROTECTED] wrote:
shoaib r wrote: This is the /tmp/amanda/amandad.20051005130850.debug file on the CLIENT server (bkpclient): amandad: debug 1
shoaib r wrote:
Yes this was the debug file resulting from the start manually and wait
30 seconds . As yet I have no debug file produced from inetd.
Then I would conclude that you have a problem with your inetd configuration.
--
Paul Bijnens, XplanationTel +32 16
Fair enough, I'll check again.
f.y.i I ran a snoop from the client (bkpclient) whilst running an "amcheck -c daily" on the server (tapesvr) and this is what I got:
tapesvr - bkpclient UDP D=10080 S=980 LEN=125bkpclient - tapesvr ICMP Destination unreachable (UDP port 10080 unreachable)tapesvr -
Hi folks
I've been trying to get Amanda to be able to query the one backup client host that I have with no luck. I've been thru all the tech pages with no progress yet.
Am I missing something?
My .amandahosts file has the FQDN and I've only got one line specified for the client as a test in the
On Wed, Oct 05, 2005 at 07:53:26AM -0400, Scott R. Burns enlightened us:
Is the error report reporting the FQDN or a shorter name. Try putting the
name it is reporting in the .amandahosts.
If it was a problem with .amandahosts, it would most likely be returning a
Permission Denied from Host
shoaib r wrote:
I've been trying to get Amanda to be able to query the one backup client
host that I have with no luck. I've been thru all the tech pages with no
progress yet.
Am I missing something?
We miss the exact error messages. :-)
My .amandahosts file has the FQDN and I've only
Thanks for the responses so far folks
Ok. I have 2 hosts tapesrv and bkpclient The error message is:
+ running on tapesvr +
$ amcheck -c daily
Amanda Backup Client Hosts CheckWARNING: tapesvr.b.c.uk: selfcheck request timed out. Host down?Client
shoaib r wrote:
Thanks for the responses so far folks
Ok. I have 2 hosts tapesrv and bkpclient The error message is:
+ running on tapesvr +
$ amcheck -c daily
Amanda Backup Client Hosts Check
WARNING: tapesvr.b.c.uk: selfcheck request timed
and bkpclient The error message is: + running on tapesvr + $ amcheck -c daily Amanda Backup Client Hosts Check WARNING: tapesvr.b.c.uk: selfcheck request timed out. Host down? Client check: 2 hosts checked in 30.072 seconds, 1 problem found (brought to you
shoaib r wrote:
+ running on tapesvr +
$ amcheck -c daily
Amanda Backup Client Hosts Check
WARNING: tapesvr.b.c.uk: selfcheck request timed out. Host down?
Client check: 2 hosts checked in 30.072 seconds, 1
: time 30.006: pid 7021 finish time Wed Oct 5 13:09:20 2005Alexander Jolk [EMAIL PROTECTED] wrote:
shoaib r wrote: sorry Alexander My mistake. As I'm working on a gov't project, I had to change the hostnames for aliases for the amanda mailing list. I basically vut and paste the wrong alias. Here
I've checked there are definately no firewalls between. Also both servers are connected to the same switch.Alexander Jolk [EMAIL PROTECTED] wrote:
shoaib r wrote: This is the /tmp/amanda/amandad.20051005130850.debug file on the CLIENT server (bkpclient):[...] amandad: time 30.005: dgram_recv:
shoaib r wrote:
This is the /tmp/amanda/amandad.20051005130850.debug file on the CLIENT
server (bkpclient):
amandad: debug 1 pid 7021 ruid 198 euid 198: start at Wed Oct 5
13:08:50 2005
amandad: version 2.4.5
...
amandad: time 30.005: dgram_recv: timeout after 30 seconds
Was this the
anyone have any ideas?
When I run the following
server:/usr/lib/amanda # su amanda -c /usr/sbin/amcheck -c DailySet1
Amanda Backup Client Hosts Check
WARNING: server.domain.co.uk: selfcheck request timed out. Host down?
Client check: 1 host checked in 30.003
WARNING: server.domain.co.uk: selfcheck request timed out. Host down?
Client check: 1 host checked in 30.003 seconds, 1 problem found
As I am back to this - going backwards. I have read and digested the doc's
but this is now getting frustrating .
My /var/log/messages info as below
Chuck Amadi wrote:
server:/usr/lib/amanda # su amanda -c /usr/sbin/amcheck -c DailySet1
Amanda Backup Client Hosts Check
WARNING: server.domain.co.uk: selfcheck request timed out. Host down?
Client check: 1 host checked in 30.003 seconds, 1 problem found
And now
/amcheck -c DailySet1
Amanda Backup Client Hosts Check
WARNING: server.domain.co.uk: selfcheck request timed out. Host down?
Client check: 1 host checked in 30.003 seconds, 1 problem found
And now do you have messages in /tmp/amanda? Could you cite them
Chuck Amadi wrote:
amandad: time 29.996: dgram_recv: timeout after 30 seconds
amandad: error receiving message: timeout
amandad: time 29.996: error receiving message: timeout
amandad: time 29.996: pid 26781 finish time Tue May 17 13:20:13 2005
It would appear that the UDP packets for communication
Hi I did and it's working I had used the wrong path where my tar was
located.
Cheers
Chuck
On Tue, 2005-05-10 at 17:42 +0200, Stefan G. Weichinger wrote:
Hi, Chuck,
on Dienstag, 10. Mai 2005 at 15:57 you wrote to amanda-users:
CA Here's my advance I will sort this alot out as it's self
timed
out. Host down?
Any other areas to checkover I have gone through this with a fine tooth
comb.
Cheers
--
Unix/ Linux Systems Administrator
The Surgical Material Testing Laboratory (SMTL),
Princess of Wales Hospital
Coity Road
Bridgend,
United Kingdom, CF31 1RQ.
Tel: +44 1656 752820
On Tue, May 10, 2005 at 12:52:32PM +0100, Chuck Amadi enlightened us:
Also in /var/lib/amanda/.amandahosts I have my client
setup as below
#localhost amanda
server.domain.co.uk /etc comp-root-tar
This is wrong. you've put a disklist entry in amandahosts. amandahosts
should contain host
Hi, Chuck,
on Dienstag, 10. Mai 2005 at 13:52 you wrote to amanda-users:
CA Hi I added the files amanda and amandaix to /etc/xinetd.d
CA enable running chkconfig -s xinetd 345 and run /etc/init/xinet.d restart
CA shutdown SuSE internal firewall.
CA server:~ # netstat -a | grep -i amanda
CA tcp
I got a bit further
I had forgot to add -
server.domain.co.uk root as well as server.domain.co.uk amanda.
Here's my advance I will sort this alot out as it's self explanatory.
Amanda Tape Server Host Check
-
Holding disk /dumps/amanda: 137244996 KB disk space
Hi, Chuck,
on Dienstag, 10. Mai 2005 at 15:57 you wrote to amanda-users:
CA Here's my advance I will sort this alot out as it's self explanatory.
and
CA Amanda Backup Client Hosts Check
CA
CA ERROR: server.domain.co.uk: [GNUTAR program not available]
Install
Hosts Check
WARNING: server.domain.co.uk: selfcheck request timed out. Host down?
Client check: 1 host checked in 30.002 seconds, 1 problem found
I assume that I my tape server cant see the client which is the same
machine.
I have checked and I have got in the /etc
: server.domain.co.uk: selfcheck request timed
out. Host down?
Any Ideas relating to my Client being down.
--
Unix/ Linux Systems Administrator
The Surgical Material Testing Laboratory (SMTL),
Princess of Wales Hospital
Coity Road
Bridgend,
United Kingdom, CF31 1RQ.
Tel: +44 1656 752820
Fax
*:amandaidx (LISTEN)
server:~ #
Also in /var/lib/amanda/.amandahosts I have my client
#localhost amanda
server.domain.co.uk /etc comp-root-tar
But I still get WARNING: server.domain.co.uk: selfcheck request timed
out. Host down?
Any Ideas relating to my Client being down
check took 0.013 seconds
Amanda Backup Client Hosts Check
WARNING: server.domain.co.uk: selfcheck request timed out. Host down?
Client check: 1 host checked in 30.002 seconds, 1 problem found
Have I got to create a file in /etc/xinit.d/amidxtape
As I haven't got
Hosts Check
WARNING: server.domain.co.uk: selfcheck request timed out. Host down?
Client check: 1 host checked in 30.002 seconds, 1 problem found
Have I got to create a file in /etc/xinit.d/amidxtape
Only on the server, not on all the clients.
As I
WARNING: snap1: selfcheck request timed out. Host down?
WARNING: wins4: selfcheck request timed out. Host down?
Client check: 3 hosts checked in 29.156 seconds, 2 problems found
The disklist:
snap1 //snap1/iss/ samba
wins4 //wins4/software/ samba
sun10 /var/www/ comp-user-tar
On Thu, 11 Mar 2004 at 1:40pm, Tim Krieglstein wrote
The log of amcheck -c looks like this:
Amanda Backup Client Hosts Check
WARNING: snap1: selfcheck request timed out. Host down?
WARNING: wins4: selfcheck request timed out. Host down?
Client check: 3
Hi Joshua
The client in your disklist (the first column) for 'doze boxes backed up
via samba needs to be a *nix box with smbclient installed. When amanda
contacts the *nix box, that box will then initiate the smbclient
connection to the 'doze box.
Thanks for the hint. It did the trick.
On Sun, Dec 21, 2003 at 12:47:24PM -, Dean Pullen wrote:
Thanks for your interest and replys guys, I think we're getting closer to a solution
[I hope].
I'm using SuSE 8.2 (but using the amanda rpm from SuSE 9.0) - which I believe uses
xinetd.
Not that I know the difference. I'm
Ok back at work...
There seems to be no xinetd or inetd messages during startup (I performed a
dmesg dmesg.txt and searched for xinetd/inetd).
Is it worth trying to install xinetd from the supplied SuSE rpms?
Note: The guy who first configured these machines has put various networking
scripts
Just a quick note.
Looking at the SuSE manuals, it appears SuSE 8.2 uses xinetd (whereas 8.1
uses inetd).
Which makes me wonder why it doesn't appear in the start up log.
Dean.
On Monday 22 December 2003 05:01, Dean Pullen wrote:
Ok back at work...
There seems to be no xinetd or inetd messages during startup (I
performed a dmesg dmesg.txt and searched for xinetd/inetd).
Is it worth trying to install xinetd from the supplied SuSE rpms?
Note: The guy who first
On Monday 22 December 2003 05:36, Dean Pullen wrote:
Just a quick note.
Looking at the SuSE manuals, it appears SuSE 8.2 uses xinetd
(whereas 8.1 uses inetd).
Which makes me wonder why it doesn't appear in the start up log.
Dean.
Humm, it sure should. Do you have, in /etc/rc(your runlevel as
-Original Message-
From: Gene Heskett [mailto:[EMAIL PROTECTED]
Sent: 22 December 2003 11:03
To: Dean Pullen; [EMAIL PROTECTED]
Subject: Re: WARNING: database01: selfcheck request timed out. Host down?
On Monday 22 December 2003 05:36, Dean Pullen wrote:
Just a quick note.
Looking
Performing an xinted from command line gives me this in my
/var/log/messages:
Dec 22 13:20:14 database01 xinetd[1716]: Reading included configuration
file: /etc/xinetd.d/amanda [line=26]
Dec 22 13:20:14 database01 xinetd[1716]: Reading included configuration
file: /etc/xinetd.d/amandaidx
Doing this:
# /etc/init.d/xinetd start
Produces this:
# Starting INET services. (xinetd) failed
And by the way the end of the log states:
Dec 22 13:39:38 database01 xinetd[1909]: 1909 {init_services} no services.
Exiting...
Wooo hooo!!
# Amanda Backup Client Hosts Check
#
# Client check: 1 host checked in 0.072 seconds, 0 problems found
after much fiddling...and a manual execution of xinetd
How do I go about booting xinetd at startup? The link in rc3.d doesn't seem
to load
Oh well it seems to be coming up now on reboot, link seems to be working
suddenly...
Well all I can say is thank you very much for all the advice guys: Frank,
Josh, Jon and especially Gene.
I'm sure something else will crop up, but until then, happy
Christmas/holidays and many many many thanks
On Monday 22 December 2003 08:12, Dean Pullen wrote:
[...]
Gene,
Well there was no link in any of the rcX.d directories. I tried
adding one to rc3.d but xinetd still does not print anything on
startup.
Dean
Ok, now my problem is in not knowing which runlevel is the full run
but without x
On Monday 22 December 2003 08:17, Dean Pullen wrote:
Performing an xinted from command line gives me this in my
/var/log/messages:
Dec 22 13:20:14 database01 xinetd[1716]: Reading included
configuration file: /etc/xinetd.d/amanda [line=26]
Dec 22 13:20:14 database01 xinetd[1716]: Reading
On Monday 22 December 2003 08:36, Dean Pullen wrote:
Doing this:
# /etc/init.d/xinetd start
Produces this:
# Starting INET services. (xinetd)
failed
And by the way the end of the log states:
Dec 22 13:39:38 database01 xinetd[1909]: 1909 {init_services} no
On Monday 22 December 2003 08:57, Dean Pullen wrote:
Wooo hooo!!
# Amanda Backup Client Hosts Check
#
# Client check: 1 host checked in 0.072 seconds, 0 problems found
after much fiddling...and a manual execution of xinetd
How do I go about booting xinetd
Thanks for your interest and replys guys, I think we're getting closer to a solution
[I hope].
I'm using SuSE 8.2 (but using the amanda rpm from SuSE 9.0) - which I believe uses
xinetd.
Not that I know the difference. I'm afraid I'm a bit of a newbie in all areas, so
please bare with me.
On Sunday 21 December 2003 07:47, Dean Pullen wrote:
Thanks for your interest and replys guys, I think we're getting
closer to a solution [I hope].
I'm using SuSE 8.2 (but using the amanda rpm from SuSE 9.0) - which
I believe uses xinetd. Not that I know the difference. I'm afraid
I'm a bit of
On Sunday 21 December 2003 07:47, Dean Pullen wrote:
Thanks for your interest and replys guys, I think we're getting
closer to a solution [I hope].
I'm using SuSE 8.2 (but using the amanda rpm from SuSE 9.0) - which
I believe uses xinetd. Not that I know the difference. I'm afraid
I'm a bit of
I did have the FQDN in the hosts file, then tried IP and just machine name on its own.
Still no difference.
Surely if amandad isn't running (which I think I've concluded from looking through the
running processes and the fact that nothing appears in /tmp/amanda after startup),
then I need to
This .amandahosts file only needs to be configured on the machine to be backed up
(client) as opposed to the machine backing up (server) yes?
Dean.
On Sunday 21 December 2003 12:43, Dean Pullen wrote:
I did have the FQDN in the hosts file, then tried IP and just
machine name on its own. Still no difference.
Surely if amandad isn't running (which I think I've concluded from
looking through the running processes and the fact that nothing
--On Sunday, December 21, 2003 17:48:59 + Dean Pullen [EMAIL PROTECTED] wrote:
This .amandahosts file only needs to be configured on the machine to be backed up
(client) as opposed to the machine backing up (server) yes?
Dean.
Technically, yes, but if the server is also a client
-- In [EMAIL PROTECTED], Gene Heskett [EMAIL PROTECTED] wrote:
On Sunday 21 December 2003 12:43, Dean Pullen wrote:
I did have the FQDN in the hosts file, then tried IP and just
machine name on its own. Still no difference.
Surely if amandad isn't running (which I think I've concluded from
--On Sunday, December 21, 2003 17:43:21 + Dean Pullen [EMAIL PROTECTED] wrote:
I did have the FQDN in the hosts file, then tried IP and just machine name on its
own. Still no difference.
Surely if amandad isn't running (which I think I've concluded from looking through
the running
--- In [EMAIL PROTECTED], Frank Smith [EMAIL PROTECTED] wrote:
--On Sunday, December 21, 2003 17:43:21 + Dean Pullen [EMAIL PROTECTED] wrote:
I did have the FQDN in the hosts file, then tried IP and just machine name on its
own. Still no difference.
Surely if amandad isn't
On Sunday 21 December 2003 13:02, Frank Smith wrote:
--On Sunday, December 21, 2003 17:43:21 + Dean Pullen
[EMAIL PROTECTED] wrote:
I did have the FQDN in the hosts file, then tried IP and just
machine name on its own. Still no difference.
Surely if amandad isn't running (which I think
On Sunday 21 December 2003 13:09, Dean Pullen wrote:
-- In [EMAIL PROTECTED], Gene Heskett [EMAIL PROTECTED]
wrote:
On Sunday 21 December 2003 12:43, Dean Pullen wrote:
I did have the FQDN in the hosts file, then tried IP and just
machine name on its own. Still no difference.
Surely if
On Sunday 21 December 2003 13:26, Dean Pullen wrote:
--- In [EMAIL PROTECTED], Frank Smith [EMAIL PROTECTED] wrote:
--On Sunday, December 21, 2003 17:43:21 + Dean Pullen
[EMAIL PROTECTED] wrote:
I did have the FQDN in the hosts file, then tried IP and just
machine name on its own. Still
On Sunday 21 December 2003 13:26, Dean Pullen wrote:
--- In [EMAIL PROTECTED], Frank Smith [EMAIL PROTECTED] wrote:
--On Sunday, December 21, 2003 17:43:21 + Dean Pullen
[EMAIL PROTECTED] wrote:
I did have the FQDN in the hosts file, then tried IP and just
machine name on its own. Still
Hi.
Having recently setup Amanda I'm having the following
problem.
Performing an amcheck gives:
WARNING: database01: selfcheck request timed out. Host
down?
Originally I thought this was a shorewall [firewall] problem
as it reported that it was rejecting packets on port 10080
On Saturday 20 December 2003 04:33, Dean Pullen wrote:
Hi.
Having recently setup Amanda I'm having the following problem.
Performing an amcheck gives:
WARNING: database01: selfcheck request timed out. Host down?
Originally I thought this was a shorewall [firewall] problem
PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dean Pullen
Sent: 20 December 2003 09:33
To: [EMAIL PROTECTED]
Subject: WARNING: database01:
selfcheck request timed out. Host down?
Hi.
Having recently setup Amanda I'm having the following
problem.
Performing an amcheck gives:
WARNING
On Saturday 20 December 2003 07:11, Dean Pullen wrote:
I'm not actually getting any debug files in /tmp/amanda on my client
machine (database01).
Does this probably mean amandad isn't being run on startup?
If I manually try to start amandad a debug file appears, so I
believe all the directory
On Sat, 20 Dec 2003 at 3:54pm, Dean Pullen wrote
Here is my amandad line in /etc/inetd.conf:
amanda dgram udp waitamanda /usr/lib/amanda/amandad amandad
I would strongly suspect that SuSE uses xinetd, not inetd. Look at the
entries Gene posted.
--
Joshua Baker-LePain
On Saturday 20 December 2003 23:48, Joshua Baker-LePain wrote:
On Sat, 20 Dec 2003 at 3:54pm, Dean Pullen wrote
Here is my amandad line in /etc/inetd.conf:
amanda dgram udp waitamanda /usr/lib/amanda/amandad
amandad
I would strongly suspect that SuSE uses xinetd, not inetd. Look
Hi,
We have had Amanda running for a while now - just recently we re-booted our
server and are getting the following when AMCHECK is run - have I missed
something.
WARNING: dilmom: selfcheck request timed out. Host down?
Client check: 1 host checked in 30.005 seconds, 1 problem found
On Tue, 20 Nov 2001 at 12:41pm, Rafe Thayer wrote
I've been trying to configure an amanda client on a Sun box. When I do an
amcheck the server checks out fine, but I get this warning from the
client:
WARNING: al-bundy.cs.ucla.edu: selfcheck request timed out. Host down?
I've attached
|
| WARNING: localhost: selfcheck request timed out. Host down?
| Client check: 1 host checked in 30.007 seconds, 1 problem found
|
| (brought to you by Amanda 2.4.2p2)
\-
I've checked the inetd.conf, and I
Hi Folks,
I've been trying to configure an amanda client on a Sun box. When I do an
amcheck the server checks out fine, but I get this warning from the
client:
WARNING: al-bundy.cs.ucla.edu: selfcheck request timed out. Host down?
I've attached the contents of the amandad.xxx.debug file from
At 12:58 15.04.02 -0400, Jon LaBadie [EMAIL PROTECTED] wrote:
amanda prefers real host names, both in the .amandahosts and in the disklist.
Try to avoid localhost.
OK, done. Now, the FQDN is set. But the error is the same.
I may be wrong, but I think the .amandahost file is supposed to be in
: localhost: selfcheck request timed out. Host down?
| Client check: 1 host checked in 30.007 seconds, 1 problem found
|
| (brought to you by Amanda 2.4.2p2)
\-
I've checked the inetd.conf, and I think, that the amanda.conf in
/etc
Axel Schaefer [mailto:[EMAIL PROTECTED]] wrote:
The .amandahosts (in var/lib/amanda) shows this:
amanda@ll11:~ less .amandahosts
localhost amanda
localhost root
One of the standard recommendations is to never use 'localhost' -- use the
FQDN...
This might not solve your problem, but it's
Scenario:
Solaris 2.7 and 2.8 Amanda 2.4.2p2
Ran amcheck of backup config (total of 28 hosts) and initially 10 hosts
failed so I HUP'd the inetd on all of the hosts again and then only 2
failed. Ran a netstat -a|grep amanda and saw that the ports are
listening. Ran the amcheck again and
... 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.
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
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
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]
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
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
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
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
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
[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
1 - 100 of 110 matches
Mail list logo
