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).
ALM-1110021 AS Jetty Process Does Not Exist

ALM-1110021 AS Jetty Process Does Not Exist

Description

This alarm is generated when the schedule process on an AutoScaling-Schedule node does not exist.

Attribute

Alarm ID

Alarm Severity

Auto Clear

1110021

Major

Yes

Parameters

Parameter

Description

Alarm Name

Alarm name.

Source System

Name of the source system where the alarm is generated.

IP Address

IP address of the ECS where the alarm is generated.

Last Occurred At

Time when the alarm was generated for the last time.

Additional Information

Supplementary information about the alarm.

Impact on the System

An AS service exception occurs and scaling actions cannot be implemented.

Possible Causes

The schedule process does not exist.

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. On the menu bar in the upper part of the page, choose Alarms > Current Alarms.
  3. In the alarm list, locate the alarm to be handled, and click on the left of the alarm. The Details page is displayed.
  4. Choose Location Info, obtain the host IP address, that is, the IP address of the node where the alarm is generated.
  5. Use PuTTY to log in to the VM identified in 4.

    Default username: admin; default password: IaaS@OS-CLOUD9!

  1. Run the following command to disable PuTTY logout upon timeout:

    TMOUT=0

  2. Run the following command to check whether the schedule process exists:

    ps -ef|grep autoscaling-schedule

    If the following information is displayed, the process exists:

    admin    32250     1 27 15:10 pts/0    00:00:19 /opt/autoscaling/jre1.8/bin
    ...
    • If yes, go to 13.
    • If no, go to 8.

  3. Run the following command to view the AS-SCHEDULE-SCHEDULE01 or AS-SCHEDULE-SCHEDULE02 node logs and check for exception logs by searching for keyword Exception:

    vi /var/log/autoscaling-schedule/schedule.log

    If the error message HibernateException,cannot open session is displayed, the database cannot be connected. Go to 9.

  4. Use PuTTY to log in to the AS-SCHEDULEDB node using the floating IP address of the AS-Schedule-DB-Float-IP node.

    Default username: admin; default password: IaaS@OS-CLOUD9!

  5. Run the following command and enter the password of the root user to switch to the root user:

    sudo su - root

    The default password of the root user is Cloud12#$.

  6. Run the following command to disable PuTTY logout upon timeout:

    TMOUT=0

  7. Run the following command to check whether the database status is normal:

    service had query

    If the following information is displayed, the database status is normal:

    NODE                                     ROLE           PHASE           RESS            VER             START          
    AS-Schedule-DB01(AS-Schedule-DB01)       active         Actived         normal          V100R001C01     2019-01-01 12:16:29
    AS-Schedule-DB02(AS-Schedule-DB02)       standby        Deactived       normal          V100R001C01     2019-01-07 21:30:05
    
    --------------------------------------------------------------------------------------------------------
                                             ID    RES                      STAT            RET             TYPE           
    AS-Schedule-DB01(AS-Schedule-DB01):      1     exfloatip                Normal          Normal          Single_active  
                                             2     gaussDB                  Normal          Active_normal   Active_standby 
    
    AS-Schedule-DB02(AS-Schedule-DB02):      1     exfloatip                Normal          Abnormal        Single_active  
                                             2     gaussDB                  Normal          Standby_normal  Active_standby 
    • If yes, go to 13.
    • If no, contact technical support for assistance.

  8. After rectifying the fault, log in to the AS-SCHEDULE-SCHEDULE01 or AS-SCHEDULE-SCHEDULE02 node as the admin user and run the following command to restart the schedule process:

    sh /opt/autoscaling/autoscaling-schedule/bin/schedule.sh restart

    If the following information is displayed, the jetty process is restarted successfully:

    stop schedule succeed.
    start schedule succeed.

  9. If the AS service is still unavailable, contact technical support for assistance.

Related Information

None

Translation
Download
Updated: 2019-08-30

Document ID: EDOC1100062365

Views: 34307

Downloads: 31

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