[Pkg-haproxy-maintainers] Bug#762608: haproxy: service haproxy stop returns 4 if haproxy was already not running.

Serge Hallyn serge.hallyn at ubuntu.com
Tue Sep 23 17:30:29 UTC 2014

Package: haproxy
Version: 1.5.4-1
Severity: normal
Tags: patch
User: ubuntu-devel at lists.ubuntu.com
Usertags: origin-ubuntu utopic ubuntu-patch

Dear Maintainer,

pacemaker was running haproxy.  haproxy was killed by oom.  pacemaker
tries to stop then start haproxy, but fails because stop failed with 4
rather than exiting with 0.  Since haproxy was in fact stopped after
the 'service haproxy stop' call, 0 should be returned rather than 4
(by my reading of http://www.debian.org/doc/debian-policy/ch-opersys.html)

*** /tmp/tmpykD9sX/bug_body

In Ubuntu, the attached patch was applied to achieve the following:

  * haproxy.init: return 0 on stop if haproxy was not running.  (LP: #1038139)

Thanks for considering the patch.

-- System Information:
Debian Release: jessie/sid
  APT prefers utopic-updates
  APT policy: (500, 'utopic-updates'), (500, 'utopic-security'), (500, 'utopic'), (100, 'utopic-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16.0-16-generic (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
-------------- next part --------------
A non-text attachment was scrubbed...
Name: haproxy_1.5.4-1ubuntu1.debdiff
Type: text/x-diff
Size: 831 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-haproxy-maintainers/attachments/20140923/a1279508/attachment.diff>

More information about the Pkg-haproxy-maintainers mailing list