On Wednesday 10 December 2008, Jean-Louis Martineau wrote:
>Check firewall
No firewall
>Check xinetd configuration
Unchanged since:
[root@coyote etc]# ls -l xinetd.conf
-rw-r--r-- 1 root root 1001 2008-07-16 04:57 xinetd.conf
And the amanda file in /etc/xinetd.d:
-rw-r--r-- 1 root root 939 2008-01-15 21:41 amanda
>Check system log for error to start amandad
=======
Dec 10 01:15:01 coyote xinetd[4657]: START: amanda pid=7071
from=::ffff:192.168.71.3
Dec 10 01:15:01 coyote xinetd[7071]: FAIL: amanda address
from=::ffff:192.168.71.3
Dec 10 01:15:01 coyote xinetd[4657]: EXIT: amanda status=0 pid=7071
duration=0(sec)
Dec 10 01:15:11 coyote xinetd[4657]: START: amanda pid=7106
from=::ffff:192.168.71.3
Dec 10 01:15:11 coyote xinetd[7106]: FAIL: amanda address
from=::ffff:192.168.71.3
Dec 10 01:15:11 coyote xinetd[4657]: EXIT: amanda status=0 pid=7106
duration=0(sec)
Dec 10 01:15:21 coyote xinetd[4657]: START: amanda pid=7110
from=::ffff:192.168.71.3
Dec 10 01:15:21 coyote xinetd[7110]: FAIL: amanda address
from=::ffff:192.168.71.3
Dec 10 01:15:21 coyote xinetd[4657]: EXIT: amanda status=0 pid=7110
duration=0(sec)
Dec 10 01:15:32 coyote xinetd[4657]: START: amanda pid=7141
from=::ffff:192.168.71.3
Dec 10 01:15:32 coyote xinetd[7141]: FAIL: amanda address
from=::ffff:192.168.71.3
Dec 10 01:15:32 coyote xinetd[4657]: EXIT: amanda status=0 pid=7141
duration=0(sec)
Dec 10 01:15:42 coyote xinetd[4657]: START: amanda pid=7176
from=::ffff:192.168.71.3
Dec 10 01:15:42 coyote xinetd[7176]: FAIL: amanda address
from=::ffff:192.168.71.3
Dec 10 01:15:42 coyote xinetd[4657]: EXIT: amanda status=0 pid=7176
duration=0(sec)
Dec 10 01:15:52 coyote xinetd[4657]: START: amanda pid=7179
from=::ffff:192.168.71.3
Dec 10 01:15:52 coyote xinetd[7179]: FAIL: amanda address
from=::ffff:192.168.71.3
Dec 10 01:15:52 coyote xinetd[4657]: EXIT: amanda status=0 pid=7179
duration=0(sec)
==========
What is this ipv6 stuff anyway? Is this ffff: etc the new
requirement I have to put in my /etc/hosts file?
>Check amandad.*.debug files.
The last one it generated last night is attached. It looks like some ipv6
addressing is being used, but nothing else grabs my eye. I don't have any
ipv6 addresses setup other than localhost, which a fresh FU8 install did.
With a single block in the 192.168.XX. here, and dd-wrt for a firewall, I
see zero reasons to muck with what was a working system.
>Check selfcheck.*.debug files.
Nothing there, but in /tmp/amanda-dbg/server/Daily/
the tail of the last amcheck-date there is:
------
1228889702.247934: amcheck-server: changer: << EXITSTATUS 0
1228889702.247942: amcheck-server: changer: << 5 file:/amandatapes/Dailys/
1228889711.519059: amcheck-clients: dgram_send_addr(addr=0xa01f248,
dgram=0xb7f11aa4)
1228889711.519080: amcheck-clients: (sockaddr_in *)0xa01f248 = { 2, 10080,
192.168.71.3 }
1228889711.519087: amcheck-clients: dgram_send_addr: 0xb7f11aa4->socket = 4
1228889721.569018: amcheck-clients: dgram_send_addr(addr=0xa01f248,
dgram=0xb7f11aa4)
1228889721.569038: amcheck-clients: (sockaddr_in *)0xa01f248 = { 2, 10080,
192.168.71.3 }
1228889721.569045: amcheck-clients: dgram_send_addr: 0xb7f11aa4->socket = 4
1228889731.618962: amcheck-clients: security_seterror(handle=0xa01f228,
driver=0xb7f09ae0 (BSD) error=timeout
waiting for ACK)
1228889731.619000: amcheck-clients: security_close(handle=0xa01f228,
driver=0xb7f09ae0 (BSD))
1228889731.619975: amcheck: pid 7067 finish time Wed Dec 10 01:15:31 2008
--------
And my logs are drowning in cups failure messages too.
----------
Dec 10 08:00:55 coyote automount[2174]: lookup_nss_mount: key ".directory" not
found in map.
Dec 10 08:00:55 coyote automount[2174]: create_udp_client:104: hostname lookup
failed: No such process
Dec 10 08:00:55 coyote automount[2174]: create_tcp_client:318: hostname lookup
failed: No such process
Dec 10 08:00:55 coyote automount[2174]: lookup_mount: exports lookup failed for
.directory
Dec 10 08:12:30 coyote smbd[16983]: [2008/12/10 08:12:30, 0]
printing/print_cups.c:cups_connect(69)
Dec 10 08:12:30 coyote smbd[16983]: Unable to connect to CUPS server
coyote.coyote.den:631 - Success
Dec 10 08:12:30 coyote smbd[22954]: [2008/12/10 08:12:30, 0]
printing/print_cups.c:cups_connect(69)
Dec 10 08:12:30 coyote smbd[22954]: Unable to connect to CUPS server
coyote.coyote.den:631 - Success
Which occured after the cups stuff was updated due to a denial of service.
If you ask me, this is a "denial of service"...
FWIW, FF's home page is localhost:631/printers, and that displays normally.
Right now. But, it has been denying me the ability to setup a new printer
profile for about 10 days now. I'm discussing with Dan Walsh about that.
And I'm a pint low on coffee yet. So I'm no smarter than I was 6 hours ago. :)
>Jean-Louis
>
>Gene Heskett wrote:
>> Greetings;
>>
>> Its borken:
>> [root@coyote amanda-2.6.2alpha-20081209]# su amanda -c "amcheck Daily"
>> Amanda Tape Server Host Check
>> -----------------------------
>> Holding disk /dumps: 360378368 kB disk space available, using 359866368 kB
>> slot 5:read label `Dailys-5', date `20081109151648'.
>> NOTE: skipping tape-writable test
>> Tape Dailys-5 label ok
>> Server check took 0.774 seconds
>>
>> Amanda Backup Client Hosts Check
>> --------------------------------
>> WARNING: coyote: selfcheck request failed: timeout waiting for ACK
>> Client check: 1 host checked in 30.034 seconds. 1 problem found.
>>
>> (brought to you by Amanda 2.6.2alpha-20081209)
>>
>> But, I get the same response from 2.6.2alpha-20081208 too, wth? It worked
>> perfectly here last night.
>>
>> Yumex had just installed updates for awstats, two cups packages, and
>> kdelibs4. I don't see a connection. I used the same ./gh.cf script:
>> =============
>> #!/bin/sh
>> # since I'm always forgetting to su amanda...
>> if [ `whoami` != 'amanda' ]; then
>> echo
>> echo "!!!!!!!!!!!! Warning !!!!!!!!!!!!"
>> echo "Amanda needs to be configured and built by the user amanda,"
>> echo "but must be installed by user root."
>> echo
>> exit 1
>> fi
>> make clean
>> rm -f config.status config.cache
>> ./configure --with-user=amanda \
>> --with-group=disk \
>> --with-owner=amanda \
>> --with-gnu-ld \
>> --prefix=/usr/local \
>> --with-tapedev="FILE:/amandatapes" \
>> --with-debugging=/tmp/amanda-dbg/ \
>> --with-tape-server=coyote \
>> --with-bsdtcp-security --with-amandahosts \
>> --with-configdir=/usr/local/etc/amanda \
>> --with-config=Daily \
>> --with-gnutar=/bin/tar
>> make
>> =============
>> That I have been using for ages.
>>
>> One item I noted, cups was, maybe is also being difficult, and its error
>> messages are showing the ipv6 stuff, but I don't have that setup here.
>>
>> The amcheck-debug logs for just now all end like this:
>> 1228884453.747217: amcheck-server: changer: << 5 file:/amandatapes/Dailys/
>> 1228884462.991055: amcheck-clients: dgram_send_addr(addr=0x958b258,
>> dgram=0xb7ea6aa4)
>> 1228884462.991077: amcheck-clients: (sockaddr_in *)0x958b258 = { 2, 10080,
>> 192.168.71.3 }
>> 1228884462.991083: amcheck-clients: dgram_send_addr: 0xb7ea6aa4->socket =
>> 4 1228884473.001013: amcheck-clients: dgram_send_addr(addr=0x958b258,
>> dgram=0xb7ea6aa4)
>> 1228884473.001034: amcheck-clients: (sockaddr_in *)0x958b258 = { 2, 10080,
>> 192.168.71.3 }
>> 1228884473.001040: amcheck-clients: dgram_send_addr: 0xb7ea6aa4->socket =
>> 4 1228884483.010961: amcheck-clients: security_seterror(handle=0x958b238,
>> driver=0xb7e9eae0 (BSD) error=timeout waiting for ACK)
>> 1228884483.010994: amcheck-clients: security_close(handle=0x958b238,
>> driver=0xb7e9eae0 (BSD))
>> 1228884483.011940: amcheck: pid 4664 finish time Tue Dec 9 23:48:03 2008
>>
>>
>> /home/amanda/.amandahosts hasn't changed in 2 years:
>> -rw------- 1 amanda amanda 417 2006-11-27 19:29 .amandahosts
>>
>> Ideas folks?
--
Cheers, Gene
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
<zpx> it's amazing how "not-broken" debian is compared to slack and rh
amandad.20081209022731.debug
Description: Text document
|
