Fixed
Created: Apr 6, 2015
Updated: Dec 3, 2018
Resolved Date: Apr 29, 2015
Found In Version: 6.0.0.16
Fix Version: 6.0.0.20
Severity: Standard
Applicable for: Wind River Linux 6
Component/s: Userspace
Our customer encountered rsyslog segmentation fault which was occurred when log rotate was occurred with heavy load. The backtrace is as follows:
(gdb) bt
#0 0x000000394020a214 in pthread_mutex_lock () from /lib64/libpthread.so.0
#1 0x0000000000454394 in AddRef (pThis=0x0) at prop.c:135
#2 0x00000000004357fe in MsgSetRcvFrom (pThis=0x7f0f281b7490, new=0x0)
at msg.c:2248
#3 0x00007f0f399d301a in SubmitMsg (
pRcv=0x7f0f280008c0 "<157>Apr 1 13:32:36 ovs-vswitchd[1002]: type=OFPIT_APPLY_ACTIONS, action:oxm_hasmask=1, oxm_value=0x0000000000200001, oxm_mask=0x00000000007f0001_id=11, command=ADD, idle_timeout=0, hard_timeout=0"...,
lenRcv=77, pLstn=0x7f0f39c32d60 <listeners>, cred=0x7f0f38fb7cc0,
ts=0x7f0f38fb7ca0) at imuxsock.c:928
#4 0x00007f0f399d32ed in readSocket (pLstn=0x7f0f39c32d60 <listeners>)
at imuxsock.c:1011
This problem was fixed upstream version of rsyslog. Our customer confirmed that version 7.4.6 of rsyslog does not reproduce the problem.
According to the customer's analysis, following patch fixes the problem.
https://github.com/rsyslog/rsyslog
commit 9a775051f7373176c6e54bee1110965342dd41ad
Author: Rainer Gerhards <rgerhards@adiscon.com>
Date: Mon Oct 28 12:56:02 2013 +0100
bugfix: potential abort during HUP
This could happen when one of imklog, imzmq3, imkmsg, impstats,
imjournal, or imuxsock were under heavy load during a HUP.
closes: http://bugzilla.adiscon.com/show_bug.cgi?id=489
Thanks to Guy Rozendorn for reporting the problem and Peval Levhshin for
his analysis.
