Red Hat Bugzilla – Bug 1313804
Leap year handling broken for rsyslog, timestamps issue one day earlier
Last modified: 2016-10-26 05:43:57 EDT
I just wanted to let you know that we have found an issue with the
unixtimestamp formatting option in leap years. The problem started on
March, 1st and will persist till the end of the year. The timestamp is
one day in the past.
A patch is available here, it shall probably work with almost all
Full details can be found in this issue tracker:
Note that I will NOT release a 8.16.1 version for this fix. Usually, I
would have done so, but the 8.17.0 release is due next Tuesday and
will probably available as RC on friday. Given the fact that I would
need at least one additional day to craft 8.16.1, I don't think this
makes much sense.
Distro packages (and other users as well, of course) can apply
above-mentioned short patch. I actually suggest to do so, as this
problem exists, I think, in all versions supporting the
"unixtimestamp" formatting option (side-note: v5.8 does not have this
Note that this appears to be a very old problem with the code and is likely affecting any rsyslog configuration that is using the "timegenerated" property in their rsyslog templates.
This will also likely need to be fixed in RHEL 7 releases, too.
(In reply to Peter Portante from comment #0)
> Note that this appears to be a very old problem with the code and is likely
> affecting any rsyslog configuration that is using the "timegenerated"
> property in their rsyslog templates.
> This will also likely need to be fixed in RHEL 7 releases, too.
Cloning for el7...
I was trying to reproduce on rhel6 and I'm not able to do so. From my point of view timestamps are correct.
in rsyslog7 we have state before this commit:
So if it is really not working, please give me the reproducer.
The full PR is https://github.com/rsyslog/rsyslog/pull/831, with tests, too.
This only occurs when using the "unixtimestamp" reference, see "date-unixtimestamp" property options.
this bug does not occur in our version of rsyslog in rhel6 as we are using older version in which the code is different from the current upstream version and works fine. I'm closing this.