Jóhann noticed this: systemd[1]: Assertion 's->state == SERVICE_START || s->state == SERVICE_START_POST' failed at src/service.c:2609, function service_fd_event(). Aborting I found a reproducer: # cat /etc/systemd/system/buggy.service [Unit] Description=buggy [Service] Type=forking PIDFile=/var/run/buggy.pid ExecStart=/bin/sh -c '(sleep 5; echo $$ > /var/run/buggy.pid; sleep 60 ) &' # systemctl start buggy.service & sleep 2 && systemctl daemon-reload The bug is related to the PID file waiting (new in systemd-38 and backported to 37-8).
http://cgit.freedesktop.org/systemd/systemd/commit/?id=3e52541ef51b1004357fbcd4bf863fb955ab83e9 http://koji.fedoraproject.org/koji/taskinfo?taskID=3716425
systemd-37-10.fc16 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/FEDORA-2012-0409/systemd-37-10.fc16
Package systemd-37-10.fc16: * should fix your issue, * was pushed to the Fedora 16 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing systemd-37-10.fc16' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-0409/systemd-37-10.fc16 then log in and leave karma (feedback).
Package systemd-37-11.fc16: * should fix your issue, * was pushed to the Fedora 16 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing systemd-37-11.fc16' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-0409/systemd-37-11.fc16 then log in and leave karma (feedback).
systemd-37-11.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report.