Warnings

Message Description
Logfile error: error_number Generic logging error.

Bad cluster major version range

version1-version2 for node

IP address connect failed

Incompatible software versions causing a problem.
can’t open config file filename for reading custom formats Custom logging is enabled, but Content Gateway cannot find the logs.config file.

connect by disallowed client

IP address, closing connection

The specified client is not allowed to connect to Content Gateway. The client IP address is not listed in the ip_allow.config file.

Could not rename log filename to

rolled filename

System error when renaming log file during roll.

Did this_amount of backup still to do

remaining_amount

Congestion is approaching.
Different clustering minor versions version 1, version 2 for node IP address continuing Incompatible software versions causing a problem.
log format symbol symbol_name not found Custom log format references a field symbol that does not exist. See Event Logging Formats.
missing field for field marker Error reading a log buffer.
Unable to accept cluster connections on port: cluster_port_number Contact Technical Support. Go to support.forcepoint.com for Technical Support contact information
Unable to open log file filename, errno=error_number Cannot open the log file.
Error accessing disk disk_name Content Gateway might have a read problem. You might have to replace the disk.

Too many errors accessing disk

disk_name: declaring disk bad

Content Gateway is not using the disk because it encountered too many errors. The disk might be corrupt and might have to be replaced.

Missing DC parameter

<missing_param> on auth.profile line

A required parameter was not specified. Please provide a value for the missing parameter.

Bad DC parameter <bad_param> -

<dc_name>

A specified Domain Controller parameter is invalid. Please enter a valid value for the cited parameter.

[ParentSelection]

<error_description> for default parent proxy

Proxy chaining is not working due to misconfiguration of the parent proxy in the child proxy. Please check the chaining configuration of parent proxy values in the child proxy.
WCCP2: Cannot find Interface name. Please check that the variable proxy.local.wccp2. ethernet_interface is set correctly No value is specified for the WCCP interface. In the Content Gateway manager, check Configure > Networking > WCCP > General, or assign a value to proxy.local.wccp2.ethernet_interface in records.config.
ARMManager: Unable to read network interface configuration There is a format or configuration error in ipnat.conf. In the Content Gateway manager, go to Configure > Networking > ARM > General and click Edit File to view and correct ipnat.conf.