PDA

View Full Version : Fedora 12 and IPv6 in zmanda client



marcus
May 23rd, 2010, 11:54 PM
Hi,

I have been using Amanda for some time (version 2.5) very successfully. Recently I added a Fedora 12 server, with the default amanda client packages. amcheck is ok but the dumps on this server are failing. It appears that the Amanda 2.6 client on the Fedora server is trying to use IPv6:



1274682932.734191: amandad: (sockaddr_in6 *)0xa1c1f0 = { 10, 708, ::ffff:192.168.1.30 }
1274682932.734224: amandad: received ACK pkt:
<<<<<
>>>>>
1274682962.761545: amandad: stream_accept: timeout after 30 seconds
1274682962.761680: amandad: security_stream_seterr(0x1e602a0, can't accept new stream connection: No such file or directory)
1274682962.761703: amandad: stream 0 accept failed: unknown protocol error


IPv6 is disabled on the F12 server.

I have reviewed other forum posts without finding anything obvious other than a reference to the similar log issues. Aany advise/guidance would be appreciated

Mark

marcus
May 24th, 2010, 12:21 AM
Also, it looks like it is receiving an IPv6 request from the backup server:


1274685200.528075: amandad: dgram_send_addr(addr=0x1ab6698, dgram=0x15a204)
1274685200.528095: amandad: (sockaddr_in6 *)0x1ab6698 = { 10, 659, ::ffff:192.168.1.30 }
1274685200.528117: amandad: dgram_send_addr: 0x15a204->socket = 0
1274685200.550495: amandad: dgram_recv(dgram=0x15a204, timeout=0, fromaddr=0x16a1f0)
1274685200.550592: amandad: (sockaddr_in6 *)0x16a1f0 = { 10, 659, ::ffff:192.168.1.30 }
1274685200.550624: amandad: received ACK pkt:

Is that a correct interpretation?

marcus
May 24th, 2010, 07:02 AM
ipv6 disabled - same error:


1274709335.431000: amandad: bind_portrange2: Try port 40760: Available - Address already in use
1274709335.436772: amandad: bind_portrange2: Try port 40761: Available - Address already in use
1274709335.442871: amandad: bind_portrange2: Try port 40762: Available - Success
1274709335.442951: amandad: stream_server: waiting for connection: 0.0.0.0.40762
1274709335.442991: amandad: sending REP pkt:
<<<<<
CONNECT DATA 40760 MESG 40761 INDEX 40762
OPTIONS features=ffffffff9ffeffffffff00;
>>>>>
1274709335.443018: amandad: dgram_send_addr(addr=0x1b19e08, dgram=0xcfc204)
1274709335.443035: amandad: (sockaddr_in *)0x1b19e08 = { 2, 755, 192.168.1.30 }
1274709335.443053: amandad: dgram_send_addr: 0xcfc204->socket = 0
1274709335.474525: amandad: dgram_recv(dgram=0xcfc204, timeout=0, fromaddr=0xd0c1f0)
1274709335.474622: amandad: (sockaddr_in *)0xd0c1f0 = { 2, 755, 192.168.1.30 }
1274709335.474656: amandad: received ACK pkt:
<<<<<
>>>>>
1274709365.504826: amandad: stream_accept: timeout after 30 seconds
1274709365.504956: amandad: security_stream_seterr(0x1b2e2a0, can't accept new stream connection: No such file or directory)
1274709365.504979: amandad: stream 0 accept failed: unknown protocol error

marcus
May 29th, 2010, 08:06 PM
Ok - solved my own problem - it is always a lot more simple than you think... Bad DNS entry - found the reference in the dumper debug files on the server.