List of alarms

Alarms are listed alphabetically.

To investigate an alarm raised in your Secure Email Gateway, you might need to check a specific log. See List of logs for more information on the logs.

A-E

• A certificate could not be generated by the Trust Center. See the Infrastructure log for details
• A download prior to upgrade has failed

  Secure Email Gateway detected a failure while trying to download new updates. For online updates, check for connectivity issues. For offline updates, ensure the update disk is available to the system.

• Anti Spam Service has failed. See SMTP log for more information

  The Anti Spam Service is not running. The alarm is cleared when the service is restarted successfully.

• A supplementary licensed module has failed to install

  Installation of a licensed module, such as an anti-virus scanner, has not been successful. See the Upgrade Service log for details. You should also perform a connectivity test to check your connection to the upgrade server. When fixed, you may need to validate the license again.

• A supplementary license feature is no longer available

  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 Fortra to renew your license.

• A system log file is very large

  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.

• Avira Service has failed

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

  Conditions that can trigger this alarm are:

  • Anti-virus definition updates.
  • Configuration deployments.
  • Gateway reboots.
  • System upgrades.
  • The service was terminated from the command line.
• Avira update has failed

  Avira anti-virus definitions have failed to be updated.

• Backup failed - see Backup Log for details
• Certificate Store has failed
• Contact your reseller or Fortra to renew your license
• CPU usage is high for sustained period

  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.
• Disk space is critical (data) / (main)

  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 (data) or (main).

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

  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 (data) or (main).

  • (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.
  • (main) indicates that the root disk partition is running out of space.

F-L

• Failed to add audit data to database

  The Message Auditor service has failed to add audit data to the database. See the Audit log for details.

• Failed to add held message to database

  The Message Area Manager service has failed to add a held message to the database. See the Infrastructure log for details.

• Failed to fetch PMM data from peer

  The PMM Infrastructure service has failed to access a Peer Gateway to retrieve PMM information to consolidate. See the PMM Infrastructure log for details.

  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.
• Failed to update LDAP address list

  The LDAP Address Synchronization service has failed to update an LDAP Synchronized Address List. See the LDAP Agent log for details.

• Hardware event - disk error

  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.

• Hardware event - see Hardware Event Log for details

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

• Hardware event - temperature high

  A temperature-related hardware event has occurred.

• Health and Statistic Gatherer has failed

  The Health and Statistics 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.

  Conditions that can trigger this alarm are:

  • The service has crashed.
  • Gateway re-boots.
  • The service was terminated from the command line.
• IG Server unreachable. See Messaging Service log for more information

  This alarm relates to licenseable functionality; if you do not see this alarm, it may be because you have not licensed this feature.

• Import of Encryption Certificate Store key failed. See System Services log
• Key Extraction has added a disabled certificate or key to the Certificate Store. See the User Interface Service log for details

  The alarm is raised when a disabled key or certificate A digital means of proving your identity. When you send a digitally-signed message, you are sending your certificate and public key. Certificates are issued by a certification authority and can expire or be revoked. has been added to the Certificate Store to allow the administrator to inspect the key and make a decision about the action to take, for example, enable the key, or, if the key is untrusted, either delete the key, or leave it disabled. The disadvantage of deleting an untrusted key instead of leaving it disabled, is that it could be added to the store again in the future, resulting in the administrator being alerted again. If the administrator clears this alarm, it will remain clear until the next time a disabled key is added to the Certificate Store. The alarm is automatically cleared if there are no disabled keys in the Certificate Store.

• LDAP Synchronization Service has failed

  The LDAP Address Synchronization service has failed. See the LDAP Agent log for details.

M-Q

• Managed list download failed

  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.
• Manager relationship list download failed
• Memory is critical

  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 is low

  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.

• Message Area Manager has failed

  The Message Area Manager 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.

  Conditions that can trigger this alarm are:

  • Anti-virus definition updates.
  • Configuration deployments.
  • Gateway re-boots.
  • System upgrades or rollbacks.
  • The service was stopped from the command line.
• Message Auditing has failed

  The Message 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.

  Conditions that can trigger this alarm are:

  • Anti-virus definition updates.
  • Configuration deployments.
  • Gateway re-boots.
  • System upgrades or rollbacks.
  • The service was stopped from the command line.
• One or more certificates being used in the configuration have warnings

  A certificate currently in use has been revoked or is suspicious, and requires a replacement. Identify the certificate in question in the Certificate Store using the Certificates with warnings check box in the Search Criteria.

• One or more LEQ flat files are using an insecure schema

  An LEQ file (the Data Set used by Lexical Expression Qualifiers) requires updating before it can be imported to your Secure Email Gateway as it was created using a less-secure ffcreate process.

  Use the command ffcreate -h to display the version number, and further help information.

• One or more LEQ flat files could not be imported to the latest schema

  The Lexical Data Import process has failed to import an LEQ file (Data Set). See the Infrastructure log for details.

• PMM has failed

  The PMM 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.

  Conditions that can trigger this alarm are:

  • Anti-virus definition updates.
  • Configuration deployments.
  • Gateway re-boots.
  • System upgrades or rollbacks.
  • The service was stopped from the command line.
• PMM Portal Web Server has failed
• Policy Engine error has occurred

  An error has occurred with the policy engine.

• Policy Engine failed to move a message

  The Policy Enforcement service has failed to move a message between processing areas. See the Policy Enforcement log for details.

• Policy Engine failed to process a message

  The Policy Enforcement service has failed to process a message. See the Policy Enforcement log for details.

  The failed message is moved into the Problem Messages Area and details of the message can be viewed from the Messages menu.

  These details should explain why the processing failure occurred. Conditions that can trigger this alarm are:

  • A very large message exceeded the maximum processing time.
  • A complex message part  exceeded the maximum recursive depth.
  • A text message part contained binary data.
  • A message part was badly formed and could not be decomposed.
• Policy Engine has failed
• Policy Engine health problem detected

  The Policy Enforcement service has detected problems that indicate that the service has become unreliable. See the Policy Enforcement log for details.

  If this alarm has triggered, restarting the service is recommended.

R-Z

• Restore completed successfully
• Restore failed - see Backup Log for details
• Restore interrupted - see Backup Log for details
• Sandbox connectivity problem

  Secure Email Gateway cannot communicate with the Sandbox Cloud Service.

• SMTP Alert Transport has failed

  The SMTP Alert Transport 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.

  Conditions that can trigger this alarm are:

  • Anti-virus definition updates.
  • Configuration deployments.
  • Gateway re-boots.
  • System upgrades or rollbacks.
  • The service was stopped from the command line.
• SMTP Inbound Transport has failed

  The SMTP Inbound Transport 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.

  Conditions that can trigger this alarm are:

  • Anti-virus definition updates.
  • Configuration deployments.
  • Gateway re-boots.
  • System upgrades or rollbacks.
  • The service was stopped from the command line.
• SMTP Outbound Transport has failed

  The SMTP Outbound Transport 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.

  Conditions that can trigger this alarm are:

  • Anti-virus definition updates.
  • Configuration deployments.
  • Gateway re-boots.
  • System upgrades or rollbacks.
  • The service was stopped from the command line.
• Sophos Service has failed

  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 update has failed

  Sophos anti-virus definitions have failed to be updated.

• SQL Database has failed

  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.
• Syslog server unreachable for 30 minutes. See the Infrastructure log for more information

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

• System Logging has failed
• The integrated firewall is not running
• The number of messages awaiting delivery has exceeded the configured threshold
• The number of messages waiting to be processed has exceeded the configured threshold

  By default, this alarm is triggered when 250 or more messages are waiting to be processed by the Policy Enforcement service. The alarm is canceled when the number drops below 200. Conditions that can trigger this alarm are:

  • The Policy Enforcement service is not running, or has not been running.
  • The Policy Enforcement service has been processing very large messages.
  • The CPU usage has been high for a sustained period.

  The default values can be changes to suit your preference.

• The reputation feed service is unavailable

  The service which checks spam reputations on incoming traffic is disconnected from your Secure Email Gateway. Run a connectivity test to check your HTTP connection or wait for the service to respond.

• The spam definition update service is unavailable

  The service which downloads spam definitions to your Gateway, has failed. Run a connectivity test to check your TRUSTmanager connection or wait for the service to respond.

• Transaction log export failed. See Transaction Log export log
• Trust Center automatic certificate generation has been disabled

  The peer responsible for automatic certificate generation is no longer contactable. This could be because a previous configuration has been restored to a new Gateway and is not peered to the Automatic Certificate Generation peer.

• TRUSTmanager's diagnostic logging is enabled
• Unable to connect to at least one Domain Controller
• Upgrade is available

  This alarm is raised to alert the administrator that an update for Secure Email Gateway has been downloaded and is ready to be applied.

  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.

• User Interface has failed

  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.

  Conditions that can trigger this alarm are:

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

See also...

• Service Control

• Installed Version and Upgrades

• Manage Held Messages