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

FusionInsight HD 6.5.0 Software Installation 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).
Installing the Client

Installing the Client

The Client Fails to Be Installed on a Node Outside the Cluster Because the NTP Is Not Configured on the Node

Symptom

The client fails to be deployed on a node outside the FusionInsight HD cluster.

Possible Causes
  • The NTP service is not started on the node outside the FusionInsight HD cluster.
  • The NTP service is started on the node outside the FusionInsight HD cluster, but the time difference between the node and the clock source cannot be obtained.
  • The NTP service is started on the node outside the FusionInsight HD cluster, but the time difference between the node and the clock source is greater than five minutes.
Fault Locating
  1. Check whether the NTP service is started properly.
  2. Check whether the time difference between the node and the external NTP clock source is greater than five minutes.
Procedure

Check the NTP startup status

  1. Use PuTTY to log in to the node where the client fails to be installed as the root user.
  2. Run the following command to check whether the NTP service is started:

    ps -ef | grep -w "ntpd" | grep -v grep
    Check whether the NTPd process exists.

Check the NTP synchronization

  1. Log in to the node for which the alarm is generated as the root user.
  2. Run the ntpq -np command and check whether the time synchronization is normal.

    If an asterisk (*) exists before the IP address of the NTP service on the current node, as shown in the following command output, the synchronization is normal.

    remote refid st t when poll reach delay offset jitter 
    ============================================================================== 
    *10.10.10.162 .LOCL. 1 u 1 16 377 0.270 -1.562 0.014

    If there is no asterisk (*) before the IP address of the NTP service on the active OMS node, as shown in the following command output, and the value of refid is .INIT., the synchronization is abnormal.

    remote refid st t when poll reach delay offset jitter 
    ============================================================================== 
    10.10.10.162 .INIT. 1 u 1 16 377 0.270 -1.562 0.014
    • If the synchronization is normal, go to Step Step 5.
    • If the synchronization is abnormal, go to Step Step 7.

Check the time difference of NTP service

  1. Check whether the time difference (the offset value obtained in Step Step 4) between the current node and the NTP server is greater than five minutes. (The unit is milliseconds.)

    • If yes, go to Step Step 6.
    • If no, reinstall the client. If the installation still fails, contact technical support and provide the collected fault logs.

  2. Run the following command on the NTP client to forcibly synchronize the time with the clock source. After the synchronization, perform Step Step 4 and check whether the time is consistent.

    sntp (ntpdate in the Red Hat system)
    • If the time is consistent, reinstall the client. If the installation still fails, contact technical support and provide the collected fault logs.
    • If the time is inconsistent, contact technical support and provide the collected fault logs.
      NOTE:

      For details about how to synchronize time, see Step 5 in section "Replacing the NTP Server for the Cluster".

  3. Back up the /etc/ntp.conf and etc/ntp.keys (/etc/ntp/ntpkeys in the Red Hat system) files on the current node and modify the /etc/ntp.conf file by referring to the following information.

    server 10.10.10.162 key 1 prefer burst iburst minpoll 4 maxpoll 4
    restrict -4 default kod notrap nomodify nopeer noquery
    restrict -6 default kod notrap nomodify nopeer noquery
    restrict 127.0.0.1
    restrict ::1
    tinker step 0
    tinker panic 0
    disable monitor
    disable kernel
    enable auth
    keys /etc/ntp.keys     # /etc/ntp/ntpkeys in the Red Hatsystem
    trustedkey 1
    requestkey 1
    controlkey 1

    In the preceding information, 10.10.10.162 is the IP address of the NTP clock source. Ensure that the client and FusionInsight cluster use the same clock source. The value of key is the ID of the key configured on the NTP clock source server. Ensure that the key value in the /etc/ntp.keys file (/etc/ntp/ntpkeys in the Red Hat system) is the same as that of NTP clock source.

  4. Run the following command to restart the NTP service:

    service ntp restart (service ntpd restart in the Red Hat system)

  5. Perform Step Step 2 and check whether the NTP service on the current node is normal.

    • If yes, reinstall the client. If the installation still fails, contact technical support and provide the collected fault logs.
    • If no, contact technical support and provide the collected fault logs.

Download
Updated: 2019-05-17

Document ID: EDOC1100074555

Views: 5409

Downloads: 6

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