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).
EVT-1110003 Communication Between the AutoScaling-Server Node and AutoScaling-Schedule Node Is Interrupted

EVT-1110003 Communication Between the AutoScaling-Server Node and AutoScaling-Schedule Node Is Interrupted

Description

The server process (also called the tomcat process) on the AutoScaling-Server nodes of the AS service communicates with the schedule process on the AutoScaling-Schedule nodes. This event is generated when an exception occurs in the process.

Attribute

Event ID

Event Severity

1110003

Critical

Event Parameters

Name

Meaning

Event Name

Indicates the event name.

Event Source

Indicates the device for which the event is generated.

Source System

Indicates the event source.

IP Address

Indicates the IP address of the ECS for which the event is generated.

Occurred At

Indicates the last time when the event was generated.

Additional Information

Indicates the additional information about the event.

Impact on the System

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

Possible Causes

  • The server process or the database process encounters an exception.
  • The schedule process or the database process encounters an exception.
  • A network fault occurs.
  • An LB (HAProxy at the region layer) exception occurs.

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. The Event Logs page is displayed.
  3. In the event list, locate and click the target event name in the Name column. The Event Details and Proposed Processing dialog box is displayed.
  4. In the displayed Event Details and Proposed Processing dialog box, query the following event information:

    • Event ID
    • Event Source
    • IP address: IP address of the server for which the alarm is generated
    • Location information: groupId and subTaskId
    • Additional information: error code and description of the event

  5. Use PuTTY to log in to the AS-SVR-SVR01 or AS-SVR-SVR02 node using the IP address obtained in 4.

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

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

    TMOUT=0

Checking the server process

  1. Run the following command to check whether the server process is running properly:

    ps -ef|grep autoscaling

    If the following information is displayed, the process is normal:

    [admin@I-AS-API01 ~]$ ps -ef|grep autoscaling
    admin     9448  5279  0 15:14 pts/0    00:00:00 grep --color=auto autoscaling
    admin    13069     1  6 Feb24 ?        01:29:23 /opt/autoscaling/jre1.8/bin/java -Dnop
    ...
    • If yes, go to 14.
    • If no, go to 8.

  2. Run the following command to view the AS-SVR-SVR01 or AS-SVR-SVR02 node logs and search for keyword Exception:

    vi /var/log/autoscaling/autoscaling.log

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

Checking the database process

  1. Use PuTTY to log in to the active AS-SVRDB node.

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

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

  3. 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:

    [root@AS-DB01 admin]# service had query
    NODE                   ROLE           PHASE           RESS            VER             START          
    AS-DB01(AS-DB01)       active         Actived         normal          V100R001C01     2019-02-22 00:37:50
    AS-DB02(AS-DB02)       standby        Deactived       normal          V100R001C01     2019-02-22 00:38:56
    
    --------------------------------------------------------------------------------------------------------
                           ID    RES                      STAT            RET             TYPE           
    AS-DB01(AS-DB01):      1     exfloatip                Normal          Normal          Single_active  
                           2     gaussDB                  Normal          Active_normal   Active_standby 
    
    AS-DB02(AS-DB02):      1     exfloatip                Normal          Abnormal        Single_active  
                           2     gaussDB                  Normal          Standby_normal  Active_standby 
    • If yes, go to 12.
    • If no, contact technical support for assistance.

  1. After rectifying the fault, run the following command on the AS-SVR-SVR01 or AS-SVR-SVR02 node to restart the server process:

    sh /opt/autoscaling/autoscaling-api/autoscaling.sh restart

    If the following information is displayed, the process is started properly:

    [admin@I-AS-API01 ~]$ sh /opt/autoscaling/autoscaling-api/autoscaling.sh restart
    stop autoscaling-api succeed.
    start autoscaling succeed.

  2. Check whether the event is cleared.

    • If yes, no further action is required.
    • If no, go to 14.

Checking the schedule process

  1. Use PuTTY to log in to the AS-SCHEDULE-SCHEDULE01 or AS-SCHEDULE-SCHEDULE02 node using the IP address obtained in 4.

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

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

    TMOUT=0

  3. Run the following command to check whether the schedule process is running properly:

    ps -ef|grep schedule

    If the following information is displayed, the process is normal:

    [admin@I-AS-Schedule01 ~]$ ps -ef|grep schedule
    admin      626 32002  0 15:18 pts/1    00:00:00 grep --color=auto schedule
    admin    21723     1  1 Feb24 ?        00:18:15 /opt/autoscaling/jre1.8/bin/java
    ...
    • If yes, go to 23.
    • If no, go to 17.

  4. Run the following command to view the AS-SCHEDULE-SCHEDULE01 or AS-SCHEDULE-SCHEDULE02 node logs and search 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 18.

Checking the database process

  1. Use PuTTY to log in to the active AS-SCHEDULEDB node.

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

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

  3. 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 21.
    • If no, contact technical support for assistance.

  4. After rectifying the fault, run the following command on the AS-SCHEDULE-SCHEDULE01 or AS-SCHEDULE-SCHEDULE02 node to restart the schedule process:

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

    If the following information is displayed, the process is started properly:

    [admin@I-AS-Schedule01 ~]$ sh /opt/autoscaling/autoscaling-schedule/bin/schedule.sh restart
    stop schedule succeed.
    start schedule succeed.

  5. Check whether the event is cleared.

    • If yes, no further action is required.
    • If no, go to 23.

Checking the network

  1. Log in to the AS-SVR-SVR01 or AS-SVR-SVR02 node as the admin user and run the ping command to check whether the IP address of the AS-Schedule node configured on the HAProxy node can be pinged.

    • If yes, go to 24.
    • If no, contact technical support for assistance.

Checking the HAProxy process

  1. Use PuTTY to log in to the HAPROXY01 or HAPROXY02 node using the management IP address.

    Default username: ulb; default password cnp200@HW

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

    TMOUT=0

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

    sudo su - root

    The default username is root. The default password is Cloud12#$.

  4. Run the following command to check whether HAProxy is running properly:

    /etc/init.d/haproxy status

    If the following information is displayed, HAProxy is running properly:

    [root@HAPROXY01 ulb]# /etc/init.d/haproxy status
    Checking for service haproxy                                  running
    • If yes, go to 28.
    • If no, contact technical support for assistance.

  5. If the alarm persists after the preceding operations are performed, contact technical support for assistance.

Related Information

None

Translation
Download
Updated: 2019-08-30

Document ID: EDOC1100062365

Views: 35473

Downloads: 31

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