Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I am observing the following behaviour when logging to syslog from an external application: if I send a well-formed syslog message to a UDP socket, rsyslog correctly parses it, however if the very same message is sent to a UNIX domain socket (/dev/log), it is not parsed at all (rsyslog basically assumes, that everything, that he received, is a message, so no timestamp, no anything).

The message in question is

<142>1 2010-12-29T11:11:11Z foo bar 123 baz - A Message

which is parsed as

Dec 29 11:11:11 foo bar[123] A Message

unless it isn't.

share|improve this question

Probably you should send the message without the hostname (foo) and in rfc3164 format (not rfc5424 as the above) to get it parsed.

share|improve this answer

When parsing messages rsyslog does its best to make sense of it.

For a message received from an Unix socket, rsyslog accepts RFC 3164-like messages, using these fields: pri, timestamp, tag, and content.

It accepts various message formats, like :

  • just a message
  • <pri>message
  • <pri>tag: msg

About the message timestamps:

  1. They must be RFC3164 formatted.
  2. Since the SysSock.IgnoreTimestamp option is enabled by default, your timestamps will be ignored until you disable this option.

The hostname field cannot be overridden. rsyslog will always get it from its configuration.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.