https://bugzilla.novell.com/show_bug.cgi?id=467365 Summary: amrecover fails with " Socket operation on non-socket" Classification: openSUSE Product: openSUSE 11.0 Version: Final Platform: i686 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: R.Vickers@cs.rhul.ac.uk QAContact: qa@suse.de Found By: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-GB; rv:1.9.0.5) Gecko/2008120121 Firefox/3.0.5 The Amanda backup software suffers from a number of IPV6-related problems. In the past I have always disabled IPV6 in order to get Amanda working, but after upgrading our server to 10.3 the situation seems to have got more complicated. These tests were run with amrecover 2.5.2.1-152.1 running on an 11.0 client, communicating with Amanda 2.5.2.1-46 running on a 10.3 server. In the initial situation ipv6 was not enabled, amd amrecover failed as follows: # amrecover DailyCS -s csnewton -t csnewton -d /dev/amandatape AMRECOVER Version 2.5.2p1. Contacting server on csnewton ... [request failed: error sending REQ: send REQ to csnewton.cs.rhul.ac.uk failed: S ocket operation on non-socket] So after googling I inserted the IPV6 module and tried again: # modprobe -v ipv6 install /bin/true # modprobe -v -C /dev/null ipv6 insmod /lib/modules/2.6.25.18-0.2-default/kernel/net/ipv6/ipv6.ko aspasia# amrecover DailyCS -s csnewton -t csnewton -d /dev/amandatape AMRECOVER Version 2.5.2p1. Contacting server on csnewton ... [could not connect MESG stream: can't connect stream to csnewton.cs.rhul.ac.uk p ort 34281: Resource temporarily unavailable] Some Googling revealed that this bug had been encountered on Redhat systems and could be worked round: # amrecover DailyCS -s csnewton -t csnewton -d /dev/amandatape -o "unreserved-tcp-port=1025,65535" AMRECOVER Version 2.5.2p1. Contacting server on csnewton ... [request failed: timeout waiting for ACK] I had already encountered this problem on the server and knew it could be worked round by deleting the IPV6 interface: # ifconfig eth0 del fe80::230:48ff:fe5a:9ae6/64 # amrecover DailyCS -s csnewton -t csnewton -d /dev/amandatape -o "unrese rved-tcp-port=1025,65535" AMRECOVER Version 2.5.2p1. Contacting server on csnewton ... 220 csnewton AMANDA index server (2.5.2p1) ready. Setting restore date to today (2009-01-19) 200 Working date set to 2009-01-19. 200 Config set to DailyCS. 200 Dump host set to aspasia. Use the setdisk command to choose dump disk to recover amrecover> Success at last! So to get amrecover working you must enable IPV6 globally but disable it at the interface level, and also manually configure a port range. Of course, if we actually required IPV6 to be working then this solution would be unacceptable. Reproducible: Always Steps to Reproduce: 1. Configure an amanda backup server 2. Run amrecover on a client 3. Actual Results: Alarm and despondency Expected Results: Produced happiness and smiles -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.