Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 346552 - clock on orion.eclipse.org is way off
Summary: clock on orion.eclipse.org is way off
Status: RESOLVED FIXED
Alias: None
Product: Community
Classification: Eclipse Foundation
Component: vservers (show other bugs)
Version: unspecified   Edit
Hardware: PC Mac OS X - Carbon (unsup.)
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Eclipse Webmaster CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-05-19 18:06 EDT by Boris Bokowski CLA
Modified: 2011-05-20 09:54 EDT (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Boris Bokowski CLA 2011-05-19 18:06:29 EDT 
admin@orion:~> date
Thu May 19 14:16:53 EDT 2011

Boris-Bokowskis-MacBook-Pro:~ bokowski$ date
Thu 19 May 2011 18:06:02 EDT
Comment 1 Boris Bokowski CLA 2011-05-19 18:07:07 EDT 
I don't want to just fix this once - shouldn't the time be synchronized using a time server?
Comment 2 Denis Roy CLA 2011-05-19 18:44:39 EDT 
You won't be able to change the hardware clock; virtual servers should be pulling their clock from the hypervisor. Seems the host server is not syncing properly.  I will check it.
Comment 3 Denis Roy CLA 2011-05-20 09:54:29 EDT 
I had encountered this before with other vservers -- for some reason, the timezone is computed twice, and short of setting an incorrect time on the host, I have a hard time getting it to work.

Easiest solution is to tell the domU to use an independent (from the host) clock:
echo 1 > /proc/sys/xen/independent_wallclock

... and to sync with an external source.
rdate -s build.eclipse.org


I've added this to a cron, so your clock should now always be in sync with build.eclipse.org's (which is synced from an external source).