Hi,
Thanks a lot so far.
David you assumed right. I was not able to get a coredump as only one
thread dies.
I noticed, that on my RHEL 6.7 System I have json-c AND libfastjson
installed in parallel.
As far as I read this is a bad idear and could lead into issues).
Removing it leads to new issues:
a) The latest released Version of liblognorm 1.3 depends on json-c, so
how should only libfastjson work?
b) rsyslog-mmnormalize module seems depends also on json-c !??
c) some other components (not from rsyslog universe) depend also on json-c
Comments?
best regards
Chris
See dependencies here:
----------------------------------
yum remove json-c
Dependencies Resolved
=============================================================================================================================================================
Package Arch Version
Repository
Size
=============================================================================================================================================================
Removing:
json-c x86_64
0.11-12.el6 @rhel6-base-x86_64
140 k
Removing for dependencies:
abrt x86_64
2.0.8-34.el6 @rhel6-base-x86_64
752 k
abrt-addon-ccpp x86_64
2.0.8-34.el6 @rhel6-base-x86_64
192 k
abrt-addon-kerneloops x86_64
2.0.8-34.el6 @rhel6-base-x86_64
28 k
abrt-addon-python x86_64
2.0.8-34.el6 @rhel6-base-x86_64
20 k
abrt-cli x86_64
2.0.8-34.el6 @rhel6-base-x86_64
0.0
abrt-desktop x86_64
2.0.8-34.el6 @rhel6-base-x86_64
0.0
abrt-gui x86_64
2.0.8-34.el6 @rhel6-base-x86_64
221 k
abrt-libs x86_64
2.0.8-34.el6 @rhel6-base-x86_64
28 k
abrt-python x86_64
2.0.8-34.el6 @rhel6-base-x86_64
52 k
abrt-tui x86_64
2.0.8-34.el6 @rhel6-base-x86_64
17 k
firstboot x86_64
1.110.15-1.el6
@anaconda-RedHatEnterpriseLinux-201409260744.x86_64/6.6 650
k
liblognorm1 x86_64
1.1.3-1.el6 @rsyslog_v8
104 k
liblognorm1-utils x86_64
1.1.3-1.el6 @rsyslog_v8
12 k
libreport x86_64
2.0.9-25.el6_7 @rhel6-base-x86_64
1.2 M
libreport-cli x86_64
2.0.9-25.el6_7 @rhel6-base-x86_64
26 k
libreport-compat x86_64
2.0.9-25.el6_7 @rhel6-base-x86_64
7.5 k
libreport-gtk x86_64
2.0.9-25.el6_7 @rhel6-base-x86_64
133 k
libreport-newt x86_64
2.0.9-25.el6_7 @rhel6-base-x86_64
15 k
libreport-plugin-kerneloops x86_64
2.0.9-25.el6_7 @rhel6-base-x86_64
18 k
libreport-plugin-logger x86_64
2.0.9-25.el6_7 @rhel6-base-x86_64
23 k
libreport-plugin-mailx x86_64
2.0.9-25.el6_7 @rhel6-base-x86_64
32 k
libreport-plugin-reportuploader x86_64
2.0.9-25.el6_7 @rhel6-base-x86_64
32 k
libreport-plugin-rhtsupport x86_64
2.0.9-25.el6_7 @rhel6-base-x86_64
79 k
libreport-plugin-ureport x86_64
2.0.9-25.el6_7 @rhel6-base-x86_64
23 k
libreport-python x86_64
2.0.9-25.el6_7 @rhel6-base-x86_64
73 k
python-meh noarch
0.12.1-3.el6
@anaconda-RedHatEnterpriseLinux-201409260744.x86_64/6.6 186
k
rsyslog-mmnormalize x86_64
8.18.0-1.el6 @rsyslog_v8
14 k
Transaction Summary
=============================================================================================================================================================
Remove 28 Package(s)
Installed size: 4.0 M
Is this ok [y/N]: N
----------------------------------
2016-04-20 18:31 GMT+02:00 David Lang <[email protected]>:
> If you can get a coredump, a gdb analysis of the core file is useful
>
> cat gdb.commands
> bt
> bt full
> info threads
> thread apply all bt
> thread apply all bt full
> quit
>
>
>
> gdb rsyslogd corefile <gdb.commands
>
> send the report directly to Rainer rather than the list (as it can contain
> sensitive stuff). Looking at the output of these commands may give you a
> clue as to what functions are triggering the segfault.
>
> I did see a patch for libfastjson that did not make it into a release yet
> that could cause a segfault in cases where a variable doesn't exist.
>
> moving to 8.18 should move you from json-c to libfastjson, and that fixes
> quite a number of known segfaulting issues.
>
> David Lang
>
>
> On Wed, 20 Apr 2016, Christopher Racky wrote:
>
>> Date: Wed, 20 Apr 2016 14:18:25 +0200
>> From: Christopher Racky <[email protected]>
>> Reply-To: rsyslog-users <[email protected]>
>> To: rsyslog-users <[email protected]>
>> Subject: [rsyslog] segfault with rsyslog Version > 8.16.0
>>
>>
>> Hello,
>>
>> Thanks for all your great Support in the past!
>>
>> Today I upgraded from rsyslog 8.16 over 8.17 to 8.18.
>> (As I noticed several Memory leaks in my Environment with arroung 10k
>> logs/sec)
>> I use a Red-Hat 6.7 Server with all latest patches installed.
>>
>> Unfortunately during start of rsyslog I get the following message in
>> kernel ring-buffer.
>> Apr 20 13:15:09 demosrv kernel: rsyslogd[16640]: segfault at
>> 7f3b276229d0 ip 00007f3b2cecb213 sp 00007fff3099bd30 error 4 in
>> libpthread-2.12.so[7f3b2cec3000+17000]
>>
>> This message did not appear with rsyslog 8.16. Buf after an upgrade to
>> 8.17 and with the latest version 8.18 I get this error.
>> Everythings seems to work fine, but whenever I do a restart, I get the
>> mentioned kernel error message.
>>
>>
>> Do you have any idear / hint?
>> How can I debug the issue?
>>
>>
>> My config is quite complex, so I just an excerpt about modules loaded:
>>
>> ---------------------------------------------------------------------------------------------------------
>> Module (load="imuxsock") # provides support for local system logging
>> (e.g. via logger command)
>> Module (load="imklog") # provides kernel logging support (previously
>> done by rklogd)
>> Module (load="impstats" interval="120" severity="7" log.syslog="on"
>> ruleset="pstats")
>> Module (load="imtcp" KeepAlive="on" KeepAlive.Probes="1"
>> KeepAlive.Interval="2" KeepAlive.Time="20" MaxSessions="5000")
>> Module (load="imudp")
>> Module (load="ommysql")
>> Module (load="omudpspoof")
>> Module (load="mmnormalize")
>>
>> # Message Parsers
>> $modload pmlastmsg
>> $modload pmaixforwardedfrom
>> $rulesetparser rsyslog.lastline
>> $rulesetparser rsyslog.aixforwardedfrom
>> $rulesetparser rsyslog.rfc5424
>> $rulesetparser rsyslog.rfc3164
>>
>> ---------------------------------------------------------------------------------------------------------
>>
>>
>> [root@demosrv syslog]# cat /etc/redhat-release
>> Red Hat Enterprise Linux Server release 6.7 (Santiago)
>> [root@demosrv syslog]# yum update
>> Loaded plugins: product-id, refresh-packagekit, security,
>> subscription-manager
>> This system is not registered to Red Hat Subscription Management. You
>> can use subscription-manager to register.
>> Setting up Update Process
>> No Packages marked for Update
>> [root@demosrv syslog]# tail /var/log/messages
>> Apr 20 13:15:01 demosrv rsyslogd: [origin software="rsyslogd"
>> swVersion="8.17.0" x-pid="16640" x-info="http://www.rsyslog.com"]
>> exiting on signal 15.
>> Apr 20 13:15:09 demosrv kernel: rsyslogd[16640]: segfault at
>> 7f3b276229d0 ip 00007f3b2cecb213 sp 00007fff3099bd30 error 4 in
>> libpthread-2.12.so[7f3b2cec3000+17000]
>> Apr 20 13:15:09 demosrv rsyslogd: [origin software="rsyslogd"
>> swVersion="8.17.0" x-pid="28237" x-info="http://www.rsyslog.com"]
>> start
>> Apr 20 14:01:32 demosrv yum[31727]: Updated: rsyslog-8.18.0-1.el6.x86_64
>> Apr 20 14:01:32 demosrv yum[31727]: Updated:
>> rsyslog-udpspoof-8.18.0-1.el6.x86_64
>> Apr 20 14:01:32 demosrv yum[31727]: Updated:
>> rsyslog-mysql-8.18.0-1.el6.x86_64
>> Apr 20 14:01:32 demosrv yum[31727]: Updated:
>> rsyslog-mmnormalize-8.18.0-1.el6.x86_64
>> Apr 20 14:01:32 demosrv yum[31727]: Updated:
>> rsyslog-pmaixforwardedfrom-8.18.0-1.el6.x86_64
>> Apr 20 14:01:33 demosrv rsyslogd: [origin software="rsyslogd"
>> swVersion="8.17.0" x-pid="28237" x-info="http://www.rsyslog.com"]
>> exiting on signal 15.
>> Apr 20 14:01:36 demosrv kernel: rsyslogd[28237]: segfault at
>> 7f943a72f9d0 ip 00007f943ffd8213 sp 00007fff20878110 error 4 in
>> libpthread-2.12.so[7f943ffd0000+17000]
>> Apr 20 14:01:36 demosrv rsyslogd: [origin software="rsyslogd"
>> swVersion="8.18.0" x-pid="31782" x-info="http://www.rsyslog.com"]
>> start
>> Apr 20 14:02:25 demosrv rsyslogd: [origin software="rsyslogd"
>> swVersion="8.18.0" x-pid="31782" x-info="http://www.rsyslog.com"]
>> exiting on signal 15.
>> Apr 20 14:02:26 demosrv kernel: rsyslogd[31782]: segfault at
>> 7fea41ef09d0 ip 00007fea47799213 sp 00007ffda216ff30 error 4 in
>> libpthread-2.12.so[7fea47791000+17000]
>> Apr 20 14:02:26 demosrv rsyslogd: [origin software="rsyslogd"
>> swVersion="8.18.0" x-pid="31897" x-info="http://www.rsyslog.com"]
>> start
>> ------------------------------------------
>>
>> regards
>> Chris
>> _______________________________________________
>> rsyslog mailing list
>> http://lists.adiscon.net/mailman/listinfo/rsyslog
>> http://www.rsyslog.com/professional-services/
>> 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.
>>
> _______________________________________________
> rsyslog mailing list
> http://lists.adiscon.net/mailman/listinfo/rsyslog
> http://www.rsyslog.com/professional-services/
> 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.
_______________________________________________
rsyslog mailing list
http://lists.adiscon.net/mailman/listinfo/rsyslog
http://www.rsyslog.com/professional-services/
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.