Using "ipsec start|stop|restart" confuses upstart/systemd
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
strongswan (Ubuntu) |
Triaged
|
Low
|
Unassigned |
Bug Description
When using "ipsec start|stop" directly it confuses the upstrart job that cannot track the status of the daemon.
To reproduce:
start strongswan
ipsec stop
status strongswan
The status command will report strongswan is running while it isn't. Attempting to start it will then fail: "Job is already running: strongswan"
$ lsb_release -rd
Description: Ubuntu Trusty Tahr (development branch)
Release: 14.04
$ apt-cache policy strongswan-starter
strongswan-starter:
Installed: 5.1.2-0ubuntu1
Candidate: 5.1.2-0ubuntu1
Version table:
*** 5.1.2-0ubuntu1 0
500 http://
100 /var/lib/
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: strongswan-starter 5.1.2-0ubuntu1
ProcVersionSign
Uname: Linux 3.13.0-14-generic x86_64
ApportVersion: 2.13.2-0ubuntu5
Architecture: amd64
CurrentDesktop: Unity
Date: Mon Mar 3 14:43:37 2014
InstallationDate: Installed on 2014-01-26 (35 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140124)
SourcePackage: strongswan
UpgradeStatus: No upgrade log present (probably fresh install)
modified.
modified.
mtime.conffile.
summary: |
- Using "ipsec start|stop" confuses upstart + Using "ipsec start|stop|restart" confuses upstart/systemd |
Changed in strongswan (Ubuntu): | |
importance: | High → Low |
This is a known issue. Unfortunately, because of the way strongSwan forks, and the way that Upstart handles forks, there is no clean way around this:
- http:// upstart. ubuntu. com/cookbook/ #how-to- establish- fork-count