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 FusionInsight Manager

Installing FusionInsight Manager

Failed to Log In to FusionInsight Manager After the Manager Two-node Cluster Is Installed

Symptom

After the Manager two-node cluster is installed, the login to FusionInsight Manager fails.

Possible Causes
  • Tomcat is not properly started.
  • The floating IP address is incorrectly set.
  • The subnet mask and gateway address are incorrectly set.
Troubleshooting Methods
  1. Check whether Tomcat is properly started.
  2. If Tomcat runs properly, check whether the floating IP address can be pinged. Check whether the floating IP address of WebService is configured in the ${BIGDATA_HOME}/om-server/tomcat/conf/server.xml configuration file of Tomcat.
  3. Check whether the subnet mask and gateway address information configured during the installation is consistent with those of the actual environment.
Procedure
  1. On the active management node, run the ps -ef | grep tomcat command as user root to check whether the tomcat process is available(8080 and 28443). If it is unavailable, check whether Tomcat fails to start and rectify the fault.

    ...
    root     26766 26121  0 12:26 pts/0    00:00:00 grep tomcat
    ...

  2. Check whether the port number for Tomcat is available. On the active management node, run the netstat -nap | grep command as user root to check whether another process has occupied the port for Tomcat (8080 and 28443). If the port is occupied, uninstall the program that occupies the port or assign another port to the program process.
  3. If you still cannot log in to FusionInsight Manager after the port conflict is resolved and Tomcat can properly start, check whether the floating IP address of WebService is correctly configured in the ${BIGDATA_HOME}/om-server/tomcat/conf/server.xml file.

    ...
    <Connector port="28443" address="10.10.146.117" protocol="HTTP/1.1" SSLEnabled="true" URIEncoding="UTF-8"
                   maxThreads="150" scheme="https" secure="true"
    ...

  4. If the floating IP address configured by the cluster is correctly configured in the address parameter, check whether the configured subnet mask and gateway address information is the same as that on the management node. Run the ifconfig command to view the subnet mask information.

    eth0      Link encap:Ethernet  HWaddr 90:E2:BA:90:90:D9  
              inet addr:10.10.146.2  Bcast:10.10.146.255  Mask:255.255.255.0
              inet6 addr: fe80::92e2:baff:fe90:90d9/64 Scope:Link
              UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
              RX packets:2441138850 errors:0 dropped:0 overruns:0 frame:0
              TX packets:2433787860 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:1000 
              RX bytes:321588638357 (299.5 GiB)  TX bytes:299823220940 (279.2 GiB)
              Memory:d0800000-d0820000 
    
    eth0:om   Link encap:Ethernet  HWaddr 90:E2:BA:90:90:D9  
              inet addr:10.10.146.121  Bcast:10.10.146.255  Mask:255.255.255.0
              UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
              Memory:d0800000-d0820000 
    
    eth0:ws Link encap:Ethernet  HWaddr 90:E2:BA:90:90:D9  
              inet addr:10.10.146.119  Bcast:10.10.146.255  Mask:255.255.255.0
              UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
              Memory:d0800000-d0820000 

    Run the route command to view the gateway address information.

    Kernel IP routing table
    Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
    default         10.10.146.253   0.0.0.0         UG    0      0        0 eth0
    ...

  5. If the subnet mask and gateway address are correctly set, open the ${BIGDATA_HOME}/om-server/OMS/workspace0/ha/module/harm/plugin/conf/floatip.xml file on the active and standby management nodes and change the following configuration items:

    ...
    <params>
        <param name="wsFloatIp" value="10.10.146.117" show="no"/>
        <param name="wsNetmask" value="255.255.255.0" show="no"/>
        <param name="wsInterface" value="eth0:oms" show="no"/>
        <param name="wsGateWay" value="10.10.146.253" show="no"/>
        <param name="omFloatIp" value="10.10.146.117" show="no"/>
        <param name="omNetmask" value="255.255.255.0" show="no"/>
        <param name="omInterface" value="eth0:oms" show="no"/>
        <param name="omGateWay" value="10.10.146.253" show="no"/>
        <param name="haMode" value="double" show="no"/>
    </params>
    ...

  6. After the parameter values are changed, restart the HA of the active management node.

    ${BIGDATA_HOME}/om-server/om/sbin/restart-oms.sh

Manager Installation Failure Due to Absence of Local Domain Name in the /etc/hosts File

Symptom

An error occurs during Manager installation.

Possible Causes

The local domain name 127.0.0.1 localhost of the management node is not configured in the /etc/hosts file.

Procedure
  1. Log in to a server where the Manager is to be installed as user root on the local PC. When the Manager two-node cluster is installed, log in to the standby management node and repeat the following operations.
  2. Open the hosts file.

    vi /etc/hosts

  3. Check whether the file contains 127.0.0.1 localhost. If no, press Insert to enter the editing mode and add 127.0.0.1 localhost to this file. If yes, go to Step 4.
  4. Press Esc to exit the editing mode, and enter :wq to save the configuration and exit.

Failure Due to Small shmmax Value During Manager Installation

Symptom

During Manager installation, an error indicating that the value of shmmax is too small occurs.

Possible Causes

The value of shmmax is too small.

Troubleshooting Methods

View the /var/log/Bigdata/omm/oms/install_oms.log file of the active management node and check whether the log contains an error message indicating that the value of shmmax is too small. Fault recovery takes about 1 minute.

Procedure
  1. Use PuTTY to log in to the active management node as user root.
  2. View the /var/log/Bigdata/omm/oms/install_oms.log file of the active management node and check whether the log contains an error message indicating that the value of shmmax is too small.
  3. Open the /etc/sysctl.conf file and add a kernel.shmmax=4294967296 row to this file. It is recommended that the value of shmmax be set to half the size of the physical memory. If the physical memory of the node is 8 GB, set the value of shmmax to 4294967296.
  4. Log in to the active management node as user root and run the reboot command to restart the OS.

Failure Due to Inconsistent Codes for Installing GaussDB During Manager Installation

Symptom

When GaussDB is installed for the Manager, an error occurs prompting that the codes are inconsistent.

Possible Causes

The code set specified to the database is in UTF-8 format.

Troubleshooting Methods

View the /var/log/Bigdata/omm/oms/install_oms.log file and check whether the log contains an error message indicating that the codes are inconsistent. Fault recovery takes about 2 minutes.

Procedure
  1. Use PuTTY to log in to the active management node as user root.
  2. View the /var/log/Bigdata/omm/oms/install_oms.log file and check whether the log contains an error message indicating that the codes are inconsistent (gs_initdb:encoding mismatch).

    vi /var/log/Bigdata/omm/oms/install_oms.log

  3. Run the locale command to view the LC_CTYPE parameter.

    [root@host1 ~]# locale 
    LANG=POSIX 
    LC_CTYPE="en_US.UTF-8" 
    LC_NUMERIC="POSIX" 
    LC_TIME="POSIX" 
    LC_COLLATE="POSIX" 
    LC_MONETARY="POSIX" 
    LC_MESSAGES="POSIX" 
    LC_PAPER="POSIX" 
    LC_NAME="POSIX" 
    LC_ADDRESS="POSIX" 
    LC_TELEPHONE="POSIX" 
    LC_MEASUREMENT="POSIX" 
    LC_IDENTIFICATION="POSIX" 
    LC_ALL=

  4. If a RadHat 6.X Linux OS is used, run the vi /etc/sysconfig/i18n command and set LANG to en_US.UTF-8 and SYSFONT to latarcyrheb-sun16. Save the configuration and exit.

    If a RadHat 7.X Linux OS is used, run the vi /etc/locale.conf command and set LANG to en_US.UTF-8 and SYSFONT to latarcyrheb-sun16. Save the configuration and exit.

    If a SuSE Linux OS is used, run the vi /etc/sysconfig/language command and set RC_LANG to en_US.UTF-8 . Save the configuration and exit.

Failed to Install FusionInsight Manager Because SSH Remote Login Is Interrupted

Symptom

When logging in to the server using SSH to install FusionInsight Manager, a user fails to install FusionInsight Manager because SSH remote login is interrupted. An error occurs when FusionInsight Manager installation script is executed again.

Solution
  1. After the network recovers, log in as user root to the server that runs FusionInsight Manager using PuTTY. Run the following commands to access the installation directory (for example, /opt/huawei/Bigdata) to check whether the uninstall.sh script has been generated:

    cd ${BIGDATA_HOME}/om-server/om/sbin

    ll

  2. Check whether the uninstall.sh script has been generated:

    • If yes, run the ./uninstall.sh command to uninstall FusionInsight Manager. Then reinstall it.
    • If no, run the rm -rf ${BIGDATA_HOME} command to delete the installation directory. Then reinstall FusionInsight Manager.

Download
Updated: 2019-05-17

Document ID: EDOC1100074555

Views: 5407

Downloads: 6

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