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 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).
Management Node Faults

Management Node Faults

VM Fault on the AGW-Kfk-Asgard-Shubao Node

  1. Log in to the ManageOne OM plane and check the IP address of the node where the process is abnormal.
  2. Check whether you can log in to the node where the process is abnormal.

    • If you can log in to the node, go to 3.
    • If you cannot log in to the node, contact technical support for assistance.

  3. Perform the following operations based on the abnormal process identified in 1:

    • If the Kafka process is abnormal, perform the following operations:
      1. Use PuTTY to log in to the IP address of the node where the Kafka process is abnormal by using the IP address identified in 1.

        Default account: apigateway; default password: Api@shubao88

      2. Run the following command to check the ZooKeeper service status:

        /opt/apigateway/zookeeper/bin/zkServer.sh status

        [apigateway@I-APIGW-KFK01 bin]$ sh zkServer.sh status
        JMX disabled by user request
        Using config: /opt/apigateway/zookeeper/bin/../conf/zoo.cfg
        Mode: follower

        In the command output, Mode indicates the role of the ZooKeeper node.

        • If the role is leader or follower, ZooKeeper is running properly. Go to 3.e.
        • If the role is not leader or follower, ZooKeeper is abnormal. Go to 3.c.
      3. Run the following command to stop the ZooKeeper process:

        /opt/ces/zookeeper/bin/stop_zookeeper.sh

      4. Wait for 10 minutes and repeat 3.b to check the ZooKeeper status.
        • If ZooKeeper is normal, go to 3.e.
        • If ZooKeeper is abnormal, contact technical support.
      5. Repeat 3.a through 3.b to check and record the ZooKeeper status of all nodes in the Kafka cluster.
        • For the ZooKeeper statuses of all nodes in the Kafka cluster, if only one node is leader and the other nodes are follower, the ZooKeeper statuses of all nodes in the cluster are normal. Go to 3.f.
        • Otherwise, run the following command to restart the ZooKeeper processes of all nodes in the cluster as the apigateway user and go to 3.f.

          sh /opt/apigateway/zookeeper/bin/monitor_zookeeper.sh restart

      6. Run the following command to stop the Kafka process:

        /opt/apigateway/kafka/bin/stop_kafka.sh

      7. After 10 minutes, the daemon process will automatically start the Kafka process. If Kafka is not started, run the following command to manually start it:

        /opt/apigateway/kafka/bin/start_kafka.sh

      8. Run the following command as the apigateway user to check whether the Kafka process on the faulty node is normal:

        sh /opt/apigateway/kafka/bin/monitor_kafka.sh status

        If the following information is displayed, the process is normal and Kafka is restored. If the process is still abnormal, contact technical support for assistance.

        [apigateway@I-APIGW-KFK01 bin]$ sh /opt/apigateway/kafka/bin/monitor_kafka.sh status
        apigate+ 12419 12390  0 16:04 pts/1    00:00:00 grep Kafka
        apigate+ 15825 15818  2 Apr09 ?        01:30:51 /opt/apigateway/jre180131/bin/java -Xmx1G -Xms1G -server -XX:+UseParNewGC -XX:+UseConcMarkSweepGC -XX:+CMSClassUnloadingEnabled -XX:+CMSScavengeBeforeRemark -XX:+DisableExplicitGC -Djava.awt.headless=true -Xloggc:/opt/apigateway/kafka/bin/../logs/kafkaServer-gc.log -verbose:gc -XX:+PrintGCDetails -XX:+PrintGCDateStamps -XX:+PrintGCTimeStamps -Dkafka.logs.dir=/opt/apigateway/kafka/bin/../logs -Dlog4j.configuration=file:./../config/log4j.properties -cp :/opt/apigateway/kafka/bin/../core/build/dependant-libs-2.10.4*/*.jar:/opt/apigateway/kafka/bin/../examples/build/libs//kafka-examples*.jar:/opt/apigateway/kafka/bin/../contrib/hadoop-consumer/build/libs//kafka-hadoop-consumer*.jar:/opt/apigateway/kafka/bin/../contrib/hadoop-producer/build/libs//kafka-hadoop-producer*.jar:/opt/apigateway/kafka/bin/../clients/build/libs/kafka-clients*.jar:/opt/apigateway/kafka/bin/../libs/jopt-simple-3.2.jar:/opt/apigateway/kafka/bin/../libs/kafka_2.10-0.8.2.1.jar:/opt/apigateway/kafka/bin/../libs/kafka_2.10-0.8.2.1-javadoc.jar:/opt/apigateway/kafka/bin/../libs/kafka_2.10-0.8.2.1-scaladoc.jar:/opt/apigateway/kafka/bin/../libs/kafka_2.10-0.8.2.1-sources.jar:/opt/apigateway/kafka/bin/../libs/kafka_2.10-0.8.2.1-test.jar:/opt/apigateway/kafka/bin/../libs/kafka-clients-0.8.2.1.jar:/opt/apigateway/kafka/bin/../libs/log4j-1.2.16.jar:/opt/apigateway/kafka/bin/../libs/lz4-1.2.0.jar:/opt/apigateway/kafka/bin/../libs/metrics-core-2.2.0.jar:/opt/apigateway/kafka/bin/../libs/scala-library-2.10.4.jar:/opt/apigateway/kafka/bin/../libs/slf4j-api-1.7.6.jar:/opt/apigateway/kafka/bin/../libs/slf4j-log4j12-1.6.1.jar:/opt/apigateway/kafka/bin/../libs/snappy-java-1.1.1.6.jar:/opt/apigateway/kafka/bin/../libs/zkclient-0.3.jar:/opt/apigateway/kafka/bin/../libs/zookeeper-3.4.6.jar:/opt/apigateway/kafka/bin/../core/build/libs/kafka_2.10*.jar kafka.Kafka ../config/server.properties
    • If the Asgard process is abnormal, perform the following operations:
      1. Use PuTTY to log in to the IP address of the node where the Asgard process is abnormal by using the IP address identified in 1.

        Default account: apigateway; default password: Api@shubao88

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

        ps -ef | grep asgard

        [apigateway@I-APIGW-ASGARD01 ~]$ ps -ef |grep asgard
        apigate+   813   696  0 11:33 pts/0    00:00:00 grep --color=auto asgard
        apigate+ 29928     1  1 Apr11 ?        00:16:15 java -Xms64m -Xmx1024m -XX:PermSize=128m -XX:MaxPermSize=256m -Dname=asgard.main.proc -classpath .:/opt/apigateway/asgard/lib/apache-log4j-extras-1.2.17.jar:/opt/apigateway/asgard/lib/api-metedata-plugin-3.0.10-20180331094303.build106.jar:/opt/apigateway/asgard/lib/asgard-3.0.10-20180331094303.build106.jar:/opt/apigateway/asgard/lib/cache-2.1.10.jar:/opt/apigateway/asgard/lib/commons-codec-1.9.jar:/opt/apigateway/asgard/lib/commons-collections-3.2.2.jar:/opt/apigateway/asgard/lib/commons-configuration-1.10.jar:/opt/apigateway/asgard/lib/commons-lang-2.6.jar:/opt/apigateway/asgard/lib/commons-lang3-3.3.2.jar:/opt/apigateway/asgard/lib/commons-logging-1.1.1.jar:/opt/apigateway/asgard/lib/commons-pool2-2.4.1.jar:/opt/apigateway/asgard/lib/console-framework-common-4.2.3-gamma.jar:/opt/apigateway/asgard/lib/console-framework-passthrough-4.2.3-gamma.jar:/opt/apigateway/asgard/lib/dom4j-1.6.1.jar:/opt/apigateway/asgard/lib/ehcache-core-2.5.1.jar:/opt/apigateway/asgard/lib/encoder-1.2.jar:/opt/apigateway/asgard/lib/gson-2.3.1.jar:/opt/apigateway/asgard/lib/guava-19.0.jar:/opt/apigateway/asgard/lib/jackson-annotations-2.7.0.jar:/opt/apigateway/asgard/lib/jackson-core-2.7.4.jar:/opt/apigateway/asgard/lib/jackson-core-asl-1.9.13.jar:/opt/apigateway/asgard/lib/jackson-databind-2.7.4.jar:/opt/apigateway/asgard/lib/jackson-dataformat-csv-2.2.3.jar:/opt/apigateway/asgard/lib/jackson-dataformat-smile-2.2.3.jar:/opt/apigateway/asgard/lib/jackson-dataformat-xml-2.7.4.jar:/opt/apigateway/asgard/lib/jackson-dataformat-yaml-2.2.3.jar:/opt/apigateway/asgard/lib/jackson-mapper-asl-1.9.13.jar:/opt/apigateway/asgard/lib/jackson-module-jaxb-annotations-2.7.4.jar:/opt/apigateway/asgard/lib/javax.servlet-api-3.0.1.jar:/opt/apigateway/asgard/lib/jline-0.9.94.jar:/opt/apigateway/asgard/lib/jopt-simple-3.2.jar:/opt/apigateway/asgard/lib/json-20140107.jar:/opt/apigateway/asgard/lib/junit-3.8.1.jar:/opt/apigateway/asgard/lib/jzlib-1.1.3.jar:/opt/apigateway/asgard/lib/kafka_2.10-0.8.2.1.jar:/opt/apigateway/asgard/lib/kafka-client-3.0.10-20180331094303.build106.jar:/opt/apigateway/asgard/lib/kafka-clients-0.8.2.1.jar:/opt/apigateway/asgard/lib/log4j-1.2.17.jar:/opt/apigateway/asgard/lib/lz4-1.2.0.jar:/opt/apigateway/asgard/lib/metrics-core-2.2.0.jar:/opt/apigateway/asgard/lib/netty-3.7.0.Final.jar:/opt/apigateway/asgard/lib/netty-all-4.0.28.Final.jar:/opt/apigateway/asgard/lib/oc-alarm-3.0.10-20180331094303.build106.jar:/opt/apigateway/asgard/lib/org.restlet-2.2.0.jar:/opt/apigateway/asgard/lib/org.restlet.ext.jackson-2.2.0.jar:/opt/apigateway/asgard/lib/org.restlet.ext.slf4j-2.2.0.jar:/opt/apigateway/asgard/lib/scala-library-2.10.4.jar:/opt/apigateway/asgard/lib/slf4j-api-1.7.6.jar:/opt/apigateway/asgard/lib/slf4j-log4j12-1.6.1.jar:/opt/apigateway/asgard/lib/snakeyaml-1.13.jar:/opt/apigateway/asgard/lib/snappy-java-1.1.1.6.jar:/opt/apigateway/asgard/lib/spymemcached-2.1.10.jar:/opt/apigateway/asgard/lib/stax2-api-3.1.4.jar:/opt/apigateway/asgard/lib/stax-api-1.0-2.jar:/opt/apigateway/asgard/lib/validation-api-1.1.0.Final.jar:/opt/apigateway/asgard/lib/wcc_appsrv-1.2.4.jar:/opt/apigateway/asgard/lib/wcc_common-1.2.9.jar:/opt/apigateway/asgard/lib/wcc_crypt-1.2.9.jar:/opt/apigateway/asgard/lib/wcc_log-1.2.15.jar:/opt/apigateway/asgard/lib/wcc_util-1.2.11.jar:/opt/apigateway/asgard/lib/woodstox-core-asl-4.2.0.jar:/opt/apigateway/asgard/lib/xml-apis-1.3.04.jar:/opt/apigateway/asgard/lib/xmlpull-1.1.3.1.jar:/opt/apigateway/asgard/lib/xpp3_min-1.1.4c.jar:/opt/apigateway/asgard/lib/xstream-1.4.9.jar:/opt/apigateway/asgard/lib/zkclient-0.3.jar:/opt/apigateway/asgard/lib/zookeeper-3.4.6.jar com.huawei.apigateway.asgard.server.AsgardMain
        • If the preceding information is displayed, the process exists. Run the following command to restart the Asgard process:

          sh /opt/apigateway/asgard/bin/asgard_monitor.sh restart

        • Otherwise, run the following command to start the Asgard process:

          sh /opt/apigateway/asgard/bin/asgard_monitor.sh start

      3. Run the following command to check the Asgard process status:

        sh /opt/apigateway/asgard/bin/asgard_monitor.sh status

        If the following information is displayed, the Asgard process is normal and no further action is required. Otherwise, contact technical support for assistance.

        [apigateway@I-APIGW-ASGARD01 bin]$ sh asgard_monitor.sh status
        [asgard_monitor.sh] normal
    • If the Shubao process is abnormal, perform the following operations:
      1. Use PuTTY to log in to the IP address of the node where the Shubao process is abnormal by using the IP address identified in 1.

        Default account: apigateway; default password: Api@shubao88

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

        ps -ef | grep shubao

        [apigateway@I-APIGW-SB01 ~]$ ps -ef |grep shubao
        apigate+   570 31423  0 09:11 pts/0    00:00:00 grep --color=auto shubao
        apigate+ 24546     1  1 Apr11 ?        00:07:30 ./shubao
        • If the Shubao process exists, run the following command to restart it:

          sh /opt/apigateway/shubao/bin/shubao_monitor.sh restart

        • If the Shubao process does not exist, run the following command to start it:

          sh /opt/apigateway/shubao/bin/shubao_monitor.sh start

      3. Run the following command to check whether the Shubao process is started:

        sh opt/apigateway/shubao/bin/shubao_monitor.sh status

        If normal is returned, the Shubao process is normal and no further action is required. If an exception is returned, contact technical support for assistance.

    • If the ZooKeeper process is abnormal, perform the following operations:
      1. Use PuTTY to log in to the IP address of the node where the ZooKeeper process is abnormal by using the IP address identified in 1.

        Default account: apigateway; default password: Api@shubao88

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

        ps -ef | grep zookeeper

        If the following information is displayed, the process exists. Go to 3.d. Otherwise, go to 3.c.

        apigate+ 15010     1  0 15:05 ?        00:00:12 /opt/apigateway/jre180131/bin/java -Dzookeeper.log.dir=/var/log/apigateway/zookeeper -Dzookeeper.root.logger=INFO,ROLLINGFILE -cp /opt/apigateway/zookeeper/bin/../build/classes:/opt/apigateway/zookeeper/bin/../build/lib/*.jar:/opt/apigateway/zookeeper/bin/../lib/slf4j-log4j12-1.6.1.jar:/opt/apigateway/zookeeper/bin/../lib/slf4j-api-1.6.1.jar:/opt/apigateway/zookeeper/bin/../lib/netty-3.7.0.Final.jar:/opt/apigateway/zookeeper/bin/../lib/log4j-1.2.16.jar:/opt/apigateway/zookeeper/bin/../lib/jline-0.9.94.jar:/opt/apigateway/zookeeper/bin/../zookeeper-3.4.6.jar:/opt/apigateway/zookeeper/bin/../src/java/lib/*.jar:/opt/apigateway/zookeeper/bin/../conf: org.apache.zookeeper.server.quorum.QuorumPeerMain /opt/apigateway/zookeeper/bin/../conf/zoo.cfg
      3. Run the following command to start the ZooKeeper process:

        /opt/apigateway/zookeeper/bin/start_zookeeper.sh

      4. Run the following command to check the ZooKeeper status of the node:

        /opt/apigateway/zookeeper/bin/zkServer.sh status

        JMX disabled by user request
        Using config: /opt/apigateway/zookeeper/bin/../conf/zoo.cfg
        Mode: follower

        In the command output, Mode indicates the role of the ZooKeeper node.

        • If the ZooKeeper role is leader or follower, the ZooKeeper process is normal and no further action is required.
        • If the ZooKeeper role is not leader or follower, ZooKeeper is abnormal. Go to 3.e.
      5. Run the following command to stop the ZooKeeper process:

        /opt/apigateway/zookeeper/bin/stop_zookeeper.sh

        After the ZooKeeper process stops, the daemon process automatically starts the ZooKeeper process.

      6. Wait for 10 minutes and repeat 3.d to check the ZooKeeper status.
        • If ZooKeeper is normal, no further action is required.
        • If ZooKeeper is abnormal, contact technical support for assistance.

VM Fault on the AGW-Silvan-MEM Node

  1. Log in to the ManageOne OM plane and check the IP address of the node where the process is abnormal.
  2. Check whether you can log in to the node where the process is abnormal.

    • If you can log in to the node, go to 3.
    • If you cannot log in to the node, contact technical support for assistance.

  3. Perform the following operations based on the abnormal process identified in 1:

    • If the Memcached process is abnormal, perform the following operations:
      1. Use PuTTY to log in to the IP address of the node where the Memcached process is abnormal by using the IP address identified in 1.

        Default account: onframework; default password: Api@shubao88

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

        ps -ef | grep memcache

        [onframework@I-APIGW-MEM01 ~]$ ps -ef |grep memcached
        onframe+ 10187  8878  0 09:45 pts/0    00:00:00 grep --color=auto memcached
        onframe+ 29556     1  0 Apr09 ?        00:00:14 ./memcached -d -u memcached -B ascii -l 192.168.112.23 -p 11211 -m 1024 -U 0 -c 1024 -v
        • If the preceding information is displayed, the process exists. Run the following command to restart the Memcached process:

          sh /opt/onframework/memcached/bin/memcached_monitor.sh restart

        • Otherwise, run the following command to start the Memcached process:

          sh /opt/onframework/memcached/bin/memcached_monitor.sh start

      3. Run the following command to check the Memcached process status:

        sh /opt/onframework/memcached/bin/memcached_monitor.sh status

        If the following information is displayed, the Memcached process is normal and no further action is required. Otherwise, contact technical support for assistance.

        [onframework@I-APIGW-MEM01 bin]$ sh /opt/onframework/memcached/bin/memcached_monitor.sh status
        status check: normal
        [onframework@I-APIGW-MEM01 bin]$ ps -ef |grep memcache
        onframe+ 18282 13244  0 10:50 pts/0    00:00:00 grep --color=auto memcache
        onframe+ 29556     1  0 Apr09 ?        00:00:14 ./memcached -d -u memcached -B ascii -l 192.168.112.23 -p 11211 -m 1024 -U 0 -c 1024 -v
    • If the Silvan process is abnormal, perform the following operations:
      1. Use PuTTY to log in to the IP address of the node where the Silvan process is abnormal by using the IP address identified in 1.

        Default account: onframework; default password: Api@shubao88

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

        ps -ef | grep silvan

        [onframework@I-APIGW-DB01 ~]$ ps -ef |grep silvan
        onframe+ 13510     1  1 Apr11 ?        00:17:31 java -Xms64m -Xmx1024m -XX:PermSize=128m -XX:MaxPermSize=256m -Dname=silvan.main.proc -classpath .:lib/antlr-2.7.7.jar:lib/apache-log4j-extras-1.2.17.jar:lib/bcpkix-jdk15on-1.53.jar:lib/bcprov-jdk15on-1.53.jar:lib/cache-2.1.9.jar:lib/commons-beanutils-1.8.0.jar:lib/commons-codec-1.9.jar:lib/commons-configuration-1.10.jar:lib/commons-lang-2.6.jar:lib/commons-lang3-3.2.jar:lib/commons-logging-1.1.1.jar:lib/commons-pool2-2.4.1.jar:lib/console-framework-common-4.2.3-gamma.jar:lib/dom4j-1.6.1.jar:lib/ehcache-core-2.5.1.jar:lib/encoder-1.2.jar:lib/gsjdbc4-V100R003C10SPC115.jar:lib/hibernate-commons-annotations-4.0.2.Final.jar:lib/hibernate-core-4.2.5.Final.jar:lib/hibernate-jpa-2.0-api-1.0.1.Final.jar:lib/hibernate-proxool-4.2.5.Final.jar:lib/hibernate-validator-4.3.1.Final.jar:lib/jackson-annotations-2.7.0.jar:lib/jackson-core-2.7.4.jar:lib/jackson-core-asl-1.9.13.jar:lib/jackson-databind-2.7.4.jar:lib/jackson-dataformat-csv-2.2.3.jar:lib/jackson-dataformat-smile-2.2.3.jar:lib/jackson-dataformat-xml-2.7.4.jar:lib/jackson-dataformat-yaml-2.2.3.jar:lib/jackson-mapper-asl-1.9.13.jar:lib/jackson-module-jaxb-annotations-2.7.4.jar:lib/javassist-3.15.0-GA.jar:lib/javax.servlet-api-3.1.0.jar:lib/jaxen-1.1.6.jar:lib/jboss-logging-3.1.0.GA.jar:lib/jboss-transaction-api_1.1_spec-1.0.1.Final.jar:lib/json-20140107.jar:lib/log4j-1.2.17.jar:lib/netty-all-4.0.28.Final.jar:lib/oc-alarm-3.0.10-20180331094303.build106.jar:lib/org.restlet-2.2.0.jar:lib/org.restlet.ext.jackson-2.2.0.jar:lib/org.restlet.ext.slf4j-2.2.0.jar:lib/proxool-0.8.3.jar:lib/silvan-3.0.10-20180331094303.build106.jar:lib/slf4j-api-1.7.5.jar:lib/snakeyaml-1.13.jar:lib/spymemcached-2.1.9.jar:lib/stax2-api-3.1.4.jar:lib/stax-api-1.0-2.jar:lib/validation-api-1.1.0.Final.jar:lib/wcc_appsrv-1.2.4.jar:lib/wcc_common-1.2.8.jar:lib/wcc_crypt-1.2.9.jar:lib/wcc_log-1.2.12.jar:lib/wcc_util-1.2.11.jar:lib/woodstox-core-asl-4.2.0.jar:lib/xml-apis-1.3.04.jar:lib/xmlpull-1.1.3.1.jar:lib/xpp3_min-1.1.4c.jar:lib/xstream-1.4.5.jar com.huawei.console.silvan.server.SilvanMain
        onframe+ 16715 14604  0 11:42 pts/0    00:00:00 grep --color=auto silvan
        • If the preceding information is displayed, the process exists. Run the following command to restart the Silvan process:

          sh /opt/onframework/silvan/bin/silvan_monitor.sh restart

        • Otherwise, run the following command to start the Silvan process:

          sh /opt/onframework/silvan/bin/silvan_monitor.sh start

      3. Run the following command to check the Silvan process status:

        sh /opt/onframework/silvan/bin/silvan_monitor.sh status

        If the following information is displayed, the Silvan process is normal and no further action is required. Otherwise, contact technical support for assistance.

        [onframework@I-APIGW-DB01 bin]$ sh /opt/onframework/silvan/bin/silvan_monitor.sh status
        status check: normal

VM Fault on the AGW-LB and AGW-PODLB Nodes

  1. Log in to the ManageOne OM plane and check the IP address of the node where the process is abnormal.
  2. Check whether you can log in to the node where the process is abnormal.

    • If you can log in to the node, go to 3.
    • If you cannot log in to the node, contact technical support for assistance.

  3. Use PuTTY to log in to the IP address of the node where the Nginx process is abnormal by using the IP address identified in 1.

    Default account: onframework; default password: Api@shubao88

  4. Run the following command to check whether the Nginx process exists:

    ps -ef | grep nginx

    [onframework@I-APIGW-NGXS01 ~]$ ps -ef |grep nginx
    onframe+  3503  3090  0 11:46 pts/0    00:00:00 grep --color=auto nginx
    root      6239     1  0 Apr09 ?        00:00:00 nginx: master process /opt/onframework/nginx/sbin/nginx
    root      6240  6239  0 Apr09 ?        00:00:39 nginx: worker process
    root      6242  6239  0 Apr09 ?        00:00:40 nginx: worker process
    root      6243  6239  0 Apr09 ?        00:00:38 nginx: worker process
    root      6244  6239  0 Apr09 ?        00:00:41 nginx: worker process
    • If the preceding information is displayed, the process exists. Run the following command to restart the Nginx process:

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

    • Otherwise, run the following command to start the Nginx process:

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

  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 check the Nginx process status:

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

    If the following information is displayed, the Nginx process is normal and no further action is required. Otherwise, contact technical support for assistance.

    [onframework@I-APIGW-NGXS01 bin]$ sh /opt/onframework/nginx/bin/nginx_monitor.sh status
    normal

Translation
Download
Updated: 2019-06-10

Document ID: EDOC1100063248

Views: 23094

Downloads: 37

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