Error logs and templates

This topic includes the error log labels, error log types, and associated explanations for group servicdes.

Table 1 shows the error log templates that Group Services uses.

Each entry refers to a particular instance of the Group Services daemon on the local node. One entry is logged for each occurrence of the condition, unless otherwise noted in the entry's Detail Data section in the AIX® error log or Details File section in the Linux®, Solaris, or Windows system log. The condition is logged on every node where the event occurred.

The Detail Data or Details File section of these entries is not translated and appears only in English.

The valid error types are:

A: Alert, which indicates a failure in a Group Services client
E: Error, which indicates a failure in Group Services
I: Informational, which indicates status information

Table 1. Error log templates for Group Services
Label	Type	Diagnostic explanation and details
GS_ASSERT_EM	E	Explanation: The Group Services daemon produced a core dump. Details: The Group Services daemon encountered an irrecoverable assertion failure. This occurs only if the daemon core dumps due to a specific Group Services assertion failure. Group services will be restarted automatically and the situation will be cleared. However, its state is not cleared and the system administrator must determine the cause of the failure. In AIX error logs, the REFERENCE CODE field in the Detail Data section might refer to the error log entry that caused this event. See Information to collect before contacting the IBM Support Center and contact the IBM Support Center.
GS_AUTH_DENIED_ST	A	Explanation: An unauthorized user tried to access Group Services. Details: An unauthorized user tried to connect to the Group Services daemon. Standard fields indicate that Group Services daemon detected an attempt to connect from an unauthorized user. Detailed fields explain the detail information. Possibilities are: the user is not a root user, the user is not a member of the hagsuser group, or the user is not a supplemental member of the hagsuser group.
GS_CLNT_SOCK_ER	E	Explanation: A warning or error occurred on the Group Services client socket. Details: Group Services has an error on the client socket or the hagsuser group is not defined. Standard fields indicate that Group Services received an error or warning condition on the client socket. Detailed fields explain which error or warning caused this problem.
GS_DAEMON_UNRESP_WA	E	Explanation: The RSCT daemon (rmcd) is not responding, so the Group Services daemon will exit. Details: The RSCT daemon is not working correctly or might be blocked or the RSCT subsystem might be overloaded. Check the RSCT daemons.
GS_DEACT_FAIL_ST	I	Explanation: Failure of the deactivation script. Details:The Group Services daemon is unable to run the deactivation script. Standard fields indicate that the Group Services daemon is unable to run the script. Detailed fields give more information. The deactivation script might not exist or system resources are not sufficient to run the deactivation script.
GS_DOM_MERGE_ER	A, E	Explanation: Two Group Services domains were merged. Details: Two disjoint Group Services domains are merged because Topology Services has merged two disjoint node groups into a single node group. There may be several nodes with the same entries. Detailed fields contains the merging node numbers. At the time of domain merge, Group Services daemons on the nodes that generate GS_DOM_MERGE_ER entries will exit and be restarted. After the restart, (by GS_START_ST) Group Services will clear this situation. See Action 2: verify the status of the Group Services subsystem. In AIX error logs, the REFERENCE CODE field in the Detail Data section might refer to the error log entry that caused this event. See Information to collect before contacting the IBM Support Center and contact the IBM Support Center.
GS_DOM_NOT_FORM_WA	I	Explanation: A Group Services domain was not formed. Details: The Group Services daemon writes this entry periodically until the Group Services domain is formed. There may be several nodes in the same situation at the same time. The Group Services domain cannot be formed because: On some nodes, Topology Services might be running, but Group Services is not running. Name server recovery protocol is not complete. This entry is written periodically until the domain is established. The entry is written as follows: every 5, 30, 60, and 90 minutes, and then once every two hours as long as the domain is not established. The domain establishment is recorded by a GS_MESSAGE_ST template label. In AIX error logs, the REFERENCE CODE field in the Detail Data section might refer to the error log entry that caused this event.
GS_ERROR_ER	A, E	Explanation: A Group Services logic failure occurred. Details: The Group Services daemon encountered an irrecoverable logic failure. Detailed fields describes what kind of error is encountered. The Group Services daemon exits due to the Group Services logic failure. Group Services will be restarted automatically and the situation will be cleared. However, if the state is not cleared, the administrator must determine what caused the group services daemon to terminate. In AIX error logs, the REFERENCE CODE field in the Detail Data section might refer to the error log entry that caused this event. See Information to collect before contacting the IBM Support Center and contact the IBM Support Center.
GS_GLSM_ERROR_ER	A, E	Explanation: A Group Services globalized switch membership (GLSM) daemon logic failure occurred. This entry applies to AIX only. Details: The Group Services GLSM daemon encountered an irrecoverable logic failure. Standard fields indicate that the daemon stopped. Detailed fields point to the error log entry created when the daemon started. The Group Services GLSM daemon exited due to the logic failure. The Group Services GLSM daemon will be restarted automatically and the situation will be cleared. However, if the state is not cleared, the administrator must determine what caused the problem. The standard fields are self-explanatory. The REFERENCE CODE field in the Detail Data section might refer to the error log entry that caused this event. See Information to collect before contacting the IBM Support Center and contact the IBM Support Center.
GS_GLSM_START_ST	I	Explanation: The Group Services GLSM daemon started. This entry applies to AIX only. Details: The Group Services GLSM daemon has started. Standard fields indicate that the daemon started. Detailed fields contain the path name of the log file. The Group Services GLSM subsystem was started by a user or by a process. Issue this command: lssrc -l -s glsm_subsystem If the daemon is started, the output will contain a status of "active" for cthagsglsm. Otherwise, the output will contain a status of "inoperative" for cthagsglsm.
GS_GLSM_STARTERR_ER	A, E	Explanation: The Group Services GLSM daemon cannot be started. This entry applies to AIX only. Details: The Group Services GLSM daemon encountered a problem during startup. Standard fields indicate that the daemon is stopped. Detailed fields point to the error log entry created when the daemon started. The Group Services daemon cannot be started because exec to hagsglsmd has failed. The AIX log entry may be the only remaining information about the cause of the problem after it is cleared.
GS_GLSM_STOP_ST	I	Explanation: The HA Group Services globalized switch membership (HAGSGLSM) daemon stopped. This entry applies to AIX only. Details: The Group Services GLSM daemon was stopped by a user or by a process. Standard fields indicate that the daemon stopped. Detailed fields point to the error log entry created when the daemon started. If the daemon was stopped by the system resource controller (SRC), the phrase SRC will be present in the Detail Data section. The REFERENCE CODE field in the Detail Data section might refer to the error log entry that caused this event. Issue this command: lssrc -l -s glsm_subsystem If the daemon is stopped, the output will contain a status of "inoperative" for cthagsglsm. Otherwise, the output will contain a status of "active" for cthagsglsm.
GS_HATS_BLOCKED_ER	E	Explanation: The Topology Services subsystem is not responding. Details: The Topology Services daemon is blocked due to resource contention.
GS_INVALID_MSG_ER	A, E	Explanation: The Group Services daemon received an unknown message. Details: The Group Services daemon received an incorrect or unknown message from another daemon. The transmitted messages may be corrupted on the wire, or a daemon sent a corrupted message. The Group Services daemon will restart and clear the problem. See Information to collect before contacting the IBM Support Center and contact the IBM Support Center.
GS_MESSAGE_ST	I	Explanation:This is an informational message about Group Services. Details: The Group Services daemon has an informational message about the Group Services activity, or condition. Detailed fields describes the information. It is one of the following: The Group Services daemon is not connected to Topology Services. The Group Services domain has not recovered or been established after a long time. Any other message, which will be in the detailed field. In AIX error logs, the REFERENCE CODE field in the Detail Data section might refer to the error log entry that caused this event.
GS_START_ST	I	Explanation: The Group Services daemon started. Details: The Group Services subsystem is started by a user or by a process. Detailed fields contain the log file name.
GS_STARTERR_ER	A, E	Explanation: Group Services cannot be started. Details: The Group Services daemon encountered a problem during startup. Information about the cause of this problem may not be available once the problem is cleared. The group services daemon cannot start because one of the following conditions occurred: exec to hagsd failed. The environment variables used by the startup scripts are not set properly. Daemon initialization failed.
GS_STOP_ST	I	Explanation: The Group Services daemon stopped. Details: The Group Services daemon was stopped by a user or by a process. Detailed fields indicate how the daemon stops. If this was not intended, the system administrator must determine what caused the Group Services daemon to terminate. If the daemon was stopped by the system resource controller (SRC), the phrase SRC will be present in the Detail Data or Details File section.
Group Services_TS_RETCODE_ER	A, E	Explanation: The Topology Services library detected an error condition. Details: The Group Services daemon received an incorrect or unknown message from another daemon. This entry refers to a particular instance of the Topology Services library on the local node. Standard fields indicate that Group Services received an error condition from Topology Services. Detailed fields contain the explanation and Topology Services library error number. The Group Services daemon will restart and clear the problem.
GS_XSTALE_PRCLM_ER	A, E	Explanation: A "non-stale" proclaim message was received. This means that inconsistent domain join request messages were received. Details: The local node received a valid domain join request (proclaim) message from its name server twice. This should not happen in a normal situation. Detailed fields point to the error log entry of a NodeUp event. Topology Services reports inconsistent node down and up events among nodes. The Group Services daemon will restart and clear the problem. For more information, see the symptom "Non-stale proclaim message received" in Error symptoms, responses, and recoveries. In AIX error logs, the REFERENCE CODE field in the Detail Data section might refer to the error log entry that caused this event. See Information to collect before contacting the IBM Support Center and contact the IBM Support Center.