Reconnect blocking
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
shroudBNC |
Confirmed
|
High
|
Gunnar Beutner |
Bug Description
Since the three bugs are closely related I'm going to post them as a single post, especially since there is already about 5 bugs related to this one already posted but don't quite address the issue.
Bug1: For some reason even with the current patches if a reconnect attempt fails (can be ipv4 or ipv6) that user will be unable to reconnect untill the bnc is restarted.
Note: Possibly fixed in latest git.
Bug2: sBNC seems to only allow 'x' number of users to be added to the reconnect 'loop' that is, if there is 20+ users to be reconnected, the bnc will only try the first 4 or so over and over until one of those users reconnects. If for some reason a irc server is down, this would prevent other users on the bnc reconnecting.
http://
Bug3:
For some reason when connecting, some event caused the bnc to get stuck reconnecting a single user.
http://
description: | updated |
Changed in shroudbnc: | |
importance: | Undecided → High |
assignee: | nobody → Gunnar Beutner (gunnarbeutner) |
milestone: | none → 1.3 |
description: | updated |
description: | updated |
I cannot confirm your first issue: I had a connection timeout while connecting to QuakeNet, yet the user recovered from that and connected on a latter attempt just fine.