Chris,
Thank you for catching that mistake, which I think I have propogated
over many machines.
Unfortunately, that isn't the source of my problems.
spinoza!root 554# more /tmp/amanda/amandad.debug
amandad: debug 1 pid 13822 ruid 500 euid 500 start time Sun Oct 29 13:26:01
2000
amandad: version 2.4.1p1
amandad: build: VERSION="Amanda-2.4.1p1"
amandad: BUILT_DATE="Wed Aug 9 17:09:57 PDT 2000"
amandad: BUILT_MACH="Linux spinoza 2.2.14-5.0smp #1 SMP Tue Mar 7
21:01:40 EST 2000 i686 unknown"
amandad: CC="gcc"
amandad: paths: bindir="/g/rcs/sw/pkgs/amanda-2.4.1p1.client/bin"
amandad: sbindir="/g/rcs/sw/pkgs/amanda-2.4.1p1.client/sbin"
amandad: libexecdir="/g/rcs/sw/pkgs/amanda-2.4.1p1.client/libexec"
amandad: mandir="/g/rcs/sw/pkgs/amanda-2.4.1p1.client/man"
amandad: CONFIG_DIR="/g/rcs/sw/pkgs/amanda-2.4.1p1.client/etc/amanda"
amandad: DEV_PREFIX="/dev/" RDEV_PREFIX="/dev/"
amandad: SAMBA_CLIENT="/g/rcs/sw/bin/smbclient"
amandad: GNUTAR="/g/rcs/sw/bin/tar"
amandad: COMPRESS_PATH="/g/rcs/sw/bin/gzip"
amandad: UNCOMPRESS_PATH="/g/rcs/sw/bin/gzip"
amandad: MAILER="/usr/bin/Mail"
amandad:
listed_incr_dir="/g/rcs/sw/pkgs/amanda-2.4.1p1.client/var/amanda/gnutar-lists"
amandad: defs: DEFAULT_SERVER="spinoza" DEFAULT_CONFIG="DailySet1"
amandad: DEFAULT_TAPE_SERVER="spinoza"
amandad: DEFAULT_TAPE_DEVICE="/dev/null" HAVE_MMAP HAVE_SYSVSHM
amandad: LOCKING=POSIX_FCNTL SETPGRP_VOID DEBUG_CODE BSD_SECURITY
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: error receiving message: timeout
spinoza!root 555# more /tmp/amanda/selfcheck.debug
selfcheck: debug 1 pid 13823 ruid 500 euid 500 start time Sun Oct 29 13:26:01
2000
/g/rcs/sw/pkgs/amanda-2.4.1p1.client/libexec/selfcheck: version 2.4.1p1
checking disk /home: device /home: OK
checking disk /var: device /var: OK
checking disk /usr: device /usr: OK
checking disk /: device /: OK
selfcheck: pid 13823 finish time Sun Oct 29 13:26:44 2000
spinoza!root 556#
While I generated these, I ran a little monitoring script:
while [ date ]; do ps -ax | fgrep amand ; date; sleep 10 ; done
and it shows clearly that 15 amandads and 3 client selfchecks are running.
One of them times out. Why?
My next experiment is to increase netusage from 1800 to 5000 Kbps - I have a
100 MBit/sec conncetion and I want to get the backups done faster anyway, so
I can justify it on those grounds.
Again, many thanks,
Jeff
Chris Karakas wrote:
> 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
--
Jeff Silverman, sysadmin for the Research Computing Systems (RCS)
University of Washington, School of Engineering, Electrical Engineering Dept.
Box 352500, Seattle, WA, 98125-2500 FAX: (206) 221-5264 Phone (206) 543-9378
[EMAIL PROTECTED] http://rcs.ee.washington.edu/~jeffs
