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

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Log messagesCritical messages (600-699)261603 - Fork failedDescription: One of the security gateway’s services attempts to fork but fails. The system may have run out of swapspace or available processes. Power cycling is necessary to release system resources.604 - Failed to install configurationDescription: The process attempts to synchronize the configuration across the cluster, but fails to install theconfiguration.604 - User count limit exceededDescription: The license limit has been reached. You may need to acquire more licenses or release some accounts.605 - Cannot executeDescription: The component was unable to run a user script. The log message identifies the component. Execute thescript from the command-line to check if the script is valid.If this message is sent by the secure remote login (SRL) daemon, it indicates that the user was attemptingto logon at the shell prompt, and the execution of the login script failed. Delete and add this to the useragain.If this message is sent by the notify daemon, it indicates that it was unable to execute a pager, mail or clientprogram. Check the configuration parameters for these notifications.605 - Cannot execute (child limit reached)Description: The notify daemon has reached the limit on the number of client programs that the security gateway canstart. This notification is not sent to the client program.606 - Failed to notify transportDescription: The notify daemon failed to send a message using the transport.606 - Failed to send notificationDescription: The notify daemon was unable to send a notification for the log message because either the message iscorrupted or the transport failed (in which case there should be additional messages with details prior tothis message).607 - Daemon exited on signalDescription: A security gateway server application exited because of a software signal.608 - Daemon exiting because the blacklist port cannot be bound toDescription: Blacklist daemon is unable to listen to a blacklist address request because the blacklist port cannot bebound to it.608 - Daemon exiting because a socket for the blacklist port cannot be createdDescription: Blacklist daemon is unable to listen to a blacklist address request because a socket for the blacklist portcannot be created.

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

Saved successfully!

Ooh no, something went wrong!