Ubuntu
haproxy package

haproxy init script gives incorrect exit status

Bug #1187469 reported by Aaron Kaplan on 2013-06-04

This bug affects 2 people

Affects		Status	Importance	Assigned to	Milestone
	haproxy (Ubuntu)	Fix Released	Undecided	Unassigned

Bug Description

In /etc/init.d/haproxy, the reload and restart commands always exit with status 0 (success), even when the haproxy command failed. reload and restart should be rewritten to follow the pattern of start and stop, which give informative exit codes.

I'm using ubuntu 12.04, but the problem still appears to exist in 13.04.

See original description

Tags:

Related branches

lp:debian/haproxy

lp:debian/experimental/haproxy

lp:ubuntu/saucy/haproxy

CVE References

2013-2175

Revision history for this message

Aaron Kaplan (5-launchpad5425-aaronkaplan-info) wrote on 2013-06-04:

haproxy-init-script-exit-status.patch Edit (2.3 KiB, text/plain)

description:

updated

Revision history for this message

Ubuntu Foundations Team Bug Bot (crichton) wrote on 2013-06-04:

The attachment "haproxy-init-script-exit-status.patch" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.]

tags:

added: patch

Revision history for this message

Launchpad Janitor (janitor) wrote on 2013-06-18:

This bug was fixed in the package haproxy - 1.4.24-1

---------------
haproxy (1.4.24-1) unstable; urgency=high

  [ Vincent Bernat ]
  * New upstream version.
     + CVE-2013-2175: fix a possible crash when using negative header
       occurrences.

  [ Prach Pongpanich ]
  * Drop bashism patch. It seems useless to maintain a patch to convert
    example scripts from /bin/bash to /bin/sh.
  * Fix reload/restart action of init script (LP: #1187469).

-- Vincent Bernat <email address hidden> Mon, 17 Jun 2013 21:56:26 +0200