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

FusionCloud 6.3.1.1 Troubleshooting Guide 03

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).
Nginx Troubleshooting

Nginx Troubleshooting

Symptom

The alarm generated by the ManageOne OM plane indicates that the Nginx node is faulty and needs to be restored.

Possible Causes

  • The VM is faulty.
  • A nginx process exception occurs.

Fault Demarcation Methods

Figure 24-2 shows the troubleshooting flowchart for a management node fault.

Figure 24-2 Troubleshooting flowchart for a management node fault

Procedure

  1. Identify the IP address of the node where the process is abnormal based on the IP address in the alarm email on the ManageOne OM plane.
  2. Check whether the faulty node can be logged in to using PuTTY.

    The default username is onframework. The default password is cnp200@HW.

    • If yes, go to 3.
    • If no, the VM is faulty. Contact technical support for assistance.

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

    sudo su - root

    The default password is Cloud12#$.

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

    ps -ef|grep nginx

    • If yes, contact technical support for assistance.
    • If no, go to 5.
    NOTE:

    If the command output contains the nginx process, the process is running properly. If the nginx process does not exist, the process is abnormal.

  5. Run the following command to start Nginx:

    /opt/onframework/nginx/bin/nginx_monitor.sh start

    Information similar to the following is displayed:
    [root@NGINX01 bin]# /opt/onframework/nginx/bin/nginx_monitor.sh start
    start success

  6. Run the following command to check whether the nginx process is running properly:

    ps -ef|grep nginx

    • If yes, no further action is required.
    • If no, contact technical support for assistance.

Translation
Download
Updated: 2019-08-16

Document ID: EDOC1100063248

Views: 25209

Downloads: 40

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