--- Begin Message ---

Subject:	Re: backup suddenly not working on server
From:	Jeanne Case <jdcase AT stmarys-ca DOT edu>
To:	Brian Cuttler <brian AT wadsworth DOT org>
Date:	Mon, 04 Apr 2005 13:25:25 -0700

I see on the day it quit working in the /var/log/messages file:

xinetd[13343]: libwrap refused connection to amanda (libwrap=amandad) from 123.456.789.203

This is one of its 2 IP addresses.

I have made sure amanda is in /etc/services
I do not run nis on this host

The output from ldd /usr/local/libexec/amandad is:

libamclient-2.4.4p2.so => /usr/local/lib/libamclient-2.4.4p2.so (0x4001a000)

        libamanda-2.4.4p2.so => /usr/local/lib/libamanda-2.4.4p2.so (0x40021000)
        libm.so.6 => /lib/i686/libm.so.6 (0x40050000)
        libncurses.so.5 => /lib/libncurses.so.5 (0x40073000)
        libnsl.so.1 => /lib/libnsl.so.1 (0x400b9000)
        libc.so.6 => /lib/i686/libc.so.6 (0x400cf000)
        /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)

Suse has xinet.d files, I added the bind = IP option, but it has made no difference. I have kill -HUP 1775 for xinetd services. There are some interesting errors that popped up once I added the bind= statement:

{mem_fault_handler} Address of fault: c
{mem_fault_handler} address is not mapped for object
{general_handler} (17771) Unexpected signal: 11 (Segmentation fault)

So my guess is the bind= statement is not working in any postive way.

-Jeanne


Brian Cuttler wrote:

Sorry Jeanne,

Hvaen't followed your thread, but off the top of my head...

What suggestions did you try... specifically.

services in /etc/services or nis(plus)/ldap ?
service in /etc/inetd.conf (or OS equiv) ?
SIGHUP inetd ?
.amandahosts in services login directory ?
# ldd /usr/libexec/amandad - to make sure all required libraries
                            are present ?
checked error messages in /var/adm/messages or SYSLOG (OS dependent) ?

On Mon, Apr 04, 2005 at 12:33:53PM -0700, Jeanne Case wrote:

I have had amanda running on a server for over a year. It backs up itself and another machine. Suddenly last week it stops backing up itself. I do not recall making any changes on this server. It is a multihomed server running SuSE 9.0.

I did go to the FAQ-o-Matic and tried all the suggestions there, no joy.

The amcheck returns:

WARNING: home2.my.domain: selfcheck request timed out.  Host down?
Client check: 2 hosts checked in 29.919 seconds, 1 problem found

(brought to you by Amanda 2.4.p2)


Yes, /tmp/amanda is writable. Suggestions?

-JD.Case

---
   Brian R Cuttler                 brian.cuttler AT wadsworth DOT org
   Computer Systems Support        (v) 518 486-1697
   Wadsworth Center                (f) 518 473-6384
   NYS Department of Health        Help Desk 518 473-0773

--- End Message ---