ALM-1150017 No Tomcat Process on a Combined API Node
Description
This alarm is generated when no Tomcat process runs on a Combined API node.
Attribute
Alarm ID |
Alarm Severity |
Auto Clear |
|---|---|---|
1150017 |
Critical |
Yes |
Parameters
Name |
Meaning |
|
|---|---|---|
Alarm Name |
Indicates the alarm name. |
|
Source system |
Indicates the name of the interconnected system. |
|
IP Address |
Indicates the IP address of the application server for which the alarm is generated. |
|
First Occurred At |
Indicates the time when the alarm was generated for the first time. |
|
Location Information |
Service |
Indicates the service for which the alarm is generated. |
Resource Type |
Indicates the type of the resource for which the alarm is generated. |
|
Monitor Type |
Indicates the type of the monitoring unit that generates the alarm. |
|
Host Ip |
Indicates the IP address of the host for which the alarm is generated. |
|
Detailed Information |
Indicates the detailed alarm information. |
|
Impact on the System
Combined API is unavailable.
Possible Causes
Combined API is not started.
Procedure
- Log in to ManageOne Maintenance Portal using a browser.
- URL: https://Address for accessing the homepage of ManageOne Maintenance Portal:31943, for example, https://oc.type.com:31943
- Default username: admin; default password: Huawei12#$
- On the menu bar in the upper part of the page, choose Alarms > Current Alarms.
- In the alarm list, locate the alarm to be handled, and click
![]()
on the left of the alarm. The Details page is displayed. - Choose Location Info, obtain the host IP address, that is, the IP address of the node where the alarm is generated.
- Use PuTTY to log in to the VM identified in 4.
The default username is apicom, and the default password is Huawei12#$.
- Run the following command to query the current Tomcat process:
ps -ef | grep tomcat | grep apicom
apicom 3087 1 2 Apr25 ? 00:39:02 /opt/common/jre/bin/java
In the command output, "3087" indicates the process ID of a Tomcat process.
- Run the following command to stop the Tomcat process:
kill -9 Process ID
In this command, Process ID indicates the process ID obtained in 6.
- Run the following command to restart the Tomcat process:
sh /opt/apicom/tomcat/bin/startup.sh
- After one minute, check whether the alarm is cleared.
- If yes, no further action is required.
- If no, contact technical support for assistance.
on the left of the alarm. The Details page is displayed.Reference
None
Previous
