linux server time change in a sudden

suicidaleggroll · 05-22-2017, 12:18 PM

I'm not sure I buy that explanation. Mostly because if what you said was true, the PIDs should be more or less random. Instead the PID of the process with the incorrect date seems to always be within a few hundred of the process with the correct date, indicating that they likely started at near the same time.

Are you sure you don't have a cron job running that's inadvertently trying to change the system date/time?

smallpond · 05-22-2017, 01:25 PM

If you take a look at the syslog message format

https://tools.ietf.org/html/rfc5424#page-7

you will see that the timestamp is part of the message, so it means you are receiving syslog messages from a sender that is confused about the time and date.

AwesomeMachine · 05-22-2017, 09:13 PM

I definitely don't understand.

hilou · 05-24-2017, 11:44 AM

Quote:

Originally Posted by pan64

I'm not really sure I understand that.

Hi,

I updated my answer, maybe there is some problem of my expression, you could list you question and I will answer that to make this more claear

hilou · 05-26-2017, 05:46 AM

this is duplicate, however I don't know how to delete this.

pan64 · 05-26-2017, 05:51 AM

looks like it is a bug in syslog. The entry itself is ok (I think all of them), but syslog has problems with multiply inputs, therefore some logs will be delayed. Sometimes several days. The new, fresh implementations usually works, so probably you need to upgrade. (you can reproduce it on ubuntu 14.04 for example)