Syslog Timestamp incorrect on some entries on 31.12.
-
Hi,
I stumbled over some syslog entries in our system which were being generated just before midnight on 31.12.2017 and ended up with a timestamp of 31.12.2018 in the NetXMS database. Screenshot below. The timestamp on the left is the NetXMS database one. The one on the right is part of the syslog message generated by the device.
The entries appear to all be in the one minute before midnight, so possibly a bug?
Cheers
-
Hi,
likely is is because syslog message does not contain year in timestamp, only month and day. Server uses current year when parsing. So most likely those messages was delayed by few seconds, and actual parsing happens after midnight, and server just use current year, which was just changed. Probably we have to add some check for it - like if resulting timestamp is one year in the future and current date is 01.01 then assume previous year.
Best regards,
Victor
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login