Wrong server time

ShArDiCk · Post by **ShArDiCk** » Sat Jun 11, 2005 10:46 pm

Hi,
i've a strange problem on my network.

All server time are right. But, if i set a ban or set a topic, when i rejoin the channel, or another user join the channel, he see topic date or ban date sets at 11 hours later.

Ex: it's 9.00 . Set a topic. Rejoin channel. I see topic setted at 20.00.

What's the problem? all machines are timed with ntp. and machines time are right.
All /time server returns the correct time.

oO...

Thanx in advance.

Post by **Syzop** » Sat Jun 11, 2005 11:08 pm

Could you paste the output of '/tsctl time'? (from the same server you have this topic problem).

Also, what IRC client are you using?
If you use mIRC, try doing '/debug -pt @debug' and do a '/topic #chan' and copypaste the debug output (the line with numeric 333). Naturally, let me know what topic time it SHOULD have been as well (eg: just set it right before you do this command) :).

-

This could be caused by: wrong tsoffset, wrong timezone on servers, wrong timezone on your machine, etc.
With the output of the above commands I'll be able to say what it is :p.

ShArDiCk · Post by **ShArDiCk** » Sun Jun 12, 2005 1:46 am

tsctl time : -server- *** TStime=1118740866 time()=1118540342 TSoffset=200526

i'm using mIRC now.

Time would be 12 June 03:42 .

Set the topic.

Rejoin channel.

[03:45] <- :server 333 ShArDiCk #channel ShArDiCk 1118741096 .

my client say that the topic is setted by me on Tue Jun 14 11:24:56

uhm... i noted that:
my services server reports time as: Sun Jun 12 03:49:38 2005 CEST
my server reports time as: Sunday June 12 2005 -- 03:49 +02:00

Services are on other machine respect to my server. the ircd on that machine reports this time: Sunday June 12 2005 -- 03:49 +02:00

we are using anope.

Any ideas?

[funny]we are already watching the future[/funny]

w00t · Post by **w00t** » Sun Jun 12, 2005 2:33 am

How about /tsctl alltime ?

Post by **Syzop** » Sun Jun 12, 2005 3:04 am

Right, you got a nice TSoffset (the TSoffset=200526). This might be caused by services synching the clock wrongly (especially if you see such a value around 200000 on the other servers too if you do /TSCTL ALLTIME). Basically the ircd got the time right but something told the ircd that it has to add 200526 seconds to it to get the 'correct time' ;).

You can manually reset the offset by doing '/TSCTL OFFSET + 0', or by synching the time trough services (assuming they work ok). The latter method would work network-wide.

NOTE NOTE: If you do this all your clients might stall forever (up to 200526 seconds). The IRCd really really doesn't like it if time gets changed (just like any other server program, in fact). So it could well be that you'll have to restart the ircd after this has been done. But then, the TSCTL OFFSET might not have been saved ;). As a last resort you can remove 'ircd.tune', along with the max users it also stores the time offset (or you can manually edit the value)..

blablabla.. it's way too late... I'm gone to bed ;)

w00t · Post by **w00t** » Sun Jun 12, 2005 4:38 am

Actually according to that post time it's early syzop

.

I missed the huge offset value *smacks forhead*.

aquanight · Post by **aquanight** » Sun Jun 12, 2005 5:31 am

Also, client timezones make a difference here. The topic time sent is a TS (an integer value representing the number of seconds since Jan 1, 1970 midnight GMT), so your client will apply it's timezone offset (and daylight savings time, etc) from that when converting the number to a date. So if the two people here are 11 timezones apart then yes the dates will be 11 hours apart :) .

(Of course, the wonky clock would be more likely, that blurb is just FYI :) .)

ShArDiCk · Post by **ShArDiCk** » Sun Jun 12, 2005 11:45 am

Yes! it runs!

Thanx syzop.

But i'have to do /TSCTL OFFSET + 0 on every server has wrong offset?
There'isnt a command that sync all server together with one shot?

w00t · Post by **w00t** » Sun Jun 12, 2005 1:36 pm

Unfortunatly no as you need to compare the output of TSCTL ALLTIME and then use TSCTL OFFSET to adjust the clocks accordingly - Many services include a way to do this automatically.

Alternativly you can run ntpd on your servers to keep time synchronised properly, this is a better situation.

Jason · Post by **Jason** » Sun Jun 12, 2005 3:03 pm

Uh.. w00t?

ShArDiCk wrote: What's the problem? all machines are timed with ntp. and machines time are right.

aquanight · Post by **aquanight** » Sun Jun 12, 2005 6:12 pm

Yes, you'll need to go through each server and fix the TSCTL. I wouldn't trust using services in case that was how you got into this mess to begin with :P .

ShArDiCk · Post by **ShArDiCk** » Sun Jun 12, 2005 9:22 pm

a time we had os_tssync, a great module for anope. but anope sites, since two days is down.

Anyone has this module?

Jason · Post by **Jason** » Mon Jun 13, 2005 1:29 am

Yes, I have that module loaded. PM me your email address

ShArDiCk · Post by **ShArDiCk** » Mon Jun 13, 2005 7:31 am

Thanx Jason but at the end i've found it.

To syzop:

we have installed the module for sync all servers together. loaded and used. Naturally it created a great network desync an all servers.

Now topic setted show time correctly.

But:

- me, from my server, dont see #great_channel with 150 users on it
- me, from my server, see #little_channel without modes (but registrered) with 1 user.
- another server admin, from his server, dont see #great_channel but see #little_channel with 11 users.

we had an empty server and we restart it. At relink, this server return at TSOffet of 200526, like yesterday!!!

We have tried to restart services but nothing.

... Any ideas?

Thanx in advance

Dukat · Post by **Dukat** » Mon Jun 13, 2005 7:38 am

Just don't use this module or whatever method to synchronize your clocks.... Use ntpd, it's the best solution.

UnrealIRCd Forums

Wrong server time

Wrong server time

Re: Wrong server time