RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1778844 - haproxy status failed after stopping the service
Summary: haproxy status failed after stopping the service
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: haproxy
Version: 8.1
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: rc
: 8.0
Assignee: Ryan O'Hara
QA Contact: Brandon Perkins
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-12-02 16:04 UTC by Jeremy Harris
Modified: 2023-03-24 16:16 UTC (History)
1 user (show)

Fixed In Version: haproxy-1.8.23-2.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-04-28 16:03:37 UTC
Type: Bug
Target Upstream Version:
Embargoed:
pm-rhel: mirror+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-31108 0 None None None 2023-03-07 12:28:49 UTC
Red Hat Product Errata RHSA-2020:1725 0 None None None 2020-04-28 16:03:50 UTC

Description Jeremy Harris 2019-12-02 16:04:16 UTC 
This is an effective clone of bz 1444709; the same syptom being seen for 8.1
as that bug had for 7.3 :-

# systemctl status haproxy.service
● haproxy.service - HAProxy Load Balancer
   Loaded: loaded (/usr/lib/systemd/system/haproxy.service; disabled; vendor preset: disabled)
   Active: failed (Result: exit-code) since Thu 2019-11-28 10:38:15 JST; 4h 13min ago
  Process: 8403 ExecStart=/usr/sbin/haproxy -Ws -f $CONFIG -p $PIDFILE (code=exited, status=143)
  Process: 8402 ExecStartPre=/usr/sbin/haproxy -f $CONFIG -c -q (code=exited, status=0/SUCCESS)
 Main PID: 8403 (code=exited, status=143)

11月 28 10:38:00 lb11 systemd[1]: Starting HAProxy Load Balancer...
11月 28 10:38:00 lb11 systemd[1]: Started HAProxy Load Balancer.
11月 28 10:38:15 lb11 systemd[1]: Stopping HAProxy Load Balancer...
11月 28 10:38:15 lb11 haproxy[8403]: [WARNING] 331/103800 (8403) : Exiting Master process...
11月 28 10:38:15 lb11 haproxy[8403]: [ALERT] 331/103800 (8403) : Current worker 8405 exited with code 143
11月 28 10:38:15 lb11 haproxy[8403]: [WARNING] 331/103800 (8403) : All workers exited. Exiting... (143)
11月 28 10:38:15 lb11 systemd[1]: haproxy.service: Main process exited, code=exited, status=143/n/a
11月 28 10:38:15 lb11 systemd[1]: haproxy.service: Failed with result 'exit-code'.
11月 28 10:38:15 lb11 systemd[1]: Stopped HAProxy Load Balancer.
Comment 1 Ryan O'Hara 2019-12-02 16:32:00 UTC 
Not sure this is the same thing as bz 1444709. That bug was fixed by using KillMode=mixed in the systemd service file. RHEL8 definitely uses KillMode=mixed.
Comment 2 Ryan O'Hara 2019-12-03 18:24:33 UTC 
Found something interesting in the upstream systemd service file:

----

[Unit]
Description=HAProxy Load Balancer
After=network.target

[Service]
Environment="CONFIG=/etc/haproxy/haproxy.cfg" "PIDFILE=/run/haproxy.pid"
ExecStartPre=@SBINDIR@/haproxy -f $CONFIG -c -q
ExecStart=@SBINDIR@/haproxy -Ws -f $CONFIG -p $PIDFILE
ExecReload=@SBINDIR@/haproxy -f $CONFIG -c -q
ExecReload=/bin/kill -USR2 $MAINPID
KillMode=mixed
Restart=always
SuccessExitStatus=143
Type=notify

----

Note the "SuccessExitStatus=143" line. That is exactly the exit status shown above. I added this line to the service file and reloaded. Seems to fix it.
Comment 8 errata-xmlrpc 2020-04-28 16:03:37 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2020:1725
Note You need to log in before you can comment on or make changes to this bug.