This bug was fixed in the package haproxy - 1.8.8-1ubuntu0.8
---
haproxy (1.8.8-1ubuntu0.8) bionic; urgency=medium
* d/p/lp-1848902-MINOR-systemd-consider-exit-status-143-as-successful.patch:
fix potential hang in haproxy (LP: #1848902)
-- Christian Ehrhardt Tue, 12 Nov
Verified to be working on Bionic using the provided test case and
another simpler one (simply stopping haproxy resulted in the error/143
status).
Preparing to unpack .../haproxy_1.8.8-1ubuntu0.8_amd64.deb ...
Unpacking haproxy (1.8.8-1ubuntu0.8) over (1.8.8-1ubuntu0.7) ...
Setting up haproxy
Hello James, or anyone else affected,
Accepted haproxy into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/haproxy/1.8.8-1ubuntu0.8 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
Uploaded to Bionic-unapproved
** Description changed:
[Impact]
- * The master process will exit with the status of the last worker.
-When the worker is killed with SIGTERM, it is expected to get 143 as an
-exit status. Therefore, we consider this exit status as normal from a
-
Confirmed the test case, waiting for MP review now
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1848902
Title:
haproxy in bionic can get stuck
To manage notifications about this bug go to:
** Merge proposal linked:
https://code.launchpad.net/~paelzer/ubuntu/+source/haproxy/+git/haproxy/+merge/375433
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1848902
Title:
haproxy in bionic
PPA: https://launchpad.net/~paelzer/+archive/ubuntu/bug-1848902-haproxy-hang
MP:
https://code.launchpad.net/~paelzer/ubuntu/+source/haproxy/+git/haproxy/+merge/375433
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Description changed:
+ [Impact]
+
+ * The master process will exit with the status of the last worker.
+When the worker is killed with SIGTERM, it is expected to get 143 as an
+exit status. Therefore, we consider this exit status as normal from a
+systemd point of view. If it
This was also backported to the 2.x and 1.8 series.
According to git this is included in:
1.8.13
fdc6c62dbebf4b646b4f80c383e3b00f34b0440f
Anything >=1.9
3b479bd5f5f50ce91cabed32bb26556313552d23
Thereby all >Bionic are fixed already.
Consider pulling the fix into the Bionic version.
** Also
Note it was not ported to the 1.6.x series and I'd also want to keep
Xenial out of this in general.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1848902
Title:
haproxy in bionic can get stuck
To
** Changed in: haproxy (Ubuntu)
Importance: Undecided => High
** Changed in: haproxy (Ubuntu)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1848902
** Changed in: haproxy (Ubuntu)
Importance: Undecided => High
** Changed in: haproxy (Ubuntu)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1848902
Title:
In our HAProxy deployments, we always add the following drop-in on
Bionic:
[Service]
# XXX: returns 143 when SIGTERM'ed by systemd
SuccessExitStatus=143
It would be great to have the default unit fixed, so thanks!
--
You received this bug notification because you are a member of
** Tags added: server-next
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1848902
Title:
haproxy in bionic can get stuck
To manage notifications about this bug go to:
To reproduce:
apt install haproxy
for x in {1..100}; do pkill -TERM -x haproxy ; sleep 0.1 ; done
systemctl status haproxy
Observe that the unit has failed due to exit-code: "Active: failed (Result:
exit-code)"
To test the fix:
Repeat the steps above with the fixed package
This seems to fix our haproxy problem, although the HA stack still needs
help to recover from the situation. But at least haproxy isn't getting
in the way anymore.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
It looks like this is the patch that was merged: https://www.mail-
archive.com/hapr...@formilux.org/msg30473.html
2018/07/30 : 1.8.13
- MINOR: systemd: consider exit status 143 as successful
I've built a package with this patch and deployed it to the problematic
cloud.
Here's the PPA:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: haproxy (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1848902
Title:
18 matches
Mail list logo
