Diagnosis Guide

Error information

AIX Error Logs and templates

Table 60 shows the AIX error log templates used by GS.

GS_ASSERT_ER
GS_AUTH_DENIED_ST
GS_CLNT_SOCK_ER
GS_DEACT_FAIL_ST
GS_DOM_MERGE_ER
GS_DOM_NOT_FORM_WA
GS_ERROR_ER
GS_GLSM_ERROR_ER
GS_GLSM_START_ST
GS_GLSM_STARTERR_ER
GS_GLSM_STOP_ST
GS_INVALID_MSG_ER
GS_MESSAGE_ST
GS_START_ST
GS_STARTERR_ER
GS_STOP_ST
GS_TS_RETCODE_ER
GS_XSTALE_PRCLM_ER

When you retrieve an error log entry, look for the Detail Data section near the bottom of the entry.

Each entry refers to a particular instance of the GS daemon on the local node. One entry is logged for each occurrence of the condition, unless otherwise noted in the Detail Data section. The condition is logged on every node where the event occurred.

The Detail Data section of these entries is not translated to other languages. This section is in English.

The error type is:

A - Alert (failure in a GS client)
E - Error (failure in GS)
I - Informational (status information)

Table 60. AIX Error Log templates for Group Services

Label and Error ID	Type	Diagnostic explanation and details
GS_ASSERT_ER 5608839C	E	Explanation: The GS daemon produced a core dump. Details: The GS daemon encountered an irrecoverable assertion failure. This occurs only if the daemon core dumps due to a specific GS assertion failure. GS 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. The REFERENCE CODE field in the Detail Data section may refer to the error log entry which caused this event. See Information to collect before contacting the IBM Support Center and contact the IBM Support Center.
GS_AUTH_DENIED_ST 23628CC2	A	Explanation: An unauthorized user tried to access GS. Details: An unauthorized user tried to connect to the GS daemon. Standard fields indicate that GS 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, or the user is not a member of the hagsuser group.
GS_CLNT_SOCK_ER E31202B3	E	Explanation: Warning or error on the Group Services client socket. Details: Group Services has an error on the client socket, or the AIX hagsuser group is not defined. Standard fields indicate that Group Services received an error or warning condition on the client socket. Detailed fields explain what error or warning caused this problem.
GS_DEACT_FAIL_ST 972737A5	I	Explanation: Failure of the deactivate script. Details: The GS daemon is unable to run the deactivate script. Standard fields indicate that the GS daemon is unable to run the script. Detailed fields give more information. The deactivate script may not exist, or system resources are not sufficient to run the deactivate script.
GS_DOM_MERGE_ER 267369E6	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, GS 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. The REFERENCE CODE field in the Detail Data section may refer to the error log entry that caused this event. See Action 2 - Verify Status of Group Services Subsystem. See Information to collect before contacting the IBM Support Center and contact the IBM Support Center.
GS_DOM_NOT_FORM_WA 83B3361F	I	Explanation: A Group Services domain was not formed. Details: The GS daemon writes this entry periodically until the GS domain is formed. There may be several nodes in the same situation at the same time. The GS domain cannot be formed because: On some nodes, Topology Services may be running but GS is not. Nameserver 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, 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. The REFERENCE CODE field in the Detail Data section may refer to the error log entry that caused this event.
GS_ERROR_ER 2C582BE2	A, E	Explanation: Group Services logic failure. Details: The GS daemon encountered an irrecoverable logic failure. Detailed fields describes what kind of error is encountered. The GS daemon exits due to the GS 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 GS daemon to terminate. The REFERENCE CODE field in the Detail Data section may 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 E0A52CFA	A, E	Explanation: Group Services GLSM daemon logic failure. 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 may 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 3C447B26	I	Explanation: Group Services GLSM Daemon started (AIX error log entry). 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` where `subsystem` is: hagsglsm.`partition` on the PSSP control workstation hagsglsm on a PSSP node grpglsm on a HACMP node If the daemon is started, the output will contain a status of "operative" for hagsglsm. Otherwise, the output will contain a status of "inoperative" for hagsglsm.
GS_GLSM_STARTERR_ER 2BF4FAC3	A, E	Explanation: Group Services GLSM daemon cannot be started. 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 GS daemon cannot be started because: Syspar class in the SDR cannot be obtained. 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 177CF680	I	Explanation: HAGSGLSM (HA Group Services GLobalized Switch Membership) daemon stopped. 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 SRC, the word "SRC" will be present in the Detail Data. The REFERENCE CODE field in the Detail Data section may reference the error log entry that caused this event. Issue this command: lssrc -l -s `glsm_subsystem` where `subsystem` is: hagsglsm.`partition` on the PSSP control workstation hagsglsm on a PSSP node grpglsm on a HACMP node If the daemon is stopped, the output will contain a status of "inoperative" for hagsglsm. Otherwise, the output will contain a status of "operative" for hagsglsm.
GS_INVALID_MSG_ER 4242B470	A, E	Explanation: The GS daemon received an unknown message. Details: The GS 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 GS 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 F3AB2E54	I	Explanation: Group Services informational message Details: The GS daemon has an informational message about the Group Services activity, or condition. Detailed fields describes the information. It is one of the following: The GS daemon is not connected to Topology Services. The GS domain has not recovered or been established after a long time. Any other message, which will be in the detailed field. The REFERENCE CODE field in the Detail Data section may refer to the error log entry that caused this event.
GS_START_ST B4D19120	I	Explanation: Group Services daemon started. Details: The GS subsystem is started by a user or by a process. Detailed fields contain the log file name.
GS_STARTERR_ER 66E04502	A, E	Explanation: Group Services cannot be started. Details: The GS daemon encountered a problem during startup. Information about the cause of this problem may not be available once the problem is cleared. The GS daemon cannot start because one of the following conditions occurred: Syspar class in the SDR cannot be obtained. exec to hagsd failed. The environment variables used by the startup scripts are not set properly. Daemon initialization failed.
GS_STOP_ST 28EDAA82	I	Explanation: Group Services daemon stopped. Details: The GS 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 GS daemon to terminate. If the daemon was stopped by the AIX SRC, "SRC" will be present in the Detail Data.
GS_TS_RETCODE_ER EB38514E	A, E	Explanation: The Topology Services library detected an error condition. Details: The GS 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 GS daemon will restart and clear the problem. The standard fields are self-explanatory. The REFERENCE CODE field in the Detail Data section may contain the Topology Services log entry that causes this event. See Action 7 - Investigate Group Services failure.
GS_XSTALE_PRCLM_ER 6D790718	A, E	Explanation: 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 his Nameserver 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 between nodes. The GS daemon will restart and clear the problem. The REFERENCE CODE field in the Detail Data may reference the error log entry that caused this event. For more information, see the symptom "Non-stale proclaim message received" in Error symptoms, responses, and recoveries. See Information to collect before contacting the IBM Support Center and contact the IBM Support Center.

[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]