this affects all fedora releases and results in case of having customized watchdogs in alert messages Dec 25 21:05:36 srv-rhsoft haveged[18251]: haveged Stopping due to signal 15 Dec 25 21:05:36 srv-rhsoft systemd[1]: haveged.service: main process exited, code=exited, status=1/FAILURE additionally you should consider Type=simple instead "Type=forking" as it should be done for all services supporting foreground mode, besides less costs at startup this way you do not need any PIDFile and avoid warnings in /var/log/messages that they are not existing - i which maintainers would take a deeper look in systemlogs at all ___________________________________________ Type=simple ExecStart=/usr/sbin/haveged -w 1024 -v 1 --Foreground
Hi, I can change the service type to Simple. However, the main problem appears to be that SIGTERM will cause the program to end with exit code 1: signal(SIGTERM, tidy_exit); static void tidy_exit( /* OUT: nothing */ int signum) /* IN: signal number */ { error_exit("Stopping due to signal %d\n", signum); } static void error_exit(..) { .... exit(1); } I will talk to the upstream to change this. Jirka
Hi, I talked to the upstream. There will be new release soon with fixed exit codes - in case of signal it will be 128+signal for SIGTERM the exit code is 143. systemd has to be notified that exit code 143 indicates success via SuccessExitStatus=143 I will update the service file and pack with the new version of haveged. Service file now looks like this: more /dev/shm/haveged.service [Unit] Description=Entropy Daemon based on the HAVEGE algorithm Documentation=man:haveged(8) http://www.issihosts.com/haveged/ [Service] Type=simple ExecStart=/usr/sbin/haveged -w 1024 -v 1 --Foreground SuccessExitStatus=143 [Install] WantedBy=multi-user.target
thank you very much for the quick and positive feedback, not only in case of the bug itself, also in case of the systemd-improvement!
haveged-1.8-0.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/haveged-1.8-0.fc20
haveged-1.8-0.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/haveged-1.8-0.fc19
Package haveged-1.8-0.fc20: * should fix your issue, * was pushed to the Fedora 20 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing haveged-1.8-0.fc20' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2014-0121/haveged-1.8-0.fc20 then log in and leave karma (feedback).
haveged-1.8-0.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.
haveged-1.8-0.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.