** Tags removed: haproxy
** Tags added: trusty
--
You received this bug notification because you are a member of Ubuntu
High Availability Team, which is subscribed to haproxy in Ubuntu.
https://bugs.launchpad.net/bugs/1494141
Title:
HAProxy 1.5 init script does not terminate processes
Status
** No longer affects: haproxy (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
High Availability Team, which is subscribed to haproxy in Ubuntu.
https://bugs.launchpad.net/bugs/1494141
Title:
HAProxy 1.5 init script does not terminate processes
Status in
** Changed in: trusty-backports
Assignee: Louis Bouchard (louis-bouchard) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
High Availability Team, which is subscribed to haproxy in Ubuntu.
https://bugs.launchpad.net/bugs/1494141
Title:
HAProxy 1.5
Vincent Bernat (vbernat) is the Debian maintainer for haproxy. His PPA
assumes a version of dpkg that is newer than 1.17.7. I'll try to open a
Debian bug on that.
The problem lies in the use of start-stop-daemon's new --pid option that
is only available after wily.
If 1.6 is backported to any
Greg, 1.6.2 is not packaged for Trusty. I don't know where it comes
from.
--
You received this bug notification because you are a member of Ubuntu
High Availability Team, which is subscribed to haproxy in Ubuntu.
https://bugs.launchpad.net/bugs/1494141
Title:
HAProxy 1.5 init script does not
Just to throw in on this, I'm running 1.6.2 on 14.04.3 and it's not
working here either. Specifically I see it running /usr/sbin/haproxy -f
/etc/haproxy/haproxy.cfg -D -p /var/run/haproxy.pid, but
/var/run/haproxy.pid doesn't exist.
--
You received this bug notification because you are a member
** Changed in: haproxy (Ubuntu)
Importance: Undecided => Medium
** Changed in: haproxy (Ubuntu Trusty)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
High Availability Team, which is subscribed to haproxy in Ubuntu.
Claudio, it is only partly fixed by Jorge's patch.
I have proposed the same fix than for this bug in LP: #1481737.
Unfortunately, not being a core dev, it needs to be sponsored to be
accepted. Then I can backport the fix here in 1.5
Sorry for the delay, I'll chase a sponsor.
--
You received
By the way... this bug was also backported into the official trusty version of
HAProxy (1.4).. Jeez!
In the meantime its fixed again.
haproxy (1.4.24-2ubuntu0.2) trusty; urgency=high
* debian/haproxy.init:
+ Pass the pidfile to the --pidfile argument instead
of the PID number. (LP:
Chase them with beer. Works faster ^^
--
You received this bug notification because you are a member of Ubuntu
High Availability Team, which is subscribed to haproxy in Ubuntu.
https://bugs.launchpad.net/bugs/1494141
Title:
HAProxy 1.5 init script does not terminate processes
Status in
The "new bug" for trusty concerning if nproc > 1 is probably this one:
https://bugs.launchpad.net/ubuntu/+source/haproxy/+bug/1481737 ?
--
You received this bug notification because you are a member of Ubuntu
High Availability Team, which is subscribed to haproxy in Ubuntu.
Good catch Claudio. The bug is present in Trusty and Trusty-backports.
Prior to LP: #1477198, the stop script did not stop at all because it
relied on the --pid option that is introduced in dpkg version 1.17.6 as
outlined in the man page of start-stop-daemon :
[--pid] pid
Hello,
Unfortunately Jorge's patch is incomplete. The reason for the looping on
pid is that, if nproc > 1, the pidfile will contain more than one PID
and using --pidfile will only kill the first one.
The proposed patch here will fix both situation, i.e. the fact that
--pid is silently ignored
Oh, I didn't realize that my previous backport upload was already
accepted. This still needs a patch. I think we should just apply
http://launchpadlibrarian.net/213125772/haproxy_1.4.24-2ubuntu0.1_1.4.24-2ubuntu0.2.diff.gz
to backports, could you please test this? I've upload a test package to
Marking task Trusty as invalid, since haproxy 1.4 uses --pidfile and is
unaffected.
Marking task Wily as fix released as the --pid option is available in
Wily so haproxy 1.5 is unaffected
** Also affects: haproxy (Ubuntu)
Importance: Undecided
Status: New
** Also affects: haproxy
Salut Louis,
Thanks for taking care of this bug. Have I understood correctly that the
haproxy package in trusty-backports is already updated? Or do I have to
wait until the package is released to all mirrors?
--
You received this bug notification because you are a member of Ubuntu
High
Bonjour Claudio,
No, I have just submitted the fix for inclusion in the backported
package. Once the backport team has taken care of it, it will be
indicated as such in the bug.
Kind regards,
..Louis
--
You received this bug notification because you are a member of Ubuntu
High Availability
Patch for the fix to the backport package
** Patch added: "lp1494141_fix_stop_failure.debdiff"
https://bugs.launchpad.net/ubuntu/+source/haproxy/+bug/1494141/+attachment/4466700/+files/lp1494141_fix_stop_failure.debdiff
--
You received this bug notification because you are a member of
** Package changed: haproxy (Ubuntu) => trusty-backports
--
You received this bug notification because you are a member of Ubuntu
High Availability Team, which is subscribed to haproxy in Ubuntu.
https://bugs.launchpad.net/bugs/1494141
Title:
HAProxy 1.5 init script does not terminate
Louis,
I can't sponsor your debdiff into backports, but be careful of ordering
issues in your patch. clean() should be defined before the trap is set,
and tmp should be defined before any point that clean() could be called.
In general you should quote "$tmp" as well in case it ends up with
spaces
** Patch removed: "lp1494141_fix_stop_failure.debdiff"
https://bugs.launchpad.net/trusty-backports/+bug/1494141/+attachment/4466700/+files/lp1494141_fix_stop_failure.debdiff
--
You received this bug notification because you are a member of Ubuntu
High Availability Team, which is subscribed
Micah, got the bug number ? Maybe we should make this one a duplicate
then ?
..Louis
--
You received this bug notification because you are a member of Ubuntu
High Availability Team, which is subscribed to haproxy in Ubuntu.
https://bugs.launchpad.net/bugs/1494141
Title:
HAProxy 1.5 init
There's another haproxy backport request that should fix this (from
utopic version). It was missing the testing of one of the reverse
dependencies.
--
You received this bug notification because you are a member of Ubuntu
High Availability Team, which is subscribed to haproxy in Ubuntu.
** Changed in: haproxy (Ubuntu)
Status: New => In Progress
** Changed in: haproxy (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
High Availability Team, which is subscribed to haproxy in Ubuntu.
Hi,
haproxy 1.5.4 introduces the following change :
ret=0
- start-stop-daemon --quiet --oknodo --stop \
- --retry 5 --pidfile $PIDFILE --exec $HAPROXY || ret=$?
+ for pid in $(cat $PIDFILE); do
+ start-stop-daemon --quiet --oknodo --stop \
+
** Changed in: haproxy (Ubuntu)
Assignee: (unassigned) => Louis Bouchard (louis-bouchard)
--
You received this bug notification because you are a member of Ubuntu
High Availability Team, which is subscribed to haproxy in Ubuntu.
https://bugs.launchpad.net/bugs/1494141
Title:
HAProxy 1.5
26 matches
Mail list logo
