Which clock is out of sync on VPS non-exit relay?
On Sun, Sep 01, 2013 at 06:57:38PM -0800, I wrote:
Hej,<br><br>On trying to get a non-exit relay going on a cheap VPS Vidalia says<br>Sep 02 03:48:32.146 [Warning] Received NETINFO cell with skewed time from server at 128.31.0.34:9101. It seems that our clock is ahead by 9 hours, 0 minutes, or that theirs is behind. Tor requires an accurate clock to work: please check your time and date settings.<br><br>I've tried the virtual server clock but with no luck.<br>Any help would be greatly appreciated.Robert
Sounds like you have the right time but the wrong timezone. --Roger
Thanks, Roger, I believe the server is in France and ultimately owned by a German company but it has some sort of connection to the USA and I am ten hours ahead. I have tried the timezone as Germany and Belgium to see, and set the clock on the server for the nine hours difference. Also I have tried my clock separately. After changing the server clock I got this! Sep 02 04:17:45.031 [Warning] Received NETINFO cell with skewed time from server at 154.35.32.5:443. It seems that our clock is ahead by 9 hours, 0 minutes, or that theirs is behind. Sep 02 13:19:10.300 [Warning] Received NETINFO cell with skewed time from server at 171.25.193.9:80. It seems that our clock is ahead by 9 hours, 0 minutes, or that theirs is behind. Could the clock be one in some other part of the virtual network? Robert
On Sun, Sep 01, 2013 at 06:57:38PM -0800, I wrote:
Hej,<br><br>On trying to get a non-exit relay going on a cheap VPS Vidalia says<br>Sep 02 03:48:32.146 [Warning] Received NETINFO cell with skewed time from server at 128.31.0.34:9101. It seems that our clock is ahead by 9 hours, 0 minutes, or that theirs is behind. Tor requires an accurate clock to work: please check your time and date settings.<br><br>I've tried the virtual server clock but with no luck.<br>Any help would be greatly appreciated.Robert
Sounds like you have the right time but the wrong timezone.
--Roger
____________________________________________________________ FREE ONLINE PHOTOSHARING - Share your photos online with your friends and family! Visit http://www.inbox.com/photosharing to find out more!
On Sun, 1 Sep 2013 19:54:27 -0800 I <beatthebastards@inbox.com> wrote:
Thanks, Roger,
I believe the server is in France and ultimately owned by a German company but it has some sort of connection to the USA and I am ten hours ahead. I have tried the timezone as Germany and Belgium to see, and set the clock on the server for the nine hours difference. Also I have tried my clock separately.
Let me guess, this is an OpenVZ or VServer-based VPS... You can't change date/time on those from inside the VPS. And date/time issues are so common on those, a symptom of lousy server management from the provider admins. You need to contact the provider and ask them to fix their date/time. To check if they fixed it, run in your VPS: TZ=UTC date And then compare what you get with e.g.: http://www.worldtimeserver.com/current_time_in_UTC.aspx Both should match to begin with, without that no matter which timezone you specify it won't work. -- With respect, Roman
On 09/01/2013 10:57 PM, I wrote:
Hej,
On trying to get a non-exit relay going on a cheap VPS Vidalia says Sep 02 03:48:32.146 [Warning] Received NETINFO cell with skewed time from server at 128.31.0.34:9101. It seems that our clock is ahead by 9 hours, 0 minutes, or that theirs is behind. Tor requires an accurate clock to work: please check your time and date settings.
I've tried the virtual server clock but with no luck. Any help would be greatly appreciated.
Let me guess: running Tor in an OpenVZ container? The timezone is an *offset* applied to the UTC time. It doesn't matter what offset is applied if the actual (UTC) time is wrong. Try this: ntpdate -q pool.ntp.org to get a 2nd opinion on how far you are from the actual time. It won't vary depending on the configured timezone. OpenVZ containers inherit their system time from the host. (That '-q' is for query because that is all you can do - you can't set the time.) Your only recourse is to open a ticket with the VPS vendor and tell them to fix the system time on the node that is hosting your VPS.
participants (4)
-
I -
Roger Dingledine -
Roman Mamedov -
Steve Snyder