Red Hat Bugzilla – Bug 1255148
init script fails to start
Last modified: 2016-10-07 14:09:53 EDT
Description of problem: znc init script fails to start giving error: Starting znc: /usr/bin/dirname: extra operand `2>&1.pid' Try `/usr/bin/dirname --help' for more information. Version-Release number of selected component (if applicable): znc-1.4-1.el6.x86_64 How reproducible: Always Steps to Reproduce: 1. start znc: service znc start 2. Watch it fail 3. Release annoyed grunt Actual results: Fails to start with error: Starting znc: /usr/bin/dirname: extra operand `2>&1.pid' Try `/usr/bin/dirname --help' for more information. Expected results: znc starts with no errors
The error message is annoying but it's not the reason znc doesn't start... There is no configuration after the installation and znc fails to start because of it. I made it work by doing the following: 1. Login as root 2. znc -r --makeconf -d /var/lib/znc This will ask many questions and create the configuration in /var/lib/znc When prompted to "Launch ZNC now?", say no. 3. chown -R znc:znc /var/lib/znc ...since we created it as root. 4. service znc start This will spit the error message about extra operand again, but znc seems to start just fine. I understand packaging ZNC is somewhat tough... Maybe fixing the initscript so it would simply refuse to start znc when there is no configuration (and explain why) would make the user's life easier.
I am retiring ZNC in epel5 and epel6 since there are deps that are not available.