Using ‘init’ Scripts to Run HAPEE Services

The following section applies to all Linux distribution, except CentOS//RedHat 7 and Debian, which use ‘systemd’

The table below lists the services managed by ‘init’ scripts:

  • hapee-1.7
  • hapee-1.7-lb
  • hapee-1.7-log
  • hapee-1.7-rhi
  • hapee-1.7-route
  • hapee-1.7-route6
  • hapee-1.7-snmp
  • hapee-1.7-vrrp

Enable a service

By default, the services installed with HAPEE are not enabled.

  • CentOS/RedHat: run chkconfig <service name> on
  • Debian/Ubuntu: run update-rc.d <service name> defaults

Start a service

To start a service, run: service <service name> start

  • Example to start hapee-1.7-lb: service hapee-1.7-lb start
  • Example to start hapee-1.7-log: service hapee-1.7-log start

Stop a service

To stop a service, run: service <service name> stop

  • Example to stop hapee-1.7-lb: service hapee-1.7-lb stop
  • Example to stop hapee-1.7-log: service hapee-1.7-log stop

Restart a service

To restart a service, run: service <service name> restart

  • Example to restart hapee-1.7-lb: service hapee-1.7-lb restart
  • Example to restart hapee-1.7-log: service hapee-1.7-log restart

Reload a service

To reload a service, run: service <service name> reload

Example to reload hapee-1.7-lb: service hapee-1.7-lb reload

Example to reload hapee-1.7-log: service hapee-1.7-log reload

Check the status of a service

To know the status of a service, run: service <service name> status

Example output of a server status:

# service hapee-1.7-lb status
hapee-1.7-lb (pid  315) is running...
index