ZNC disconnects every 33 minutes from freenode server #298

New Issue

2026-10-05T04:11:11+02:00

adam commented

2026-10-05 04:11:11 +02:00

I'm running version 1.2-6 of ZNC on DSM 4.3.
If a client is attached to the bouncer everything works just fine. As soon as I close my client, ZNC starts disconnecting from the freenode server every 33 minutes or so. Like this:
[21:51:28] Disconnected from IRC (kornbluth.freenode.net +7070)
[21:51:43] Connected to IRC (kornbluth.freenode.net +7070)
[22:25:29] Disconnected from IRC (kornbluth.freenode.net +7070)
[22:25:45] Connected to IRC (kornbluth.freenode.net +7070)
And so on.
I've already asked for help on SynoCommunity but they told me that "this is most likely not package related I suggest you seek help upstream to ZNC directly."
Is there some settings I should check? Thanks.

I'm running version 1.2-6 of ZNC on DSM 4.3. If a client is attached to the bouncer everything works just fine. As soon as I close my client, ZNC starts disconnecting from the freenode server every 33 minutes or so. Like this: [21:51:28] Disconnected from IRC (kornbluth.freenode.net +7070) [21:51:43] Connected to IRC (kornbluth.freenode.net +7070) [22:25:29] Disconnected from IRC (kornbluth.freenode.net +7070) [22:25:45] Connected to IRC (kornbluth.freenode.net +7070) And so on. I've already asked for help on SynoCommunity but they told me that "this is most likely not package related I suggest you seek help upstream to ZNC directly." Is there some settings I should check? Thanks.

adam closed this issue

2026-10-05 04:11:11 +02:00

adam commented

2026-10-05 04:11:12 +02:00

Show output of znc -D (remove any passwords from it before)

Show output of `znc -D` (remove any passwords from it before)

adam commented

2026-10-05 04:11:13 +02:00

This is what I get:

Starting ZNC ...
[ ok ] Checking for list of available modules...
[ ok ] Opening config [/usr/local/znc/var/configs/znc.conf]...
[ ok ] Loading global module [webadmin]... [/usr/local/znc/lib/znc/webadmin.so]
[ ok ] Loading global module [adminlog]... [/usr/local/znc/lib/znc/adminlog.so]
[ ok ] Loading global module [certauth]... [/usr/local/znc/lib/znc/certauth.so]
[ ] Loading global module [log]... Logging to [/usr/local/znc/var/moddata/log/$USER_$NETWORK_$WINDOW_%Y%m%d.log].[Logging to [/usr/local/znc/var/moddata/log/$USER_$NETWORK_$WINDOW_%Y%m%d.l[ ok ][/usr/local/znc/lib/znc/log.so]
[ ok ] Binding to port [8250] on host [0.0.0.0] using ipv4...
[ ** ] Loading user [calvin]
[ ** ] Loading network [freenode]
[ ok ] Loading network module [chansaver]... [/usr/local/znc/lib/znc/chansaver.so]
[ ok ] Loading network module [keepnick]... [/usr/local/znc/lib/znc/keepnick.so]
[ ok ] Loading network module [kickrejoin]... [/usr/local/znc/lib/znc/kickrejoin.so]
[ ok ] Loading network module [simple_away]... [/usr/local/znc/lib/znc/simple_away.so]
[ ok ] Loading network module [nickserv]... [/usr/local/znc/lib/znc/nickserv.so]
[ ok ] Adding server [kornbluth.freenode.net +7070 MyPassword]...
[ ok ] Loading user module [chansaver]... [/usr/local/znc/lib/znc/chansaver.so]
[ ok ] Loading user module [clientnotify]... [/usr/local/znc/lib/znc/clientnotify.so]
[ ok ] Loading user module [dcc]... [/usr/local/znc/lib/znc/dcc.so]
[ ] Loading user module [log]... Logging to [/usr/local/znc/var/users/calvin/moddata/log/$NETWORK_$WINDOW_%Y%m%d.log].[Logging to [/usr/local/znc/var/users/calvin/moddata/log/$NETWORK_$WIN[ ok ]%m%d.log].] [/usr/local/znc/lib/znc/log.so]
[ ok ] Loading user module [webadmin]... [/usr/local/znc/lib/znc/webadmin.so]
[ ok ] Forking into the background... [pid: 8400]
[ ok ] Writing pid file [/usr/local/znc/var/znc.pid]...
[ ** ] ZNC 1.2 - http://znc.in

Then it comes back to the command prompt.

This is what I get: Starting ZNC ... [ ok ] Checking for list of available modules... [ ok ] Opening config [/usr/local/znc/var/configs/znc.conf]... [ ok ] Loading global module [webadmin]... [/usr/local/znc/lib/znc/webadmin.so] [ ok ] Loading global module [adminlog]... [/usr/local/znc/lib/znc/adminlog.so] [ ok ] Loading global module [certauth]... [/usr/local/znc/lib/znc/certauth.so] [ ] Loading global module [log]... Logging to [/usr/local/znc/var/moddata/log/$USER_$NETWORK_$WINDOW_%Y%m%d.log].[Logging to [/usr/local/znc/var/moddata/log/$USER_$NETWORK_$WINDOW_%Y%m%d.l[ ok ][/usr/local/znc/lib/znc/log.so] [ ok ] Binding to port [8250] on host [0.0.0.0] using ipv4... [ *\* ] Loading user [calvin] [ *\* ] Loading network [freenode] [ ok ] Loading network module [chansaver]... [/usr/local/znc/lib/znc/chansaver.so] [ ok ] Loading network module [keepnick]... [/usr/local/znc/lib/znc/keepnick.so] [ ok ] Loading network module [kickrejoin]... [/usr/local/znc/lib/znc/kickrejoin.so] [ ok ] Loading network module [simple_away]... [/usr/local/znc/lib/znc/simple_away.so] [ ok ] Loading network module [nickserv]... [/usr/local/znc/lib/znc/nickserv.so] [ ok ] Adding server [kornbluth.freenode.net +7070 MyPassword]... [ ok ] Loading user module [chansaver]... [/usr/local/znc/lib/znc/chansaver.so] [ ok ] Loading user module [clientnotify]... [/usr/local/znc/lib/znc/clientnotify.so] [ ok ] Loading user module [dcc]... [/usr/local/znc/lib/znc/dcc.so] [ ] Loading user module [log]... Logging to [/usr/local/znc/var/users/calvin/moddata/log/$NETWORK_$WINDOW_%Y%m%d.log].[Logging to [/usr/local/znc/var/users/calvin/moddata/log/$NETWORK_$WIN[ ok ]%m%d.log].] [/usr/local/znc/lib/znc/log.so] [ ok ] Loading user module [webadmin]... [/usr/local/znc/lib/znc/webadmin.so] [ ok ] Forking into the background... [pid: 8400] [ ok ] Writing pid file [/usr/local/znc/var/znc.pid]... [ *\* ] ZNC 1.2 - http://znc.in Then it comes back to the command prompt.

adam commented

2026-10-05 04:11:14 +02:00

This is not -D

10.02.2014 22:31, damfino пишет:

This is what I get:

Starting ZNC ...
[ ok ] Checking for list of available modules...
[ ok ] Opening config [/usr/local/znc/var/configs/znc.conf]...
[ ok ] Loading global module [webadmin]...
[/usr/local/znc/lib/znc/webadmin.so]
[ ok ] Loading global module [adminlog]...
[/usr/local/znc/lib/znc/adminlog.so]
[ ok ] Loading global module [certauth]...
[/usr/local/znc/lib/znc/certauth.so]
[ ] Loading global module [log]... Logging to
[/usr/local/znc/var/moddata/log/$USER_$NETWORK_$WINDOW_%Y%m%d.log].[Logging
to [/usr/local/znc/var/moddata/log/$USER_$NETWORK_$WINDOW_%Y%m%d.l[ ok
][/usr/local/znc/lib/znc/log.so]
[ ok ] Binding to port [8250] on host [0.0.0.0] using ipv4...
[ ** ] Loading user [calvin]
[ ** ] Loading network [freenode]
[ ok ] Loading network module [chansaver]...
[/usr/local/znc/lib/znc/chansaver.so]
[ ok ] Loading network module [keepnick]...
[/usr/local/znc/lib/znc/keepnick.so]
[ ok ] Loading network module [kickrejoin]...
[/usr/local/znc/lib/znc/kickrejoin.so]
[ ok ] Loading network module [simple_away]...
[/usr/local/znc/lib/znc/simple_away.so]
[ ok ] Loading network module [nickserv]...
[/usr/local/znc/lib/znc/nickserv.so]
[ ok ] Adding server [kornbluth.freenode.net +7070 MyPassword]...
[ ok ] Loading user module [chansaver]...
[/usr/local/znc/lib/znc/chansaver.so]
[ ok ] Loading user module [clientnotify]...
[/usr/local/znc/lib/znc/clientnotify.so]
[ ok ] Loading user module [dcc]... [/usr/local/znc/lib/znc/dcc.so]
[ ] Loading user module [log]... Logging to
[/usr/local/znc/var/users/calvin/moddata/log/$NETWORK_$WINDOW_%Y%m%d.log].[Logging
to [/usr/local/znc/var/users/calvin/moddata/log/$NETWORK_$WIN[ ok
]%m%d.log].] [/usr/local/znc/lib/znc/log.so]
[ ok ] Loading user module [webadmin]...
[/usr/local/znc/lib/znc/webadmin.so]
[ ok ] Forking into the background... [pid: 8400]
[ ok ] Writing pid file [/usr/local/znc/var/znc.pid]...
[ ** ] ZNC 1.2 - http://znc.in

—
Reply to this email directly or view it on GitHub
https://github.com/znc/znc/issues/487#issuecomment-34692158.

This is not -D 10.02.2014 22:31, damfino пишет: > This is what I get: > > Starting ZNC ... > [ ok ] Checking for list of available modules... > [ ok ] Opening config [/usr/local/znc/var/configs/znc.conf]... > [ ok ] Loading global module [webadmin]... > [/usr/local/znc/lib/znc/webadmin.so] > [ ok ] Loading global module [adminlog]... > [/usr/local/znc/lib/znc/adminlog.so] > [ ok ] Loading global module [certauth]... > [/usr/local/znc/lib/znc/certauth.so] > [ ] Loading global module [log]... Logging to > [/usr/local/znc/var/moddata/log/$USER_$NETWORK_$WINDOW_%Y%m%d.log].[Logging > to [/usr/local/znc/var/moddata/log/$USER_$NETWORK_$WINDOW_%Y%m%d.l[ ok > ][/usr/local/znc/lib/znc/log.so] > [ ok ] Binding to port [8250] on host [0.0.0.0] using ipv4... > [ *\* ] Loading user [calvin] > [ *\* ] Loading network [freenode] > [ ok ] Loading network module [chansaver]... > [/usr/local/znc/lib/znc/chansaver.so] > [ ok ] Loading network module [keepnick]... > [/usr/local/znc/lib/znc/keepnick.so] > [ ok ] Loading network module [kickrejoin]... > [/usr/local/znc/lib/znc/kickrejoin.so] > [ ok ] Loading network module [simple_away]... > [/usr/local/znc/lib/znc/simple_away.so] > [ ok ] Loading network module [nickserv]... > [/usr/local/znc/lib/znc/nickserv.so] > [ ok ] Adding server [kornbluth.freenode.net +7070 MyPassword]... > [ ok ] Loading user module [chansaver]... > [/usr/local/znc/lib/znc/chansaver.so] > [ ok ] Loading user module [clientnotify]... > [/usr/local/znc/lib/znc/clientnotify.so] > [ ok ] Loading user module [dcc]... [/usr/local/znc/lib/znc/dcc.so] > [ ] Loading user module [log]... Logging to > [/usr/local/znc/var/users/calvin/moddata/log/$NETWORK_$WINDOW_%Y%m%d.log].[Logging > to [/usr/local/znc/var/users/calvin/moddata/log/$NETWORK_$WIN[ ok > ]%m%d.log].] [/usr/local/znc/lib/znc/log.so] > [ ok ] Loading user module [webadmin]... > [/usr/local/znc/lib/znc/webadmin.so] > [ ok ] Forking into the background... [pid: 8400] > [ ok ] Writing pid file [/usr/local/znc/var/znc.pid]... > [ *\* ] ZNC 1.2 - http://znc.in > > — > Reply to this email directly or view it on GitHub > https://github.com/znc/znc/issues/487#issuecomment-34692158.

adam commented

2026-10-05 04:11:14 +02:00

Sorry, my bad. ZNC on DSM starts using a script and that whas the output of script -D.
Anyway, I managed to make it starts directly and the output text file is 221 Kb, so I put the file on Dropbox:

https://dl.dropboxusercontent.com/u/1832920/ZNCTest.log

It seems to me that the interesting part is this one:
2014-02-11 13:23:30.604352 IRC -> ZNC [PING :kornbluth.freenode.net]
2014-02-11 13:23:30.604545 ZNC -> IRC [PONG :kornbluth.freenode.net]
2014-02-11 13:28:14.181992 ZNC -> IRC [PING :ZNC]
[2014-02-11 13:28:14.250429] IRC::calvin::freenode == SockError(104 Connection reset by peer)
[2014-02-11 13:28:14.251660] IRC::calvin::freenode == Disconnected()
2014-02-11 13:28:14.251997 ZNC -> IRC [QUIT :ZNC - http://znc.in]

Thank you for your patience.

Sorry, my bad. ZNC on DSM starts using a script and that whas the output of script -D. Anyway, I managed to make it starts directly and the output text file is 221 Kb, so I put the file on Dropbox: https://dl.dropboxusercontent.com/u/1832920/ZNCTest.log It seems to me that the interesting part is this one: [2014-02-11 13:23:30.604352](calvin/freenode) IRC -> ZNC [PING :kornbluth.freenode.net] [2014-02-11 13:23:30.604545](calvin/freenode) ZNC -> IRC [PONG :kornbluth.freenode.net] [2014-02-11 13:28:14.181992](calvin/freenode) ZNC -> IRC [PING :ZNC] [2014-02-11 13:28:14.250429] IRC::calvin::freenode == SockError(104 Connection reset by peer) [2014-02-11 13:28:14.251660] IRC::calvin::freenode == Disconnected() [2014-02-11 13:28:14.251997](calvin/freenode) ZNC -> IRC [QUIT :ZNC - http://znc.in] Thank you for your patience.

adam commented

2026-10-05 04:11:15 +02:00

How does the disconnect look from IRC side?
Usually server pings ZNC every 2 minutes, according to those logs. But for some reason nothing comes from server for ~5 min
Do you have some kind of NAT between DSM and internet?

How does the disconnect look from IRC side? Usually server pings ZNC every 2 minutes, according to those logs. But for some reason nothing comes from server for ~5 min Do you have some kind of NAT between DSM and internet?

adam commented

2026-10-05 04:11:16 +02:00

Other IRC users told me that the reason I get disconnected is always ping timeout. And no, I don't think I have any kind of NAT issue between my NAS and the internet.
But listen to this: I did a test using another IRC network, OFTC, and guess what? No disconnections. The remote server answers to ZNC Ping requests and nothing nasty happens:

2014-02-12 14:34:57.967397 ZNC -> IRC [PING :ZNC]
2014-02-12 14:35:03.354334 IRC -> ZNC [PING :oxygen.oftc.net]
2014-02-12 14:35:03.354529 ZNC -> IRC [PONG :oxygen.oftc.net]
2014-02-12 14:35:03.354985 IRC -> ZNC [:oxygen.oftc.net PONG oxygen.oftc.net :ZNC]
2014-02-12 14:39:07.967129 IRC -> ZNC [PING :oxygen.oftc.net]
2014-02-12 14:39:07.967337 ZNC -> IRC [PONG :oxygen.oftc.net]

If you need to look at the whole session, I've uploaded the file to Dropbox:

https://dl.dropboxusercontent.com/u/1832920/OFTCTest.log

Other IRC users told me that the reason I get disconnected is always ping timeout. And no, I don't think I have any kind of NAT issue between my NAS and the internet. But listen to this: I did a test using another IRC network, OFTC, and guess what? No disconnections. The remote server answers to ZNC Ping requests and nothing nasty happens: [2014-02-12 14:34:57.967397](calvin/oftc) ZNC -> IRC [PING :ZNC] [2014-02-12 14:35:03.354334](calvin/oftc) IRC -> ZNC [PING :oxygen.oftc.net] [2014-02-12 14:35:03.354529](calvin/oftc) ZNC -> IRC [PONG :oxygen.oftc.net] [2014-02-12 14:35:03.354985](calvin/oftc) IRC -> ZNC [:oxygen.oftc.net PONG oxygen.oftc.net :ZNC] [2014-02-12 14:39:07.967129](calvin/oftc) IRC -> ZNC [PING :oxygen.oftc.net] [2014-02-12 14:39:07.967337](calvin/oftc) ZNC -> IRC [PONG :oxygen.oftc.net] If you need to look at the whole session, I've uploaded the file to Dropbox: https://dl.dropboxusercontent.com/u/1832920/OFTCTest.log

adam commented

2026-10-05 04:11:17 +02:00

freenode recently had some network issues, probably that's the reason?

freenode recently had some network issues, probably that's the reason?

adam commented

2026-10-05 04:11:17 +02:00

Do you mean that freenode doesn't answer to ping requests on purpose? I have no idea. It would be interesting to see if this happens only with ZNC 1.2 for DSM. Could you please be so kind to verify that on your system? Thanks.

Do you mean that freenode doesn't answer to ping requests on purpose? I have no idea. It would be interesting to see if this happens only with ZNC 1.2 for DSM. Could you please be so kind to verify that on your system? Thanks.

adam commented

2026-10-05 04:11:18 +02:00

For me everything works just fine. But I don't have DSM

14.02.2014 02:30, damfino пишет:

Do you mean that freenode doesn't answer to ping requests on purpose?
I have no idea. It would be interesting to see if this happens only
with ZNC 1.2 for DSM. Could you please be so kind to verify that on
your system? Thanks.

—
Reply to this email directly or view it on GitHub
https://github.com/znc/znc/issues/487#issuecomment-35050139.

For me everything works just fine. But I don't have DSM 14.02.2014 02:30, damfino пишет: > Do you mean that freenode doesn't answer to ping requests on purpose? > I have no idea. It would be interesting to see if this happens only > with ZNC 1.2 for DSM. Could you please be so kind to verify that on > your system? Thanks. > > — > Reply to this email directly or view it on GitHub > https://github.com/znc/znc/issues/487#issuecomment-35050139.

adam commented

2026-10-05 04:11:19 +02:00

Is this resolved? I still see the same behavior on Freenode with my ZNC

Is this resolved? I still see the same behavior on Freenode with my ZNC

adam commented

2026-10-05 04:11:19 +02:00

@alolis /msg *status version

@alolis `/msg *status version`

adam commented

2026-10-05 04:11:20 +02:00

@Mikaela

 <*status>  ZNC 1.2 - http://znc.in
 <*status>  IPv6: yes, SSL: yes, DNS: threads

The disconnects on my case are within 5 minutes.

@Mikaela ``` <*status> ZNC 1.2 - http://znc.in <*status> IPv6: yes, SSL: yes, DNS: threads ``` The disconnects on my case are within 5 minutes.

adam commented

2026-10-05 04:11:21 +02:00

@alolis ZNC 1.2 is 1.5 years old and not supported by ZNC. Please upgrade to 1.6.0 or 1.6.1-rc1.

@alolis ZNC 1.2 is 1.5 years old and not supported by ZNC. Please upgrade to 1.6.0 or 1.6.1-rc1.

adam commented

2026-10-05 04:11:21 +02:00

@Mikaela , I will give it a go, thanks

@Mikaela , I will give it a go, thanks

adam commented

2026-10-05 04:11:22 +02:00

@alolis did newer version fix the issue?

I am wondering if this could be closed.

@alolis did newer version fix the issue? I am wondering if this could be closed.

adam commented

2026-10-05 04:11:23 +02:00

@Mikaela , well, I have been using the following version:

<*status> ZNC - 1.6.0 - http://znc.in

and indeed the situation is better. I do notice disconnects every now and then like the ones I was noticing before but definitely not as often. I am using znc on Freenode, not sure if the irc server plays a part on the problem. It's not every 33 minutes or any specific period, it just happens every now and then.

A friend has mentioned the exact same problem on Freenode as well. If you need a specific test I can try it out.

@Mikaela , well, I have been using the following version: `<*status> ZNC - 1.6.0 - http://znc.in` and indeed the situation is better. I do notice disconnects every now and then like the ones I was noticing before but definitely not as often. I am using znc on Freenode, not sure if the irc server plays a part on the problem. It's not every 33 minutes or any specific period, it just happens every now and then. A friend has mentioned the exact same problem on Freenode as well. If you need a specific test I can try it out.

adam commented

2026-10-05 04:11:23 +02:00

I think this might be closable then depending on how often that is. Freenode often has DDoS issues and the previous one was few week(s) ago, I think.

I think this might be closable then depending on how often that is. Freenode often has DDoS issues and the previous one was few week(s) ago, I think.

adam commented

2026-10-05 04:11:24 +02:00

Maybe you are right. I haven't seen anything weird the last 3 days. You can close the issue if you want and I will just open a new one if i notice something out of the ordinary.

Maybe you are right. I haven't seen anything weird the last 3 days. You can close the issue if you want and I will just open a new one if i notice something out of the ordinary.

adam commented

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

Please leave a comment if the problem persists.

Please leave a comment if the problem persists.

adam commented

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

Apologies in advance for resurrecting such an old issue, But i seem to have come across the very same thing, on multiple occasions.

At first, I was running the znc-msvc builds, namely a ZNC 1.5 build running on a Windows 10 Intel NUC machine. Obviously that is quite old and somewhat unsupported, So i ended up running a self-compiled 1.6.3 from source, running in my local LAN on Raspbian (Raspberry Pi 3). The former Windows machine was on WiFi, the Pi is directly attached by ethernet to the router.

Machine(s) and/or connection doesn't seem to be dropping when this happens.
As noted, a client attached seems to alleviate this in some way, possibly because of a client's own pings to ZNC.

In both cases, I used the AdiIRC client for Windows, But I've also tried others, and as said, the problem is far less frequent when a client is attached.

Version output is as follows:

[22:38:56]  *status > ZNC 1.6.3 - http://znc.in
[22:38:56]  *status > IPv6: yes, SSL: yes, DNS: threads, charset: yes

The relevant excerpt from znc -D :

[2016-05-30 22:02:15.926477] (chaosblade/freenode) IRC -> ZNC [PING :sinisalo.freenode.net]
[2016-05-30 22:02:15.926710] (chaosblade/freenode) ZNC -> IRC [PONG :sinisalo.freenode.net]
[2016-05-30 22:04:39.926008] (chaosblade/freenode) IRC -> ZNC [PING :sinisalo.freenode.net]
[2016-05-30 22:04:39.926238] (chaosblade/freenode) ZNC -> IRC [PONG :sinisalo.freenode.net]
[2016-05-30 22:09:29.370408] (chaosblade/freenode) ZNC -> IRC [PING :ZNC]
[2016-05-30 22:09:29.469420] (chaosblade/freenode) ZNC -> IRC [QUIT :ZNC 1.6.3 - http://znc.in]

.. followed by the usual SockError(104 Connection reset by peer) line that i seem to have accidentally omitted from the original log.

When IRC asks ZNC for pings, it seems to be fine. When ZNC asks for one, something goes awry.
This could possibly be my LAN or some other issue locally related, but i don't notice any other issues with networking at the same time; I'm also on QuakeNet in this case and it does not disconnect, Nor do any of my other non-IRC services experience this.

Any help in looking into this will be greatly appreciated.

Apologies in advance for resurrecting such an old issue, But i seem to have come across the very same thing, on multiple occasions. At first, I was running the znc-msvc builds, namely a ZNC 1.5 build running on a Windows 10 Intel NUC machine. Obviously that is quite old and somewhat unsupported, So i ended up running a self-compiled 1.6.3 from source, running in my local LAN on Raspbian (Raspberry Pi 3). The former Windows machine was on WiFi, the Pi is directly attached by ethernet to the router. Machine(s) and/or connection doesn't seem to be dropping when this happens. As noted, a client attached seems to alleviate this in some way, possibly because of a client's own pings to ZNC. In both cases, I used the AdiIRC client for Windows, But I've also tried others, and as said, the problem is far less frequent when a client is attached. Version output is as follows: ``` [22:38:56] *status > ZNC 1.6.3 - http://znc.in [22:38:56] *status > IPv6: yes, SSL: yes, DNS: threads, charset: yes ``` The relevant excerpt from znc -D : ``` [2016-05-30 22:02:15.926477] (chaosblade/freenode) IRC -> ZNC [PING :sinisalo.freenode.net] [2016-05-30 22:02:15.926710] (chaosblade/freenode) ZNC -> IRC [PONG :sinisalo.freenode.net] [2016-05-30 22:04:39.926008] (chaosblade/freenode) IRC -> ZNC [PING :sinisalo.freenode.net] [2016-05-30 22:04:39.926238] (chaosblade/freenode) ZNC -> IRC [PONG :sinisalo.freenode.net] [2016-05-30 22:09:29.370408] (chaosblade/freenode) ZNC -> IRC [PING :ZNC] [2016-05-30 22:09:29.469420] (chaosblade/freenode) ZNC -> IRC [QUIT :ZNC 1.6.3 - http://znc.in] ``` .. followed by the usual SockError(104 Connection reset by peer) line that i seem to have accidentally omitted from the original log. When IRC asks ZNC for pings, it seems to be fine. When ZNC asks for one, something goes awry. This could possibly be my LAN or some other issue locally related, but i don't notice any other issues with networking at the same time; I'm also on QuakeNet in this case and it does not disconnect, Nor do any of my other non-IRC services experience this. Any help in looking into this will be greatly appreciated.

adam commented

2026-10-05 04:11:26 +02:00

All I can see from that log is: ZNC tries to PING the IRC server. When writing that to the socket, the kernel returns "connection reset by peer" (so neither of the PING nor the QUIT are actually sent). That means that the connection is already dead at this point and just because it writes something does ZNC (and the kernel) now find out about this.

Technical details:
So I guess the following happens: ZNC sends the PING. Kernel says "ok" and sends a TCP packet to the other end of the connection with this data. The other end replies with a a packet with the RST flag set ("reset"), because it does not know about this TCP connection. Kernel informs ZNC that the "connection was reset by peer" (packet with RST flag set).
On why the connection is dead: No idea. Something on the other end of the connection or in the network (lots of packet loss). Neither seems plausible to me.

All I can see from that log is: ZNC tries to PING the IRC server. When writing that to the socket, the kernel returns "connection reset by peer" (so neither of the PING nor the QUIT are actually sent). That means that the connection is already dead at this point and just because it writes something does ZNC (and the kernel) now find out about this. Technical details: So I guess the following happens: ZNC sends the PING. Kernel says "ok" and sends a TCP packet to the other end of the connection with this data. The other end replies with a a packet with the RST flag set ("reset"), because it does not know about this TCP connection. Kernel informs ZNC that the "connection was reset by peer" (packet with RST flag set). On why the connection is dead: No idea. Something on the other end of the connection or in the network (lots of packet loss). Neither seems plausible to me.

adam commented

2026-10-05 04:11:27 +02:00

Some other ideas:

Since I doubt that the computer that the IRC server runs on crashed: What message did others on IRC see you quit with? Ping timeout? That would mean that the IRC server sent a PING which never reached ZNC.
What's your normal round-trip-time to the IRC server (ping)? In the above log, there is about 0.1 seconds between sending the PING and noticing that the connection is dead. If this were much lower, then it could have been some local NAT router interfering.

Some other ideas: - Since I doubt that the computer that the IRC server runs on crashed: What message did others on IRC see you quit with? Ping timeout? That would mean that the IRC server sent a PING which never reached ZNC. - What's your normal round-trip-time to the IRC server (ping)? In the above log, there is about 0.1 seconds between sending the PING and noticing that the connection is dead. If this were much lower, then it could have been some local NAT router interfering.

adam commented

2026-10-05 04:11:27 +02:00

Thanks for the quick response and info.

It doesn't seem like the ZNC process or server crash, but I've switched ZNC
to run in -D for a day or so, writing it's log to a file. Might get more
useful information from there.

My quit messages were indeed ping timeouts, every single time. On average,
freenode disconnects every hour or so, while quakenet happens (maybe) once
a day or two.

From the quick look i had, the round trips seem similar, around 0.1s. I'll
have a look at the extended debug log later today and see.

Any suggestions on thing i could try to check to pinpoint the problem
further?
On May 31, 2016 10:15, "Uli Schlachter" notifications@github.com wrote:

Some other ideas:

Since I doubt that the computer that the IRC server runs on crashed:
What message did others on IRC see you quit with? Ping timeout? That would
mean that the IRC server sent a PING which never reached ZNC.

What's your normal round-trip-time to the IRC server (ping)? In the
above log, there is about 0.1 seconds between sending the PING and noticing
that the connection is dead. If this were much lower, then it could have
been some local NAT router interfering.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/znc/znc/issues/487#issuecomment-222609963, or mute
the thread
https://github.com/notifications/unsubscribe/AGeIIn-2GIMucr6wE3lEIUKla-S6f9_Xks5qG-AZgaJpZM4BgsFf
.

Thanks for the quick response and info. It doesn't seem like the ZNC process or server crash, but I've switched ZNC to run in -D for a day or so, writing it's log to a file. Might get more useful information from there. My quit messages were indeed ping timeouts, every single time. On average, freenode disconnects every hour or so, while quakenet happens (maybe) once a day or two. From the quick look i had, the round trips seem similar, around 0.1s. I'll have a look at the extended debug log later today and see. Any suggestions on thing i could try to check to pinpoint the problem further? On May 31, 2016 10:15, "Uli Schlachter" notifications@github.com wrote: > Some other ideas: > - Since I doubt that the computer that the IRC server runs on crashed: > What message did others on IRC see you quit with? Ping timeout? That would > mean that the IRC server sent a PING which never reached ZNC. > - What's your normal round-trip-time to the IRC server (ping)? In the > above log, there is about 0.1 seconds between sending the PING and noticing > that the connection is dead. If this were much lower, then it could have > been some local NAT router interfering. > > — > You are receiving this because you commented. > Reply to this email directly, view it on GitHub > https://github.com/znc/znc/issues/487#issuecomment-222609963, or mute > the thread > https://github.com/notifications/unsubscribe/AGeIIn-2GIMucr6wE3lEIUKla-S6f9_Xks5qG-AZgaJpZM4BgsFf > .

adam commented

2026-10-05 04:11:28 +02:00

I think that means that the problem didn't occur in your computer. There must have been something on the network. To ZNC it looks like Freenode stopped sending PINGs, to Freenode it looks like ZNC stopped answering PINGs.

I think that means that the problem didn't occur in your computer. There must have been something on the network. To ZNC it looks like Freenode stopped sending PINGs, to Freenode it looks like ZNC stopped answering PINGs.

adam commented

2026-10-05 04:11:29 +02:00

Here's a more through log, grep'd to contain only the relevant parts.

znc_pingpong_sockerror.txt

The SockError 101's are due to not resolving the hostname during the reconnection, i believe.
I wonder if there's something i can do about it from ZNC's side or is it something entirely up to freenode.

Here's a more through log, grep'd to contain only the relevant parts. [znc_pingpong_sockerror.txt](https://github.com/znc/znc/files/296434/znc_pingpong_sockerror.txt) The SockError 101's are due to not resolving the hostname during the reconnection, i believe. I wonder if there's something i can do about it from ZNC's side or is it something entirely up to freenode.

adam commented

2026-10-05 04:11:29 +02:00

I don't see reconnects in that log, but I guess the following:

E:\znc.log:2604:[2016-06-01 09:58:00.366238] (chaosblade/freenode) ZNC -> IRC [PING :ZNC]
E:\znc.log:2605:[2016-06-01 09:58:00.433719] IRC::chaosblade::freenode == SockError(104 Connection reset by peer)
E:\znc.log:2613:[2016-06-01 09:58:00.629373] IRC::chaosblade::freenode == SockError(101 Network is unreachable)

means that the connection first broke and then the reconnect failed because "Network is unreachable". That points a lot towards network issues. Since apparently only you see this, the network issues likely are between the computer you run ZNC on and "the internet".

(This pattern is visible several times)

Still, nothing ZNC-related.

I don't see reconnects in that log, but I guess the following: ``` E:\znc.log:2604:[2016-06-01 09:58:00.366238] (chaosblade/freenode) ZNC -> IRC [PING :ZNC] E:\znc.log:2605:[2016-06-01 09:58:00.433719] IRC::chaosblade::freenode == SockError(104 Connection reset by peer) E:\znc.log:2613:[2016-06-01 09:58:00.629373] IRC::chaosblade::freenode == SockError(101 Network is unreachable) ``` means that the connection first broke and then the reconnect failed because "Network is unreachable". That points a lot towards network issues. Since apparently only you see this, the network issues likely are between the computer you run ZNC on and "the internet". (This pattern is visible several times) Still, nothing ZNC-related.

adam commented

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

Those seemed related to the IRC server trying to find my hostname. It
succeeds mostly.
Either way, Looks like i'll have to take it up with freenode or try to lock
into some specific servers of theirs.

Thanks again for the help.

Regards,
Ran Sagy
Software Engineer

On Fri, Jun 3, 2016 at 10:01 AM, Uli Schlachter notifications@github.com
wrote:

I don't see reconnects in that log, but I guess the following:

E:\znc.log:2604:2016-06-01 09:58:00.366238 ZNC -> IRC [PING :ZNC]
E:\znc.log:2605:[2016-06-01 09:58:00.433719] IRC::chaosblade::freenode == SockError(104 Connection reset by peer)
E:\znc.log:2613:[2016-06-01 09:58:00.629373] IRC::chaosblade::freenode == SockError(101 Network is unreachable)

means that the connection first broke and then the reconnect failed
because "Network is unreachable". That points a lot towards network issues.
Since apparently only you see this, the network issues likely are between
the computer you run ZNC on and "the internet".

(This pattern is visible several times)

Still, nothing ZNC-related.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/znc/znc/issues/487#issuecomment-223505714, or mute
the thread
https://github.com/notifications/unsubscribe/AGeIIrcZkhPoYa8DYGeZk1kKOAel6dx3ks5qH9E_gaJpZM4BgsFf
.

Those seemed related to the IRC server trying to find my hostname. It succeeds mostly. Either way, Looks like i'll have to take it up with freenode or try to lock into some specific servers of theirs. Thanks again for the help. Regards, Ran Sagy Software Engineer On Fri, Jun 3, 2016 at 10:01 AM, Uli Schlachter notifications@github.com wrote: > I don't see reconnects in that log, but I guess the following: > > E:\znc.log:2604:[2016-06-01 09:58:00.366238](chaosblade/freenode) ZNC -> IRC [PING :ZNC] > E:\znc.log:2605:[2016-06-01 09:58:00.433719] IRC::chaosblade::freenode == SockError(104 Connection reset by peer) > E:\znc.log:2613:[2016-06-01 09:58:00.629373] IRC::chaosblade::freenode == SockError(101 Network is unreachable) > > means that the connection first broke and then the reconnect failed > because "Network is unreachable". That points a lot towards network issues. > Since apparently only you see this, the network issues likely are between > the computer you run ZNC on and "the internet". > > (This pattern is visible several times) > > Still, nothing ZNC-related. > > — > You are receiving this because you commented. > Reply to this email directly, view it on GitHub > https://github.com/znc/znc/issues/487#issuecomment-223505714, or mute > the thread > https://github.com/notifications/unsubscribe/AGeIIrcZkhPoYa8DYGeZk1kKOAel6dx3ks5qH9E_gaJpZM4BgsFf > .

adam commented

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

I can confirm that this has been fixed in latest master (e86efb08bd).
However the latest release — 1.6.5 — is still broken.

I can confirm that this has been fixed in latest master (e86efb08bd606ea7b38749904e2347237dede6e3). However the latest release — 1.6.5 — is still broken.

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: adam/znc#298