Description of problem: When trying to do amcheck -c on the server, I get a connection refused error message from my Fedora 18 client Version-Release number of selected component (if applicable): amanda-3.3.2-2.fc18.x86_64 How reproducible: Always Steps to Reproduce: 1.Run amcheck -c 'organization name' 2. 3. Actual results: WARNING: guru: selfcheck request failed: Connection refused Expected results: No error message. Additional info: I noticed that amanda on Fedora 18 no longer supplies a file at /etc/xinted.d/amanda. I am at a loss to understand how amanda can possibly work with this file. "systemctl enable amanda.service" also fails.
I started from the xfce respin and then installed the amanda client though yum which brought in the usual list of dependencies. Seeing the same thing with this installation base.
There are some permission issues with amanda-3.3.2-2 which should be fixed in amanda-3.3.2-3, but this is probably not the cause. Amanda is now started by socket activation of systemd. Can you please make sure, that it is started 'systemctl status amanda.socket' and if not 'systemctl start amanda.socket'. If you want to start it automatically after boot 'systemctl enable amanda.socket'.
on the amanda-client machine: [root@x60 amanda]# systemctl stop firewalld.service [root@x60 amanda]# rpm -qa amanda\* amanda-3.3.2-3.fc18.x86_64 amanda-client-3.3.2-3.fc18.x86_64 [root@x60 amanda]# systemctl status amanda.socket amanda.socket - Amanda Activation Socket Loaded: loaded (/usr/lib/systemd/system/amanda.socket; enabled) Active: active (listening) since Mon 2013-01-21 20:42:18 CET; 7min ago Accepted: 0; Connected: 0 Jan 21 20:42:18 x60.pcfe.net systemd[1]: Starting Amanda Activation Socket. Jan 21 20:42:18 x60.pcfe.net systemd[1]: Listening on Amanda Activation Socket. on the amanda-server: -bash-4.1$ amcheck -c HouseNet_Mo-Fr x60 Amanda Backup Client Hosts Check -------------------------------- WARNING: x60: selfcheck request failed: timeout waiting for ACK Client check: 1 host checked in 30.032 seconds. 1 problem found. (brought to you by Amanda 2.6.1p2) FWIW: /var/lib/amanda/.amandahosts and /var/lib/amanda/exclude.gtar were taken from F17 (this was a clean F18 install, not an update) If I tcpdump on the amanda-client machine, I see 21:01:56.831626 IP 192.168.50.250.914 > 192.168.50.15.amanda: UDP, length 131 21:01:56.831685 IP 192.168.50.15 > 192.168.50.250: ICMP 192.168.50.15 udp port amanda unreachable, length 167 21:02:06.842197 IP 192.168.50.250.914 > 192.168.50.15.amanda: UDP, length 131 21:02:06.842250 IP 192.168.50.15 > 192.168.50.250: ICMP 192.168.50.15 udp port amanda unreachable, length 167 21:02:16.849431 IP 192.168.50.250.914 > 192.168.50.15.amanda: UDP, length 131 21:02:16.849485 IP 192.168.50.15 > 192.168.50.250: ICMP 192.168.50.15 udp port amanda unreachable, length 167 Also in /usr/lib/systemd/system/amanda@.service I see -auth=bsdtcp instead of the -auth=bsd I used fine under F17. If I follow http://wiki.zmanda.com/index.php/Selfcheck_request_failed#Clients_are_using_.22bsdtcp.22_authentication_but_server_is_not then this client works. But that is not really what I want. That work-around would require me to either define additional dumptypes or to change all the other clients to bsdtcp auth. Just changing the ExecStart line in /usr/lib/systemd/system/amanda@.service to read bsd instead of bsdtcp did not help. question: what is the correct way to adjust the file so that the amanda-client expects and handles bsd type auth?
Thanks for the info. Using amanda.socket worked fine. Perhaps you should consider adding a README.Fedora to let people know that amanda.socket and not amanda.service should now be used with systemctl.
Patrick can you try these configuration files? https://bugzilla.redhat.com/attachment.cgi?id=523154 https://bugzilla.redhat.com/attachment.cgi?id=523349
(In reply to comment #5) > Patrick can you try these configuration files? > > https://bugzilla.redhat.com/attachment.cgi?id=523154 > https://bugzilla.redhat.com/attachment.cgi?id=523349 With these two in place and after a # systemctl enable amanda-udp.socket ; systemctl start amanda-udp.socket I am able to run amcheck just fine. I'll let you know how the nightly backups go in a day or three.
(In reply to comment #6) > I'll let you know how the nightly backups go in a day or three. Confirm, the backup of two Fedora 18 machines went fine with the config files from comment #5. Thanks.
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
amanda-3.3.3-2.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/amanda-3.3.3-2.fc19
The both unit files were added into amanda package. scm-commit (https://lists.fedoraproject.org/pipermail/scm-commits/Week-of-Mon-20130617/1041505.html) -> MODIFIED
amanda-3.3.2-4.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/amanda-3.3.2-4.fc18
Package amanda-3.3.3-2.fc19: * should fix your issue, * was pushed to the Fedora 19 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing amanda-3.3.3-2.fc19' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-11132/amanda-3.3.3-2.fc19 then log in and leave karma (feedback).
I seem to be doing something wrong with systemd, in the shipped package there is /usr/lib/systemd/system/amanda-udp@.service but I had to rename it to /usr/lib/systemd/system/amanda-udp.socket What part to the systemd docs should I RTFM?
amanda-3.3.2-4.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.
(In reply to Patrick C. F. Ernzer from comment #13) > I seem to be doing something wrong with systemd, in the shipped package > there is /usr/lib/systemd/system/amanda-udp@.service but I had to rename it > to /usr/lib/systemd/system/amanda-udp.socket Not sure what brainfart I had there, works just fine on F20 with; - install amanda-client - enable amanda-client in firewall-config (best to set your interface to the home zone and allow amanda-client in home zone only) - systemctl enable amanda-udp.socket ; systemctl start amanda-udp.socket - SELinux adjustments as per Bug 1043268