Administration

Manage the HAProxy Enterprise service

This section describes how to manage the load balancer service on Linux.

Get the HAProxy Enterprise version Jump to heading

To see the installed version of the software:

nix
/opt/hapee-2.9/sbin/hapee-lb version
nix
/opt/hapee-2.9/sbin/hapee-lb version

Start and stop the service Jump to heading

HAProxy Enterprise runs as a service, which you can start or stop by calling systemctl:

Start the service:

nix
sudo systemctl start hapee-2.9-lb
nix
sudo systemctl start hapee-2.9-lb

Stop the service:

nix
sudo systemctl stop hapee-2.9-lb
nix
sudo systemctl stop hapee-2.9-lb

Use the systemctl status command to check whether the service is running:

nix
sudo systemctl status hapee-2.9-lb
nix
sudo systemctl status hapee-2.9-lb
output
text
hapee-2.9-lb.service - HAPEE Load Balancer
Loaded: loaded (/lib/systemd/system/hapee-2.9-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.9-lb.service
├─12977 /opt/hapee-2.9/sbin/hapee-lb -Ws -f /etc/hapee-2.9/hapee-lb.cfg -p /ruhapee-2.9-lb.pid
└─12992 /opt/hapee-2.9/sbin/hapee-lb -Ws -f /etc/hapee-2.9/hapee-lb.cfg -p /run/ hapee-2.9-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.
output
text
hapee-2.9-lb.service - HAPEE Load Balancer
Loaded: loaded (/lib/systemd/system/hapee-2.9-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.9-lb.service
├─12977 /opt/hapee-2.9/sbin/hapee-lb -Ws -f /etc/hapee-2.9/hapee-lb.cfg -p /ruhapee-2.9-lb.pid
└─12992 /opt/hapee-2.9/sbin/hapee-lb -Ws -f /etc/hapee-2.9/hapee-lb.cfg -p /run/ hapee-2.9-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 Jump to heading

To reload the configuration without restarting the process, call systemctl reload:

nix
sudo systemctl reload hapee-2.9-lb
nix
sudo systemctl reload hapee-2.9-lb

This sends the SIGUSR2 signal, which causes the load balancer’s main process to re-execute itself. It reloads the configuration file and creates new workers. No connections will be dropped.

In versions prior to 2.6r1, you must add the expose-fd listeners parameter on the stats socket line in the global section of your configuration for this to work. Versions 2.6r1 and later do not require this.

haproxy
stats socket /var/run/hapee-2.9/hapee-lb.sock user hapee-lb group hapee mode 660 level admin expose-fd listeners
haproxy
stats socket /var/run/hapee-2.9/hapee-lb.sock user hapee-lb group hapee mode 660 level admin expose-fd listeners

Validate your configuration Jump to heading

Use the hapee-lb program’s -c flag to check the validity of your configuration.

nix
sudo /opt/hapee-2.9/sbin/hapee-lb -c -f /etc/hapee-2.9/hapee-lb.cfg
nix
sudo /opt/hapee-2.9/sbin/hapee-lb -c -f /etc/hapee-2.9/hapee-lb.cfg

About the configuration checking command

  • In version 2.8 and earlier, the command indicates a valid configuration by printing Configuration file is valid in addition to setting the zero return status.
  • In version 2.9 and later, the command sets the zero return status for a valid configuration but does not display a message. To display the message, include the -V option on the command line.

Multiple configuration files

If you have multiple configuration files in your application, be sure to check them all in the correct order.

Do you have any suggestions on how we can improve the content of this page?