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 changed my (Debian 6.0) rsyslog configuration so that it uses high-precision timestamps. Indeed it does, and it gives me microseconds, both in kernel entries and in some other entries such as puppet's. But haproxy's entries are precise to the second. For example:

2012-04-23T17:48:23.122513+03:00 debianvboxtest puppet-agent[11367]: Finished catalog run in 1.82 seconds
2012-04-23T17:49:01+03:00 debianvboxtest haproxy[11555]: Proxy http-in started.
2012-04-23T17:49:27+03:00 debianvboxtest haproxy[11556]: [23/Apr/2012:17:49:26.273] http-in http-in/server01 0/0/0/0/1046 403 324 - - ---- 0/0/0/0/0 0/0 "GET / HTTP/1.1"

Is this problem at the haproxy side or at the rsyslog side?

share|improve this question

The timestamp is written by rsyslog; do a simple tcpdump of one of these packets if you want to be sure.

share|improve this answer
up vote 1 down vote accepted

The difference between haproxy and other processes was that hparoxy was logging to (udp port 514), whereas the other processes were logging to /dev/log. I changed haproxy to log to /dev/log as well, and now timestamps also have microseconds. Either a bug or a feature of rsyslog.

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.