Bug#913754: syslog-ng hangs in getrandom(2) on boot
Hi, Péter.
On Thu, Nov 15, 2018 at 08:33:13AM +0100, Kókai Péter wrote:
>Hello,
>Which was the previous syslog-ng version ?
The version 3.13.2-5 was installed 25 Oct, and according to boot logs
previous version was free from this bug. As far as I understand
contents of /var/log/dpkg.log, those lines
2018-10-25 13:06:19 status half-installed syslog-ng:all 3.13.2-4.1
2018-10-25 13:06:20 status unpacked syslog-ng:all 3.13.2-5
mean that version 3.13.2-4.1 was upgraded to 3.13.2-5.
>--
>Kokan
>On Wed, 14 Nov 2018 at 21:21 Eugene Berdnikov <[1]b...@protva.ru> wrote:
>
> Package: syslog-ng
> Version: 3.13.2-5
> Severity: minor
>
> On boot start of syslog-ng as daemon from /etc/init.d (SysV-init)
> leads to hangup of boot process for several minutes. Strace shows
> that delay caused by getrandom(2) syscall:
>
> 1501 22:44:00
>
> getrandom("\x74\x78\x56\x35\x28\xad\x52\xd2\xcb\x51\xb1\x30\xc7\x67\x14\x26\x01\xa4\x2d\xa0\x30\x1d\xad\x09\x9e\xe3\x2c\x4e\x07\x55\x0d\x29",
> 32, 0) = 32 <322.583360>
>
> Got with "strace -Tt", means reading of 32 random bytes tooks 322
> seconds.
> This is expectable: on boot system has no enоuph entropy, so this
> syscall
> blocks until entropy is collected by kernel from device drivers.
>
> Previous versions of syslog-ng do not hang.
> --
> Eugene Berdnikov
>
> References
>
>Visible links
>1. mailto:b...@protva.ru
--
Eugene Berdnikov
Bug#913754: Info received (Bug#913754: syslog-ng hangs in getrandom(2) on boot)
Hello,
I've injected a getrandom implementation with infinite loop, so I could
simulate your case(the syslog-ng core does not).
I tested on master and found two modules http and riemann that called
getrandom when those shared objects were loaded (they are dynamically
loaded), when I removed those libs, syslog-ng could started.
Does your libcurl and rieman-c version changed ? Does also removing those
libs (those libs are stored under ${install_prefix}/lib/syslog-ng/) allow
you to boot (not suggesting to do that, just to verify that those modules
are causing the issues for you as well).
--
Kokan
On Thu, 15 Nov 2018 at 08:36 Debian Bug Tracking System <
ow...@bugs.debian.org> wrote:
> Thank you for the additional information you have supplied regarding
> this Bug report.
>
> This is an automatically generated reply to let you know your message
> has been received.
>
> Your message is being forwarded to the package maintainers and other
> interested parties for their attention; they will reply in due course.
>
> Your message has been sent to the package maintainer(s):
> syslog-ng maintainers
>
> If you wish to submit further information on this problem, please
> send it to 913...@bugs.debian.org.
>
> Please do not send mail to ow...@bugs.debian.org unless you wish
> to report a problem with the Bug-tracking system.
>
> --
> 913754: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913754
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems
>
Bug#913754: syslog-ng hangs in getrandom(2) on boot
Hello,
Which was the previous syslog-ng version ?
--
Kokan
On Wed, 14 Nov 2018 at 21:21 Eugene Berdnikov wrote:
> Package: syslog-ng
> Version: 3.13.2-5
> Severity: minor
>
> On boot start of syslog-ng as daemon from /etc/init.d (SysV-init)
> leads to hangup of boot process for several minutes. Strace shows
> that delay caused by getrandom(2) syscall:
>
> 1501 22:44:00
> getrandom("\x74\x78\x56\x35\x28\xad\x52\xd2\xcb\x51\xb1\x30\xc7\x67\x14\x26\x01\xa4\x2d\xa0\x30\x1d\xad\x09\x9e\xe3\x2c\x4e\x07\x55\x0d\x29",
> 32, 0) = 32 <322.583360>
>
> Got with "strace -Tt", means reading of 32 random bytes tooks 322 seconds.
> This is expectable: on boot system has no enоuph entropy, so this syscall
> blocks until entropy is collected by kernel from device drivers.
>
> Previous versions of syslog-ng do not hang.
> --
> Eugene Berdnikov
>
>
Bug#913754: syslog-ng hangs in getrandom(2) on boot
Package: syslog-ng
Version: 3.13.2-5
Severity: minor
On boot start of syslog-ng as daemon from /etc/init.d (SysV-init)
leads to hangup of boot process for several minutes. Strace shows
that delay caused by getrandom(2) syscall:
1501 22:44:00
getrandom("\x74\x78\x56\x35\x28\xad\x52\xd2\xcb\x51\xb1\x30\xc7\x67\x14\x26\x01\xa4\x2d\xa0\x30\x1d\xad\x09\x9e\xe3\x2c\x4e\x07\x55\x0d\x29",
32, 0) = 32 <322.583360>
Got with "strace -Tt", means reading of 32 random bytes tooks 322 seconds.
This is expectable: on boot system has no enоuph entropy, so this syscall
blocks until entropy is collected by kernel from device drivers.
Previous versions of syslog-ng do not hang.
--
Eugene Berdnikov
