Symantec™ Security Gateways Reference Guide - Sawmill

Log messagesError messages (400-499)233401 - Cannot find kill file descriptor for daemonDescription: Gwcontrol attempted to kill a connection but the connection information was invalid.401 - Cannot generate a key schedule from the session keyDescription: A secure remote login (SRL) client was unable to connect to the security gateway’s SRL daemon because itcould not generate a key schedule from the session key.401 - Cannot get blacklist protocol numberDescription: The notify daemon was unable to communicate with the remote blacklist daemon because of an invalidprotocol. The IP address is not blacklisted.401 - Cannot get interface listDescription: Blacklist daemon attempts to get the interface list to track the intruder, but fails.401 - Cannot get IP address of blacklist firewallDescription: Unable to get the IP address of the blacklist daemon that runs on another security gateway. The list ofblacklisted hosts are not sent.401 - Cannot get process listDescription: Vulture daemon is unable to acquire a list of legitimate processes that are functioning.401 - Cannot get socket for connectionDescription: Unable to allocate a socket for the connection between the security gateway services and gwcontrol.401 - Cannot get system nameDescription: (Microsoft Windows only) Unable to get the name of the security gateway, which is required by MicrosoftInternet Information Server.401 - Cannot initialize rule cacheDescription: The component was unable to load the security gateway rules as it does not have sufficient memory.401 - Cannot initialize rule caches, so performance may be degradedDescription: The HTTP daemon was unable to read the rules into its cache. The HTTP daemon will continue to apply therules, but will have to read the rule file repeatedly.401 - Cannot kill processDescription: The process cannot be killed.401 - Cannot lookup attached devicesDescription: There were either no interfaces configured, or an error occurred while building a list of interfaces.