View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0006219 | unreal | ircd | public | 2023-02-03 15:05 | 2023-03-19 11:16 |
| Reporter | armyn | Assigned To | syzop | ||
| Priority | normal | Severity | major | Reproducibility | sometimes |
| Status | closed | Resolution | no change required | ||
| Product Version | 6.0.5 | ||||
| Summary | 0006219: An issue with SASL not doing this before UnrealIRCd 6.0.4 or not before Anope 2.0.11 | ||||
| Description | Sometimes when I disconnect all users by shutting down nodejs for example, it disconnects about 200-500 people, and then I do an update, when I restart all clients and they reconnect, it kind of goes flood connection because everyone reconnects at the same time and then there is a problem with SASL, no one can identify with SASL anymore because the SASL has bugged or this service is not found or it is freez.. . This shows an error message, I believe there is the word "aborted" and "sasl" in the error message. Do you know where it can come from? The trick I found is to always restart Anope before all users reconnect en masse/automatically. | ||||
| Tags | No tags attached. | ||||
| 3rd party modules | |||||
|
|
Ah also I forgot to say: It's the whole sasl service that is down, even with mIRC I can no longer identify myself. The only solution found is to restart Anope. |
|
|
Do the anope logs have any useful information? |
|
|
I just cut everyone (all disconnected) without touching Anope and with my irc web client I get this: SASL request timed out (server or client misbehaving) -- aborting SASL and continuing connection... Then now it's good he agreed to connect to the relaunch Then I decide to reconnect with mIRC (in sasl as usual) and there I see this: <- :irc.d.com NOTICE Gk :SASL request timed out (server or client misbehaving) -- aborting SASL and continuing connection... <-:irc.d.com 906 Gk:SASL authentication aborted -> irc.d.com CAP LIST -> irc.d.com CAP END <- :irc.d.com CAP Gk LIST :away-notify invite-notify extended-join userhost-in-names multi-prefix cap-notify sasl=EXTERNAL,PLAIN setname chghost account-notify message-tags batch server-time account -tag labeled-response So it's NickServ that asks to identify itself with the command /nickserv id ... I'm not interested There a moment ago I reconnected with mIRC and he agreed to reconnect with SASL With the irc web client it's good too, it seemed temporary. Looks like it's related to this but not sure: flood.FLOOD_BLOCKED [info] Flood blocked (target-flood-user) from because a lot of people have this on connection and, maybe sasl hangs at the same time but it seems temporary finally so no need to restart anope, just have to wait maybe 5 minutes if we receive this error: SASL request timed out (server or client misbehaving) -- aborting SASL and continuing connection... |
|
|
It shows nothing in the anope log |
|
|
I tried connecting 500 clones with SASL, disconnecting, reconnecting, it all works fine. Sure it takes maybe up to 30 seconds for all 500 clones to connect but that's mainly because i am in debugmode, but it works OK. So yeah.. not sure. Also not sure how to help you debug this :/ |
|
|
My best guess would be that your anope is too slow, goes to 100% CPU usage, and then the SASL times out. But.. only you can tell by running 'top' or something similar on the machine when this happens. I don't see how anything would be wrong on our side (in UnrealIRCd), and my tests which were highly aggressive did not reproduce the issue. So I'm closing this because I don't think it is an issue in UnrealIRCd at the moment. Of course, can never be 100% sure but for now it certainly is looking that way. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2023-02-03 15:05 | armyn | New Issue | |
| 2023-02-03 15:07 | armyn | Note Added: 0022720 | |
| 2023-02-03 15:37 | syzop | Note Added: 0022721 | |
| 2023-02-03 16:49 | armyn | Note Added: 0022722 | |
| 2023-02-03 16:50 | armyn | Note Added: 0022723 | |
| 2023-02-03 17:39 | syzop | Note Added: 0022724 | |
| 2023-02-03 17:40 | syzop | Note Edited: 0022724 | |
| 2023-03-19 11:16 | syzop | Assigned To | => syzop |
| 2023-03-19 11:16 | syzop | Status | new => closed |
| 2023-03-19 11:16 | syzop | Resolution | open => no change required |
| 2023-03-19 11:16 | syzop | Note Added: 0022787 |
