Bug 947851 - the Bip systemd service file uses a PIDFile path that is not configured
Summary: the Bip systemd service file uses a PIDFile path that is not configured
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: bip
Version: 18
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Brian Lane
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-04-03 12:27 UTC by Josh
Modified: 2013-06-05 17:26 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-06-05 17:26:30 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Josh 2013-04-03 12:27:17 UTC 
Description of problem:
the PIDFile in the service definition points to /run/bip/bip.pid but this directory doesn't exist (and can't by default because it is a tmpfs).

Version-Release number of selected component (if applicable):
0.8.8-7.fc18.armv5tel

How reproducible:
always

Steps to Reproduce:
1. yum install bip
2. systemctl start bip.service
3.
  
Actual results:
bip fails to start

Expected results:
bip starts

Additional info:
changing the PIDFile=/run/bip/bip.pid to PIDFile=/var/run/bip/bip.pid in bip.service fixes it
Comment 1 Brian Lane 2013-04-26 18:20:53 UTC 
Do you have a /etc/tmpfiles.d/bip.conf installed? This is supposed to setup the directory. Also, /var/run/ should be a symlink to /run/
Note You need to log in before you can comment on or make changes to this bug.