** 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
** Changed in: corosync (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 corosync in Ubuntu.
https://bugs.launchpad.net/bugs/1434684
Title:
Pacema
** 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.
https://bugs.launchpad.n
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 \
+
** 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 processe
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 (Ubun
** Also affects: corosync (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: corosync (Ubuntu Trusty)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
High Availability Team, which is subscribed to corosync in Ubuntu
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 Ubuntu
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 T
** Changed in: corosync (Ubuntu Trusty)
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 corosync in Ubuntu.
https://bugs.launchpad.net/bugs/1434684
Ti
Hello,
Well, elbandi have found the answer to your question : pacemaker now
needs to be started as a separate service. To quote the document :
"Pacemaker used to obtain membership and quorum from a custom Corosync plugin.
This plugin also had the capability to start Pacemaker automatically when
** 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 to
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 scri
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 and
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
Ch
Peter, you will not be able to reproduce on Debian unless you test
versions prior to Stable.
The reason why the stop script does not stop at all processes is because
it relied on the --pidfile option and this one only kills the first PID.
When nproc > 1, the PIDFILE contains all PIDs. This is why
FYI, I will rebase the debdiff on the new version currently in backport
& repost.
--
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 do
signee: (unassigned) => Louis Bouchard (louis-bouchard)
** Changed in: haproxy (Ubuntu)
Status: Confirmed => Invalid
--
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/14
** Description changed:
+ [SRU justification]
+ The sysVinit script does not completely stop processes when nbproc > 1
+
+ [Impact]
+ Stopping haproxy without this fix leaves all but one process running
+
+ [Fix]
+ Use temporary pidfile in a loop containing one single PID as the --pid option
is
** Patch removed: "lp1494141_fix_stop_failure.debdiff"
https://bugs.launchpad.net/ubuntu/+source/haproxy/+bug/1481737/+attachment/4473139/+files/lp1494141_fix_stop_failure.debdiff
** Patch added: "lp1481737_stop_multipid.debdiff"
https://bugs.launchpad.net/ubuntu/+source/haproxy/+bug/14817
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 th
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 t
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 ver
** Also affects: haproxy (Ubuntu Vivid)
Importance: Undecided
Status: New
** Changed in: haproxy (Ubuntu Vivid)
Assignee: (unassigned) => Louis Bouchard (louis-bouchard)
** Changed in: haproxy (Ubuntu Vivid)
Importance: Undecided => Medium
** Changed in: haproxy (Ubuntu
** 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
** Tags removed: verification-needed
** Tags added: verification-done
** Changed in: haproxy (Ubuntu Trusty)
Assignee: Louis Bouchard (louis-bouchard) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
High Availability Team, which is subscribed
ok, I'm on the vivid SRU
--
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/1481737
Title:
HAProxy init script does not work correctly with nbproc configuration
option
Sta
debdiff for vivid SRU
** Patch added: "lp1481737_vivid.debdiff"
https://bugs.launchpad.net/ubuntu/+source/haproxy/+bug/1481737/+attachment/4531521/+files/lp1481737_vivid.debdiff
--
You received this bug notification because you are a member of Ubuntu
High Availability Team, which is subscrib
** Also affects: corosync (Ubuntu Trusty)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
High Availability Team, which is subscribed to corosync in Ubuntu.
https://bugs.launchpad.net/bugs/1530837
Title:
Logsys file leaks in
Fixes to the debdiff look ok to me. Sponsored to Trusty
--
You received this bug notification because you are a member of Ubuntu
High Availability Team, which is subscribed to corosync in Ubuntu.
https://bugs.launchpad.net/bugs/1530837
Title:
Logsys file leaks in /dev/shm after sigabrt, sigseg
** Also affects: corosync (Ubuntu Trusty)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
High Availability Team, which is subscribed to corosync in Ubuntu.
https://bugs.launchpad.net/bugs/1563089
Title:
Memory Leak when new
Fix accepted to the development release.
Fix sponsored for Trusty and wily; unsubscribing the Ubuntu-sponsor team
--
You received this bug notification because you are a member of Ubuntu
High Availability Team, which is subscribed to corosync in Ubuntu.
https://bugs.launchpad.net/bugs/1563089
T
32 matches
Mail list logo
