Hide Forgot
znc is enabled to start on boot using systemctl, but it fails to start: Dec 7 16:52:06 i5 znc[1227]: Opening Config [/var/lib/znc/.znc/configs/znc.conf ]... Dec 7 16:52:06 i5 znc[1227]: Binding to port [16667] on host [localhost] using ipv4... [ Unable to bind [Invalid argument] ] Dec 7 16:52:06 i5 znc[1227]: Unrecoverable config error. Dec 7 16:52:06 i5 systemd[1]: znc.service: control process exited, code=exited status=1 Dec 7 16:52:06 i5 systemd[1]: Unit znc.service entered failed state. Manually starting it, e.g. using "service znc start" succeeds. Perhaps it needs to wait for network initialization?
are you using znc-0.202-1?
Yes. $ rpm -q znc znc-0.202-1.fc16.x86_64
This message is a reminder that Fedora 16 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 16. 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 WONTFIX if it remains open with a Fedora 'version' of '16'. 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 prior to Fedora 16's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 16 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 to click on "Clone This Bug" and open it against that version of Fedora. 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. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 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. Thank you for reporting this bug and we are sorry it could not be fixed.