Start/Stop the Service
HAProxy Enterprise runs as a service, which you can start or stop by calling systemctl
:
$ sudo systemctl start hapee-2.5-lb
$ sudo systemctl stop hapee-2.5-lb
Use the systemctl status
command to check whether the service is running:
$ sudo systemctl status hapee-2.5-lb
hapee-2.5-lb.service - HAPEE Load Balancer
Loaded: loaded (/lib/systemd/system/hapee-2.5-lb.service; enabled; vendor preset: enabled)
Active: active (running) since Wed 2020-12-02 15:56:43 UTC; 1min 35s ago
Main PID: 12977 (hapee-lb)
Tasks: 3 (limit: 1152)
CGroup: /system.slice/hapee-2.5-lb.service
├─12977 /opt/hapee-2.5/sbin/hapee-lb -Ws -f /etc/hapee-2.5/hapee-lb.cfg -p /run/hapee-2.5-lb.pid
└─12992 /opt/hapee-2.5/sbin/hapee-lb -Ws -f /etc/hapee-2.5/hapee-lb.cfg -p /run/hapee-2.5-lb.pid
Dec 02 15:56:43 lb1 systemd[1]: Starting HAPEE Load Balancer...
Dec 02 15:56:43 lb1 hapee-lb[12977]: [NOTICE] 336/155643 (12977) : New worker #1 (12992) forked
Dec 02 15:56:43 lb1 systemd[1]: Started HAPEE Load Balancer.
Reload the configuration
To reload the HAProxy Enterprise configuration without restarting the process, call systemctl reload
:
$ sudo systemctl reload hapee-2.5-lb
From a technical standpoint, this sends the SIGUSR2 signal, which causes HAProxy Enterprise's main process to re-execute itself. It reloads the configuration file and creates new workers. No connections will be dropped. However, you must keep the expose-fd listeners
parameter on the stats socket
line in the global
section of your configuration for this to continue working:
$ stats socket /var/run/hapee-2.5/hapee-lb.sock user hapee-lb group hapee mode 660 level admin expose-fd listeners
Next up
Start with split configuration files