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 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).
Deploy Faults

Deploy Faults

Symptom

The HDCS Deploy process breaks down or the process fails to be started.

Possible Causes

  • The user for starting the Deploy service is not datasight.
  • The GaussDB password ciphertext in the configuration file is incorrect. As a result, the process fails to decrypt the GaussDB password, causing the Deploy process start failure.

Troubleshooting Process

  1. Check whether the user for starting the process on the Deploy node is datasight.
  2. Check the /var/log/bigdata/service-deployer/service-deployer-[username]-service-deployer-[machinename].log file of the Deploy node to locate the fault.

Procedure

  1. If the user for starting the process is not datasight, perform the following operations to rectify the fault:

    • Use PuTTY to log in to the Deploy node as the datasight user using the IP address of the Deploy node.

      Default username: datasight; default password: Cloud12#$

    • Run the ps -ef |grep java command to obtain the ID of the current Java process.
    • Run the kill -9 [java-process-id] command among which [java-process-id] indicates the Java process ID.
    • Run the monit stop service-deploy command to stop the service.
    • Run the monit start service-deploy service to start the service. The following command output is displayed:
    [datasight@MRSDeployer01 ~]$ ps -ef |grep java 
    datasig+ 21849     1 99 Dec03 pts/1    1-20:17:48 /opt/mrs/tools/jdk/bin/java -server -Xdebug -Xnoagent -Djava.compiler=NONE -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=8001 -Dservice.status.name=service-deployer -Dfile.encoding=UTF-8 -Djdk.tls.ephemeralDHKeySize=2048 -Djdk.tls.allowUnsafeServerCertChange=true -Dsun.security.ssl.allowUnsafeRenegotiation=true -Dappender=hb_routing -Ddeployer.log.dir=/var/log/bigdata/service-deployer -Ddeployer.log.file=service-deployer-datasight-service-deployer-MRSDeployer01.log -Dbeetle.application.home.path=/opt/mrs/deployer/bin/../conf/wcc_conf -Dssh.root.dir=/opt/mrs/deployer/bin/.. -cp /opt/mrs/deployer/bin/../conf:/opt/mrs/deployer/bin/../lib/* com.huawei.mrs.box.BoxKt
    datasig+ 24442     1  0 Nov26 ?        00:49:12 /opt/mrs/tools/jdk/bin/java -Dproc_zookeeper -Dzookeeper.log.file=zookeeper-datasight-server-MRSDeployer01.log -Dzookeeper.log.dir=/opt/mrs/zookeeper/bin/../logs -Dlog4j.configuration.watch=true -XX:+HeapDumpOnOutOfMemoryError -XX:OnOutOfMemoryError=kill -9 %p -Xmx1000m -Djdk.tls.ephemeralDHKeySize=2048 -cp /opt/mrs/zookeeper/bin/../build/classes:/opt/mrs/zookeeper/bin/../build/lib/*.jar:/opt/mrs/zookeeper/bin/../lib/slf4j-log4j12-1.7.5.jar:/opt/mrs/zookeeper/bin/../lib/slf4j-api-1.7.5.jar:/opt/mrs/zookeeper/bin/../lib/servlet-api-2.5-20081211.jar:/opt/mrs/zookeeper/bin/../lib/netty-3.10.6.Final.jar:/opt/mrs/zookeeper/bin/../lib/log4j-1.2.16.jar:/opt/mrs/zookeeper/bin/../lib/jline-2.11.jar:/opt/mrs/zookeeper/bin/../lib/jetty-util-6.1.26.jar:/opt/mrs/zookeeper/bin/../lib/jetty-6.1.26.jar:/opt/mrs/zookeeper/bin/../lib/jackson-mapper-asl-1.9.11.jar:/opt/mrs/zookeeper/bin/../lib/jackson-core-asl-1.9.11.jar:/opt/mrs/zookeeper/bin/../lib/dynalogger-V100R002C30.jar:/opt/mrs/zookeeper/bin/../lib/commons-cli-1.2.jar:/opt/mrs/zookeeper/bin/../lib/apache-log4j-extras-1.1.jar:/opt/mrs/zookeeper/bin/../zookeeper-3.5.1.jar:/opt/mrs/zookeeper/bin/../src/java/lib/*.jar:/opt/mrs/zookeeper/bin/../conf::/lib:/opt/mrs/tools/jdk/lib:/opt/mrs/deployer/conf:/opt/mrs/deployer/lib/mrs-box-1.0.0-jar-with-dependencies.jar -Dzookeeper.jmx.disable=true -Dbeetle.application.home.path=/opt/mrs/deployer/conf/wcc_conf com.huawei.mrs.common.security.QuorumPeerMainCryptAdapter /opt/mrs/zookeeper/bin/../conf/zoo.cfg
    

  2. If the GaussDB password ciphertext in the configuration file is incorrect, perform the following operations:

    • Contact the GaussDB administrator to obtain the plaintext password of the database.
    • Contact related personnel to encrypt the password.
    • Replace the original ciphertext of the configuration item datasource.password-encrypted in the /opt/mrs/deployer/conf /core.properties file of the Deploy node with the new one.
    • Replace the original ciphertext of the configuration item datasource.password-encrypted in the /opt/mrs/deployer/conf /deploy.properties file of the Deploy node with the new one.
    • Restart the Deploy service by referring to 1.

Translation
Download
Updated: 2019-06-01

Document ID: EDOC1100062375

Views: 2010

Downloads: 12

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