View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0003956 | unreal | ircd | public | 2010-09-07 17:17 | 2010-09-08 13:07 |
| Reporter | chotaire | Assigned To | syzop | ||
| Priority | normal | Severity | major | Reproducibility | always |
| Status | resolved | Resolution | fixed | ||
| Platform | x86 | OS | QNX | OS Version | 6.5.0 |
| Product Version | 3.2.8 | ||||
| Fixed in Version | 3.2.9-RC1 | ||||
| Summary | 0003956: Timing issue on QNX 6.5.0 in ircd.c | ||||
| Description | When starting unrealircd on QNX 6.5.0, everything seems to work just fine until taking a peak into ircd.log: [Thu Sep 2 02:19:41 2010] - TIME SYNCH: timeserver=1283818771, our=1283386781, offset = 431990 [old offset: 37] [Tue Sep 7 02:19:31 2010] - WARNING: Time running backwards! Clock set back ~-1283818771 seconds (0 -> 1283818771) [Tue Sep 7 02:19:31 2010] - [TimeShift] Resetting a few timers to prevent IRCd freeze! [Tue Sep 7 02:19:31 2010] - [TimeShift] The (IRCd) clock was set backwards. Waiting for time to be OK again. This will be in -1283818771 seconds [Tue Sep 7 02:19:34 2010] - WARNING: Time running backwards! Clock set back ~-3 seconds (1283818771 -> 1283818774) [Tue Sep 7 02:19:34 2010] - [TimeShift] Resetting a few timers to prevent IRCd freeze! [Tue Sep 7 02:19:37 2010] - WARNING: Time running backwards! Clock set back ~-3 seconds (1283818774 -> 1283818777) [Tue Sep 7 02:19:37 2010] - [TimeShift] Resetting a few timers to prevent IRCd freeze! [Tue Sep 7 02:19:40 2010] - WARNING: Time running backwards! Clock set back ~-3 seconds (1283818777 -> 1283818780) [Tue Sep 7 02:19:40 2010] - [TimeShift] Resetting a few timers to prevent IRCd freeze! [Tue Sep 7 02:19:43 2010] - WARNING: Time running backwards! Clock set back ~-3 seconds (1283818780 -> 1283818783) [Tue Sep 7 02:19:43 2010] - [TimeShift] Resetting a few timers to prevent IRCd freeze! [Tue Sep 7 02:19:46 2010] - WARNING: Time running backwards! Clock set back ~-3 seconds (1283818783 -> 1283818786) [Tue Sep 7 02:19:46 2010] - [TimeShift] Resetting a few timers to prevent IRCd freeze! [Tue Sep 7 02:19:49 2010] - WARNING: Time running backwards! Clock set back ~-3 seconds (1283818786 -> 1283818789) [Tue Sep 7 02:19:49 2010] - [TimeShift] Resetting a few timers to prevent IRCd freeze! [Tue Sep 7 02:19:52 2010] - WARNING: Time running backwards! Clock set back ~-3 seconds (1283818789 -> 1283818792) [Tue Sep 7 02:19:52 2010] - [TimeShift] Resetting a few timers to prevent IRCd freeze! [Tue Sep 7 02:19:55 2010] - WARNING: Time running backwards! Clock set back ~-3 seconds (1283818792 -> 1283818795) [Tue Sep 7 02:19:55 2010] - [TimeShift] Resetting a few timers to prevent IRCd freeze! [Tue Sep 7 02:19:58 2010] - WARNING: Time running backwards! Clock set back ~-3 seconds (1283818795 -> 1283818798) [Tue Sep 7 02:19:58 2010] - [TimeShift] Resetting a few timers to prevent IRCd freeze! [Tue Sep 7 02:20:01 2010] - WARNING: Time running backwards! Clock set back ~-3 seconds (1283818798 -> 1283818801) [Tue Sep 7 02:20:01 2010] - [TimeShift] Resetting a few timers to prevent IRCd freeze! [Tue Sep 7 02:20:04 2010] - WARNING: Time running backwards! Clock set back ~-3 seconds (1283818801 -> 1283818804) [Tue Sep 7 02:20:04 2010] - [TimeShift] Resetting a few timers to prevent IRCd freeze! [Tue Sep 7 02:20:07 2010] - WARNING: Time running backwards! Clock set back ~-3 seconds (1283818804 -> 1283818807) [Tue Sep 7 02:20:07 2010] - [TimeShift] Resetting a few timers to prevent IRCd freeze! System clock has been verified to run quite ok. It does lag behind a second every few minutes when running as virtual machine but I fixed this using regular ntpdate updates from local timeserver so the system clock is at no time ever lagging behind more than one second. kern.hz setting or similar seems to be read-only on QNX. This problem with ircd.c seems to prevent autoconnect for links (it just doesn't happen). If however manually linking the server, there is never any message about "PLEASE SYNC YOUR CLOCKS!" and similar. When linked, I see no problems on IRC network other than flooding local opers with notices (see ircd.log above) every 3 seconds. | ||||
| Steps To Reproduce | Compile unrealircd 3.2.8.1 on QNX 6.5.0 and ./unreal start ; tail -f ircd.log. | ||||
| Tags | No tags attached. | ||||
| 3rd party modules | |||||
|
|
Is this a dupe of 0003853? |
|
|
For the autoconnect issue only. |
|
|
[Thu Sep 2 02:19:41 2010] - TIME SYNCH: timeserver=1283818771, our=1283386781, offset = 431990 [old offset: 37] that's quite a lot :) [Tue Sep 7 02:19:31 2010] - WARNING: Time running backwards! Clock set back ~-1283818771 seconds (0 -> 1283818771) this is a bug, timeofday is zero the first time... what I don't understand though is how it could have triggered... if (timeofday - oldtimeofday < NEGATIVE_SHIFT_WARN) { if (<something> - 0 < -somethingelse) that would be very odd :P unless, TS / time_t on QNX is unsigned ? that might explain the rest of the messages too.. Ah yes... "The consensus is for time_t to be signed, and this is the usual practice. The software development platform for version 6 of the QNX operating system has an unsigned 32-bit time_t, though older releases used a signed type." Fun. Ok, I've fixed this in CVS [.877]: - Fixed another compile problem on QNX, reported by chotaire (0003955 too). - Fixed incorrect messages regarding clock going backwards on QNX 6 and later, reported by chotaire (0003956). Thanks for the report. If that somehow didn't fix it, let us know. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2010-09-07 17:17 | chotaire | New Issue | |
| 2010-09-07 17:28 | ohnobinki | Note Added: 0016330 | |
| 2010-09-07 18:10 | chotaire | Note Added: 0016332 | |
| 2010-09-08 12:55 | syzop | Status | new => assigned |
| 2010-09-08 12:55 | syzop | Assigned To | => syzop |
| 2010-09-08 13:07 | syzop | QA | => Not touched yet by developer |
| 2010-09-08 13:07 | syzop | U4: Need for upstream patch | => No need for upstream InspIRCd patch |
| 2010-09-08 13:07 | syzop | Note Added: 0016340 | |
| 2010-09-08 13:07 | syzop | Status | assigned => resolved |
| 2010-09-08 13:07 | syzop | Fixed in Version | => 3.2.9-RC1 |
| 2010-09-08 13:07 | syzop | Resolution | open => fixed |
| 2010-09-08 13:08 | syzop | Note Edited: 0016340 |
