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


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


FusionCloud Troubleshooting Guide 02

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).
The Disk Is Read-Only, Causing an Exception in the monit Daemon Process and a Node Status Query Failure.

The Disk Is Read-Only, Causing an Exception in the monit Daemon Process and a Node Status Query Failure.


The status of a data zone node running EulerOS fails to be queried.

Possible Causes

The disk is read-only, causing an exception in the monit daemon process and a node status query failure.

Troubleshooting Method

  1. Use PuTTY to log in to the data zone node running EulerOS as the paas user.
  2. Run the following command to query the node status:

    monit summary

    If the following information is displayed, the monit process status is abnormal.
    monit daemon not running

  3. Switch to user root and run the following command to query the read-only partition:

    touch /home/testfile

    Because the partition is read-only, the monit process is not started and the node status cannot be queried.

  4. Run the following command and check which processes are running in the partition described in 3:

    lsof | grep Partition directory

    Record the names of these processes.

  5. Run the following command to kill the processes recorded in 4:

    kill -9 process name

    After all of the processes are killed, run the lsof command to check whether any processes are still running. If yes, run the command in 5 until no process information is displayed.

  6. Unmount the directories where the abnormal disk is mounted.

    If the execution fails, wait at least 180s and perform 4 again until the unmounting is successful.


    The processes entering the "D" state cannot be killed. Therefore, the abnormal disk takes a long time to be unmounted.

  7. Run the following command to scan the abnormal disk and ensure that no data in the disk is lost:

    fsck.ext4 Abnormal disk


    This command can be used in various scenarios. If the command fails to be executed, see

  8. Remount the abnormal disk to a specified directory, and restore the service process.

    mount Abnormal disk Specified directory

    Run the command in 2 to check whether the system is running properly.

    If the system is abnormal, contact technical support for assistance..

Updated: 2019-06-10

Document ID: EDOC1100063248

Views: 22889

Downloads: 37

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