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)243401 - Trying to kill process IDDescription: Gateway control (Gwcontrol) tries to kill a process and fails. Gwcontrol may have been directed by theadministrator to kill the process.401 - Two instances of default interface in hash tableDescription: Only one interface is the default interface. Remove the undesired one.401 - Unable to add IP to blacklistDescription: The security gateway identifies a particular IP address that should be blacklisted, but was unable to add itto the list. As a result, the IP address may attempt to access the security gateway. This is an internal errorand could indicate a problem with the security gateway.401 - Unable to allocate memory for argumentsDescription: Unable to allocate enough memory to create the process information table in the raptor service (MicrosoftWindows – eaglesvc) daemon.401 - Unable to bind blacklist socketDescription: The Notify daemon encountered errors receiving a response from the blacklist daemon. The IP address isnot blacklisted.401 - Unable to bind to any UDP socket for listening to ISAKMP requests, so service will exitDescription: (Microsoft Windows only) To rectify this problem, disable the visual notification from the Dr. Watsonutility for Microsoft Windows.401 - Unable to bind to oobauthd portDescription: The oobauth daemon is unable to listen on its port because another process is listening on the oobauthport.401 - Unable to bind UDP socketDescription: In the case of bullfrog daemon, unable to bind to cluster command control port (default to 6373). Ensurethat no other service is using it, or configure bullfrogd to use a different port.401 - Unable to change log file over to the new log file nameDescription: The logservice daemon attempts to roll over the log file but fails. There should be a subsequent logmessage that indicates the next course of action.401 - Unable to clear driver blacklistDescription: The blacklist daemon is unable to inform the driver to clear the old blacklisted IP addresses. As a result,some of the addresses continue to be denied access to the security gateway services.401 - Unable to connect oobauthui datagram socketDescription: The Out of Band Authentication (OOBA) daemon is unable to make the connections that it requires toauthenticate users. No user is able to authenticate.

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

Saved successfully!

Ooh no, something went wrong!