Your package bip appears to include a file in /var/run or /var/lock. With an upcoming change in Rawhide these directories will now be mounted as tmpfs. For details about this change please consult http://lists.fedoraproject.org/pipermail/devel-announce/2010-November/000726.html For your package this means that you need add %ghost to all files that are placed in either of these two directories. Please make sure to make this change in time for the F15 cycle. For details about %ghost see http://www.rpm.org/max-rpm-snapshot/s1-rpm-inside-files-list-directives.html#S3-RPM-INSIDE-FLIST-GHOST-DIRECTIVE , for more information on the F15 feature see the feature page https://fedoraproject.org/wiki/Features/var-run-tmpfs . If your package already uses %ghost on these files, feel free to close this bug report right-away. Sorry for this mass bug filing, and if you have any further questions, don't hesitate to ask on fedora-devel or ask me personally. Thank you, Lennart
*** Bug 676409 has been marked as a duplicate of this bug. ***
bip-0.8.7-1.fc15 has been submitted as an update for Fedora 15. https://admin.fedoraproject.org/updates/bip-0.8.7-1.fc15
bip-0.8.7-1.fc15 has been pushed to the Fedora 15 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update bip'. You can provide feedback for this update here: https://admin.fedoraproject.org/updates/bip-0.8.7-1.fc15
bip-0.8.7-1.fc15 has been pushed to the Fedora 15 stable repository. If problems still persist, please make note of it in this bug report.
I'm afraid that update doesn't fix it. You need to add a file in /etc/tmpfiles.d to tell systemd to create /var/run/bip at boot time. Suggested contents are: d /var/run/bip 0755 bip bip -
I've encountered this issue in bip-0.8.7-1.fc16 /var/log/messages: --- Nov 9 12:11:18 dbox bip[2714]: Starting bip: 09-11-2011 12:11:18 FATAL: Cannot write to PID file (/var/run/bip/bip.pid.dbox.2717) No such file or directory Nov 9 12:11:18 dbox bip[2714]: [FAILED] Nov 9 12:11:18 dbox systemd[1]: bip.service: control process exited, code=exited status=1 Nov 9 12:11:18 dbox systemd[1]: Unit bip.service entered failed state. --- The workaround in comment#5 fixes the issue.
(In reply to comment #6) > I've encountered this issue in bip-0.8.7-1.fc16 > > /var/log/messages: > --- > Nov 9 12:11:18 dbox bip[2714]: Starting bip: 09-11-2011 12:11:18 FATAL: Cannot > write to PID file (/var/run/bip/bip.pid.dbox.2717) No such file or directory > Nov 9 12:11:18 dbox bip[2714]: [FAILED] > Nov 9 12:11:18 dbox systemd[1]: bip.service: control process exited, > code=exited status=1 > Nov 9 12:11:18 dbox systemd[1]: Unit bip.service entered failed state. > --- > > The workaround in comment#5 fixes the issue. Can you post for me the pid_file line from your bip.conf file? It should read: pid_file="/var/run/bip/bip.pid" Also, does /etc/tmpfiles.d/bip.conf exist? And, if so, what is the content of that file.
Darryl, the problem was that unless you reboot the pid directory isn't created. I added a call to systemd-tmpfsfiles --create /etc/tmpfsfiles.d/bip.conf
bip-0.8.8-1.fc16 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/bip-0.8.8-1.fc16
Package bip-0.8.8-1.fc16: * should fix your issue, * was pushed to the Fedora 16 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing bip-0.8.8-1.fc16' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2011-16091/bip-0.8.8-1.fc16 then log in and leave karma (feedback).
bip-0.8.8-1.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report.