PDA

View Full Version : cannot run amrecover "Socket operation on non-socket"



tim1234
May 6th, 2011, 12:16 AM
[root@bu1 recovery]# amrecover sos
AMRECOVER Version 2.5.2p1. Contacting server on localhost ...
[request failed: error sending REQ: send REQ to localhost.localdomain failed: Socket operation on non-socket]

Does anyone have any ideas here? I can't understand why it can't contact the amanda server, the services are enabled and xinetd is running:

[root@bu1 recovery]# chkconfig --list | grep am
amandaserver: on
amandaclient: on

tim1234
May 6th, 2011, 02:05 AM
Here's the full log file:

amrecover: debug 1 pid 30550 ruid 0 euid 0: start at Fri May 6 09:07:18 2011
Could not open conf file "/etc/amanda/amanda-client.conf": No such file or direc
tory
Could not open conf file "/etc/amanda/sos/amanda-client.conf": No such file or d
irectory
amrecover: debug 1 pid 30550 ruid 0 euid 0: rename at Fri May 6 09:07:18 2011
amrecover: time 0.006: security_getdriver(name=bsd) returns 0x33e3c0
amrecover: time 0.006: security_handleinit(handle=0x8a5a4b0, driver=0x33e3c0 (BS
D))
amrecover: time 0.010: dgram_bind: socket() failed: Address family not supported
by protocol
amrecover: time 0.010: dgram_send_addr(addr=0x8a5a4d0, dgram=0x350544)
amrecover: time 0.010: (sockaddr_in6 *)0x8a5a4d0 = { 10, 10080, ::ffff:127.0.0.1
}
amrecover: time 0.010: dgram_send_addr: 0x350544->socket = 0
amrecover: time 0.010: dgram_send_addr: sendto(::ffff:127.0.0.1.10080) failed: S
ocket operation on non-socket
amrecover: time 0.010: security_seterror(handle=0x8a5a4b0, driver=0x33e3c0 (BSD)
error=send REQ to localhost.localdomain failed: Socket operation on non-socket)
amrecover: time 0.010: security_seterror(handle=0x8a5a4b0, driver=0x33e3c0 (BSD)
error=error sending REQ: send REQ to localhost.localdomain failed: Socket opera
tion on non-socket)
amrecover: time 0.010: security_close(handle=0x8a5a4b0, driver=0x33e3c0 (BSD))

martineau
May 6th, 2011, 04:22 AM
It try to use an IPV6 but it is not supported, I don't know why.
Try newer amanda version, many ipv6 bug are fixed.

tim1234
May 6th, 2011, 07:04 AM
Yep, re-enabling IPv6 on the backup server fixed it