# ECE Install Fail

**URL:** <https://discuss.elastic.co/t/ece-install-fail/116397>\
**Category:** Elastic Cloud Enterprise (ECE)\
**Created:** [January 21, 2018, 6:21pm UTC](https://discuss.elastic.co/t/ece-install-fail/116397 "2018-01-21T18:21:16Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![oil](https://avatars.discourse-cdn.com/v4/letter/o/e68b1a/32.png) [@oil](https://discuss.elastic.co/u/oil)\
**Post date:** [January 21, 2018, 6:21pm UTC](https://discuss.elastic.co/t/ece-install-fail/116397/1 "2018-01-21T18:21:16Z")

</div>

Hi,

Having followed:

[https://www.elastic.co/guide/en/cloud-enterprise/current/ece-configure-hosts.html#ece-configure-hosts-rhel-centos](https://www.elastic.co/guide/en/cloud-enterprise/current/ece-configure-hosts.html#ece-configure-hosts-rhel-centos)

I'm cannot install ECE on CentOS 7.4 (with Kernel 4.4.111-1.el7.elrepo.x86\_64)

Checking internal ip connectivity... FAILED  
Can't connect $RUNNER\_HOST\_IP [10.1.1.189:20000]: Host is unreachable

Can anyone help please?

Many thanks!  
Ian

[elastic@ecec7004 ~]$ bash \<(curl -fsSL [https://download.elastic.co/cloud/elastic-cloud-enterprise.sh](https://download.elastic.co/cloud/elastic-cloud-enterprise.sh)) install --debug --host-ip 10.1.1.189 --availability-zone ECEZONE01 --memory-settings '{"runner":{"xms":"1G","xmx":"1G"},"allocator":{"xms":"4G","xmx":"4G"},"proxy":{"xms":"8G","xmx":"8G"},"zookeeper":{"xms":"4G","xmx":"4G"},"director":{"xms":"1G","xmx":"1G"},"constructor":{"xms":"4G","xmx":"4G"},"admin-console":{"xms":"4G","xmx":"4G"}}'

```auto
Elastic Cloud Enterprise Installer

Start setting up a new Elastic Cloud Enterprise installation by installing the software on your first host.
This first host becomes the initial coordinator and provides access to the Cloud UI, where you can manage your installation.
To learn more about the options you can specify, see the documentation.

NOTE: If you want to add this host to an existing installation, please specify the --coordinator-host and --roles-token flags

```

-- Debug Info --  
NODE\_TYPE - initial  
CLOUD\_ENTERPRISE\_VERSION - 1.1.2  
HOST\_DOCKER\_HOST - /var/run/docker.sock  
HOST\_STORAGE\_DEVICE\_PATH - /dev/mapper/centos\_ecec7002-root  
HOST\_STORAGE\_ROOT\_VOLUME\_PATH - /mnt/data  
HOST\_STORAGE\_PATH - /mnt/data/elastic  
NODE\_TYPE - initial  
RUNNER\_REGION - ece-region  
RUNNER\_ID - 10.1.1.189  
RUNNER\_ROLES -  
RUNNER\_ROLES\_TOKEN -  
RUNNER\_HOST\_IP - 10.1.1.189  
RUNNER\_AVAILABILITY\_ZONE - ECEZONE01  
RUNNER\_CAPACITY - 36737  
RUNNER\_ENVIRONMENT\_METADATA\_JSON - {}  
ELASTIC\_UID - 1001  
ELASTIC\_GID - 1001  
ELASTIC\_CLOUD\_PLATFORM - aws  
MEMORY\_SETTINGS - {"runner":{"xms":"1G","xmx":"1G"},"allocator":{"xms":"4G","xmx":"4G"},"proxy":{"xms":"8G","xmx":"8G"},"zookeeper":{"xms":"4G","xmx":"4G"},"director":{"xms":"1G","xmx":"1G"},"constructor":{"xms":"4G","xmx":"4G"},"admin-console":{"xms":"4G","xmx":"4G"}}  
CONFIG\_FILE -  
FORCE\_INSTALL - False  
HOST\_PREREQ\_FAILED - False  
DOCKER\_REGISTRY - [docker.elastic.co](http://docker.elastic.co)  
ECE\_DOCKER\_REPOSITORY - cloud-enterprise  
ECE\_TIMEOUT\_FACTOR - 1.0

-- Verifying Prerequisites --  
Checking host storage path... PASSED  
Checking docker version... PASSED  
Checking internal ip connectivity... FAILED  
Can't connect $RUNNER\_HOST\_IP [10.1.1.189:20000]: Host is unreachable  
Checking OS settings... PASSED  
Checking OS kernel version... PASSED  
Checking Minimum required memory... PASSED  
Checking Kernel cgroup.memory setting... PASSED

- OS setting 'cgroup.memory' should be set to cgroup.memory=nokmem

```auto
Errors have caused Elastic Cloud Enterprise installation to fail
Some of the prerequisites failed: [internal ip connectivity], please fix before continuing
Traceback (most recent call last):
  File "/elastic_cloud_apps/bootstrap-initiator/initiator.py", line 68, in <module>
    prerequisite.verify_prerequisites(prerequisites, bootstrap_properties)
  File "/elastic_cloud_apps/bootstrap-initiator/bootstrap_initiator/prerequisite/base.py", line 67, in verify_prerequisites
    raise PrerequisiteFailed(unmet)
bootstrap_initiator.prerequisite.base.PrerequisiteFailed: Some of the prerequisites failed: [internal ip connectivity], please fix before continuing

```

[elastic@ecec7004 ~]$ ip a  
1: lo: \<LOOPBACK,UP,LOWER\_UP\> mtu 65536 qdisc noqueue state UNKNOWN qlen 1  
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00  
inet 127.0.0.1/8 scope host lo  
valid\_lft forever preferred\_lft forever  
inet6 ::1/128 scope host  
valid\_lft forever preferred\_lft forever  
2: eth0: \<BROADCAST,MULTICAST,UP,LOWER\_UP\> mtu 1500 qdisc mq state UP qlen 1000  
link/ether 00:15:5d:01:bf:00 brd ff:ff:ff:ff:ff:ff  
inet 10.1.1.188/24 brd 10.1.1.255 scope global eth0  
valid\_lft forever preferred\_lft forever  
inet6 fe80::215:5dff:fe01:bf00/64 scope link  
valid\_lft forever preferred\_lft forever  
3: docker0: \<NO-CARRIER,BROADCAST,MULTICAST,UP\> mtu 1500 qdisc noqueue state DOWN  
link/ether 02:42:c1:8c:bb:15 brd ff:ff:ff:ff:ff:ff  
inet 10.1.1.189/24 scope global docker0  
valid\_lft forever preferred\_lft forever  
inet6 fe80::42:c1ff:fe8c:bb15/64 scope link  
valid\_lft forever preferred\_lft forever

[elastic@ecec7004 ~]$ sudo docker info  
Containers: 0  
Running: 0  
Paused: 0  
Stopped: 0  
Images: 1  
Server Version: 1.11.2  
Storage Driver: overlay  
Backing Filesystem: xfs  
Logging Driver: json-file  
Cgroup Driver: cgroupfs  
Plugins:  
Volume: local  
Network: bridge null host  
Kernel Version: 4.4.111-1.el7.elrepo.x86\_64  
Operating System: CentOS Linux 7 (Core)  
OSType: linux  
Architecture: x86\_64  
CPUs: 4  
Total Memory: 42.21 GiB  
Name: [ecec7004.ltg.lever.co.uk](http://ecec7004.ltg.lever.co.uk)  
ID: RUCJ:5IRU:LHAV:J3QV:QTJD:4JPO:G4TG:TK3I:DU6Y:AB3A:MJT5:RDJB  
Docker Root Dir: /mnt/data/docker  
Debug mode (client): false  
Debug mode (server): false  
Registry: [https://index.docker.io/v1/](https://index.docker.io/v1/)  
[elastic@ecec7004 ~]$ sudo docker network ls  
NETWORK ID NAME DRIVER  
3b9cc5b1bc40 bridge bridge  
104f9cb98c4c host host  
9522bf8c56e0 none null

[elastic@ecec7004 ~]$ sudo docker network inspect bridge  
[  
{  
"Name": "bridge",  
"Id": "3b9cc5b1bc400851e972cfd1212b2ddad8b918e4467228b313096d76e8a8e6b9",  
"Scope": "local",  
"Driver": "bridge",  
"EnableIPv6": false,  
"IPAM": {  
"Driver": "default",  
"Options": null,  
"Config": [  
{  
"Subnet": "10.1.1.189/24",  
"Gateway": "10.1.1.189"  
}  
]  
},  
"Internal": false,  
"Containers": {},  
"Options": {  
"com.docker.network.bridge.default\_bridge": "true",  
"com.docker.network.bridge.enable\_icc": "true",  
"com.docker.network.bridge.enable\_ip\_masquerade": "true",  
"com.docker.network.bridge.host\_binding\_ipv4": "0.0.0.0",  
"[com.docker.network.bridge.name](http://com.docker.network.bridge.name)": "docker0",  
"com.docker.network.driver.mtu": "1500"  
},  
"Labels": {}  
}  
]

[elastic@ecec7004 ~]$ sudo docker network inspect host  
[  
{  
"Name": "host",  
"Id": "104f9cb98c4ce47e0af99d6361342d248850f0064a8d3f1c1fc9b74404337dcb",  
"Scope": "local",  
"Driver": "host",  
"EnableIPv6": false,  
"IPAM": {  
"Driver": "default",  
"Options": null,  
"Config": []  
},  
"Internal": false,  
"Containers": {},  
"Options": {},  
"Labels": {}  
}  
]

---

<div class="post-metadata">

**Author:** ![uricohen](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/uricohen/32/9776_2.png) [@uricohen](https://discuss.elastic.co/u/uricohen)\
**Post date:** [January 24, 2018, 10:54am UTC](https://discuss.elastic.co/t/ece-install-fail/116397/2 "2018-01-24T10:54:01Z")

</div>

Hi @oil

Can you verify that 10.1.1.189 is a routable address in your network?

---

<div class="post-metadata">

**Author:** ![oil](https://avatars.discourse-cdn.com/v4/letter/o/e68b1a/32.png) [@oil](https://discuss.elastic.co/u/oil)\
**Post date:** [January 25, 2018, 9:35am UTC](https://discuss.elastic.co/t/ece-install-fail/116397/3 "2018-01-25T09:35:40Z")

</div>

Hi Uri,

Yes - the docker0 interface (10.1.1.189) was routable.

I made a mistake when following Elastic's ECE installation Pre-requisites (for CentOS): I changed the IP address specified in Under step 8. Configure the Docker daemon options.

I created the directory and file /etc/systemd/system/docker.service.d/docker.conf

but I changed --bip=172.17.42.1/16 to a local, routable address, thinking that was necessary.

That's obviously wrong.

It might be an idea to add a line to that part of your (excellent) documentation, telling people to keep the 172 .. IP address shown.

Many thanks Uri.

Ian

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [February 8, 2018, 9:35am UTC](https://discuss.elastic.co/t/ece-install-fail/116397/4 "2018-02-08T09:35:42Z")

</div>

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.