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.

234 Log messagesError messages (400-499)401 - Cannot open configuration fileDescription: Gwcontrol could not open its configuration file for reading. This message comes from many locationsincluding the bullfrog daemon, ISAKMP daemon, VPN, and filter utilities. Each attempt to open aconfiguration file failed. The name of the file gwcontrol requested should be in the filename parameter.401 - Cannot open fileDescription: Unable to open the specified file.401 - Cannot read configuration fileDescription: This indicates a missing cluster.cf file or corrupted file. Contact support for assistance.401 - Cannot read etc/passwdDescription: The secure remote login (SRL) daemon is unable to access the password file. All SRL connections aredenied.401 - Cannot read fileDescription: Unable to read the specified file.401 - Cannot set all transparent ranges for interfaceDescription: A tunnel or cluster is unable to set up its interfaces properly. Therefore, transport connections will notfunction.401 - Cannot set interface parametersDescription: Cannot set address and mask for interface.401 - Cannot set time of dayDescription: An attempt to set the time of day has failed.401 - Cannot start HA/LB engineDescription: Unable to start the high availability/load balancing (HA/LB) engine. The system will restart the engineafter waiting for 5 seconds. If the problem persist, try to reboot the whole cluster.401 - Cannot start logoff for userDescription: (Microsoft Windows only) The vulture daemon attempts to block a user who is unauthorized to log into thesystem.401 - Cannot synchronize battery timeDescription: The time on the hardware clock cannot be set.401 - Card name is too longDescription: This is an internal resource allocation issue. Try decreasing the load.

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

Saved successfully!

Ooh no, something went wrong!