SSH Command Execution Times Out

Applicable Versions

V100R002C30SPC60*,

V100R002C50SPC20*,

V100R002C60SPC20*,

V100R002C60U10,V100R002C60U10SPC00*,

V100R002C60U20,V100R002C60U20SPC00*

V100R002C70SPC20*

V100R002C80SPC20*

Symptom

The IP address of Linux system of a node needs to be modified first during IP address modification. If the IP address of the Linux system needs to be modified for modifying the management IP address of the LdapServer node, operations on all nodes in the cluster may become slow after network service restart.

Fault Locating

1. When the IP addresses of the cluster are not modified after IP address modification of the Linux system, LdapClient retains the old management IP address of LdapServer. Manually modify configurations of all nodes after restarting network services and before modifying the IP address configuration file. The configuration file automatically takes effect after configurations of all nodes are modified.

Solution

1. Log in to a node in the cluster as user omm by using PuTTY, and run the following command:

   vi ${BIGDATA_HOME}/FusionInsight/etc/*_*_SlapdClient/ENV_VARS

2. Set LDAP_SERVER_LIST to the new management IP addresses of the LdapServer nodes. For example, if the two new management IP addresses are 10.X.X.1 and 1.X.X.2, set the parameter as follows. Use a comma (,) to separate the IP addresses. Then save and exit the configuration file.

   LDAP_SERVER_LIST=10.X.X.1,1.X.X.2

3. Log in to all the rest nodes in the cluster as user omm, and repeat the preceding operations.