Haproxy doesn't checks for configuration on start/reload

Bug #1468879 reported by Jorge Niedbalski
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
haproxy (Ubuntu)
Fix Released
Undecided
Unassigned
Trusty
Fix Released
Undecided
Jorge Niedbalski

Bug Description

[Environment]

Trusty 14.04.2

[Description]

Configuration is not tested before service start or reload

[Suggested Fix]

Backport current check_haproxy_config function from utopic+.

Changed in haproxy (Ubuntu):
status: New → Fix Released
Changed in haproxy (Ubuntu Trusty):
status: New → In Progress
assignee: nobody → Jorge Niedbalski (niedbalski)
Revision history for this message
Brian Murray (brian-murray) wrote : Please test proposed package

Hello Jorge, or anyone else affected,

Accepted haproxy into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/haproxy/1.4.24-2ubuntu0.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Changed in haproxy (Ubuntu Trusty):
status: In Progress → Fix Committed
tags: added: verification-needed
Revision history for this message
Jorge Niedbalski (niedbalski) wrote :

After enabling -proposed and install haproxy.

Edit /etc/default/haproxy, set ENABLED=1

I modified an entry in the configuration /etc/haproxy/haproxy.cfg
global
 log /dev/log local0
 log /dev/log local1 notice
 chroot /var/lib/haproxy
 user haproxy
 group haproxy
 daemon

defaults
 log globalss

service haproxy restart
 * Restarting haproxy haproxy

[ALERT] 195/191904 (5640) : parsing [/etc/haproxy/haproxy.cfg:10] : 'log' expects either <address[:port]> and <facility> or 'global' as arguments.
[ALERT] 195/191904 (5640) : Error(s) found in configuration file : /etc/haproxy/haproxy.cfg
[WARNING] 195/191904 (5640) : config : log format ignored for proxy 'http-in' since it has no log address.
[ALERT] 195/191904 (5640) : Fatal errors found in configuration.
                                                                                                                        [fail]

tags: added: verification-done
removed: verification-needed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package haproxy - 1.4.24-2ubuntu0.1

---------------
haproxy (1.4.24-2ubuntu0.1) trusty; urgency=medium

  * debian/haproxy.init:
     + Backport of utopic start/stop routines,
       uses start-stop-daemon to reliable terminate all
       haproxy processes and return the proper exit code.
       (LP: #1462495).
     + Backport of utopic check_haproxy_config routine,
       that test the configuration before start or reload.
       (LP: #1468879)

 -- Jorge Niedbalski <email address hidden> Thu, 25 Jun 2015 12:51:05 -0700

Changed in haproxy (Ubuntu Trusty):
status: Fix Committed → Fix Released
Revision history for this message
Chris J Arges (arges) wrote : Update Released

The verification of the Stable Release Update for haproxy has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.