12.07.2015 Views

Symantec™ Security Gateways Reference Guide - Sawmill

Symantec™ Security Gateways Reference Guide - Sawmill

Symantec™ Security Gateways Reference Guide - Sawmill

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Log messagesError messages (400-499)249421 - Dropping connections because the number of process instances already at configuredmaximumDescription: The number of process instances is limited for most proxies. This is because the number of concurrentconnections for the proxy has reached the configured maximum. This message occurs only once for eachproxy per start or stop.There are several reasons for the appearance of this message. You may not have enough security gatewaysto handle the number of concurrent connections at your installation, you may be under attack, or yoursecurity gateway may have the capacity to handle a larger number of concurrent connections but needs tobe configured appropriately.421 - Unable to create ACE server socketDescription: The SDI library failed to create a socket to talk to the ACE server. Someone is probably already using thissocket.422 - Bad port number rangeDescription: The proxy was unable to listen on a selected port range.423 - Bad protocol at lineDescription: The protocol was not UDP or TCP.423 - Node down due to ping monitoring failureDescription: HA/LB is unable to ping a node in the cluster. The node may not be functional. Check the target of the ping,to ensure that it responds.423 - Node down due to process monitoring failureDescription: The cluster is constantly monitoring other nodes to update the configuration data. In this case, the HA/LBprocess is unable to monitor the other nodes in the process. Check the list of processes being monitored.424 - Cannot use TCP ports because it is a reserved port. Set tcpgsp.allow_reserved_services=TRUEto permit thisDescription: TCP GSP is unable to use the TCP port because it is a reserved port.425 - Cannot lookup service at lineDescription: Service is unable to look up the symbolic name service in the etc/services file.430 - Cannot lookup hostnameDescription: The GSP is unable to lookup the host name in the file GSP.cf or the SMTP is unable to lookup the servername.432 - Bad host nameDescription: The host name in the HTTP configuration is invalid. Check the HTTP configuration settings.433 - Cannot connect to hostDescription: The NNTP daemon is unable to contact the remote host.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!