search

labrad / servers

LabRAD servers
24 stars 21 forks source link

ADR server log is named with a timestamp in the future #404

Closed mgiustina closed 7 years ago

mgiustina commented 7 years ago

After restarting all ADR servers, a new ADR logfile is created, with a name like (e.g.) 00030 - ADR Log - 2017-01-18 17:41. I would expect this timestamp to be the time at which the logfile was created, however it is a time in the future.

maffoo commented 7 years ago

Is the system clock set properly on the machine where the ADR server is running?

ejeffrey commented 7 years ago

How far in the future? My guess is that the machine running the server just has the clock set wrong, but it could be also using UTC instead of the local timezone.

On Wed, Jan 18, 2017 at 4:08 PM, mgiustina notifications@github.com wrote:

After restarting all ADR servers, a new ADR logfile is created, with a name like (e.g.) 00030 - ADR Log - 2017-01-18 17:41. I would expect this timestamp to be the time at which the logfile was created, however it is a time in the future.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/martinisgroup/servers/issues/404, or mute the thread https://github.com/notifications/unsubscribe-auth/ABnKHLwFH67iG_UgmnpWQHUnjjCa9slBks5rTqmFgaJpZM4LnjJF .

mgiustina commented 7 years ago

Sorry for the noise. Apparently the machine clock needs to be reset.