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.

136 Log messagesInformational messages (100-199)112 - Rule expired, re-scanning rulesDescription: The time range associated with a rule has expired, so the connection has to be reauthorized.115 - Successful authentication from remote management clientDescription: A user has remotely connected to the security gateway through the GUI. The parameters indicate theidentity and location of the remote connection.116 - Remote management completedDescription: Remote management sessions include connecting to the security gateway from another host by means ofthe SGMI, secure remote login (SRL), or the remlogsuite of utilities (remotelogdir and remotelogfile). Thismessage indicates that one of these remote management sessions terminated normally.117 - Daemon startingDescription: A proxy or a security gateway service is starting normally.117 - The Scan Engine has just started upDescription: The specified daemon (ftpd, dnsd or httpd) can use the antivirus scan server.118 - Daemon exitingDescription: A proxy or security gateway service is exiting normally.118 - Daemon exiting and disabledDescription: A security gateway server application exits, and is disabled because of problems.118 - Daemon exiting. Attempting to use Symantec Client VPN on security gatewayDescription: The client version of the component is not able to run on the server, so the daemon exits. Use the serverversion of the component.119 - Read of HTTP request failed due to overly long headerDescription: The HTTP daemon has a header that is suspiciously long.119 - Read of HTTP request failed due to too many header linesDescription: The HTTP daemon has a header with numerous lines.119 - Read of HTTP response failed due to overly long headerDescription: The HTTP response failed because of a long header. The connection is dropped.119 - Read of realaudio request failedDescription: While reading from the RealAudio server, an error was encountered. The connection may remain alive, butmay fail. Reestablish the connection.

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

Saved successfully!

Ooh no, something went wrong!