Ubuntu
rsyslog package

rsyslog SEGFAULT

Bug #1097920 reported by medic on 2013-01-09

This bug affects 3 people

Affects		Status	Importance	Assigned to	Milestone
	rsyslog (Ubuntu)	Confirmed	Undecided	Unassigned

Bug Description

(gdb) c
Continuing.

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fc40669c700 (LWP 12468)]
0x00007fc40770cbba in hash () from /usr/lib/rsyslog/imuxsock.so
(gdb) bt
#0 0x00007fc40770cbba in hash () from /usr/lib/rsyslog/imuxsock.so
#1 0x00007fc40770ce35 in hashtable_search () from /usr/lib/rsyslog/imuxsock.so
#2 0x00007fc4076e4205 in ?? () from /usr/lib/rsyslog/imuxsock.so
#3 0x00007fc4076e48f4 in ?? () from /usr/lib/rsyslog/imuxsock.so
#4 0x00000000004397e6 in ?? ()
#5 0x00007fc40850fe9a in start_thread (arg=0x7fc40669c700) at pthread_create.c:308
#6 0x00007fc407e30cbd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#7 0x0000000000000000 in ?? ()
(gdb)

[2024589.279051] init: rsyslog main process ended, respawning
[2024589.537860] init: rsyslog main process (16703) killed by SEGV signal
[2024589.537890] init: rsyslog main process ended, respawning
[2024589.576948] init: rsyslog main process (16717) killed by SEGV signal
[2024589.576973] init: rsyslog main process ended, respawning
[2024589.610687] init: rsyslog main process (16728) killed by SEGV signal
[2024589.610749] init: rsyslog main process ended, respawning
[2024589.647149] init: rsyslog main process (16739) killed by SEGV signal
[2024589.647193] init: rsyslog respawning too fast, stopped

ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: rsyslog 5.8.6-1ubuntu9.1
ProcVersionSignature: Ubuntu 3.5.0-20.31-generic 3.5.7.1
Uname: Linux 3.5.0-20-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.6.1-0ubuntu9
Architecture: amd64
Date: Wed Jan 9 21:10:27 2013
MarkForUpload: True
ProcEnviron:
TERM=xterm
SHELL=/bin/bash
PATH=(custom, no user)
LANG=en_US.UTF-8
XDG_RUNTIME_DIR=<set>
SourcePackage: rsyslog
UpgradeStatus: Upgraded to quantal on 2012-11-20 (50 days ago)
mtime.conffile..etc.logrotate.d.rsyslog: 2009-11-02T17:12:16.656036
mtime.conffile..etc.rsyslog.conf: 2012-06-01T12:07:37.874075

Tags:

Revision history for this message

medic (medic123) wrote on 2013-01-09:

Dependencies.txt Edit (3.2 KiB, text/plain; charset="utf-8")
modified.conffile..etc.logrotate.d.rsyslog.txt Edit (516 bytes, text/plain; charset="utf-8")
modified.conffile..etc.rsyslog.conf.txt Edit (1.3 KiB, text/plain; charset="utf-8")

Revision history for this message

medic (medic123) wrote on 2013-01-09:

2892.027091010:7ffff633b700: file to log to: /dev/tty8
2892.027095560:7ffff633b700: write to stream, pData->pStrm 0x679510, lenBuf 66
2892.027100215:7ffff633b700: action 0x679b40 call returned -2121
2892.027105135:7ffff633b700: strm 0x679510: file 11(tty8) flush, buflen 66
2892.027117355:7ffff633b700: strm 0x679510: file 11 write wrote 66 bytes
2892.027123425:7ffff633b700: Action 0x679b40 transitioned to state: rdy
2892.027128445:7ffff633b700: ruleset: get iRet 0 from rule.ProcessMsg()
2892.027133026:7ffff633b700: ruleset.ProcessMsg() returns 0
2892.027137756:7ffff633b700: regular consumer finished, iret=0, szlog 0 sz phys 1
2892.027142871:7ffff633b700: we deleted 1 objects and enqueued 0 objects
2892.027147486:7ffff633b700: delete batch from store, new sizes: log 0, phys 0
2892.027152646:7ffff633b700: regular consumer finished, iret=4, szlog 0 sz phys 0
2892.027157221:7ffff633b700: main Q:Reg/w0: worker IDLE, waiting for work.
[New Thread 0x7ffff5b3a700 (LWP 21533)]
2892.027793046:7ffff5b3a700: --------imuxsock calling select, active file descriptors (max 7): 7
[New Thread 0x7ffff5339700 (LWP 21534)]
2892.028279839:7ffff7fcb700: initialization completed, transitioning to regular run mode
2892.489722918:7ffff5b3a700: Message from UNIX socket: #7
2892.489750488:7ffff5b3a700: XXX: pre CM loop, length of control message 32
2892.489762113:7ffff5b3a700: XXX: in CM loop, 1, 2
2892.489772789:7ffff5b3a700: XXX: got credentials pid 21535
2892.489783209:7ffff5b3a700: XXX: post CM loop

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7ffff5b3a700 (LWP 21533)]
0x00007ffff6baabba in hash () from /usr/lib/rsyslog/imuxsock.so
(gdb) bt
#0 0x00007ffff6baabba in hash () from /usr/lib/rsyslog/imuxsock.so
#1 0x00007ffff6baae35 in hashtable_search () from /usr/lib/rsyslog/imuxsock.so
#2 0x00007ffff6b82205 in ?? () from /usr/lib/rsyslog/imuxsock.so
#3 0x00007ffff6b828f4 in ?? () from /usr/lib/rsyslog/imuxsock.so
#4 0x00000000004397e6 in ?? ()
#5 0x00007ffff79ade9a in start_thread (arg=0x7ffff5b3a700) at pthread_create.c:308
#6 0x00007ffff72cecbd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#7 0x0000000000000000 in ?? ()

2892.027091010:7ffff633b700: file to log to: /dev/tty8
2892.027095560:7ffff633b700: write to stream, pData->pStrm 0x679510, lenBuf 66
2892.027100215:7ffff633b700: action 0x679b40 call returned -2121
2892.027105135:7ffff633b700: strm 0x679510: file 11(tty8) flush, buflen 66
2892.027117355:7ffff633b700: strm 0x679510: file 11 write wrote 66 bytes
2892.027123425:7ffff633b700: Action 0x679b40 transitioned to state: rdy
2892.027128445:7ffff633b700: ruleset: get iRet 0 from rule.ProcessMsg()
2892.027133026:7ffff633b700: ruleset.ProcessMsg() returns 0
2892.027137756:7ffff633b700: regular consumer finished, iret=0, szlog 0 sz phys 1
2892.027142871:7ffff633b700: we deleted 1 objects and enqueued 0 objects
2892.027147486:7ffff633b700: delete batch from store, new sizes: log 0, phys 0
2892.027152646:7ffff633b700: regular consumer finished, iret=4, szlog 0 sz phys 0
2892.027157221:7ffff633b700: main Q:Reg/w0: worker IDLE, waiting for work.
[New Thread 0x7ffff5b3a700 (LWP 21533)]
2892.027793046:7ffff5b3a700: --------imuxsock calling select, active file descriptors (max 7): 7 
[New Thread 0x7ffff5339700 (LWP 21534)]
2892.028279839:7ffff7fcb700: initialization completed, transitioning to regular run mode
2892.489722918:7ffff5b3a700: Message from UNIX socket: #7
2892.489750488:7ffff5b3a700: XXX: pre CM loop, length of control message 32
2892.489762113:7ffff5b3a700: XXX: in CM loop, 1, 2
2892.489772789:7ffff5b3a700: XXX: got credentials pid 21535
2892.489783209:7ffff5b3a700: XXX: post CM loop

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7ffff5b3a700 (LWP 21533)]
0x00007ffff6baabba in hash () from /usr/lib/rsyslog/imuxsock.so
(gdb) bt
#0  0x00007ffff6baabba in hash () from /usr/lib/rsyslog/imuxsock.so
#1  0x00007ffff6baae35 in hashtable_search () from /usr/lib/rsyslog/imuxsock.so
#2  0x00007ffff6b82205 in ?? () from /usr/lib/rsyslog/imuxsock.so
#3  0x00007ffff6b828f4 in ?? () from /usr/lib/rsyslog/imuxsock.so
#4  0x00000000004397e6 in ?? ()
#5  0x00007ffff79ade9a in start_thread (arg=0x7ffff5b3a700) at pthread_create.c:308
#6  0x00007ffff72cecbd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#7  0x0000000000000000 in ?? ()

Revision history for this message

medic (medic123) wrote on 2013-01-09:

i got it :-(

$SystemLogRateLimitInterval 999999999999999999999

is way too high :(

but it should not segfault, i guess

Brian Murray (brian-murray) on 2013-03-15

tags:

added: bot-stop-nagging

Revision history for this message

Launchpad Janitor (janitor) wrote on 2013-11-21:

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in rsyslog (Ubuntu):
status:	New → Confirmed

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Bug attachments

Add attachment

Remote bug watches

Bug watches keep track of this bug in other bug trackers.

Ubuntursyslog package

rsyslog SEGFAULT

Bug Description

Other bug subscribers

Bug attachments

Remote bug watches

Ubuntu
rsyslog package