Hide Forgot
I have a znc server running on an ARM-based machine. Whenever I reboot that machine I always get messages like this from "*status": <*status> Disconnected from IRC (Can't resolve server hostname). Reconnecting... ...but it never succeeds in reconnecting. If I then log into the machine and do a systemctl restart znc, it comes back to life. The host does use dynamically configured addresses, so maybe znc is coming up before the network interfaces are fully set up? Let me know if you need other info to help diagnose this.
I am also seeing this problem on Fedora 25. I believe the problem is that the unit file has: After=network.target instead of: After=network-online.target I think that simple change will likely solve the problem. https://www.freedesktop.org/wiki/Software/systemd/NetworkTarget/
You may also need a Requires=network-online.target line.
Alas, no...that doesn't seem to help in my case. I added this to the znc.service file Unit section: Wants=network-online.target After=network-online.target ...per the systemd.special manpage, but it still had the same behavior after a reboot.
Hello Jeff, It might be that you need Requires= as well.
As I posted in Bug 1405580: I'm not sure that this is necessarily the problem. I'm running znc-1.6.3-6.el7.x86_64 and have two networks configured, both with hostnames. If I restart the service, one network connects immediately and the other (which incidentally is Freenode) does the same thing you describe.
Hi, we are experiencing the same issue (znc-1.6.3). Users are able to "workaround" it with adding a secondary server, it can even be the IP address of the same server. ZNC fails to connect to server.example.com, but it can connect to X.Y.W.Z (IP of server.example.com) -- Milan
This message is a reminder that Fedora 25 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 25. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '25'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 25 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
This *may* be working now in the latest package in Fedora 26. I'm not sure if 25 is fixed.
Yes, I just patched and rebooted and it came right back. Seems to be ok now.
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.