View Issue Details

IDProjectCategoryView StatusLast Update
0001691unrealircdpublic2004-06-24 20:18
Reportermedice Assigned To 
PrioritynormalSeveritytrivialReproducibilityalways
Status closedResolutionopen 
Product Version3.2 
Summary0001691: /stats P miscounting...
Description"some.servername"- *** Listener on "some.IP":6668, clients -1. is PERM clientsonly

as a matter of fact i don't believe in -1 clients at all ;)

version RC2 (fix) - compiled zip and SSL (ssl not used/configed)

another server in network has even more misfits:

** Listener on *:6667, clients -2236315. is PERM

while this server only listens on 6667 for users...

all the other servers do also have wrong counts, some users are seemingly missing... (compared with /map data)
Additional Informationno modules except my own server - latest version of the bopm-helper-module

hopefully i didn't miss any prior-matching bug-report...
3rd party modules

Activities

medice

2004-03-30 13:12

reporter   ~0005686

sorry - totally miss-clicked the categoty and severity-fields...

codemastr

2004-04-07 18:24

reporter   ~0005779

*** This seems to be the second part of the thing fez reported, we've found out how to reproduce it so it should be fixed soon.

medice

2004-05-24 18:32

reporter   ~0006402

as a new hint for you, i hope helpful ;):

this miscounts together with ssl-compiles seems only affect hub-compiles
maybe it's only hub-compiles and the ssl-fact is not even important...

Rocko

2004-06-14 05:52

reporter   ~0006641

The problem isn't only, that it shows wrong counts, it prevents Ports to be unbinded.

When there is no client on the Port, and it shows this:
*** (s) *** Listener on ::ffff:123.456.789.12:6670, clients 1. is TEMPORARY clientsonly SSL

This Port won't be unbinded until a restart, and that's bad ;)

codemastr

2004-06-17 00:17

reporter   ~0006665

I agree, this is more serious than just a display error. Syzop, is there any chance you could look into this? Somewhere (if you don't remember my telling you) I wrote down the cause, and I also had a possible fix, I just wasn't sure if my fix would break anything else...

syzop

2004-06-24 20:18

administrator   ~0006775

Should be fixed in .69.

It seemed it was possible to trigger it in even more ways than I thought (even disconnecting a succesfull link triggers this), so I just added a 'outgoing' flag.. if set it doesn't decrease cptr->listener->clients ;).

Issue History

Date Modified Username Field Change
2004-03-30 07:24 medice New Issue
2004-03-30 13:12 medice Note Added: 0005686
2004-04-07 18:24 codemastr Note Added: 0005779
2004-04-07 18:25 codemastr Status new => confirmed
2004-04-07 18:25 codemastr ETA none => < 1 week
2004-05-24 18:32 medice Note Added: 0006402
2004-05-26 00:33 syzop Severity feature => trivial
2004-05-26 00:33 syzop Category documentation => ircd
2004-05-26 00:33 syzop ETA < 1 week => none
2004-05-26 00:33 syzop Product Version => 3.2
2004-06-14 05:52 Rocko Note Added: 0006641
2004-06-17 00:17 codemastr Note Added: 0006665
2004-06-24 20:18 syzop Status confirmed => closed
2004-06-24 20:18 syzop Note Added: 0006775