Symantec™ Security Gateways Reference Guide - Sawmill

Log messagesWarning messages (300-399)187301 - Failed to shutdown socketDescription: Unable to disable the send or receive action on the socket. The exact text of the error is available in the logmessage.301 - Failed to update tunnelDescription: Customers with a current support agreement may contact the Technical support group by phone or onlineat www.symantec.com/techsupp/.301 - Failed to write the pre-shared key to file for remote security gatewayDescription: This indicates an out of memory situation.301 - Failure to allocate memory to create a peer security gateway nodeDescription: This indicates an out of memory situation.301 - File required for backup is emptyDescription: The file which is required to perform a backup of the configuration, exists, but does not have anyinformation.301 - File_uncompress failed to unlink .gz fileDescription: Fetcher has successfully updated the ratings profile, but was unable to cleanup an interim file.301 - Fork failedDescription: One of the security gateway's software services tried to fork but failed. The system has probably run out ofswap space or processes. Reboot the system.If this message is sent by the notify daemon, it may indicate a problem trying to start a client notification.Ensure that the program is executable, has valid permissions, and resides in the right directory.301 - Further messages that packets from IP address were blocked will be suppressedDescription: The kernel will discontinue to send messages, which warn that it has been blocking packets from aparticular IP address.301 - Getrlimit (RLIMIT_NOFILE) failedDescription: A call to getrlimit from the system failed. If the user has specified a value for h323d.rlimit_nofile inconfig.cf, it may not be used.301 - Got ISAKMP configuration reply with zero-length attributeDescription: A bad packet was received during negotiation. The packet needs to be dropped.301 - Group cannot have other groups or workgroups as membersDescription: User groups consist of individual users, and user groups are created based on access levels. Therefore, agroup cannot have other groups or workgroup as members.