Possible negative TS Split

These are old archives. They are kept for historic purposes only.
Post Reply
MiNdErAsR
Posts: 20
Joined: Thu Mar 11, 2004 2:18 pm
Location: New York

Possible negative TS Split

Post by MiNdErAsR »

I've read the FAQ on syncing clocks. I'm running a crontab that checks/sets the system clock nightly and the time is correct. However I'm still seeing the error message about syncing server clocks.
[20:53:37] [bellevue.tx.us.afterx.net] Possible negative TS Split: bellevue.tx.us.afterx.net (1223859216 - 1223859229 = -13) [PLEASE SYNC YOUR CLOCKS!]

If I'm understanding this, the command /TSCTL ALLTIME showed me that the above server is the problem.
[21:27:59] -bellevue.tx.us.afterx.net- *** Server=bellevue.tx.us.afterx.net TStime=1223861290 time()=1223861279 TSoffset=11

All other servers had an offset of either 0 or 1. I tried using a different time server, but the tsoffset remains the same. Anything I can do to correct this?

TIA
[dx]
Posts: 107
Joined: Sat Jun 16, 2007 1:03 am

Re: Possible negative TS Split

Post by [dx] »

I've got this msg sometimes at first link with some server. After squiting and connecting again, everything is OK
MiNdErAsR
Posts: 20
Joined: Thu Mar 11, 2004 2:18 pm
Location: New York

Re: Possible negative TS Split

Post by MiNdErAsR »

[dx] wrote:I've got this msg sometimes at first link with some server. After squiting and connecting again, everything is OK
Didn't help.

[16:07:55] [bellevue.tx.us.afterx.net] Possible negative TS Split: bellevue.tx.us.afterx.net (1223928470 - 1223928484 = -14) [PLEASE SYNC YOUR CLOCKS!]
-
[16:07:55] [bellevue.tx.us.afterx.net] Link Synced: bellevue.tx.us.afterx.net to eski.mo.us.afterx.net [secs: -14 recv: 25.734 sent: 15.357]

bellevue.tx.us.afterx.net Monday October 13 2008 -- 15:09 -05:00

eski.mo.us.afterx.net Monday October 13 2008 -- 15:09 -05:00

I just don't get it.
MiNdErAsR
Posts: 20
Joined: Thu Mar 11, 2004 2:18 pm
Location: New York

Re: Possible negative TS Split

Post by MiNdErAsR »

Just a followup, and for others who might experience this same issue. Restarting the ircd appears to have corrected the problem. Go figure.

8)
Post Reply