Anope IRC Services
Anope Support => 2.0.x/1.9.x Support => Topic started by: lordcow on December 31, 2012, 10:23:33 AM
-
Hi, we're using git commit 8d0b4a1bf53788494fe0531dd62b4dd2ee655e9b and have noticed a few clients being killed for being over the session limit when they weren't.
Operserv listed this host with 17 connections even after it had banned the host:
-> Operserv session list 3
-OperServ- Hosts with at least 3 sessions:
..
-OperServ- 17 41.76.XX/32
and still thought these clients were connected when they weren't:
-> Operserv userlist *!*@41.76.XX
-OperServ- Users list:
-OperServ- Name Mask
-OperServ- HugoBoss chat27.co.za@atrum-9uu.tip.76.41.IP
-OperServ- Ivanka|afk ivanka@atrum-9uu.tip.76.41.IP
-OperServ- End of users list.
Naturally when we removed the akill it was set again when 1 client reconnected. At the moment we're just setting exceptions to get around this.
-
Hello,
Thanks for this, do you have steps to reproduce this?
How many IRCDs are linked in your network? (and what is the topology laid out like with hubs/leaves/services)
-
Hey nope, it's randomly hit 3 different hosts so I figured it was a memory leak.
We've got 2 hubs and 5 leaves (InspIRCd-2.0.5) with anope sitting on one of the hubs.