System Alarms

A content scanning engine is stuck. This alarm will display even in the event of a single engine being stuck while others are still processing correctly.

You are not able to manually clear this alarm. The alarm will be cleared when stuck engines are restarted or there is a proxy restart.

A content scanning engine was restarted.

The Gateway detected a failure while trying to download new updates. For online updates please check for connectivity issues. For offline updates please ensure the update disk is available to the system. See the Software Downloads log for more information.

Installation of a licensed module , such as an anti-virus scanner, has not been successful. Refer to the upgrade service log for more detailed information. You should also perform a connectivity test to check your connection to the upgrade server. When fixed, you may need to revalidate the license.

A license feature, such as the license required for an installed anti-virus scanner, has expired or is no longer available. Contact your reseller or Clearswift to renew your license.

A log file in /var/log/cs-gateway or /var/log is bigger than 50 MB. This alarm condition can arise if a system service is repeatedly recording warning or error messages in its daily log file.

CPU idle is 2% or less for a sustained period. The system cancels the alarm when CPU idle increases to 7% or more for a sustained period. Ignore this alarm unless it persists for more than ten minutes. Conditions that can trigger this alarm are:

• The overnight Database purge.
• System service startup.
• System upgrade or rollback.
• Abnormal system behavior.

Occupied disk space has reached 95% or more for a sustained period. The system cancels the alarm when disk space drops to 92% or less for a sustained period.  The alarm description may also include (main) or (data).

• (main) indicates that the root disk partition is running out of space.
• (data) indicates that the /var disk partition is running out of space.

Occupied disk space has reached 85% or more for a sustained period. The system cancels the alarm when disk space drops to 82% or less for a sustained period.  The alarm description may also include (main) or (data).

• (main) indicates that the root disk partition is running out of space.
• (data) indicates that the /var disk partition is running out of space. The most likely reason for low disk space is a very large number of messages held in message areas.

The LDAP Agent has failed to update an LDAP synchronized User List. See the LDAP Agent log for more information.

The Gateway Reporter has failed to access a Peer Gateway to transfer the Web Audit Logs.

Conditions that can trigger this alarm are:

• Network problems.
• The Peer Gateway has changed its administration password.
• The Peer Gateway has been taken out of service.
• The Peer Gateway and Gateway Reporter are not the same version.

The LDAP Agent has failed to update an LDAP Synchronized Address List. See the LDAP Agent log for more information.

A disk error has occurred. This may be a temporary condition. For example, a disk has been removed. However, it may indicate issues with the disk controller or hardware. More information about the error is included in the alarm description shown on the user interface.

A hardware event has occurred. See the Hardware Event Log for more details.

A temperature-related hardware event has occurred.

The Health and Statistic Gatherer Service is not running. This is usually a short-lived alarm condition, and is cleared when the next system status check occurs. Ignore this alarm unless it persists for several minutes. See Managing Services for more information.

Conditions that can trigger this alarm are:

• The service has crashed.
• Gateway re-boots.
• The service was terminated from the command line.

The Infrastructure Service is not running. This is usually a short-lived alarm condition, and is cleared when the next system status check occurs. Ignore this alarm unless it persists for several minutes. See Managing Services for more information.

Conditions that can trigger this alarm are:

• The service has crashed.
• Gateway re-boots.
• The service was terminated from the command line.

The Kaspersky Service is not running. This is usually a short-lived alarm condition, and is cleared when the next system status check occurs. See Managing Services for more information.

Conditions that can trigger this alarm are:

• Anti-virus definition updates.
• Configuration deployments.
• Gateway re-boots.
• System upgrades
• The service was terminated from the command line.

The Kaspersky anti-virus definitions have failed to be updated.

The LDAP Synchronization Service has failed. See the LDAP Log for details.

The SMTP Alert Transport is not running. This is usually a short-lived alarm condition, and is cleared when the next system status check occurs. Ignore this alarm unless it persists for several minutes. See Managing Services for more information.

Conditions that can trigger this alarm are:

• The service has crashed.
• Gateway re-boots.
• The service was terminated from the command line.

The managed list download has failed. Conditions that can trigger this alarm are:

• The download site cannot be accessed.
• A validation failure has occurred on an individual managed list.

Memory usage has reached 97% or more for a sustained period. The system cancels the alarm when memory usage drops to 94% or less for a sustained period.

Memory usage has reached 90% or more for a sustained period. The system cancels the alarm when memory usage drops to 87% or less for a sustained period.

An exception has occurred while purging the Web Audit database or while trying to publish data to the database.

The Watchdog Service is not running. This is usually a short-lived alarm condition, and is cleared when the next system status check occurs. Ignore this alarm unless it persists for several minutes. See Managing Services for more information.

Conditions that can trigger this alarm are:

• Gateway re-boots.
• The service has crashed.
• The service was terminated from the command line.

The Sophos anti-virus service is not running. This is usually a short-lived alarm condition, and is cleared when the next system status check occurs. See Managing Services for more information. This alarm is only displayed if you have licensed and enabled the Sophos anti-virus feature.

Conditions that can trigger this alarm are:

• Anti-virus definition updates.
• Configuration deployments.
• Gateway re-boots.
• System upgrades.
• The service was terminated from the command line.

Sophos anti-virus definitions have failed to be updated.

The database is not running. Conditions that can trigger this alarm are:

• The database was stopped from the command line.
• The database failed to initialise.

The Gateway has failed to connect to the external server hosting your exported system logs.

The URL databases consist of:

• The Caic URL database is out of date.
• The Malware URL database is out of date.
• The Phishing URL database is out of date.

The license required to access the URL database has expired.

The Upgrade Service has failed to apply an update. See the Upgrade Service log for more information. See Viewing Gateway Logs .

This alarm is raised to alert the administrator that an update for the Clearswift Gateway has been downloaded and is ready to be applied. See Software Version and Upgrades for details.

The alarm clears itself once the update has been applied. However a subsequent update may then be downloaded, which will result in the alarm being raised again.

The Web Proxy Service failed to load the URL database. Restarting the Web Proxy Service is recommended.

The User Interface Service is not running. This is usually a short-lived alarm condition, and is cleared when the next system status check occurs. Ignore this alarm unless it persists for several minutes. See Managing Services for more information.

Conditions that can trigger this alarm are:

• Gateway re-boots.
• The service has crashed.
• The service was terminated from the command line.

The Web Auditor Service is not running. This is usually a short-lived alarm condition, and is cleared when the next system status check occurs. Ignore this alarm unless it persists for several minutes. See Managing Services for more information.

Conditions that can trigger this alarm are:

• Gateway re-boots.
• The service has crashed.
• The service was stopped from the command line.