Page 1 of 1
wrong server time [2]
Posted: Thu Jun 16, 2005 7:48 am
by ShArDiCk
Hi,
so... this is the second time i write for this problem. i'm sorry. but the problem is big and i cant resolve it.
I followed advice of syzop to fix the problem.
- sync all servers with ntpd (synched to time.ien.it)
all servers yesterday have rights ts-offets (max 22) .
Today
Server=server TStime=1119108206 time()=1118907675 TSoffset=200531
again...
in the past days every night we have to sync with /os tssync. for all day offeset is rights. during the night it brokes!
but why?
there is another way to resolve it???
Posted: Thu Jun 16, 2005 9:16 am
by TigerKatziTatzi
offset of 200531 would mean the server is time far way off. 200531 secs ~ 2,5 days ahead for local time
- did u setup local settings probably ?
-- hwclock set, all server local correct UTC offset ( means correct timezone )
for verifying just do on the server with high offsets this #date
and check date/time. then u should get more informations about it why this could be
- what does it means tssync modul broke ? unloaded in services ?
but even without having tssync periodly running this offset wouldn'T appear. looks to me like a wrong setup on the box. if its only one box.
Posted: Thu Jun 16, 2005 9:25 am
by ShArDiCk
-- did u setup local settings probably ?
-- hwclock set, all server local correct UTC offset ( means correct timezone )
are rights.
- what does it means tssync modul broke ? unloaded in services ?
offset during the night grow
but even without having tssync periodly running this offset wouldn'T appear. looks to me like a wrong setup on the box. if its only one box
all servers have huge offsets but date-time on physical machines are rights.
Posted: Thu Jun 16, 2005 9:31 am
by TigerKatziTatzi
giving u a view like it is here. we do have only one server without ntp running. mickey.
Code: Select all
Server=egt.MindForge.org TStime=1118914095 time()=1118914096 TSoffset=-1
-hub1.MindForge.org- *** Server=hub1.MindForge.org TStime=1118914095 time()=1118914100 TSoffset=-5
-hub2.MindForge.org- *** Server=hub2.MindForge.org TStime=1118914094 time()=1118914094 TSoffset=0
-Blackhole.MindForge.org- *** Server=Blackhole.MindForge.org TStime=1118914094 time()=1118914080 TSoffset=14
-egt2.MindForge.org- *** Server=egt2.MindForge.org TStime=1118914095 time()=1118914096 TSoffset=-1
-fineartinsilver.MindForge.org- *** Server=fineartinsilver.MindForge.org TStime=1118914095 time()=1118914095 TSoffset=0
-wintermute.MindForge.org- *** Server=wintermute.MindForge.org TStime=1118914095 time()=1118914095 TSoffset=0
-neuromancer.MindForge.org- *** Server=neuromancer.MindForge.org TStime=1118914095 time()=1118914095 TSoffset=0
-Buddha.MindForge.org- *** Server=Buddha.MindForge.org TStime=1118914095 time()=1118914095 TSoffset=0
-hub3.MindForge.org- *** Server=hub3.MindForge.org TStime=1118914095 time()=1118914095 TSoffset=0
-Minerva.MindForge.org- *** Server=Minerva.MindForge.org TStime=1118914094 time()=1118914071 TSoffset=24
-Mickey.MindForge.org- *** Server=Mickey.MindForge.org TStime=1118914094 time()=1118913830 TSoffset=264
-ZenZone.MindForge.org- *** Server=ZenZone.MindForge.org TStime=1118914094 time()=1118914094 TSoffset=0
-Sydney.MindForge.org- *** Server=Sydney.MindForge.org TStime=1118914094 time()=1118914095 TSoffset=0
Some Gerneral Information
Hardwareclock vs System Time
The hardware clock basically is your BIOS clock. At boot time the hardware clock is copied to System Time which then controls the time while Linux runs.
Local Time vs GMT/UTC
On Linux systems, you have a choice of keeping the hardware clock in UTC/GMT time or local time. The preferred option is to keep it in UTC because then daylight savings can be automatically accounted for.
Time zone
The time zone setting is used to calculate the offset to UTC/GMT. Should be set to the place you live in. The offset is controlled by the file: /etc/localtime
This file is either a copy or a symlink to: /usr/share/zoneinfo/zone/city
It should point to the right file, otherwise your localtime will be messed up.
Posted: Thu Jun 16, 2005 1:15 pm
by w00t
I will add that I've heard of these kinds of problems with TS synching modules etc before - so it'll be interesting if we can find a cause.
Posted: Thu Jun 16, 2005 2:11 pm
by Syzop
I don't understand.. why do you /os tssync??
If your clocks are properly synched with ntpd then that is (100%) sufficient.
The only thing time synchronizing via services then can do is screw things up / cause problems ;P.