[Bug 271777] Re: Exit status 127 when starting openvpn when its already started.

[Thierry Carrez]

Hardy SRU Report

Bug impact: When openvpn is already started, trying to start it using
the init script results in exit status 127. This can impact heartbeat
deployments as mentionned in comment 5.

Versions affected: Hardy (openvpn initscript was rewritten in Intrepid)

Minimal patch: see comment 6 just above.

TEST CASE:
$ sudo apt-get install openvpn
Unpack the attached vpnconf.tar.gz into /etc/openvpn
$ sudo /etc/init.d/openvpn restart (should start the "server" VPN)
$ sudo /etc/init.d/openvpn start
Without the fix, fails with "/etc/init.d/openvpn: 181: STATUS: not found" and exit status 127
With the fix, warns with "server (FAILED - Already running (PID file exists).)" and exits with status 0

Regression potential:
Given the simplicity of the patch, regression potential is null. Nobody should have been relying on exit code 127 which was the result of a failed bash variable assignment.

** Attachment added: "vpnconf.tar.gz"
   http://launchpadlibrarian.net/24359843/vpnconf.tar.gz

** Changed in: openvpn (Ubuntu Hardy)
   Importance: Undecided => Medium
       Status: New => Confirmed

** Summary changed:

- Exit status 127 when starting openvpn when its already started.
+ [SRU] Exit status 127 when starting openvpn when its already started.

-- 
[SRU] Exit status 127 when starting openvpn when its already started.
https://bugs.launchpad.net/bugs/271777
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openvpn in ubuntu.