[Syslog-ng-maintainers] Bug#913754: Info received (Bug#913754: syslog-ng hangs in getrandom(2) on boot)

[Kókai Péter]

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 <
owner at 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 <syslog-ng-maintainers at alioth-lists.debian.net>
>
> If you wish to submit further information on this problem, please
> send it to 913754 at bugs.debian.org.
>
> Please do not send mail to owner at 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 owner at bugs.debian.org with problems
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/syslog-ng-maintainers/attachments/20181115/0d7b6fdb/attachment.html>