We've configured a host to send syslogs to our central repository running syslog-ng 2.0.3. This particular host is sending tab-delimited entries. The normal syslogd daemon parses and saves the messages correctly. Syslog-NG seems to save them encoded as \011. Can syslog-ng be configured to save the decoded ASCII characters? Or can the messages be shoved through something like sed to be massaged before saving? Thanks! Norman Elton
On Mon, 2008-04-14 at 11:00 -0400, Norman Elton wrote:
We've configured a host to send syslogs to our central repository running syslog-ng 2.0.3. This particular host is sending tab-delimited entries. The normal syslogd daemon parses and saves the messages correctly. Syslog-NG seems to save them encoded as \011.
Can syslog-ng be configured to save the decoded ASCII characters? Or can the messages be shoved through something like sed to be massaged before saving?
Hmm, I don't remember adding \0 octal encoding to syslog-ng. Are you sure it is syslog-ng that does this? -- Bazsi
Can syslog-ng be configured to save the decoded ASCII characters? Or can the messages be shoved through something like sed to be massaged before saving?
Hmm, I don't remember adding \0 octal encoding to syslog-ng. Are you sure it is syslog-ng that does this?
I ran a packet capture that shows the incoming syslog packet with a single tab character rather than the octal sequence. This is a RHEL box. A similarly configured Solaris box is logging the packets properly. What else could be causing the message to be encoded? Thanks! Norman
Norman Elton wrote:
Can syslog-ng be configured to save the decoded ASCII characters? Or can the messages be shoved through something like sed to be massaged before saving?
Hmm, I don't remember adding \0 octal encoding to syslog-ng. Are you sure it is syslog-ng that does this?
I ran a packet capture that shows the incoming syslog packet with a single tab character rather than the octal sequence.
This is a RHEL box. A similarly configured Solaris box is logging the packets properly.
What else could be causing the message to be encoded?
Could this be a problem with gettext? What version of RHEL, glib2, gettext, eventlog. What language is the RHEL? -- Evan Rempel
participants (3)
-
Balazs Scheidler
-
Evan Rempel
-
Norman Elton