No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

HUAWEI CLOUD Stack 6.5.0 Alarm and Event Reference 04

Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
OBS Console

OBS Console

ALM-600000007 The OBS Console tomcat process is abnormal

Description

This alarm is generated when the Tomcat process of the monitored object is interrupted.

Attribute

Alarm ID

Alarm Severity

Auto Clear

600000007

Critical

Yes

Parameters

Parameter

Description

Location Info

Resource name

Name of the device for which the alarm is generated

Resource type

MONITOR

Monitor type

Service monitoring

Host IP address

IP address of the host

Details

Monitoring data recorded in recent monitoring periods

Threshold

Threshold for generating an alarm

Impact on the System

OBS Console cannot function properly.

Possible Causes

The Tomcat process of OBS Console fails to be started.

Procedure

  1. Use PuTTY to log in to the CONSOLE01 or CONSOLE02 node using the IP address corresponding to the OBS Console field.

    Default account is obs_admin, default password: Huawei12#$.

    NOTE:

    To obtain the IP address, search for CONSOLE01 or CONSOLE02 respectively in the Tool-generated IP Parameters datasheet of the parameter summary file xxx_export_all_EN.xlsm exported after parameters are configured using HUAWEI CLOUD Stack Deploy.

  2. Run the following command to switch to user root:

    sudo su

    Enter the password of user root following password for root, the default password of root is Cloud12#$.

  3. Run the following command to check whether the OBS service has been started successfully:

    sh /etc/obs/console/control.sh status

    • If yes, OBS is started successfully and Console is running is displayed in the command output. Go to 5.
      [root@CONSOLE02 obs_admin]# sh /etc/obs/console/control.sh status 
      Console is running
    • If no, OBS fails to be started and Console is not running is displayed in the command output. go to 4.
      [root@CONSOLE02 obs_admin]# sh /etc/obs/console/control.sh status  
      Console is not running

  4. Run the following command to restart the OBS service:

    sh /etc/obs/console/control.sh restart

    • If yes, OBS is restarted successfully and Start console successfully is displayed in the command output. Go to 5.
      [root@CONSOLE02 obs_admin]# sh /etc/obs/console/control.sh restart
      Stop console successfully
      Starting console component...
      Console started successfully
      Start console successfully
    • If no, contact technical support engineers for help.

  5. Check whether the alarm is cleared in the next monitoring period (about 3 minutes later).

    • If yes, the alarm is cleared and no further action is required.
    • If no, contact technical support engineers for help.

Related Information

None

ALM-600000008 The OBS Console tomcat port is not listening

Description

This alarm is generated when the Tomcat port 7583 of the monitored object fails to be bound.

Attribute

Alarm ID

Alarm Severity

Auto Clear

600000008

Critical

Yes

Parameters

Parameter

Description

Location Info

Resource name

Name of the device for which the alarm is generated

Resource type

MONITOR

Monitor type

Service monitoring

Host IP address

IP address of the host

Details

Monitoring data recorded in recent monitoring periods

Threshold

Threshold for generating an alarm

Impact on the System

OBS Console cannot function properly.

Possible Causes

The Tomcat port 7583 of OBS Console fails to be bound.

Procedure

  1. Use PuTTY to log in to the CONSOLE01 or CONSOLE02 node using the IP address corresponding to the OBS Console field.

    Default account is obs_admin, default password: Huawei12#$.

    NOTE:

    To obtain the IP address, search for CONSOLE01 or CONSOLE02 respectively in the Tool-generated IP Parameters datasheet of the parameter summary file xxx_export_all_EN.xlsm exported after parameters are configured using HUAWEI CLOUD Stack Deploy.

  1. Following command to switch to user root:

    sudo su

    Enter the password of user root following password for root, the default password of root is Cloud12#$.

  2. Run the following command to check whether the OBS service has been started successfully:

    sh /etc/obs/console/control.sh status

    • If yes, OBS is started successfully and the following command output is displayed. Go to 4.
      [root@CONSOLE02 obs_admin]# sh /etc/obs/console/control.sh status 
      Console is running
    • If no, OBS fails to be started and Console is not running is displayed in the command output. Go to 5.
      [root@CONSOLE02 obs_admin]# sh /etc/obs/console/control.sh status  
      Console is not running

  3. Run the following command to check whether the Tomcat port is bound properly:

    netstat -ntl

    • If yes, the OBS service port is bound successfully and the OBS Console service port (7583) is displayed in the command output. Go to 6.
      [root@CONSOLE02 obs_admin]# netstat -ntl
      Active Internet connections (only servers)
      Proto Recv-Q Send-Q Local Address           Foreign Address         State
      tcp        0      0 172.16.8.8:22             0.0.0.0:*               LISTEN
      tcp        0      0 172.16.8.8:21700          0.0.0.0:*               LISTEN
      tcp6       0      0 172.16.8.8:7563           :::*                    LISTEN
      tcp6       0      0 172.16.8.8:7443           :::*                    LISTEN
      tcp6       0      0 127.0.0.1:2324          :::*                    LISTEN
      tcp6       0      0 172.16.8.8:7583           :::*                    LISTEN
    • If no, the OBS service port fails to be bound and the OBS Console service port (7583) is not displayed in the command output. Go to 5.

  4. Run the following command to restart the OBS service:

    sh /etc/obs/console/control.sh restart

    • If yes, OBS is restarted successfully and Start console successfully is displayed in the command output. Go to 6.
      [root@CONSOLE02 obs_admin]# sh /etc/obs/console/control.sh restart
      Stop console successfully
      Starting console component...
      Console started successfully
      Start console successfully
    • If no, contact technical support engineers for help.

  5. Check whether the alarm is cleared in the next monitoring period (about 3 minutes later).

    • If yes, the alarm is cleared and no further action is required.
    • If no, contact technical support engineers for help.

Related Information

None

ALM-600000100 The OBS Console tomcat certificate exception

Description

This alarm is generated if the monitored Tomcat certificate of OBS Console is about to expire or has expired, or the validity monitoring is abnormal.

Attribute

Alarm ID

Alarm Severity

Auto Clear

600000100

Major/Critical

Yes

Parameters

Parameter

Description

Location Info

Resource name

Name of the device for which the alarm is generated

Resource type

MONITOR

Monitor type

Service monitoring

Host IP address

IP address of the host

Details

Monitoring data recorded in recent monitoring periods

Threshold

Threshold for generating an alarm

Impact on the System

OBS Console cannot function properly.

Possible Causes

  1. The validity period of the OBS Console Tomcat certificate is about to expire.
  2. The validity period of the OBS Console Tomcat certificate has expired.
  3. Validity monitoring on the OBS Console Tomcat certificate is abnormal.

Procedure

  1. 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#$

  2. In the upper part of the page, choose System> Monitoring. The service monitoring page is displayed.
  3. In the navigation tree on the left, choose Instances. In the search box in the upper right corner, enter OBS.
  4. Click the instance name in the row where the instance that you want to view resides. The instance monitoring page is displayed.
  5. In the navigation tree on the left, choose keystore. Check the monitoring status value of the OBS Console Tomcat certificate on the current node.

    • If the value is 1, the certificate is about to expire. Go to 6.
    • If the value is 2, the certificate has expired. Go to 6.
    • If the value is greater than or equal to 3, the certificate validity monitoring is abnormal. Contact technical support engineers.

  6. Replace the Tomcat certificate. For details, see section Updating the TLS Authentication Certificate of Tomcat on the OBS Console in HUAWEI CLOUD Stack 6.5.0 Security Management Guide.
  7. After the certificate is replaced, check whether the alarm is cleared within the next monitoring period (about 3 minutes later).

    • If yes, the alarm is cleared and no further action is required.
    • If no, contact technical support engineers for help.

Related Information

None

Translation
Download
Updated: 2019-08-30

Document ID: EDOC1100062365

Views: 48261

Downloads: 33

Average rating:
This Document Applies to these Products
Related Version
Related Documents
Share
Previous Next