Failed to start Entropy Daemon after update to OMV 6.0.19

wouterve · 26. März 2022

Today I updated my OMV 6.0.14 installation to 6.0.19. There were some minor errors during the upgrade process (see attached log) but installation finished OK.

After reboot however, my server went into emergency mode with the following errors on the screen:

Code

Failed to start Entropy Daemon based on the HAVEGE algorithm
See systemctl status haveged.service for details

Upon second recoot It did get past this error. I checked the status for the service:

Code

haveged.service - Entropy Daemon based on the HAVEGE algorithm
Loaded: loaded (/lib/systemd/system/haveged.service; enabled; vendor preset: enabled)
Active: failed (Result: signal) since Sat 2022-03-26 08:46:52 CET; 1s ago
Docs: man:haveged(8)
http://www.issihosts.com/haveged/
Process: 4947 ExecStart=/usr/sbin/haveged --Foreground --verbose=1 $DAEMON_ARGS (code=killed, signal=SYS)
Main PID: 4947 (code=killed, signal=SYS)
CPU: 81ms


mrt 26 08:46:52 wouter-lien-naz systemd[1]: haveged.service: Scheduled restart job, restart counter is at 5.
mrt 26 08:46:52 wouter-lien-naz systemd[1]: Stopped Entropy Daemon based on the HAVEGE algorithm.
mrt 26 08:46:52 wouter-lien-naz systemd[1]: haveged.service: Start request repeated too quickly.
mrt 26 08:46:52 wouter-lien-naz systemd[1]: haveged.service: Failed with result 'signal'.
mrt 26 08:46:52 wouter-lien-naz systemd[1]: Failed to start Entropy Daemon based on the HAVEGE algorithm.

Alles anzeigen

Here is the output from syslog:

Code

Mar 26 08:46:51  systemd[1]: haveged.service: Main process exited, code=killed, status=31/SYS
Mar 26 08:46:51  systemd[1]: haveged.service: Failed with result 'signal'.
Mar 26 08:46:51  kernel: [  265.011348] audit: type=1326 audit(1648280811.210:7): auid=4294967295 uid=0 gid=0 ses=4294967295 subj==unconfined pid=4935 comm="haveged" exe="/usr/sbin/haveged" sig=31 arch=40000028 syscall=122 compat=0 ip=0xb6fe3e98 code=0x80000000
Mar 26 08:46:51  systemd[1]: haveged.service: Scheduled restart job, restart counter is at 1.
Mar 26 08:46:51  systemd[1]: haveged.service: Main process exited, code=killed, status=31/SYS
Mar 26 08:46:51  systemd[1]: haveged.service: Failed with result 'signal'.
Mar 26 08:46:51  kernel: [  265.232859] audit: type=1326 audit(1648280811.430:8): auid=4294967295 uid=0 gid=0 ses=4294967295 subj==unconfined pid=4938 comm="haveged" exe="/usr/sbin/haveged" sig=31 arch=40000028 syscall=122 compat=0 ip=0xb6ef8e98 code=0x80000000
Mar 26 08:46:51  systemd[1]: haveged.service: Scheduled restart job, restart counter is at 2.
Mar 26 08:46:51  systemd[1]: haveged.service: Main process exited, code=killed, status=31/SYS
Mar 26 08:46:51  systemd[1]: haveged.service: Failed with result 'signal'.
Mar 26 08:46:51  kernel: [  265.522210] audit: type=1326 audit(1648280811.720:9): auid=4294967295 uid=0 gid=0 ses=4294967295 subj==unconfined pid=4941 comm="haveged" exe="/usr/sbin/haveged" sig=31 arch=40000028 syscall=122 compat=0 ip=0xb6f21e98 code=0x80000000
Mar 26 08:46:51  systemd[1]: haveged.service: Scheduled restart job, restart counter is at 3.
Mar 26 08:46:51  kernel: [  265.732961] audit: type=1326 audit(1648280811.930:10): auid=4294967295 uid=0 gid=0 ses=4294967295 subj==unconfined pid=4944 comm="haveged" exe="/usr/sbin/haveged" sig=31 arch=40000028 syscall=122 compat=0 ip=0xb6f40e98 code=0x80000000
Mar 26 08:46:51  systemd[1]: haveged.service: Main process exited, code=killed, status=31/SYS
Mar 26 08:46:51  systemd[1]: haveged.service: Failed with result 'signal'.
Mar 26 08:46:52  systemd[1]: haveged.service: Scheduled restart job, restart counter is at 4.
Mar 26 08:46:52  kernel: [  265.992026] audit: type=1326 audit(1648280812.190:11): auid=4294967295 uid=0 gid=0 ses=4294967295 subj==unconfined pid=4947 comm="haveged" exe="/usr/sbin/haveged" sig=31 arch=40000028 syscall=122 compat=0 ip=0xb6efce98 code=0x80000000
Mar 26 08:46:52  systemd[1]: haveged.service: Main process exited, code=killed, status=31/SYS
Mar 26 08:46:52  systemd[1]: haveged.service: Failed with result 'signal'.
Mar 26 08:46:52  systemd[1]: haveged.service: Scheduled restart job, restart counter is at 5.
Mar 26 08:46:52  systemd[1]: haveged.service: Start request repeated too quickly.
Mar 26 08:46:52  systemd[1]: haveged.service: Failed with result 'signal'

Alles anzeigen

So basically my system is not working now. What can I do to solve this please?

votdev · 26. März 2022

This has nothing to do with openmediavault itself becasue havegedis not installed and used by OMV.

macom · 26. März 2022

Have a look here:

https://forum.armbian.com/topi…indComment&comment=134876

Proposed solution working for me:

Execute as root these two commands

Code

mkdir -p /etc/systemd/system/haveged.service.d
echo -e '[Service]\nSystemCallFilter=uname' > /etc/systemd/system/haveged.service.d/syscall.conf

wouterve · 26. März 2022

Zitat von macom
Have a look here:
https://forum.armbian.com/topi…indComment&comment=134876

Proposed solution working for me:
Execute as root these two commands
Code
mkdir -p /etc/systemd/system/haveged.service.d
echo -e '[Service]\nSystemCallFilter=uname' > /etc/systemd/system/haveged.service.d/syscall.conf

Thanks! This solved my problem. I'm running OMV on Odroid XU4 so I might be affected by this bug.

Another strange thing I noticed is that sometimes a boot fails as it cannot find my file systems. This happens +- every second reboot. So I'm a bit puzzled what could be wrong with my fstab as some boots work and some other not.

The error I'm receiving is:

Code

Time out waiting for device /dev/disk/by-uuid/...
Dependency failed for File System check on /dev/disk/by-uuid/...

and this for all disks that are attached to my OMV build.

I've readthis warningupon the update of 6.0.16 but AFAIK none of my drives does have a genesys usb adapter.

What could be causing this error or do I better start a new thread for this?

Thanks in advance.

macom · 26. März 2022

Does the boot actually fail or are only the data drives not available?

wouterve · 26. März 2022

Zitat von macom

Does the boot actually fail or are only the data drives not available?

The boot fails: the server is then in emergency mode. But when I reboot after this message, it boot normally without qny errors but the boot after this becomes stuck in emergency mode. It is as if every 2nd reboot fails

macom · 26. März 2022

Do you gracefully shutdown the XU4?

wouterve · 27. März 2022

Zitat von macom

Do you gracefully shutdown the XU4?

Not when it's in emergency mode (there is no keyboard attached to it). Would this make any difference?

macom · 27. März 2022

I would suggest to open a separate thread. Maybe also ask in the Armbian forum

wouterve · 27. März 2022

Ok thanks for your support. I'll open new thread here and if that doesn't work on armbian forums

wouterve · 27. März 2022

I've created a new thread here. I've inspected my journald log and it seems my Atolla USB 3.0 hub is causing some issues.

Jetzt mitmachen!