Gateway 6.17.3 User Guide Save PDF Selected topic Selected topic and subtopics All content Axway Gateway: Managing the Server About gatestatus messages GateController and gatestatus Possible gatestatus responses List of gatestatus messages Resetting the status prompted by the gatestatus command to the default value GateController and gatestatus Gateway is designed as a modular system of loosely-coupled processes. The GateController process collects heartbeats and status messages from each of these individual processes. Despite being delivered to the operator through the gatestatus command, most of the messages GateController relays have nothing to do with GateController itself. gatestatus is not the best way to monitor Gateway. It is a simple reference tool for a system administrator to check the functioning of Gateway. gatestatus messages do not necessarily indicate that there is problem, merely a condition that can only be cleared with user intervention. Possible gatestatus responses There are four classes of message that gatestatus can return: Gateway stopped Gateway running Gateway restarting Process crashed These messages display the most recent status change for which GateController received a notification. To obtain more complete status information, including the time and date of the event, you should refer to the Gateway logs. The best way to monitor Gateway is by tracking it in Sentinel. You can then automatically extract messages of interest and create alerts when something is wrong. List of gatestatus messages Process crash messages Message Printing Gateway status: Warning. TSD process raised a problem to GateController Description A dynamic Gateway process monitored by the TSD crashed or does not answer any more. It will be managed by its parent process. Additional information In this case, one of the child processes of the p_tsd process had to be restarted. The actions were all managed by the TSD module, and simply reported to GateController. Unless this happens frequently, it is harmless. One possible cause is insufficient resources due to system or user limits (ulimit). Gateway should resolve this issue on its own and automatically clear this message. For more details about the problem, look in <Gateway installation directory>/run_time/tmp/TSD-<timestamp>-<pid>.out Message Printing Gateway status: Minor error. TSD process raised a problem to GateController Description A dynamic Gateway process monitored by the TSD crashed or does not answer any more. It will be managed by its parent process. Additional information Gateway should resolve this issue on its own and automatically clear this message. For more details about the problem, look in <Gateway installation directory>/run_time/tmp/TSD-<timestamp>-<pid>.out Message Printing Gateway status: Minor error. SUP process raised a problem to GateController Description A dynamic Gateway process monitored by the SUP crashed or does not answer any more. It will be managed by its parent process. Additional information Gateway should resolve this issue on its own and automatically clear this message. For more details about the problem, look in <Gateway installation directory>/run_time/tmp/SUP-<timestamp>-<pid>.out Message Printing Gateway status: Minor error. TSD process raised a problem to GateController Description A dynamic Gateway process monitored by the TSD crashed or does not answer any more. It will be managed by its parent process. For more information refer to the log. Additional information Gateway should resolve this issue on its own and automatically clear this message. For more details about the problem, look in <Gateway installation directory>/run_time/tmp/TSD-<timestamp>-<pid>.out Unable to retrieve messages Message Printing Gateway status Example: -- 2009/01/24 15:17:32 - ERROR from apigc_cli_build_cli_socket 2009/01/24 15:17:32 apigc_net_connect: SOCKET CONNECTION FAILED -- 2009/01/24 15:17:32 - ERROR from apigc_cli_init 2009/01/24 15:17:32 Client socket creation + connection failed. Retries are coming. -- 2009/01/24 15:17:35 - ERROR from apigc_cli_build_cli_socket 2009/01/24 15:17:35 apigc_net_connect: SOCKET CONNECTION FAILED 2009/01/24 15:17:39 apigc_net_connect: SOCKET CONNECTION FAILED 2009/01/24 15:17:44 apigc_net_connect: SOCKET CONNECTION FAILED 2009/01/24 15:17:48 apigc_net_connect: SOCKET CONNECTION FAILED 2009/01/24 15:17:52 apigc_net_connect: SOCKET CONNECTION FAILED GateController problem. Description GateController does not answer any more, but Gateway is still running. Additional information GateController is not running, but the pid file has not been cleaned up. Check for files named core in the Gateway and system core directories. Delete the pid file and attempt to restart Gateway. Message Printing Gateway status: GateController problem Description GateController does not answer any more, but Gateway is still running. Additional information GateController is not running, but Gateway is probably still trading. Restart Gateway when convenient. Resetting the status prompted by the gatestatus command to the default value The pelmon reset command enables you to reset the status prompted by the gatestatus command to the default value. After entering this command, Gateway returns the message: Printing Gateway status: running. Related topics Overview: Monitoring Gateway Starting and stopping the server Links to documentation set for Axway Gateway 6.17.3: Installation -- User -- Unix Configuration -- Upgrade -- Interoperability -- Security, requires login -- Release Notes Related Links
Axway Gateway: Managing the Server About gatestatus messages GateController and gatestatus Possible gatestatus responses List of gatestatus messages Resetting the status prompted by the gatestatus command to the default value GateController and gatestatus Gateway is designed as a modular system of loosely-coupled processes. The GateController process collects heartbeats and status messages from each of these individual processes. Despite being delivered to the operator through the gatestatus command, most of the messages GateController relays have nothing to do with GateController itself. gatestatus is not the best way to monitor Gateway. It is a simple reference tool for a system administrator to check the functioning of Gateway. gatestatus messages do not necessarily indicate that there is problem, merely a condition that can only be cleared with user intervention. Possible gatestatus responses There are four classes of message that gatestatus can return: Gateway stopped Gateway running Gateway restarting Process crashed These messages display the most recent status change for which GateController received a notification. To obtain more complete status information, including the time and date of the event, you should refer to the Gateway logs. The best way to monitor Gateway is by tracking it in Sentinel. You can then automatically extract messages of interest and create alerts when something is wrong. List of gatestatus messages Process crash messages Message Printing Gateway status: Warning. TSD process raised a problem to GateController Description A dynamic Gateway process monitored by the TSD crashed or does not answer any more. It will be managed by its parent process. Additional information In this case, one of the child processes of the p_tsd process had to be restarted. The actions were all managed by the TSD module, and simply reported to GateController. Unless this happens frequently, it is harmless. One possible cause is insufficient resources due to system or user limits (ulimit). Gateway should resolve this issue on its own and automatically clear this message. For more details about the problem, look in <Gateway installation directory>/run_time/tmp/TSD-<timestamp>-<pid>.out Message Printing Gateway status: Minor error. TSD process raised a problem to GateController Description A dynamic Gateway process monitored by the TSD crashed or does not answer any more. It will be managed by its parent process. Additional information Gateway should resolve this issue on its own and automatically clear this message. For more details about the problem, look in <Gateway installation directory>/run_time/tmp/TSD-<timestamp>-<pid>.out Message Printing Gateway status: Minor error. SUP process raised a problem to GateController Description A dynamic Gateway process monitored by the SUP crashed or does not answer any more. It will be managed by its parent process. Additional information Gateway should resolve this issue on its own and automatically clear this message. For more details about the problem, look in <Gateway installation directory>/run_time/tmp/SUP-<timestamp>-<pid>.out Message Printing Gateway status: Minor error. TSD process raised a problem to GateController Description A dynamic Gateway process monitored by the TSD crashed or does not answer any more. It will be managed by its parent process. For more information refer to the log. Additional information Gateway should resolve this issue on its own and automatically clear this message. For more details about the problem, look in <Gateway installation directory>/run_time/tmp/TSD-<timestamp>-<pid>.out Unable to retrieve messages Message Printing Gateway status Example: -- 2009/01/24 15:17:32 - ERROR from apigc_cli_build_cli_socket 2009/01/24 15:17:32 apigc_net_connect: SOCKET CONNECTION FAILED -- 2009/01/24 15:17:32 - ERROR from apigc_cli_init 2009/01/24 15:17:32 Client socket creation + connection failed. Retries are coming. -- 2009/01/24 15:17:35 - ERROR from apigc_cli_build_cli_socket 2009/01/24 15:17:35 apigc_net_connect: SOCKET CONNECTION FAILED 2009/01/24 15:17:39 apigc_net_connect: SOCKET CONNECTION FAILED 2009/01/24 15:17:44 apigc_net_connect: SOCKET CONNECTION FAILED 2009/01/24 15:17:48 apigc_net_connect: SOCKET CONNECTION FAILED 2009/01/24 15:17:52 apigc_net_connect: SOCKET CONNECTION FAILED GateController problem. Description GateController does not answer any more, but Gateway is still running. Additional information GateController is not running, but the pid file has not been cleaned up. Check for files named core in the Gateway and system core directories. Delete the pid file and attempt to restart Gateway. Message Printing Gateway status: GateController problem Description GateController does not answer any more, but Gateway is still running. Additional information GateController is not running, but Gateway is probably still trading. Restart Gateway when convenient. Resetting the status prompted by the gatestatus command to the default value The pelmon reset command enables you to reset the status prompted by the gatestatus command to the default value. After entering this command, Gateway returns the message: Printing Gateway status: running. Related topics Overview: Monitoring Gateway Starting and stopping the server Links to documentation set for Axway Gateway 6.17.3: Installation -- User -- Unix Configuration -- Upgrade -- Interoperability -- Security, requires login -- Release Notes