Sending 155k messages to client causes client communication to fail. #502

New Issue

2026-10-05T04:25:30+02:00

adam commented

2026-10-05 04:25:30 +02:00

I have a custom log module at https://github.com/GRMrGecko/LogSQL which I have not played back in 2 days, so 2 days worth of messages is needing to be received by my client and that adds up to 155,160 messages. With ZNC 1.2, this was handled just fine. But when I decided to try upgrading, first to 1.6 then to 1.7.x, ZNC could not handle this.

On the versions I tested, ZNC will only send 6,993 messages back to the client and after that, ZNC will no longer be able to send messages to the client however the client is able to send messages to ZNC.

The number is very close to 7k, which makes me think there is some kind of limit in the newer versions of ZNC that caps out at 7K. If that is the case, how do I disable this so called limit, or increase it to 999,999?

Thanks for any help on this. I am surviving by downgrading back to ZNC 1.2.

I have a custom log module at https://github.com/GRMrGecko/LogSQL which I have not played back in 2 days, so 2 days worth of messages is needing to be received by my client and that adds up to 155,160 messages. With ZNC 1.2, this was handled just fine. But when I decided to try upgrading, first to 1.6 then to 1.7.x, ZNC could not handle this. On the versions I tested, ZNC will only send 6,993 messages back to the client and after that, ZNC will no longer be able to send messages to the client however the client is able to send messages to ZNC. The number is very close to 7k, which makes me think there is some kind of limit in the newer versions of ZNC that caps out at 7K. If that is the case, how do I disable this so called limit, or increase it to 999,999? Thanks for any help on this. I am surviving by downgrading back to ZNC 1.2.

adam closed this issue

2026-10-05 04:25:30 +02:00

adam commented

2026-10-05 04:25:31 +02:00

I don't have any idea on this issue, but

I am surviving by downgrading back to ZNC 1.2.

1.4 was security fix release and you probably want to use at least it.

I don't have any idea on this issue, but > I am surviving by downgrading back to ZNC 1.2. 1.4 was security fix release and you probably want to use at least it. - http://wiki.znc.in/ChangeLog/1.4 - http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-9403

adam commented

2026-10-05 04:25:32 +02:00

Well, debug your module. znc -D, gdb, strace, etc. can help you with this.
You use PutUser(), right? There's no any special limit for it.

Well, debug your module. `znc -D`, gdb, strace, etc. can help you with this. You use `PutUser()`, right? There's no any special limit for it.

adam commented

2026-10-05 04:25:32 +02:00

If you're sure 1.2 handled this, you can try also git bisect

If you're sure 1.2 handled this, you can try also `git bisect`

adam commented

2026-10-05 04:25:33 +02:00

I debugged with -D already and saw that it says that all messages were sent. One thing I didn't think of doing is searching for the last UNIX time that was sent and looking for any messages. I don't really have time for that now as homework is available and work starts tomorrow.

I debugged with -D already and saw that it says that all messages were sent. One thing I didn't think of doing is searching for the last UNIX time that was sent and looking for any messages. I don't really have time for that now as homework is available and work starts tomorrow.

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: adam/znc#502