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.l
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
Hey Dave,
can you check whether _this_ might be the issue:
http://lists.adiscon.net/pipermail/rsyslog/2017-August/044683.html
I ran into the same problem (rsyslog locking up the CPU).
Regards.
Andreas
___
rsyslog mailing list
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
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
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
6 matches
Mail list logo
