Issue 11 in so-class2: Check timing issues in UK server

[codesite...@google.com]

Status: Accepted
Owner: richardn10
CC: pe...@smitmail.eu
Labels: OpSys-Linux Type-Other Usability

New issue 11 by pe...@smitmail.eu: Check timing issues in UK server
http://code.google.com/p/so-class2/issues/detail?id=11

In the VM for the VPN and Nagios it happened now twice that the time was
off by approximately 24 hours. Both cases I fixed it by synchronizing the
time right using yast.

I think there must be something not correct configured on the host OS. Can
somebody check this? It is important, as key signing requests are heavenly
relying on the current time.

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings

[codesite...@google.com]

Updates:
Labels: Priority-Medium

Comment #1 on issue 11 by pe...@smitmail.eu: Check timing issues in UK
server
http://code.google.com/p/so-class2/issues/detail?id=11

(No comment was entered for this change.)

[codesite...@google.com]

Comment #2 on issue 11 by richardn10: Check timing issues in UK server
http://code.google.com/p/so-class2/issues/detail?id=11

I'l have to organise someone to go in especially and it could be awkward as
it needs to
be coordinated with someone else being there. So it could take a few weeks.

[codesite...@google.com]

Comment #3 on issue 11 by pe...@smitmail.eu: Check timing issues in UK
server
http://code.google.com/p/so-class2/issues/detail?id=11

No problem. Just know that when somebody gets the error: "Certificate not
yet valid"
to check or the time of the VPN server is still correct.