Content Gateway non-critical alerts

When you receive notification that non-critical alerts have been received from a Content Gateway instance, any of the following errors or conditions may have occurred. To determine which error occurred, check the Content Gateway manager associated with the affected Content Gateway instance.

Use the table below to get an overview of the error condition. More detailed information can be found in the system, error, and event log files on the Content Gateway machine.

Alert	Description
Content Gateway process reset	A problem that caused Content Gateway to restart. See the Content Gateway syslog file for information about what caused the reset.
Cache configuration issue	Content Gateway was unable to configure a cache. See “Configuring the Cache” in the Content Gateway Manager Help for more information.
Unable to create cache partition	An error occurred during cache configuration. See “Configuring the Cache” in the Content Gateway Manager Help.
Unable to initialize cache	A cache failure occurred. Content Gateway tolerates disk failure on any cache disk. If the disk fails completely, Content Gateway marks the disk as corrupt and continues using the remaining disks. See “Configuring the Cache” in the Content Gateway Manager Help.
Unable to open configuration file	There is a problem in a configuration file. Check the system log for information about which file is affected. Permissions to the file or directory may have changed. If the file was edited outside the Content Gateway manager, there may be invalid syntax or other problems preventing the file from being read.
Invalid fields in configuration file	One or more parameters or parameter values in a configuration file is incorrect. Check the system log for information about which file is affected.
Unable to update configuration file	There is a problem preventing a configuration file from being saved. Check the system log for information about which file is affected.
Clustering peer operating system mismatch	The nodes in a cluster must be homogeneous, with the same: Hardware platform Operating system version
Could not enable virtual IP addressing	Content Gateway attempted to enable virtual IP address failover, but failed. This often occurs when the designated virtual IP address is already in use in the network. Like all IP addresses, virtual IP addresses must be pre-reserved before they can be assigned to Content Gateway.
Connection throttle too high	A connection throttle event occurs when client or origin server connections reach 90% of half the configured connection limit (45000 by default). When you raise the connection throttle limit, the system must have adequate memory to handle the client connections required. A system with limited RAM might need a throttle limit lower than the default value.
Host database disabled	The host database stores the Domain Name Server (DNS) entries of origin servers to which the proxy connects. It tracks: DNS information (for fast conversion of hostnames to IP addresses) The HTTP version of each host (so advanced protocol features can be used with hosts running modern servers) Host reliability and availability information (to avoid waits for non- functional servers)
Logging configuration error	Content Gateway can be configured to log transactions, errors, or both to a location that you specify. See “Working with Log Files” in the Content Gateway Manager Help for information about logging.
Unable to open Content Gateway Manager	Content Gateway is unable to set up a socket to handle management API calls to start the Web interface.
ICMP echo failed for a default gateway	A Content Gateway node failed to contact its default gateway while assigning virtual IP addresses for a cluster. The node will shut down.
HTTP origin server is congested	When Content Gateway is deployed as a Web proxy cache, user requests for Web content pass through Content Gateway on the way to the destination Web server (origin server). When a client requests an HTTP object that is stale in the cache, Content Gateway revalidates the object, querying the origin server to check if the object is unchanged. If the origin server is congested (unable to accept additional connections), and does not respond to the revalidation query, the proxy does not perform any validation; it serves the stale object from the cache.
Congestion alleviated on the HTTP origin server	An origin server that previously denied connection attempts is now accepting requests again.
Content scanning skipped	Content Gateway did not scan content for a requested site that would have ordinarily be scanned. This may occur when Content Gateway is experiencing too many connections, or inadequate system resources (CPU and memory).
WCCP configuration error	See the “WCCP Configuration” section of the Content Gateway Manager Help for configuration parameter details.