# 2.8.2 to 2.9.6 HAPROXY Wont start after update

**URL:** <https://discourse.haproxy.org/t/2-8-2-to-2-9-6-haproxy-wont-start-after-update/9569>\
**Category:** Help!\
**Created:** [February 29, 2024, 11:23pm UTC](https://discourse.haproxy.org/t/2-8-2-to-2-9-6-haproxy-wont-start-after-update/9569 "2024-02-29T23:23:10Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![murusaki](https://avatars.discourse-cdn.com/v4/letter/m/85f322/32.png) [@murusaki](https://discourse.haproxy.org/u/murusaki)\
**Post date:** [February 29, 2024, 11:23pm UTC](https://discourse.haproxy.org/t/2-8-2-to-2-9-6-haproxy-wont-start-after-update/9569/1 "2024-02-29T23:23:10Z")

</div>

Help: I am currently running 2.8.2 and upgraded and built 2.9.6. HAPROXY runs as expected with no problems on 2.8.2 but fails when starting 2.9.x. I am a little lost as to why or what would cause the application not to start the service.

**Starting on 2.9.6**

● haproxy.service - HAProxy Load Balancer  
Loaded: loaded (/usr/lib/systemd/system/haproxy.service; disabled; vendor preset: disabled)  
Active: failed (Result: exit-code) since Thu 2024-02-29 17:45:48 EST; 12min ago  
Docs: man:haproxy(1)

Feb 29 17:45:48 ha01 systemd[1]: haproxy.service: Service RestartSec=100ms expired, scheduling restart.  
Feb 29 17:45:48 ha01 systemd[1]: haproxy.service: Scheduled restart job, restart counter is at 5.  
Feb 29 17:45:48 ha01 systemd[1]: Stopped HAProxy Load Balancer.  
Feb 29 17:45:48 ha01 systemd[1]: haproxy.service: Start request repeated too quickly.  
Feb 29 17:45:48 ha01 systemd[1]: haproxy.service: Failed with result ‘exit-code’.  
Feb 29 17:45:48 ha01 systemd[1]: Failed to start HAProxy Load Balancer.

**Starting on 2.8.2**  
[root@ha01]# systemctl status haproxy  
● haproxy.service - HAProxy Load Balancer  
Loaded: loaded (/usr/lib/systemd/system/haproxy.service; disabled; vendor preset: disabled)  
Active: active (running) since Thu 2024-02-29 17:58:03 EST; 2s ago  
Docs: man:haproxy(1)  
Process: 2521698 ExecStartPre=/usr/sbin/haproxy -f $CONFIG -c -q $EXTRAOPTS (code=exited, status=0/SUCCESS)  
Main PID: 2521701 (haproxy)  
Status: “Ready.”  
Tasks: 3 (limit: 47707)  
Memory: 22.2M  
CGroup: /system.slice/haproxy.service  
├─2521701 /usr/sbin/haproxy -Ws -f /etc/haproxy/haproxy.cfg -p /run/haproxy.pid -S /run/haproxy-master.sock  
└─2521703 /usr/sbin/haproxy -Ws -f /etc/haproxy/haproxy.cfg -p /run/haproxy.pid -S /run/haproxy-master.sock

Feb 29 17:58:03 ha01 systemd[1]: Starting HAProxy Load Balancer…  
Feb 29 17:58:03 ha01 haproxy[2521701]: [NOTICE] (2521701) : New worker (2521703) forked  
Feb 29 17:58:03 ha01 haproxy[2521701]: [NOTICE] (2521701) : Loading success.  
Feb 29 17:58:03 ha01 systemd[1]: Started HAProxy Load Balancer.

---

<div class="post-metadata">

**Author:** ![lukastribus](https://avatars.discourse-cdn.com/v4/letter/l/7ea924/32.png) [@lukastribus](https://discourse.haproxy.org/u/lukastribus)\
**Post date:** [March 1, 2024, 9:59am UTC](https://discourse.haproxy.org/t/2-8-2-to-2-9-6-haproxy-wont-start-after-update/9569/2 "2024-03-01T09:59:20Z")

</div>

Ran it manually and see if an error shows up:

```
systemctl stop haproxy
killall haproxy
/usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg
killall haproxy

```

---

<div class="post-metadata">

**Author:** ![murusaki](https://avatars.discourse-cdn.com/v4/letter/m/85f322/32.png) [@murusaki](https://discourse.haproxy.org/u/murusaki)\
**Post date:** [March 15, 2024, 10:16pm UTC](https://discourse.haproxy.org/t/2-8-2-to-2-9-6-haproxy-wont-start-after-update/9569/3 "2024-03-15T22:16:54Z")

</div>

That is interesting. Running it manually seems to run fine but fails if I run it through systemctl.

[root@ha01 haproxy]# ps -ef |grep haproxy  
99 3426902 1 0 18:13 ? 00:00:00 /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg  
root 3427281 3391818 0 18:13 pts/0 00:00:00 grep --color=auto haproxy  
[root@ha01 haproxy]# killall haproxy  
[root@ha01 haproxy]# systemctl start haproxy  
Job for haproxy.service failed because the control process exited with error code.  
See “systemctl status haproxy.service” and “journalctl -xe” for details.  
[root@ha01 haproxy]# /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg

---

<div class="post-metadata">

**Author:** ![jbrahy](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.haproxy.org/jbrahy/32/525_2.png) [@jbrahy](https://discourse.haproxy.org/u/jbrahy)\
**Post date:** [March 24, 2024, 8:52am UTC](https://discourse.haproxy.org/t/2-8-2-to-2-9-6-haproxy-wont-start-after-update/9569/4 "2024-03-24T08:52:35Z")

</div>

> [@murusaki](#):
>
> “systemctl status haproxy.service” and “journalctl -xe”

Did you look at the output of those commands?

---

<div class="post-metadata">

**Author:** ![murusaki](https://avatars.discourse-cdn.com/v4/letter/m/85f322/32.png) [@murusaki](https://discourse.haproxy.org/u/murusaki)\
**Post date:** [March 26, 2024, 6:14pm UTC](https://discourse.haproxy.org/t/2-8-2-to-2-9-6-haproxy-wont-start-after-update/9569/5 "2024-03-26T18:14:56Z")

</div>

Here is one of the outputs.

ha01 ~]# **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 Fri 2024-03-15 18:27:28 EDT; 1 weeks 3 days ago  
Docs: man:haproxy(1)  
Process: 3436939 ExecStartPre=/usr/sbin/haproxy -f $CONFIG -c -q $EXTRAOPTS (code=exited, status=1/FAILURE)

Mar 15 18:27:28 ha01 systemd[1]: haproxy.service: Service RestartSec=100ms expired, scheduling restart.  
Mar 15 18:27:28 ha01 systemd[1]: haproxy.service: Scheduled restart job, restart counter is at 5.  
Mar 15 18:27:28 ha01 systemd[1]: Stopped HAProxy Load Balancer.  
Mar 15 18:27:28 ha01 systemd[1]: haproxy.service: Start request repeated too quickly.  
Mar 15 18:27:28 ha01 systemd[1]: haproxy.service: Failed with result ‘exit-code’.  
Mar 15 18:27:28 ha01 systemd[1]: Failed to start HAProxy Load Balancer.

---

<div class="post-metadata">

**Author:** ![jbrahy](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.haproxy.org/jbrahy/32/525_2.png) [@jbrahy](https://discourse.haproxy.org/u/jbrahy)\
**Post date:** [March 26, 2024, 7:53pm UTC](https://discourse.haproxy.org/t/2-8-2-to-2-9-6-haproxy-wont-start-after-update/9569/6 "2024-03-26T19:53:17Z")

</div>

try this command to check syntax

`haproxy -c -f /etc/haproxy/haproxy.cfg`

let me know the output

---

<div class="post-metadata">

**Author:** ![jbrahy](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.haproxy.org/jbrahy/32/525_2.png) [@jbrahy](https://discourse.haproxy.org/u/jbrahy)\
**Post date:** [March 26, 2024, 7:54pm UTC](https://discourse.haproxy.org/t/2-8-2-to-2-9-6-haproxy-wont-start-after-update/9569/7 "2024-03-26T19:54:14Z")

</div>

> [@murusaki](#):
>
> Loaded: loaded (/usr/lib/systemd/system/haproxy.service; disabled; vendor preset: disabled)

This tells me that you need to run this command

```auto
systemctl enable haproxy

```

---

<div class="post-metadata">

**Author:** ![sam7](https://avatars.discourse-cdn.com/v4/letter/s/bc8723/32.png) [@sam7](https://discourse.haproxy.org/u/sam7)\
**Post date:** [May 15, 2024, 8:58pm UTC](https://discourse.haproxy.org/t/2-8-2-to-2-9-6-haproxy-wont-start-after-update/9569/8 "2024-05-15T20:58:03Z")

</div>

I have the same issue on Rocky Linux 8. This is caused by the following in systemd file:-

```auto
ExecStartPre=/usr/sbin/haproxy -f $CONFIG -c -q $EXTRAOPTS

```

where “EXTRAOPTS=-S /run/haproxy-master.sock”  
This works fine on 2.8 but not 2.9.

Changing to this resolves the problem:-

```auto
ExecStartPre=/usr/sbin/haproxy -f $CONFIG -c -q -P $EXTRAOPTS

```