View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000908 | unreal | ircd | public | 2003-04-20 02:23 | 2003-04-29 01:27 |
| Reporter | pj_gregory | Assigned To | |||
| Priority | normal | Severity | minor | Reproducibility | sometimes |
| Status | closed | Resolution | open | ||
| Product Version | 3.2-beta15 | ||||
| Summary | 0000908: SJOIN for channel #lobby has a fishy timestamp (1) | ||||
| Description | server notice: *** Notice -- Warning! Possible desynch: SJOIN for channel #lobby has a fishy timestamp (1) happens about every 2 seconds | ||||
| Steps To Reproduce | does it automaticly | ||||
| 3rd party modules | |||||
|
|
Got any services linked? |
|
|
Every channel has a (creation) timestamp, the timestamp is measured in seconds since 1-1-1970 00:00, so '30' is NOT good (is normally something with 9 or 10 digits) :P... Two possible reasons: - a service set the timestamp wrong - server memory corruption (could be both software or hardware) You could try throwing everyone out of the channel and back.. that way the channel probably gets re-created. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2003-04-20 02:23 | pj_gregory | New Issue | |
| 2003-04-20 20:35 | syzop | Note Added: 0002440 | |
| 2003-04-20 21:59 | syzop | Category | => documentation |
| 2003-04-20 21:59 | syzop | Summary | 22:17] •• server notice: *** Notice -- Warning! Possible desynch: SJOIN for channel #lobby has a fishy timestamp (1) => SJOIN for channel #lobby has a fishy timestamp (1) |
| 2003-04-20 21:59 | syzop | Description Updated | |
| 2003-04-20 22:01 | syzop | Severity | major => minor |
| 2003-04-20 22:01 | syzop | Reproducibility | always => sometimes |
| 2003-04-20 22:01 | syzop | Category | documentation => ircd |
| 2003-04-20 22:07 | syzop | Note Added: 0002442 | |
| 2003-04-29 01:27 | syzop | Status | new => closed |
