All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] syslog-ng test does not work due to lack of random numbers
Date: Fri, 21 Jun 2019 21:41:30 +0200	[thread overview]
Message-ID: <20190621214130.1074b702@windsurf> (raw)

Hello,

The syslog-ng runtime test is no longer working:

  https://gitlab.com/buildroot.org/buildroot/-/jobs/237108732

I had a look, and the problem is that syslog-ng is stuck when starting,
waiting for random numbers. strace shows:

[pid    65] open("/dev/random", O_RDONLY|O_LARGEFILE) = 6
[pid    65] _newselect(7, [6], NULL, NULL, NULL

And then nothing.

Adding haveged to the configuration would have been an option, but
haveged is started as S21haveged, while syslog-ng is started as
S01syslog-ng, so obviously, this won't help.

What should we do ?

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

             reply	other threads:[~2019-06-21 19:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-21 19:41 Thomas Petazzoni [this message]
2019-07-29  2:21 ` [Buildroot] syslog-ng test does not work due to lack of random numbers Ricardo Martincoski

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190621214130.1074b702@windsurf \
    --to=thomas.petazzoni@bootlin.com \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.