Jeff Silverman wrote:
>
> Hi. I have amanda 2.4.1p1 on a RedHat Linux/Intel for the tape host.
> The tape host, spinoza, is also getting backed up and it also runs samba
> so it handles backing up the PCs.
>
> I had a working configuration, and then I added a lot of PCs to the
> disklist file and amanda stopped working, partly anyway. I am not
> worried about freya, spiff, tucker, owlglass, or umtanum. I am very
> worried about spinoza.
>
> I am testing amcheck by running the inetd from a terminal with the -d
> switch, and I see
>
> spinoza!root 506# inetd -d
> ADD : amandaidx proto=tcp, wait.max=0.40, user.group=backup.(null)
^^^^
> builtin=0 server=/usr/local/libexec/amindexd
> ADD : amidxtape proto=tcp, wait.max=0.40, user.group=backup.(null)
^^^^
I don't know if this will solve your problem, but for for amandaidx and
amidxtape the parameter should be "nowait". From your log I see that you
use "wait", which is wrong for these two.
Check the inetd.conf file on spinoza. It should contain:
# amanda backup server with indexing capabilities
#
amandaidx stream tcp nowait amanda /usr/lib/amanda/amindexd
amindexd
amidxtape stream tcp nowait amanda
/usr/lib/amanda/amidxtaped amidxtaped
#
# amanda client
#
amanda dgram udp wait amanda /usr/lib/amanda/amandad
amandad
#
Restart inetd (or send it a HUP signal, "kill -HUP pid") and
try again.
Also check the /etc/services file on spinoza. You should
have
something like:
#
# services for amanda backup software
#
amanda 10080/udp
amandaidx 10082/tcp
amidxtape 10083/tcp
Again, you need only the 1st line for the client.
Further, I may recite John R. Jackson in the chapter about
AMANDA in
O'Reilly's Book "Unix backup and recovery":
---------------
Is there a line in the inetd configuration file on the
client to start
amandad?
Was inetd sent a HUP signal after the
configuration
file was changed?
Are there system log messages from inetd
about amanda
or amandad? For instance, inetd
complains if it cannot look up the AMANDA
services.
Is /tmp/amanda/amandad*debug being
updated?
Is the access time on the amandad
executable (ls -lu)
being updated? If not, inetd is probably not
able to run it, possibly because of an
error in the
inetd configuration file or a permission problem.
Run the amandad program by hand as the
AMANDA user on
the client. It should sit for about 30
seconds, then terminate. Enter the full
path exactly
as it was given to inetd, perhaps by using
copy/paste.
Do not proceed until amcheck is happy with
the
configuration.
----------------------
I hope this helps.
--
Regards
Chris Karakas
Don´t waste your cpu time - crack rc5: http://www.distributed.net
