[rsyslog] Problems with rsyslog Versions > 8.16 and Thread-Handling
david at lang.hm
Thu Jan 12 12:48:31 CET 2017
is the version you are using linked to json-c or libfastjson?
we know there were thread-safe problems as a result of json-c
On Thu, 12 Jan 2017, Christopher Racky via rsyslog wrote:
> Date: Thu, 12 Jan 2017 12:43:31 +0100
> From: Christopher Racky via rsyslog <rsyslog at lists.adiscon.com>
> To: rsyslog-users <rsyslog at lists.adiscon.com>
> Cc: Christopher Racky <christopher.racky at gmail.com>
> Subject: [rsyslog] Problems with rsyslog Versions > 8.16 and Thread-Handling
> I still have big issues with different Servers running RHEL 6.8 (incl.
> latest updates) and rsyslog > 8.16.
> While 8.16 works fine, all following versions, including 8.24 which
> was released a few days ago leads to problems that results in
> rsyslogd: segfault at 7f9f2910b9d0 ip 00007f9f2e18e213 sp
> 00007ffd3d9fe080 error 4 in libpthread-2.12.so[7f9f2e186000+17000]
> rsyslogd: segfault at 7f991c0789d0 ip 00007f99210fb213 sp
> 00007ffec5155240 error 4 in libpthread-2.12.so[7f99210f3000+17000]
> rsyslogd: segfault at 7f5f695399d0 ip 00007f5f6e5bd213 sp
> 00007ffe4b4da5c0 error 4 in libpthread-2.12.so[7f5f6e5b5000+17000]
> rsyslogd: segfault at 7f519ad269d0 ip 00007f519fdaa213 sp
> 00007ffd22bf2470 error 4 in libpthread-2.12.so[7f519fda2000+17000]
> My hope was that this topic was solved by
> But it was not.
> As problems seems not (directly) related to lookup-table, I guess it
> also has a problem with thread handling.
> Do you have any further idea?
> With single-thread mode problem does not appear and also in lab, I was
> not able to reproduce it.
> But on several production servers the issue occures quite often.
> rsyslog mailing list
> What's up with rsyslog? Follow https://twitter.com/rgerhards
> NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T LIKE THAT.
More information about the rsyslog