Bug#858134: marked as done (haveged.service should depend on systemd-tmpfiles-setup.service)
Your message dated Sun, 06 Aug 2017 12:32:08 + with message-id and subject line Bug#858134: fixed in haveged 1.9.1-5+deb9u1 has caused the Debian Bug report #858134, regarding haveged.service should depend on systemd-tmpfiles-setup.service to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 858134: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=858134 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: haveged Version: 1.9.1-5 Severity: important Dear maintainer, Haveged fails to start often (but not always) during boot. Manually starting it later with "systemctl start haveged" is successful. Systemd version is 232-19. Journalctl showed the following error message: systemd[557]: haveged.service: Failed at step NAMESPACE spawning /usr/sbin/haveged: No such file or directory Searching for more information on this issue led to the PrivateTmp option in the service configration file. Setting PrivateTmp=no in haveged.service did avoid the problem on my system. Additionally, I was able to find the likely cause by enabling systemd debug messages with systemd.log_level=debug on the kernel command line. The log is quite long. I've tried to extract the relevant parts: Mar 18 14:29:05 notebook systemd[1]: Reached target Local File Systems. Mar 18 14:29:05 notebook systemd[1]: systemd-tmpfiles-setup.service: Passing 0 fds to service Mar 18 14:29:05 notebook systemd[1]: systemd-tmpfiles-setup.service: About to execute: /bin/systemd-tmpfiles --create --remove --boot --exclude-prefix=/dev Mar 18 14:29:05 notebook systemd[1]: systemd-tmpfiles-setup.service: Forked /bin/systemd-tmpfiles as 554 Mar 18 14:29:05 notebook systemd[1]: systemd-tmpfiles-setup.service: Changed dead -> start Mar 18 14:29:05 notebook systemd[1]: Starting Create Volatile Files and Directories... [...] Mar 18 14:29:05 notebook systemd[1]: haveged.service: ConditionVirtualization=!container succeeded. Mar 18 14:29:05 notebook systemd[555]: nfs-config.service: Executing: /usr/lib/systemd/scripts/nfs-utils_env.sh Mar 18 14:29:05 notebook systemd[1]: haveged.service: Passing 0 fds to service Mar 18 14:29:05 notebook systemd[1]: haveged.service: About to execute: /usr/sbin/haveged --Foreground --verbose=1 $DAEMON_ARGS Mar 18 14:29:05 notebook systemd[1]: haveged.service: Forked /usr/sbin/haveged as 557 Mar 18 14:29:05 notebook systemd[1]: haveged.service: Changed dead -> running Mar 18 14:29:05 notebook systemd[1]: haveged.service: Job haveged.service/start finished, result=done Mar 18 14:29:05 notebook systemd[1]: Started Entropy daemon using the HAVEGE algorithm. [...] Mar 18 14:29:05 notebook systemd[554]: systemd-tmpfiles-setup.service: Executing: /bin/systemd-tmpfiles --create --remove --boot --exclude-prefix=/dev [...] Mar 18 14:29:05 notebook systemd-tmpfiles[554]: Running create action for entry D /tmp Mar 18 14:29:05 notebook systemd-tmpfiles[554]: Found existing directory "/tmp". Mar 18 14:29:05 notebook systemd-tmpfiles[554]: "/tmp" has right mode 41777 Mar 18 14:29:05 notebook systemd-tmpfiles[554]: Running remove action for entry D /tmp Mar 18 14:29:05 notebook systemd-tmpfiles[554]: rm -rf "/tmp" [...] Mar 18 14:29:05 notebook systemd-tmpfiles[554]: Running create action for entry x /tmp/systemd-private-585850ad3e454158ae8ab3f9afe67cd9-* Mar 18 14:29:05 notebook systemd-tmpfiles[554]: Running remove action for entry x /tmp/systemd-private-585850ad3e454158ae8ab3f9afe67cd9-* Mar 18 14:29:05 notebook systemd-tmpfiles[554]: Running create action for entry X /tmp/systemd-private-585850ad3e454158ae8ab3f9afe67cd9-*/tmp Mar 18 14:29:05 notebook systemd-tmpfiles[554]: Running remove action for entry X /tmp/systemd-private-585850ad3e454158ae8ab3f9afe67cd9-*/tmp Mar 18 14:29:05 notebook systemd-tmpfiles[554]: Running create action for entry x /var/tmp/systemd-private-585850ad3e454158ae8ab3f9afe67cd9-* Mar 18 14:29:05 notebook systemd-tmpfiles[554]: Running remove action for entry x /var/tmp/systemd-private-585850ad3e454158ae8ab3f9afe67cd9-* Mar 18 14:29:05 notebook systemd-tmpfiles[554]: Running create action for entry X /var/tmp/systemd-private-585850ad3e454158ae8ab3f9afe67cd9-*/tmp Mar 18 14:29:05 notebook systemd-tmpfiles[554]: Running remove action for entry X /var/tmp/systemd-private-585850ad3e454158ae8ab3f9afe67cd9-*/tmp [...] Mar 18 14:29:05 notebook systemd[1]: Received SIGCHLD from PID 554 (systemd-tmpfile). Mar 18 14:29:05 notebook systemd[1]: Child 554 (systemd-tmpfile) died (code=exited, status=0/SUCCESS) Mar 18 14:29:05 notebook systemd[1]: systemd-tmpfiles-setup.service: Child 5
Bug#858134: marked as done (haveged.service should depend on systemd-tmpfiles-setup.service)
Your message dated Mon, 17 Jul 2017 16:34:46 + with message-id and subject line Bug#858134: fixed in haveged 1.9.1-6 has caused the Debian Bug report #858134, regarding haveged.service should depend on systemd-tmpfiles-setup.service to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 858134: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=858134 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: haveged Version: 1.9.1-5 Severity: important Dear maintainer, Haveged fails to start often (but not always) during boot. Manually starting it later with "systemctl start haveged" is successful. Systemd version is 232-19. Journalctl showed the following error message: systemd[557]: haveged.service: Failed at step NAMESPACE spawning /usr/sbin/haveged: No such file or directory Searching for more information on this issue led to the PrivateTmp option in the service configration file. Setting PrivateTmp=no in haveged.service did avoid the problem on my system. Additionally, I was able to find the likely cause by enabling systemd debug messages with systemd.log_level=debug on the kernel command line. The log is quite long. I've tried to extract the relevant parts: Mar 18 14:29:05 notebook systemd[1]: Reached target Local File Systems. Mar 18 14:29:05 notebook systemd[1]: systemd-tmpfiles-setup.service: Passing 0 fds to service Mar 18 14:29:05 notebook systemd[1]: systemd-tmpfiles-setup.service: About to execute: /bin/systemd-tmpfiles --create --remove --boot --exclude-prefix=/dev Mar 18 14:29:05 notebook systemd[1]: systemd-tmpfiles-setup.service: Forked /bin/systemd-tmpfiles as 554 Mar 18 14:29:05 notebook systemd[1]: systemd-tmpfiles-setup.service: Changed dead -> start Mar 18 14:29:05 notebook systemd[1]: Starting Create Volatile Files and Directories... [...] Mar 18 14:29:05 notebook systemd[1]: haveged.service: ConditionVirtualization=!container succeeded. Mar 18 14:29:05 notebook systemd[555]: nfs-config.service: Executing: /usr/lib/systemd/scripts/nfs-utils_env.sh Mar 18 14:29:05 notebook systemd[1]: haveged.service: Passing 0 fds to service Mar 18 14:29:05 notebook systemd[1]: haveged.service: About to execute: /usr/sbin/haveged --Foreground --verbose=1 $DAEMON_ARGS Mar 18 14:29:05 notebook systemd[1]: haveged.service: Forked /usr/sbin/haveged as 557 Mar 18 14:29:05 notebook systemd[1]: haveged.service: Changed dead -> running Mar 18 14:29:05 notebook systemd[1]: haveged.service: Job haveged.service/start finished, result=done Mar 18 14:29:05 notebook systemd[1]: Started Entropy daemon using the HAVEGE algorithm. [...] Mar 18 14:29:05 notebook systemd[554]: systemd-tmpfiles-setup.service: Executing: /bin/systemd-tmpfiles --create --remove --boot --exclude-prefix=/dev [...] Mar 18 14:29:05 notebook systemd-tmpfiles[554]: Running create action for entry D /tmp Mar 18 14:29:05 notebook systemd-tmpfiles[554]: Found existing directory "/tmp". Mar 18 14:29:05 notebook systemd-tmpfiles[554]: "/tmp" has right mode 41777 Mar 18 14:29:05 notebook systemd-tmpfiles[554]: Running remove action for entry D /tmp Mar 18 14:29:05 notebook systemd-tmpfiles[554]: rm -rf "/tmp" [...] Mar 18 14:29:05 notebook systemd-tmpfiles[554]: Running create action for entry x /tmp/systemd-private-585850ad3e454158ae8ab3f9afe67cd9-* Mar 18 14:29:05 notebook systemd-tmpfiles[554]: Running remove action for entry x /tmp/systemd-private-585850ad3e454158ae8ab3f9afe67cd9-* Mar 18 14:29:05 notebook systemd-tmpfiles[554]: Running create action for entry X /tmp/systemd-private-585850ad3e454158ae8ab3f9afe67cd9-*/tmp Mar 18 14:29:05 notebook systemd-tmpfiles[554]: Running remove action for entry X /tmp/systemd-private-585850ad3e454158ae8ab3f9afe67cd9-*/tmp Mar 18 14:29:05 notebook systemd-tmpfiles[554]: Running create action for entry x /var/tmp/systemd-private-585850ad3e454158ae8ab3f9afe67cd9-* Mar 18 14:29:05 notebook systemd-tmpfiles[554]: Running remove action for entry x /var/tmp/systemd-private-585850ad3e454158ae8ab3f9afe67cd9-* Mar 18 14:29:05 notebook systemd-tmpfiles[554]: Running create action for entry X /var/tmp/systemd-private-585850ad3e454158ae8ab3f9afe67cd9-*/tmp Mar 18 14:29:05 notebook systemd-tmpfiles[554]: Running remove action for entry X /var/tmp/systemd-private-585850ad3e454158ae8ab3f9afe67cd9-*/tmp [...] Mar 18 14:29:05 notebook systemd[1]: Received SIGCHLD from PID 554 (systemd-tmpfile). Mar 18 14:29:05 notebook systemd[1]: Child 554 (systemd-tmpfile) died (code=exited, status=0/SUCCESS) Mar 18 14:29:05 notebook systemd[1]: systemd-tmpfiles-setup.service: Child 554 bel
