Hitachi Content Platform​

 HCI 1.3.1.54 Install, cannot connect to deployment wizard

  • Object Storage
  • Hitachi Content Intelligence HCI
Thomas Massano's profile image
Thomas Massano posted 10-11-2018 20:40

This content was either too long or contained formatting that did not work with our migration. A PDF document is attached that contains the original representation

 

I have installed HCI several times with no issue, I have even created a cheat sheet.But I must be missing something basic here, the install goes as planned, but i can never connect to the deployment wizard. I keep getting ERR_CONNECTION_REFUSED.I have tried to install this several times, and with the same result. I must be missing something basic here.I have done the install from a terminal (not console), so I know I have IP connectivity.My Cheet sheet:8 cores32 GB Mem1TB storage1 InterfaceInstalled CentOS 7.4 from DVD, with no additional packages.Put static IPv4 and enabled NTP.yum install -y yum-utils device-mapper-persistent-data lvm2yum-config-manager --add-repo https://download.docker.com/linux/centos/docker-ce.repo <https://download.docker.com/linux/centos/docker-ce.repo>yum install -y docker-cedocker --version -> Docker version 18.06.1-cesystemctl status firewalld systemctl stop firewalldsystemctl mask firewalldsystemctl disable firewalldsystemctl status firewalldsysctl -w vm.max_map_count=262144 vi /etc/sysctl.confadd 'vm.max_map_count=262144' to /etc/sysctl.confsystemctl status docker systemctl start dockersystemctl enable dockersystemctl status docker -lmkdir /opt/hcicd /opt/hciupload HCI-1.3.1.54.tgztar -zxvf HCI-1.3.1.54.tgz ./1.3.1.54/bin/installnode 1 bin/setup -i 192.168.35.235 -m 192.168.35.236,192.168.35.237,192.168.35.238node 2 bin/setup -i 192.168.35.236 -m 192.168.35.235,192.168.35.237,192.168.35.238node 3 bin/setup -i 192.168.35.237 -m 192.168.35.235,192.168.35.236,192.168.35.238node 4 bin/setup -i 192.168.35.238 -m 192.168.35.235,192.168.35.236,192.168.35.237TERMINAL OUTPUT WITH MESSAGES:I bolded my commands so they were easier to find~~~~~~~~~~~~~~~~~~~~~~~~~~~~[root@hci-node1 ~]# cat /etc/*eleaseCentOS Linux release 7.4.1708 (Core)NAME="CentOS Linux"VERSION="7 (Core)"ID="centos"ID_LIKE="rhel fedora"VERSION_ID="7"PRETTY_NAME="CentOS Linux 7 (Core)"ANSI_COLOR="0;31"CPE_NAME="cpe:/o:centos:centos:7"HOME_URL="https://www.centos.org/ <https://www.centos.org/>"BUG_REPORT_URL="https://bugs.centos.org/ <https://bugs.centos.org/>" CENTOS_MANTISBT_PROJECT="CentOS-7"CENTOS_MANTISBT_PROJECT_VERSION="7"REDHAT_SUPPORT_PRODUCT="centos"REDHAT_SUPPORT_PRODUCT_VERSION="7" CentOS Linux release 7.4.1708 (Core)CentOS Linux release 7.4.1708 (Core) [root@hci-node1 ~]# yum install -y yum-utils device-mapper-persistent-data lvm2Loaded plugins: fastestmirrorLoading mirror speeds from cached hostfile * base: mirror.jaleco.com * extras: repos.lax.quadranet.com * updates: mirror.den1.denvercolo.netResolving Dependencies--> Running transaction check---> Package device-mapper-persistent-data.x86_64 0:0.7.0-0.1.rc6.el7 will be updated---> Package device-mapper-persistent-data.x86_64 0:0.7.3-3.el7 will be an update---> Package lvm2.x86_64 7:2.02.171-8.el7 will be updated---> Package lvm2.x86_64 7:2.02.177-4.el7 will be an update--> Processing Dependency: lvm2-libs = 7:2.02.177-4.el7 for package: 7:lvm2-2.02.177-4.el7.x86_64--> Processing Dependency: libdevmapper.so.1.02(DM_1_02_141)(64bit) for package: 7:lvm2-2.02.177-4.el7.x86_64---> Package yum-utils.noarch 0:1.1.31-46.el7_5 will be installed--> Processing Dependency: python-kitchen for package: yum-utils-1.1.31-46.el7_5.noarch--> Processing Dependency: libxml2-python for package: yum-utils-1.1.31-46.el7_5.noarch--> Running transaction check---> Package device-mapper-libs.x86_64 7:1.02.140-8.el7 will be updated--> Processing Dependency: device-mapper-libs = 7:1.02.140-8.el7 for package: 7:device-mapper-1.02.140-8.el7.x86_64---> Package device-mapper-libs.x86_64 7:1.02.146-4.el7 will be an update---> Package libxml2-python.x86_64 0:2.9.1-6.el7_2.3 will be installed---> Package lvm2-libs.x86_64 7:2.02.171-8.el7 will be updated---> Package lvm2-libs.x86_64 7:2.02.177-4.el7 will be an update--> Processing Dependency: device-mapper-event = 7:1.02.146-4.el7 for package: 7:lvm2-libs-2.02.177-4.el7.x86_64---> Package python-kitchen.noarch 0:1.1.1-5.el7 will be installed--> Processing Dependency: python-chardet for package: python-kitchen-1.1.1-5.el7.noarch--> Running transaction check---> Package device-mapper.x86_64 7:1.02.140-8.el7 will be updated---> Package device-mapper.x86_64 7:1.02.146-4.el7 will be an update---> Package device-mapper-event.x86_64 7:1.02.140-8.el7 will be updated---> Package device-mapper-event.x86_64 7:1.02.146-4.el7 will be an update--> Processing Dependency: device-mapper-event-libs = 7:1.02.146-4.el7 for package: 7:device-mapper-event-1.02.146-4.el7.x86_64---> Package python-chardet.noarch 0:2.2.1-1.el7_1 will be installed--> Running transaction check---> Package device-mapper-event-libs.x86_64 7:1.02.140-8.el7 will be updated---> Package device-mapper-event-libs.x86_64 7:1.02.146-4.el7 will be an update--> Finished Dependency ResolutionDependencies Resolved===================================================================================================================================================================== Package                                               Arch                           Version                                  Repository                       Size=====================================================================================================================================================================Installing: yum-utils                                             noarch                         1.1.31-46.el7_5                          updates                         120 kUpdating: device-mapper-persistent-data                         x86_64                         0.7.3-3.el7                              base                            405 k lvm2                                                  x86_64                         7:2.02.177-4.el7                         base                            1.3 MInstalling for dependencies: libxml2-python                                        x86_64                         2.9.1-6.el7_2.3                          base                            247 k python-chardet                                        noarch                         2.2.1-1.el7_1                            base                            227 k python-kitchen                                        noarch                         1.1.1-5.el7                              base                            267 kUpdating for dependencies: device-mapper                                         x86_64                         7:1.02.146-4.el7                         base                            289 k device-mapper-event                                   x86_64                         7:1.02.146-4.el7                         base                            185 k device-mapper-event-libs                              x86_64                         7:1.02.146-4.el7                         base                            184 k device-mapper-libs                                    x86_64                         7:1.02.146-4.el7                         base                            316 k lvm2-libs                                             x86_64                         7:2.02.177-4.el7                         base                            1.0 MTransaction Summary=====================================================================================================================================================================Install  1 Package  (+3 Dependent packages)Upgrade  2 Packages (+5 Dependent packages)Total download size: 4.5 MDownloading packages:Delta RPMs disabled because /usr/bin/applydeltarpm not installed.warning: /var/cache/yum/x86_64/7/base/packages/device-mapper-1.02.146-4.el7.x86_64.rpm: Header V3 RSA/SHA256 Signature, key ID f4a80eb5: NOKEYPublic key for device-mapper-1.02.146-4.el7.x86_64.rpm is not installed(1/11): device-mapper-1.02.146-4.el7.x86_64.rpm                                                                                               | 289 kB  00:00:00(2/11): device-mapper-event-1.02.146-4.el7.x86_64.rpm                                                                                         | 185 kB  00:00:00(3/11): device-mapper-event-libs-1.02.146-4.el7.x86_64.rpm                                                                                    | 184 kB  00:00:00(4/11): libxml2-python-2.9.1-6.el7_2.3.x86_64.rpm                                                                                             | 247 kB  00:00:00(5/11): python-chardet-2.2.1-1.el7_1.noarch.rpm                                                                                               | 227 kB  00:00:00(6/11): python-kitchen-1.1.1-5.el7.noarch.rpm                                                                                                 | 267 kB  00:00:00(7/11): device-mapper-persistent-data-0.7.3-3.el7.x86_64.rpm                                                                                  | 405 kB  00:00:00(8/11): device-mapper-libs-1.02.146-4.el7.x86_64.rpm                                                                                          | 316 kB  00:00:00(9/11): lvm2-2.02.177-4.el7.x86_64.rpm                                                                                                        | 1.3 MB  00:00:0...
#HitachiContentIntelligenceHCI
Jonathan Chinitz's profile image
Jonathan Chinitz

First off you have a problem with your master nodes:

node 1 bin/setup -i 192.168.35.235 -m 192.168.35.236,192.168.35.237,192.168.35.238

The above has the masters at 236,237,238

node 2 bin/setup -i 192.168.35.236 -m 192.168.35.235,192.168.35.237,192.168.35.238

This one has a master at 235

node 3 bin/setup -i 192.168.35.237 -m 192.168.35.235,192.168.35.236,192.168.35.238

This one has 235 but doesn't have 237

node 4 bin/setup -i 192.168.35.238 -m 192.168.35.235,192.168.35.236,192.168.35.237

The list of masters MUST be the same for ALL nodes in the cluster.

 

Thomas Massano's profile image
Thomas Massano

Thanks Jon, so it should be:

node 1 bin/setup -i 192.168.35.235 -m 192.168.35.235,192.168.35.236,192.168.35.237,192.168.35.238

node 2 bin/setup -i 192.168.35.236 -m 192.168.35.235,192.168.35.236,192.168.35.237,192.168.35.238

node 3 bin/setup -i 192.168.35.237 -m 192.168.35.235,192.168.35.236,192.168.35.237,192.168.35.238

node 4 bin/setup -i 192.168.35.238 -m 192.168.35.235,192.168.35.236,192.168.35.237,192.168.35.238

Jonathan Chinitz's profile image
Jonathan Chinitz

NO. If you have 3 masters then pick the 3 IPs and use them for all FOUR nodes. Example:

node 1 bin/setup -i 192.168.35.235 -m 192.168.35.235,192.168.35.236,192.168.35.237

node 2 bin/setup -i 192.168.35.236 -m 192.168.35.235,192.168.35.236,192.168.35.237

node 3 bin/setup -i 192.168.35.237 -m 192.168.35.235,192.168.35.236,192.168.35.237

node 4 bin/setup -i 192.168.35.238 -m 192.168.35.235,192.168.35.236,192.168.35.237

 

 

Thomas Massano's profile image
Thomas Massano

GOT IT!

Thank you for your guidance and patience.

Data Conversion's profile image
Data Conversion
Attachment  View in library
65919.pdf 299 KB