Description of problem: munin-asyncd needs munin-node to properly run. Maybe systemctl knows how to do this? munin-asyncd should be launched in background. Maybe systemctl knows how to do this? Also, in the systemctl service file, the pid file is the same as the one from munin-node. But I don't know if this matters. Version-Release number of selected component (if applicable): munin-node-2.0.11.1-1.fc18.noarch munin-async-2.0.11.1-1.fc18.noarch munin-common-2.0.11.1-1.fc18.noarch How reproducible: always Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
munin-2.0.11.1-2.el5 has been submitted as an update for Fedora EPEL 5. https://admin.fedoraproject.org/updates/munin-2.0.11.1-2.el5
munin-2.0.11.1-2.el6 has been submitted as an update for Fedora EPEL 6. https://admin.fedoraproject.org/updates/munin-2.0.11.1-2.el6
munin-2.0.11.1-2.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/munin-2.0.11.1-2.fc17
munin-2.0.11.1-2.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/munin-2.0.11.1-2.fc18
I didn't see anything in this update that fixes the service files. I was referring to this: 1. currently munin-asyncd could be started before munin-node, which will fail because it can't connect to localhost port 4949 2. doing "systemctl start munin-asyncd" is killed after a timeout because munin-asyncd doesn't go in background. 3. in /usr/lib/systemd/system/munin-asyncd.service we have: PIDFile=/var/run/munin/munin-node.pid
Really? that's odd. $ git log -n 1 -p munin-asyncd.service diff --git a/munin-asyncd.service b/munin-asyncd.service index adfdf55..b3e8a0d 100644 --- a/munin-asyncd.service +++ b/munin-asyncd.service @@ -1,7 +1,8 @@ [Unit] Description=Munin Async Server. Documentation=man:munin-node -After=network.target +Requires=munin-node.service +After=network.target munin-node.service [Service] Type=forking After applying the update, it should wait until node starts up.
Sorry about that, I read the file only between the lines it seems. If "Type=forking" is not working for me, can I debug it somehow? My result: # systemctl status munin-asyncd | more munin-asyncd.service - Munin Async Server. Loaded: loaded (/usr/lib/systemd/system/munin-asyncd.service; enabled) Active: failed (Result: timeout) since Fri 2013-03-01 23:50:37 EET; 18 min ago Docs: man:munin-node Process: 827 ExecStart=/usr/sbin/munin-asyncd & (code=killed, signal=TE RM) Mar 02 00:49:07 wikivpn.mindsoft.com systemd[1]: Starting Munin Async Server.... Mar 01 23:50:37 wikivpn.mindsoft.com systemd[1]: munin-asyncd.service operation timed out. Terminating. Mar 01 23:50:37 wikivpn.mindsoft.com systemd[1]: Failed to start Munin Async Ser ver.. Mar 01 23:50:37 wikivpn.mindsoft.com systemd[1]: Unit munin-asyncd.service enter ed failed state
Package munin-2.0.11.1-2.fc18: * should fix your issue, * was pushed to the Fedora 18 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing munin-2.0.11.1-2.fc18' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-3199/munin-2.0.11.1-2.fc18 then log in and leave karma (feedback).
# yum update munin\* --enablerepo=updates-testing munin-async-2.0.11.1-2.fc18.noarch Edit /lib/systemd/system/munin-asyncd.service, [Service] Type=simple ExecStart=/usr/sbin/munin-asyncd PrivateTmp=true Leave [Unit] and [Install] sections as they were, but modify [Service] so it looks like the above. # systemctl --system daemon-reload # systemctl start munin-asyncd # systemctl status munin-asyncd Does it work correctly for you? (Seems to startup ok here, and appears to be less messy than making Type=forking happy)
Type=simple works for me.
munin-2.0.11.1-2.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.
munin-2.0.11.1-2.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.
munin-2.0.11.1-2.el6 has been pushed to the Fedora EPEL 6 stable repository. If problems still persist, please make note of it in this bug report.
munin-2.0.11.1-2.el5 has been pushed to the Fedora EPEL 5 stable repository. If problems still persist, please make note of it in this bug report.
munin-2.0.12-2.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/munin-2.0.12-2.fc18
munin-2.0.12-2.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/munin-2.0.12-2.fc17
munin-2.0.12-2.el6 has been submitted as an update for Fedora EPEL 6. https://admin.fedoraproject.org/updates/munin-2.0.12-2.el6
munin-2.0.12-2.el5 has been submitted as an update for Fedora EPEL 5. https://admin.fedoraproject.org/updates/munin-2.0.12-2.el5
munin-2.0.12-2.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.
munin-2.0.12-2.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.
munin-2.0.12-2.el5 has been pushed to the Fedora EPEL 5 stable repository. If problems still persist, please make note of it in this bug report.
munin-2.0.12-2.el6 has been pushed to the Fedora EPEL 6 stable repository. If problems still persist, please make note of it in this bug report.