[rsyslog-notify] Forum Thread: Uncompression of a message failed, cannot enable debug - (Mode 'post')

noreply at adiscon.com noreply at adiscon.com
Mon Aug 18 20:07:37 CEST 2014


User: mtovey 
Forumlink: http://kb.monitorware.com/viewtopic.php?p=24846#p24846

Message: 
----------
I am frequently seeing the message "Uncompression of a message failed with
return code -3" on my central Rsyslog server.  The message provides further
instructions to "enable debug logging if you need further information", but
I can't seem to get that to work.  I have set the environment variable
RSYSLOG_DEBUG to "DebugOnDemand NoStdOut" and RSYSLOG_DEBUGLOG to
"/var/tmp/rsyslog.dbg".  When I start rsyslogd, start-up debug messages are
written to the rsyslog.dbg file, but I cannot get any more messages to be
written when I send the USR1 signal.  The signal seems to be ignored.

My server OS is Oracle Enterprise Linux 6.5 (RHEL equivalent) and the
Rsyslog version is 5.8.10 (the version delivered with the OS).  I know the
version is old, but we prefer to stay with the package versions that are
provided by the vendor as much as possible.  Alternatively, if we can find
an officially published newer version in a RPM package, we are open to
evaluating that.  Does anyone know of one?

Meanwhile, I am trying to understand what is causing the original error
"Uncompression" message.  I can see a couple of other references to it in
the forum, but no resolutions.  Can anyone assist with that?
    Thanks,
    -Mark


More information about the rsyslog-notify mailing list