Anope IRC Services

Please login or register.

Login with username, password and session length
Advanced search  


Pages: [1]   Go Down

Author Topic: Session limit leak  (Read 3014 times)

0 Members and 1 Guest are viewing this topic.


  • Anope User
  • Offline Offline
  • Posts: 13
Session limit leak
« 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
-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.

Charles Kingsley

  • Contributor
  • *
  • Offline Offline
  • Posts: 1405
Re: Session limit leak
« Reply #1 on: December 31, 2012, 10:41:50 AM »


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)


  • Anope User
  • Offline Offline
  • Posts: 13
Re: Session limit leak
« Reply #2 on: December 31, 2012, 10:55:53 AM »

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.
Pages: [1]   Go Up