I am using ZNC 1.9.1 with Gentoo as my main bouncer. I noticed, that I have a very strange behauvior. Send messages are being extremly delayed and its possible, that other people see them weeks later. Not a single error is shown on my client. When I do send a message, it's being shown on my chatlog normally, but apperntly in reality, it has not been send. But at the same time, I am receiving messages from channel without any problems. Apparently those messages are silently then send from days up to weeks later really send.
I have absolutly no idea, how to debug this. Any ideas?
I am using ZNC 1.9.1 with Gentoo as my main bouncer. I noticed, that I have a very strange behauvior. Send messages are being extremly delayed and its possible, that other people see them weeks later. Not a single error is shown on my client. When I do send a message, it's being shown on my chatlog normally, but apperntly in reality, it has not been send. But at the same time, I am receiving messages from channel without any problems. Apparently those messages are silently then send from days up to weeks later really send.
I have absolutly no idea, how to debug this. Any ideas?
<!-- github-sync-id:2997654800 -->
There may be a small delay caused by flood protection, but definitely not weeks. What are your settings for flood?
What modules are loaded?
There may be a small delay caused by flood protection, but definitely not weeks. What are your settings for flood?
What modules are loaded?
<!-- github-comment-id:2807547593 -->
Why have you set them to 100/100? That's the issue.
ZNC is sending to server no more than 1 line per 100 seconds.
The default values are rate=2, burst=9, please try those
Why have you set them to 100/100? That's the issue.
ZNC is sending to server no more than 1 line per 100 seconds.
The default values are rate=2, burst=9, please try those
<!-- github-comment-id:2807577573 -->
Why have you set them to 100/100? That's the issue.
I can't say, why I have set it. I haven't touched for a long time my config. Maybe just an error, which I never noticed or from some old version migration? Could you please explain me that option? Based on docs, burst set maximum count of lines to be send at once and rate sets a pause, when that limit is reached.
Give my wrong setting with 100/100, I don't understand, how that works as an issue? Wouldn't that mean, that first after sending 100 lines, I would hit flood protection, but in case for 100 seconds? Sending a single line into channel should never trigger that? Did I missunderstand something here?
ZNC is sending to server no more than 1 line per 100 seconds.
What do you mean by this?
The default values are rate=2, burst=9, please try those
Thank you, I've set back default and will observe.
> Why have you set them to 100/100? That's the issue.
I can't say, why I have set it. I haven't touched for a long time my config. Maybe just an error, which I never noticed or from some old version migration? Could you please explain me that option? Based on [docs](https://wiki.znc.in/Configuration), burst set maximum count of lines to be send at once and rate sets a pause, when that limit is reached.
Give my wrong setting with 100/100, I don't understand, how that works as an issue? Wouldn't that mean, that first after sending 100 lines, I would hit flood protection, but in case for 100 seconds? Sending a single line into channel should never trigger that? Did I missunderstand something here?
> ZNC is sending to server no more than 1 line per 100 seconds.
What do you mean by this?
> The default values are rate=2, burst=9, please try those
Thank you, I've set back default and will observe.
<!-- github-comment-id:2807598193 -->
There are Burst lines allowed to be sent. Every time the line is successfully sent, the counter is decreased. Every Rate seconds, the counter is increased (capped at Burst) and the next line from the queue is sent (decreasing the counter again).
So after your first 100, or maybe 150 messages the counter is always near 0, and since that moment you can only send 1 message per 100 seconds. That includes PONG, NAMES and other internal messages, not only PRIVMSG.
Because server doesn't see any traffic from you for 100 seconds, it starts sending PINGs. But PONGs are put in front of the queue to avoid disconnects. So most of this slow traffic will probably be just PONGs, and anything else will happen to be sent more rarely
There are Burst lines allowed to be sent. Every time the line is successfully sent, the counter is decreased. Every Rate seconds, the counter is increased (capped at Burst) and the next line from the queue is sent (decreasing the counter again).
So after your first 100, or maybe 150 messages the counter is always near 0, and since that moment you can only send 1 message per 100 seconds. That includes PONG, NAMES and other internal messages, not only PRIVMSG.
Because server doesn't see any traffic from you for 100 seconds, it starts sending PINGs. But PONGs are put in front of the queue to avoid disconnects. So most of this slow traffic will probably be just PONGs, and anything else will happen to be sent more rarely
<!-- github-comment-id:2807617497 -->
Whoops. I understand the problem now. That would perfectly explain the issue ineed. Thanks for spotting this. I will observe this the next days, and close the issue then. But I guess, it should now work afte restart.
Whoops. I understand the problem now. That would perfectly explain the issue ineed. Thanks for spotting this. I will observe this the next days, and close the issue then. But I guess, it should now work afte restart.
<!-- github-comment-id:2807625905 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
I am using ZNC 1.9.1 with Gentoo as my main bouncer. I noticed, that I have a very strange behauvior. Send messages are being extremly delayed and its possible, that other people see them weeks later. Not a single error is shown on my client. When I do send a message, it's being shown on my chatlog normally, but apperntly in reality, it has not been send. But at the same time, I am receiving messages from channel without any problems. Apparently those messages are silently then send from days up to weeks later really send.
I have absolutly no idea, how to debug this. Any ideas?
There may be a small delay caused by flood protection, but definitely not weeks. What are your settings for flood?
What modules are loaded?
Flooding-protection: enabled
Flood rate: 100.00
Flood burst: 100
Channel entry delay: 0
You mean this?
Why have you set them to 100/100? That's the issue.
ZNC is sending to server no more than 1 line per 100 seconds.
The default values are rate=2, burst=9, please try those
I can't say, why I have set it. I haven't touched for a long time my config. Maybe just an error, which I never noticed or from some old version migration? Could you please explain me that option? Based on docs, burst set maximum count of lines to be send at once and rate sets a pause, when that limit is reached.
Give my wrong setting with 100/100, I don't understand, how that works as an issue? Wouldn't that mean, that first after sending 100 lines, I would hit flood protection, but in case for 100 seconds? Sending a single line into channel should never trigger that? Did I missunderstand something here?
What do you mean by this?
Thank you, I've set back default and will observe.
There are Burst lines allowed to be sent. Every time the line is successfully sent, the counter is decreased. Every Rate seconds, the counter is increased (capped at Burst) and the next line from the queue is sent (decreasing the counter again).
So after your first 100, or maybe 150 messages the counter is always near 0, and since that moment you can only send 1 message per 100 seconds. That includes PONG, NAMES and other internal messages, not only PRIVMSG.
Because server doesn't see any traffic from you for 100 seconds, it starts sending PINGs. But PONGs are put in front of the queue to avoid disconnects. So most of this slow traffic will probably be just PONGs, and anything else will happen to be sent more rarely
Whoops. I understand the problem now. That would perfectly explain the issue ineed. Thanks for spotting this. I will observe this the next days, and close the issue then. But I guess, it should now work afte restart.
I tend to say, its now fixed. Thanks again.