Package: rsyslog Version: 4.4.2-1~bpo50+1 Severity: normal I use rsyslog to relay messages from old bsd style loggers (RSYSLOG_TraditionalForwardFormat) and rfc5424 message loggers (RSYSLOG_ForwardFormat) to one bsd style loghost. Every old style log message is relayed correctly to the loghost and is written correctly to the logfile. Rfc5424 messages are relayed to the loghost without a double point after the "processname[id]" string. Additionally rsyslog does not write the double point to the logfile (with RSYSLOG_TraditionalFileFormat).
I did not jet use any structured data, so I don't know if this is buggy, too. This behaviour is idential in version 3.18.6 (lenny stable) Example from the logs: --- snip --- Sep 8 22:32:24 new_host old_process[2868] - Hello with new rfc5424 log Sep 8 22:32:24 old_host new_process[2890]: Hello with old style bsd log --- snip --- The way it should be: --- snip --- Sep 8 22:32:24 new_host old_process[2868]: - Hello with new rfc5424 log Sep 8 22:32:24 old_host new_process[2890]: Hello with old style bsd log --- snip --- -- System Information: Debian Release: 5.0.5 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.26-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages rsyslog depends on: ii libc6 2.7-18lenny4 GNU C Library: Shared libraries ii lsb-base 3.2-20 Linux Standard Base 3.2 init scrip ii zlib1g 1:1.2.3.3.dfsg-12 compression library - runtime Versions of packages rsyslog recommends: ii logrotate 3.7.1-5 Log rotation utility Versions of packages rsyslog suggests: pn rsyslog-doc <none> (no description available) pn rsyslog-gnutls <none> (no description available) pn rsyslog-gssapi <none> (no description available) pn rsyslog-mysql | rsyslog-pgsql <none> (no description available) pn rsyslog-relp <none> (no description available) -- no debconf information -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
