MonitorWare Knowledge Base

Hello,

I have installed rsyslog from source on an ubuntu box and seeing a segmentation fault when it receives syslog messages from a syslog-ng machine on the tcp port (udp based works fine)

1554.910262608:action 1 queue:Reg/w0: action 1 queue:Reg/w0: worker IDLE, waiting for work.
1554.942598042:imtcp.c: New connect on TCP inetd socket: #12
Segmentation fault


strace:
select(1, NULL, NULL, NULL, {30, 0}1644.946035277:imtcp.c: New connect on TCP inetd socket: #12
) = ? ERESTARTNOHAND (To be restarted)
+++ killed by SIGSEGV +++
Process 31528 detached

root@syslogServer:~# rsyslogd -v
rsyslogd 3.12.4, compiled with:
FEATURE_REGEXP: Yes
FEATURE_LARGEFILE: Yes
FEATURE_NETZIP (message compression): Yes
GSSAPI Kerberos 5 support: No
FEATURE_DEBUG (debug build, slow code): No
Runtime Instrumentation (slow code): No


Is there any reason what could cause this?

Thanks,

Sachar

• Custom written rsyslog.conf?
• Maintenance Contract?
• Installation support?

Hi Sachar,

this looks like it dies immediately when the connect comes in - what is a bit crazy. I've never seen this before.

Could you help me with debugging it? If so, please do a new ./configure with --enable-debug --enable-rtinst added to the options. Then, run rsyslogd interactively with the -d -n options added. Please send me the resulting debug output (which is quite large). If you don't like to post it publically, you can email me at rgerhards@adiscon.com.

Thanks,
Rainer

Hello Rainer,

Yes it dies the moment a packet is received via tcp (rsyslog stays alive as long as no loginput is sent to the port)

I will email you the debug info.

Cheers

Sachar