7.219. rsyslog

Bug Fixes

BZ#838148

Prior to this update, the rsyslog packages depended on a newer selinux-policy which the rsyslog spec file did not reflect. The command "yum --security update" updated rsyslog but not the selinux-policy. As a consequence, rsyslog malfunctioned when booting and depending services failed, including login. This update modifies the spec file to prevent installation with an incompatible selinux-policy package and enforce its update if available.

BZ#847568

Prior to this update, the rule that was specified immediately before the "$IncludeConfig" directive to be reordered after the contents of the included configuration file due to handling problem with the configuration file parser. As a consequence, the order of processing was different from the intended one with the potential of message losses. This update modifies the underlying code so that the order of processing is the same as in the configuration file.

BZ#886004

Prior to this update, the Unix Socket Input plug-in for rsyslog did not consider the timestamp format specified by the RFC 5424 Syslog Protocol for timestamps derived from RFC 3339. As a consequence, messages sent to the syslog daemon via Unix sockets that used the RFC 3339-derived timestamp format were silently discarded. This update supports this timestamp format. Messages sent to the rsyslog system logging daemon via Unix sockets that use the RFC 3339-derived timestamp format are now accepted and processed properly.