Hi,
(forgot to send this to the list as well)

I indeed tried restarting HAProxy as well. But it doesn't matter. It just 
doesn't start without error.

Regards,

Sander



December 3, 2024 at 10:41 AM, "Aleksandar Lazic" <al-hapr...@none.at 
mailto:al-hapr...@none.at?to=%22Aleksandar%20Lazic%22%20%3Cal-haproxy%40none.at%3E
 > wrote:


> 
> Hi.
> 
> On 2024-12-03 (Di.) 10:03, Sander Klein wrote:
> 
> > 
> > Hi,
> >  
> >  I've tried upgrading from HAProxy 3.0.6 to 3.1.0. On my primary active 
> >  loadbalancer this succeeds, but on my back-up load balancer HAProxy will 
> > not 
> >  start. Moreover, it fails silently without logging anything.
> >  
> >  The config on both loadbalancers is the same except for the backup having 
> > no 
> >  active VRRP IP's ofcourse. When starting HAProxy in debug mode it just 
> > starts 
> >  without problem, Checking the config gives no errors, but HAProxy behaves 
> > 'odd'. 
> >  When I run haproxy -c -V -f /path/to/config I first return to the prompt 
> > and 
> >  then get the output of the check. Like this:
> >  
> >  root@lb01-b:~# mailto:root@lb01-b:~#  haproxy -c -V -f /etc/haproxy/conf.d/
> >  root@lb01-b:~# mailto:root@lb01-b:~#  Configuration file is valid
> >  
> >  Systemd output:
> >  
> >  Dec 03 09:47:10 lb01-b.pictura-hosting.nl systemd[1]: haproxy.service: 
> > Control 
> >  process exited, code=exited, status=1/FAILURE
> >  ░░ Subject: Unit process exited
> >  ░░ Defined-By: systemd
> >  ░░ Support: https://www.debian.org/support 
> > <https://www.debian.org/support> https://www.debian.org/support%3E 
> >  ░░
> >  ░░ An ExecReload= process belonging to unit haproxy.service has exited.
> >  ░░
> >  ░░ The process' exit code is 'exited' and its exit status is 1.
> >  Dec 03 09:47:10 lb01-b.pictura-hosting.nl systemd[1]: Reload failed for 
> >  haproxy.service - HAProxy Load Balancer.
> >  ░░ Subject: A reload job for unit haproxy.service has finished
> >  ░░ Defined-By: systemd
> >  ░░ Support: https://www.debian.org/support 
> > <https://www.debian.org/support> https://www.debian.org/support%3E 
> >  ░░
> >  ░░ A reload job for unit haproxy.service has finished.
> >  ░░
> >  ░░ The job identifier is 3334 and the job result is failed.
> >  
> >  ● haproxy.service - HAProxy Load Balancer
> >       Loaded: loaded (/etc/systemd/system/haproxy.service; enabled; preset: 
> > enabled)
> >       Active: active (running) since Mon 2024-12-02 15:50:00 CET; 18h ago
> >         Docs: man:haproxy(1)
> >               file:/usr/share/doc/haproxy/configuration.txt.gz
> >      Process: 146648 ExecReload=/usr/sbin/haproxy -f $CONFIG -c -q 
> > $EXTRAOPTS 
> >  (code=exited, status=1/FAILURE)
> >     Main PID: 3963 (haproxy)
> >       Status: "Ready."
> >        Tasks: 5 (limit: 9513)
> >       Memory: 207.2M
> >          CPU: 41min 53.364s
> >       CGroup: /system.slice/haproxy.service 
> > <http://system.slice/haproxy.service> 
> > http://system.slice/haproxy.service%3E 
> >               ├─ 3963 /usr/sbin/haproxy -Ws -f /etc/haproxy/conf.d -p /run/ 
> >  haproxy.pid -S /run/haproxy-master.sock
> >               └─98679 /usr/sbin/haproxy -sf 3994 -x sockpair@5 -Ws -f /etc/ 
> >  haproxy/conf.d -p /run/haproxy.pid -S /run/haproxy-master.sock
> >  
> >  [some lines redacted]
> >  Dec 03 09:47:10 lb01-b.pictura-hosting.nl systemd[1]: Reloading 
> > haproxy.service 
> >  - HAProxy Load Balancer...
> >  Dec 03 09:47:10 lb01-b.pictura-hosting.nl systemd[1]: haproxy.service: 
> > Control 
> >  process exited, code=exited, status=1/FAILURE
> >  Dec 03 09:47:10 lb01-b.pictura-hosting.nl systemd[1]: Reload failed for 
> >  haproxy.service - HAProxy Load Balancer.
> >  
> >  If any more info is needed or if I can do anything please let me know.
> > 
> As the master-worker stuff was heavily rewritten in 3.1 can you try to stop 
> and 
> start HAP instead of a reload?
> 
> > 
> > Regards,
> >  
> >  Sander
> > 
> Regards
> Alex
>

Reply via email to