Re: [rsyslog] rsyslogd 8.29.0 - crash when omrelp server port is not open + build error in imptcp

Since this is all "only just" a test-setup, I have not yet gotten into creating an optimized configuration. I am aware, that default queue sizes are overkill, however the problems I encountered here were happening on an idle system. Though I am not familiar with the internals, I would at least

Re: [rsyslog] rsyslogd 8.29.0 - crash when omrelp server port is not open + build error in imptcp

On 08/23/2017 01:13 AM, Thomas Deutschmann via rsyslog wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 2017-08-21 13:21, Andreas Wehrmann via rsyslog wrote: actionProcessMessage() always returns RS_RET_ACTION_FAILED (which is -2123), meaning i will be decremented for re-submit and

Re: [rsyslog] rsyslogd 8.29.0 - crash when omrelp server port is not open + build error in imptcp

2017-08-23 1:13 GMT+02:00 Thomas Deutschmann via rsyslog : > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA512 > > On 2017-08-21 13:21, Andreas Wehrmann via rsyslog wrote: >>> actionProcessMessage() always returns RS_RET_ACTION_FAILED (which is >>> -2123), >>> meaning i

Re: [rsyslog] rsyslogd 8.29.0 - crash when omrelp server port is not open + build error in imptcp

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 2017-08-21 13:21, Andreas Wehrmann via rsyslog wrote: >> actionProcessMessage() always returns RS_RET_ACTION_FAILED (which is >> -2123), >> meaning i will be decremented for re-submit and the loop starts all >> over again. But this is not the

Re: [rsyslog] rsyslogd 8.29.0 - crash when omrelp server port is not open + build error in imptcp

On 08/21/2017 12:03 PM, Andreas Wehrmann via rsyslog wrote: So, I was able to make some progress in the meantime: I turned off compiler optimizations and rsyslog doesn't crash anymore though I have yet to figure out, what optimization breaks the program. Nevertheless, an issue remains: When

Re: [rsyslog] rsyslogd 8.29.0 - crash when omrelp server port is not open + build error in imptcp

5839.353174748:main Q:Reg/w0 : iminternal.c: signaling new internal message via SIGTTOU: 'action 'action 0' suspended, next retry is Sun Aug 13 03:04:29 2000 [v8.29.0 try http://www.rsyslog.com/e/2007 ]' I am not sure but I have the feelings you are just running badly out of memory which

Re: [rsyslog] rsyslogd 8.29.0 - crash when omrelp server port is not open + build error in imptcp

On 08/18/2017 03:22 PM, Thomas Deutschmann via rsyslog wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 2017-08-18 13:05, Andreas Wehrmann via rsyslog wrote: Compiling 8.29.0 with the option "--enable-imptcp" breaks the compilation process: CC imptcp_la-imptcp.lo imptcp.c: In

Re: [rsyslog] rsyslogd 8.29.0 - crash when omrelp server port is not open + build error in imptcp

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 2017-08-18 13:05, Andreas Wehrmann via rsyslog wrote: > Compiling 8.29.0 with the option "--enable-imptcp" breaks the > compilation process: > > CC imptcp_la-imptcp.lo imptcp.c: In function > 'AcceptConnReq': imptcp.c:831:2: error: