View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0006079 | unreal | ircd | public | 2022-03-22 18:25 | 2022-03-23 13:56 |
| Reporter | armyn | Assigned To | syzop | ||
| Priority | normal | Severity | minor | Reproducibility | have not tried |
| Status | closed | Resolution | no change required | ||
| Product Version | 6.0.1 | ||||
| Summary | 0006079: Expired glines not retiring after restarting irc server | ||||
| Description | I haven't tested to see if it does it every time. My server was in maintenance yesterday all afternoon and in relighting around 8:00 p.m. no gline expired which had to expire while the irc server was off | ||||
| Steps To Reproduce | 1) For example, it is noon, you put a gline on an IP or an ~account for 6 hours. Normally it expires at 6:00 p.m. 2) You cut the irc server from 4pm to 8pm, you turn on the irc server at 8pm and the gline which should have expired at 6pm has not been removed, it must be removed manually. | ||||
| Tags | No tags attached. | ||||
| 3rd party modules | |||||
|
|
I cannot reproduce this exact issue. I set a GLINE (even on account as you suggested), then let the server write to tkldb and kill it, wait for the time of the expiry to pass by, and then boot op the ircd again, the gline is gone. I don't think it can be what you describe, as we use < or > for comparison to see if an entry should be expired or not, we never use == for an "exact match" since that would be way too problematic/fragile. It can, of course, be a completely different issue that you were experiencing, but the exact one with the cause you describe sounds unlikely. Do you have proof of a "STATS G" entry or some other STATS for a *LINE? |
|
|
Yes, I had located that on /stats g However, maybe I was wrong and that the gline should have expired only 1 hour after the start of the irc server, at 1 hour or so and that I manually unglined 30 or 45 minutes before. I would come back if I encounter this problem again which may not be a problem after all |
|
|
Ah yes, the problem is solved Here is the summary: 1) I actually glined this person on March 19 at 11:13 p.m. 2) I unglined manually on March 21 around 9 p.m., thinking that it must have expired 3) in reality the gline was supposed to expire on March 21 at 11:13 p.m., because it lasted 48 hours. So it's fixed Can you remove this bug sig? and sorry to have bothered you for nothing |
|
|
Sure, no problem, can happen :) |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2022-03-22 18:25 | armyn | New Issue | |
| 2022-03-23 07:31 | syzop | Note Added: 0022415 | |
| 2022-03-23 07:35 | syzop | Note Edited: 0022415 | |
| 2022-03-23 07:37 | syzop | Note Edited: 0022415 | |
| 2022-03-23 07:46 | syzop | Assigned To | => syzop |
| 2022-03-23 07:46 | syzop | Status | new => feedback |
| 2022-03-23 13:28 | armyn | Note Added: 0022423 | |
| 2022-03-23 13:35 | armyn | Note Added: 0022424 | |
| 2022-03-23 13:56 | syzop | Status | feedback => closed |
| 2022-03-23 13:56 | syzop | Resolution | open => no change required |
| 2022-03-23 13:56 | syzop | Note Added: 0022425 |
