Re: on OpenRD "client" ( arch = armv5tel ) Upgraded from Buster to Bullseye and haveged stoped working.

["Rick Thomas" <rick.thomas@pobox.com>]

On Sat, Mar 27, 2021, at 1:07 PM, Vagrant Cascadian wrote:
> On 2021-03-14, Rick Thomas wrote:
> > I recently updated my OpenRD "client" ( arch = armv5tel ) from Buster to Bullseye and now haveged crashes.
> >
> > $ sudo service haveged status
> > * 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 2021-03-13 05:06:23 PST; 19h ago
> >        Docs: man:haveged(8)
> >              http://www.issihosts.com/haveged/
> >     Process: 1610 ExecStart=/usr/sbin/haveged --Foreground --verbose=1 $DAEMON_ARGS (code=killed, signal=SYS)
> >    Main PID: 1610 (code=killed, signal=SYS)
> >         CPU: 247ms
> >
> > Mar 13 05:06:23 client systemd[1]: haveged.service: Scheduled restart job, restart counter is at 5.
> > Mar 13 05:06:23 client systemd[1]: Stopped Entropy Daemon based on the HAVEGE algorithm.
> > Mar 13 05:06:23 client systemd[1]: haveged.service: Start request repeated too quickly.
> > Mar 13 05:06:23 client systemd[1]: haveged.service: Failed with result 'signal'.
> > Mar 13 05:06:23 client systemd[1]: Failed to start Entropy Daemon based on the HAVEGE algorithm.
> 
> Wild guess here, but maybe try the workaround from:
> 
>   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866306#59
> 
> e.g. pass --data=16 (or maybe some other value) to haveged.

Thanks for taking a look at this!   Unfortunately, it doesn't seem to work.
Here's what I did to try it:

I changed /etc/default/haveged as follows --
    < #DAEMON_ARGS=""
    ---
    > DAEMON_ARGS="--data=16"

Then as root did
    service haveged restart
and
    service haveged status

Results same as above.

I also tried --
    < #DAEMON_ARGS=""
    ---
    > DAEMON_ARGS="--data=16 --inst=16"

which does not seem to work, either.

Interestingly, running haveged in the foreground, without any cache size hints, seems to work fine:

    root@client:~# haveged -n 2048 -f - > /tmp/sample
    haveged: command socket is listening at fd 3
    Writing 2 K byte output to stdout
    root@client:~# ls -l /tmp/sample
    -rw-r--r-- 1 root root 2048 Mar 31 00:15 /tmp/sample

Rick