OpenSuse 11.0 problems with Amanda

wjtaylor · 03-31-2009, 09:49 PM

I cannot get my OS 11.0 system to pass amcheck. I installed the package from YAST.

Here's the output

Code:

Tesla:/etc/xinetd.d # su amanda
amanda@Tesla:/etc/xinetd.d> amcheck DailySet1
Amanda Tape Server Host Check
-----------------------------
slot 1: read label `DailySet1-01', date `X'
NOTE: skipping tape-writable test
Tape DailySet1-01 label ok
NOTE: conf info dir /var/lib/amanda/DailySet1/curinfo does not exist
NOTE: it will be created on the next run.
NOTE: index dir /var/lib/amanda/DailySet1/index does not exist
NOTE: it will be created on the next run.
Server check took 0.061 seconds

Amanda Backup Client Hosts Check
--------------------------------
WARNING: Tesla: selfcheck request failed: error sending REQ: send REQ to Tesla.WJT failed: Socket operation on non-socket
Client check: 1 host checked in 0.017 seconds, 1 problem found

(brought to you by Amanda 2.5.2p1)
amanda@Tesla:/etc/xinetd.d>

The logs...

Code:

amanda@Tesla:/tmp/amanda/server/DailySet1> cat amcheck.20090331181829.debug
amcheck: debug 1 pid 10809 ruid 37 euid 0: start at Tue Mar 31 18:18:29 2009
amcheck: debug 1 pid 10809 ruid 37 euid 37: rename at Tue Mar 31 18:18:29 2009
amcheck-clients: time 0.002: security_getdriver(name=BSD) returns 0x7f61c80628a0
amcheck-clients: time 0.002: security_handleinit(handle=0x7f61c80bcf00, driver=0x7f61c80628a0 (BSD))
amcheck-clients: time 0.014: dgram_bind: socket() failed: Address family not supported by protocol
amcheck-clients: time 0.019: dgram_send_addr(addr=0x7f61c80bcf40, dgram=0x7f61c807a4c8)
amcheck-clients: time 0.019: (sockaddr_in6 *)0x7f61c80bcf40 = { 10, 10080, ::ffff:127.0.0.2 }
amcheck-clients: time 0.019: dgram_send_addr: 0x7f61c807a4c8->socket = 0
amcheck-clients: time 0.019: dgram_send_addr: sendto(::ffff:127.0.0.2.10080) failed: Socket operation on non-socket
amcheck-clients: time 0.019: security_seterror(handle=0x7f61c80bcf00, driver=0x7f61c80628a0 (BSD) error=send REQ to Tesla.WJT failed: Socket operation on non-socket)
amcheck-clients: time 0.019: security_seterror(handle=0x7f61c80bcf00, driver=0x7f61c80628a0 (BSD) error=error sending REQ: send REQ to Tesla.WJT failed: Socket operation on non-socket)
amcheck-clients: time 0.019: security_close(handle=0x7f61c80bcf00, driver=0x7f61c80628a0 (BSD))
changer_query: changer return was 25 1
changer_query: searchable = 0
changer_find: looking for NULL changer is searchable = 0
amcheck: time 0.063: pid 10809 finish time Tue Mar 31 18:18:29 2009
amanda@Tesla:/tmp/amanda/server/DailySet1>

xinetd files.... (I've also tried changing the first one to stream/tcp with no luck)

Code:

amanda@Tesla:/etc/xinetd.d> cat amanda
# default: off
# description: Amanda backup client
#
service amanda
{
        socket_type     = dgram
        protocol        = udp
        wait            = yes
        user            = amanda
        group           = disk
        server          = /usr/lib/amanda/amandad
        disable         = no
}

amanda@Tesla:/etc/xinetd.d>

Code:

amanda@Tesla:/etc/xinetd.d> cat amandaidx
# default: off
# description: Amanda backup server with indexing capabilities
#
service amandaidx
{
        socket_type     = stream
        protocol        = tcp
        wait            = no
        user            = amanda
        group           = disk
        server          = /usr/lib/amanda/amindexd
        disable         = no
}

amanda@Tesla:/etc/xinetd.d>

Code:

amanda@Tesla:/etc/xinetd.d> cat amidxtape
# default: off
# description: Amanda backup server with indexing capabilities
#
service amidxtape
{
        socket_type     = stream
        protocol        = tcp
        wait            = no
        user            = amanda
        group           = disk
        server          = /usr/lib/amanda/amidxtaped
        disable         = no
}

amanda@Tesla:/etc/xinetd.d>

Any advice??

Thanks for your help,
WT

choogendyk · 04-01-2009, 09:34 PM

I found a similar post on the Zmanda forums and the answer given was:

Quote:

Your system returns IPv6 address to amanda, but amanda can't use them because you disabled them at the kernel level.

Either, fix your system to not return IPv6 address to amanda
or enable IPv6 in the kernel
or reconfigure amanda with '--without-ipv6'

on another similar thread:

Quote:

Make sure you are using "auth bsdtcp" in your dumtype definition.

and

Quote:

Please take a look at Amanda wiki for trouble shooting this problem.

http://wiki.zmanda.com/index.php/Amc...request_failed

Note: I was specifically searching for the error message you got that included "Socket operation on non-socket." Going to bsdtcp gets around the udp issues, but if it is an IPV6, taking care of that directly solves it as well. The wiki reference is a general troubleshooting page for the various situations where the selfcheck request fails.

Note that if you change your dumptype to include auth bsdtcp, you will need to change your xinetd entry for amanda to stream tcp nowait as well. (And restart xinetd.)

wjtaylor · 04-03-2009, 08:17 AM

Thanks for your reply. I actually read those two posts searching for the same string.

I'm glad you posted it though, because I solved the problem after rereading them. For those of you who are reading this and experiencing the same situation, I've included a fix.

Problem: IPv6 not enabled in kernel

Troubleshooting:
Dispite Yast having a setting in Global Options for Enable IPv6, it appearantly does not work correctly. I checked the modproble files and I don't see all the changes I was expecting to see. I also did not see this feature in the command line version of YAST. So, this told me that this GUI feature might not work.

reference: http://forums.opensuse.org/network-i...6-default.html

So, I tested currently running kernel for IPv6 compatibility with:

test -f /proc/net/if_inet6 && echo "Running kernel is IPv6 ready"

This did nothing and told me that this kernel module was not being loaded at boot, even with "Enable IPv6" checked in YAST.

Resulution/Test:
So, I tried to load the module manually with:

modprobe ipv6

To test if it worked:

lsmod | grep -w 'ipv6' && echo "IPv6 module successfully loaded"

It loaded fine. Sweet! I run the first line again just as a sanity check and it told me my running kernel was IPv6 ready. Still sane, awesome!

I ran amcheck and have moved on to other errors (that were common and covered on the wiki above).

Followup:
So, the only thing I had to do is make sure that IPv6 module gets loaded at boot. That is covered in the refereces below and also where I got the testing info above.

reference: http://tldp.org/HOWTO/Linux+IPv6-HOW...ck-kernel.html

see also: http://forums.opensuse.org/archives/...el-module.html

Good luck,
WT

choogendyk · 04-03-2009, 07:49 PM

Cool. Glad to hear it worked out.