Bug 929362 - flow-tools service (flow-capture) will not start
Summary: flow-tools service (flow-capture) will not start
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: flow-tools
Version: 18
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Paul P Komkoff Jr
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-03-29 22:33 UTC by Chris Bull
Modified: 2013-09-17 00:32 UTC (History)
2 users (show)

Fixed In Version: flow-tools-0.68.5.1-10.fc19
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-09-17 00:29:43 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Chris Bull 2013-03-29 22:33:29 UTC
Description of problem:

The service provided by flow-tools (flow-capture) will not start 


Version-Release number of selected component (if applicable):
 flow-tools         x86_64         0.68.5.1-6.fc18         fedora



How reproducible:

Reproducible always

Steps to Reproduce:
1. yum install flow-tools
2. systemctl start flow-capture.service
3. (fails to start
  
Actual results:
ar 29 22:30:44 localhost systemd[1]: Starting Flow-capture Capture Traffic Flow Data...
Mar 29 22:30:44 localhost flow-capture[23286]: setsockopt(size=4194304)
Mar 29 22:30:44 localhost flow-capture[23286]: open(/run/flow-capture.pid.8818): Permission denied
Mar 29 22:30:44 localhost systemd[1]: PID file /run/flow-capture.pid not readable (yet?) after start.

Expected results:
service ran without issue on FC16 - I've not tried it on FC17


Additional info:

Comment 1 Mike Iglesias 2013-06-23 14:22:56 UTC
It doesn't start correctly on F17 as well.

Comment 2 Mike Iglesias 2013-08-22 20:29:05 UTC
The problem appears to be that flow-capture appends the port it is listening on to the pidfile name (for example, /run/flow-capture.pid.9996 if you're listening on port 9996), so systemd can't find the pidfile and stops the process.

Comment 3 Paul P Komkoff Jr 2013-08-23 07:44:34 UTC
I think I'd better run it without forking, as a simple service.

Comment 4 Paul P Komkoff Jr 2013-08-23 07:49:32 UTC
http://pkgs.fedoraproject.org/cgit/flow-tools.git/commit/?id=9b9516cfb2fffc93bd657346b20b758a6a6d3241

like this.
I've pushed the build to master, if you can modify the service file locally on your host and verify it works i'll push it to other branches as well.

Comment 5 Mike Iglesias 2013-08-23 15:07:40 UTC
It appears to work.  Thanks!

Comment 6 Fedora Update System 2013-09-01 13:04:30 UTC
flow-tools-0.68.5.1-10.fc19 has been submitted as an update for Fedora 19.
https://admin.fedoraproject.org/updates/flow-tools-0.68.5.1-10.fc19

Comment 7 Fedora Update System 2013-09-01 13:04:39 UTC
flow-tools-0.68.5.1-10.fc18 has been submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/flow-tools-0.68.5.1-10.fc18

Comment 8 Fedora Update System 2013-09-01 22:58:41 UTC
Package flow-tools-0.68.5.1-10.fc19:
* should fix your issue,
* was pushed to the Fedora 19 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing flow-tools-0.68.5.1-10.fc19'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-15614/flow-tools-0.68.5.1-10.fc19
then log in and leave karma (feedback).

Comment 9 Fedora Update System 2013-09-17 00:29:43 UTC
flow-tools-0.68.5.1-10.fc18 has been pushed to the Fedora 18 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 10 Fedora Update System 2013-09-17 00:32:00 UTC
flow-tools-0.68.5.1-10.fc19 has been pushed to the Fedora 19 stable repository.  If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.