{{ message }}
Repository navigation
Latest Ubuntu Kernel 146 does shutdown happroxy #3530
Description
Detailed Description of the Problem
After using the official updates for Ubuntu 24.04 LTS the new version of the kernel Linux 6.8.0-146-generic on x86_64 got installed
From that moment Haproxy random shuts down and need the login to the system to restart it
Expected Behavior
As with all updates nothing was wrong with the working of Haproxy.
I expect a reliable working of Haproxy without shutting down the websites
Steps to Reproduce the Behavior
Use the Linux 6.8.0-146-generic on x86_64 and start Haproxy, after some hours Haproxy shutdown without any log information from a configuration that worked for many years without modification
Do you have any idea what may have caused this?
No idea, can not be related to changes excerpt for the kernel update
Do you have an idea how to solve the issue?
reporting this
What is your configuration?
HAProxy version 2.8.16-0ubuntu0.24.04.3 2026/06/19 - https://haproxy.org/
Status: long-term supported branch - will stop receiving fixes around Q2 2028.
Known bugs: http://www.haproxy.org/bugs/bugs-2.8.16.html
Running on: Linux 6.8.0-146-generic #146-Ubuntu SMP PREEMPT_DYNAMIC Thu Sep 3 16:12:30 UTC 2026 x86_64Output of haproxy -vv
HAProxy version 2.8.16-0ubuntu0.24.04.3 2026/06/19 - https://haproxy.org/
Status: long-term supported branch - will stop receiving fixes around Q2 2028.
Known bugs: http://www.haproxy.org/bugs/bugs-2.8.16.html
Running on: Linux 6.8.0-146-generic #146-Ubuntu SMP PREEMPT_DYNAMIC Thu Sep 3 16:12:30 UTC 2026 x86_64
Last Outputs and Backtraces
Additional Information
No response
Activity
GentleRV commentedon Oct 12, 2026
After noticed a shutdown again found in the log files:
2026-10-11T14:31:19.898311+02:00 backup0 haproxy[256915]: [NOTICE] (256915) : haproxy version is 2.8.16-0ubuntu0.24.04.3
2026-10-11T14:31:19.898409+02:00 backup0 haproxy[256915]: [NOTICE] (256915) : path to executable is /usr/sbin/haproxy
2026-10-11T14:31:19.898459+02:00 backup0 haproxy[256915]: [WARNING] (256915) : config : parsing [/etc/haproxy/haproxy.cfg:142] : a 'tcp-request' rule placed after an 'http-request' rule will still be processed before.
2026-10-11T14:31:19.898521+02:00 backup0 haproxy[256915]: [WARNING] (256915) : config : parsing [/etc/haproxy/haproxy.cfg:147] : a 'tcp-request' rule placed after an 'http-request' rule will still be processed before.
2026-10-11T14:31:20.002990+02:00 backup0 haproxy[256915]: [NOTICE] (256915) : New worker (256918) forked
2026-10-11T14:31:20.003112+02:00 backup0 haproxy[256915]: [NOTICE] (256915) : Loading success.
2026-10-11T23:31:27.262582+02:00 backup0 haproxy[256915]: [NOTICE] (256915) : haproxy version is 2.8.16-0ubuntu0.24.04.3
2026-10-11T23:31:27.262659+02:00 backup0 haproxy[256915]: [NOTICE] (256915) : path to executable is /usr/sbin/haproxy
2026-10-11T23:31:27.262702+02:00 backup0 haproxy[256915]: [WARNING] (256915) : Exiting Master process...
2026-10-11T23:31:27.267153+02:00 backup0 haproxy[256915]: [ALERT] (256915) : Current worker (256918) exited with code 143 (Terminated)
2026-10-11T23:31:27.267201+02:00 backup0 haproxy[256915]: [WARNING] (256915) : All workers exited. Exiting... (0)
wlallemand commentedon Oct 12, 2026
I doubt this has anything to do with the kernel, it looks like you have something requesting the stop of the service. But that's difficult to know what with only the haproxy logs, you should try to dig into your system logs to see if a stop event is requested at this timestamp.
GentleRV commentedon Oct 14, 2026
Today it happen again
sudo systemctl status haproxy.service
○ haproxy.service - HAProxy Load Balancer
Loaded: loaded (/usr/lib/systemd/system/haproxy.service; enabled; preset: enabled)
Active: inactive (dead) since Tue 2026-10-13 23:06:43 CEST; 6h ago
Duration: 14h 36min 47.221s
Docs: man:haproxy(1)
file:/usr/share/doc/haproxy/configuration.txt.gz
Process: 983 ExecStart=/usr/sbin/haproxy -Ws -f $CONFIG -p $PIDFILE $EXTRAOPTS (code=exited, status=0/SUCCESS)
Main PID: 983 (code=exited, status=0/SUCCESS)
Status: "Ready."
CPU: 44.752s
Oct 13 08:29:56 backup0 systemd[1]: Started haproxy.service - HAProxy Load Balancer.
Oct 13 23:06:43 backup0 systemd[1]: Stopping haproxy.service - HAProxy Load Balancer...
Oct 13 23:06:43 backup0 haproxy[983]: [NOTICE] (983) : haproxy version is 2.8.16-0ubuntu0.24.04.3
Oct 13 23:06:43 backup0 haproxy[983]: [NOTICE] (983) : path to executable is /usr/sbin/haproxy
Oct 13 23:06:43 backup0 haproxy[983]: [WARNING] (983) : Exiting Master process...
Oct 13 23:06:43 backup0 haproxy[983]: [ALERT] (983) : Current worker (2063) exited with code 143 (Terminated)
Oct 13 23:06:43 backup0 haproxy[983]: [WARNING] (983) : All workers exited. Exiting... (0)
Oct 13 23:06:43 backup0 systemd[1]: haproxy.service: Deactivated successfully.
Oct 13 23:06:43 backup0 systemd[1]: Stopped haproxy.service - HAProxy Load Balancer.
Oct 13 23:06:43 backup0 systemd[1]: haproxy.service: Consumed 44.752s CPU time.
Didn't touched the server but spontaneous Haproxy shutdown
This is happen with kernel 146 and now also with 147, all kernels before that all was working fine
The Haproxy config is more then 2 years old and never changed
GentleRV commentedon Oct 14, 2026
The server on where Haproxy is running is stable for many years even an old backup with a older kernel was working fine, only the update to kernel 146 started to give the problems of intermittent shutdown of Haproxy.
In the error.log file from Haproxy is nothing to find and I don't think that a website can initiate a shutdown
wlallemand commentedon Oct 14, 2026
These particular lines shows that someting is doing a
systemctl stop haproxyand even asystemcl disable haproxy, so that's probably something else than your kernel. The kernel has nothing to do with the services management, you probably have something else that changed, or someone is toying with the service.GentleRV commentedon Oct 14, 2026
Will dig deeper in the system why this can happen