ECE Install Fail


(Ian) #1

Hi,

Having followed:

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) 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"}}'

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
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
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
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/
[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": "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": {}
}
]


(Uri Cohen) #2

Hi @oil

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


(Ian) #3

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


(system) #4

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