Guardian Configuration

From Wiki

Jump to: navigation, search


Guardian Configuration overview

After you have completed all the steps from the Guardian installation process you may want to apply some custom configurations on the software. You may configure through console or through the WHM Plugin/Local Interface Settings. The following options can be altered according to your needs:

Restart interval

Guardian checks if each service is up every 0.5 seconds. If a service is down the Guardian will automatically restart it. However, the restart process itself may take longer than 0.5 seconds and thus the service will still be down on the next check although the restart is actually in progress. To avoid multiple unnecessary restarts Guardian will wait 30 seconds before initiating a second restart for the same service. This default 30 seconds period can be customized by the user. We will show you how below.

Values for Normal, High and Critical load levels

Guardian monitors server load level and depending on the values takes measures to prevent overload. It has a sophisticated system that applies hierarchy of different solutions (renice, ionice, pause, kill) for different load levels.

There are three values of load normal, high and critical based on which the measures are applied. The values are set by default to 8, 15 and 20 respectively, but can be customized. The default logic is as follows

Any Load

Guardian monitors all processes running on the server and kills the ones, that are running more than 120 seconds, unless the
processes are owned by protected users. This setting is default and can be configured.

Normal Load

If the average load on the server is above the Normal Load value:

* PHP processes(child of suexec) that are running more than 15 seconds are killed
* ionice and renice are applied to the currently running rsync and archive processes - those are automatically removed when the
  load drops below the normal value

High Load

If the average load on the server is above the High Load value:

* PHP processes(child of suexec) that are running more than 15 seconds are killed
* IMAP processes that are running more than 360 seconds are killed
* All rsync and archive processes are PAUSED

Critical Load

If the average load on the server is above the Critical Load value:

* All PHP processes are killed, no matter how much time they are running
* IMAP processes that are running more than 360 seconds are killed
* All archive processes are killed

These settings are Guardian defaults. You can change them at any time. To see details refer to Guardian kill logic article

Monitored services

By default Guardian will be monitoring all the services listed below, unless you configure it to exclude any of them :

The most common services ran on a hosting server using cPanel: 

* cpanel - The cPanel for the server
* directadmin - The DirectAdmin control panel
* cpanellogd - The cPanel log daemon
* crond - The Cron Jobs daemon
* dovecot - The Dovecot secure IMAP server
* courier - The Courier IMAP server
* exim - The exim mail server
* ftp - The pureftpd daemon
* httpd - The web server: Apache, LiteSpeed, nginx
* ionotify - The daemon used to catch received callbacks about IO activity.
* klogd - The Kernel Logging Daemon
* mysql - The MySQL server
* mailquotad - The Mailquota Daemon
* named - The Domain Name System (DNS) server
* nscd - The Name Service Cache Daemon
* postgres - The PostgreSql server
* pop3/imap - The POP3 and IMAP mail services
* plesk - The Plesk control panel
* proftpd - The proftpd daemon
* qmail - The qmail SMTP service
* smtp - The SMTP (Simple Mail Transfer Protocol) service
* syslogd - The Linux system logging utilities
* lfd - ConfigServer Firewal (CSF) Login Failure Daemon 
* clamav - Antivirus engine for detecting Trojans, viruses, malware and other malicious threats
* cdp-agent - R1Soft back agent
* cdp-server  - R1Soft back server 
1H Software services:

* lifesigns - a daemon part of the1H Guardian
* cpustatsd - a statistics daemon part of 1H Hive
* hawk - The 1H Hawk software
* licd - The 1H Licensing Daemon

Important: Other services can be added to the list by 1H per customer request.

Important: Note that if any of the services is not detected on your hosting server it will be automatically excluded from the list by the Guardian.

Protected users

By default there are several system users that are protected, which means that processes ran by those users will remain untouched regardless of the current server load. You can remove and add users to this protected list, but it is highly recommended to add only system users. The default list of protected users include:

protected users: root, mysql, nscd, named, mailnull, postgres, cpanel

Configuration through console

To configure Guardian through console you have to manually edit this file:


It includes the following:

archivers_re=rar|tar |gzip|bzip2|zip|zcat


Note: If you change the location of the status file. Be sure to change it in lifesigns.conf also. Failure to do so, will cause LifeSigns to consider guardian as down.

Configuration through Local Interface Settings/WHM Plugin

Guardian configuration can be adjusted via both the 1H WHM Plugin and the Settings section for the 1H Local Interface.

Both interfaces will provide you with the same options:

Guardian configuration.png

In this panel you will be able to modify the restart interval, the normal,high and critical load values, as well as enable/disable monitoring for the predefined services in the configuration and add/remove protected users.

Guardian Articles

Here you can find a list of relevant articles regarding the 1H Guardian Software.

Personal tools