Today, I installed havaged to my Arch Linux System (rolling release, systemd).
# systemctl start haveged
is supposed to start the daemon but that just wouldn't work. This is what the log had to say:
systemd[3916]: haveged.service: Failed at step STDIN spawning /usr/bin/haveged: No such file or directory
systemd[1]: haveged.service: Main process exited, code=exited, status=208/STDIN
systemd[1]: haveged.service: Unit entered failed state.
systemd[1]: haveged.service: Failed with result 'exit-code'.
The first error message in the log is wrong. /usr/bin/haveged
does exist, of course. I even tried removing the package and reinstalling it but nothing helped, the daemon just could not be started properly. I even tried to restart systemd using systemctl daemon-reload
but to no avail.
In the end, I rebooted the system and - voilà - haveged can be properly started.
Why was this reboot necessary? Was there anything I could have done differently to avoid this reboot?
Update: The content of the unit file:
$ /usr/lib/systemd/system/haveged.service
[Unit]
Description=Entropy Harvesting Daemon
Documentation=man:haveged(8)
[Service]
ExecStart=/usr/bin/haveged -F -w 1024 -v 1
SuccessExitStatus=143
[Install]
WantedBy=multi-user.target