Hi, I'm having trouble running the install script. Here is a debug output.
System details:
[root@ops-ece001.mgo.lax ~]# uname -a Linux ops-ece001.mgo.lax 3.10.0-327.22.2.el7.x86_64 #1 SMP Thu Jun 23 17:05:11 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux [root@ops-ece001.mgo.lax ~]# docker -v Docker version 1.11.2, build b9f10c9 [root@ops-ece001.mgo.lax ~]# cat /etc/redhat-release CentOS Linux release 7.2.1511 (Core) [root@ops-ece001.mgo.lax ~]#
Debug Output:
[root@ops-ece001.mgo.lax ~]# ./elastic-cloud-enterprise-installer.sh --debug
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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 flag
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-- Debug Info --
NODE_TYPE - initial
REPOSITORY - docker.elastic.co/cloud-enterprise
MEMORY_SETTINGS - {}
HOST_STORAGE_PATH - /mnt/data/elastic
RUNNER_HOST_IP - 10.174.88.185
CLOUD_ENTERPRISE_VERSION - 1.0.0-beta1
RUNNER_ID - 10.174.88.185
ELASTIC_GID - 0
HOST_STORAGE_ROOT_VOLUME_PATH - /mnt/data
HOST_STORAGE_DEVICE_PATH - /dev/mapper/lxc-data
RUNNER_REGION - ece-region
NODE_TYPE - initial
RUNNER_AVAILABILITY_ZONE - ece-region-1a
ELASTIC_UID - 0
RUNNER_CAPACITY - 13006
-- Verifying Prerequisites --
Checking host storage path... PASSED
Checking docker version... PASSED
Checking internal ip connectivity... PASSED
Checking OS settings... PASSED
Checking OS kernel version... PASSED
Checking Minimum required memory... PASSED
-- Completed Verifying Prerequisites --
- Running Bootstrap container
- Monitoring bootstrap process
^CProcess bootstrap logging processor:
Traceback (most recent call last):
File "/elastic_cloud_apps/bootstrap-initiator/initiator.py", line 81, in <module>
monitor.logging_and_bootstrap_monitor(bootstrap_properties, enable_debug)
File "/elastic_cloud_apps/bootstrap-initiator/bootstrap_initiator/monitor.py", line 18, in logging_and_bootstrap_monitor
sleep(5)
KeyboardInterrupt
Traceback (most recent call last):
File "/usr/lib/python3.5/multiprocessing/process.py", line 249, in _bootstrap
self.run()
File "/usr/lib/python3.5/multiprocessing/process.py", line 93, in run
self._target(*self._args, **self._kwargs)
File "/elastic_cloud_apps/bootstrap-initiator/bootstrap_initiator/logging.py", line 67, in monitor_bootstrap_log
file_exists = check_log_file_exists(bootstrap_properties)
File "/elastic_cloud_apps/bootstrap-initiator/bootstrap_initiator/logging.py", line 60, in check_log_file_exists
sleep(1)
KeyboardInterrupt
[root@ops-ece001.mgo.lax ~]# ^C
Also, when looking at the docker container logs, I see this:
[root@ops-ece001.mgo.lax ~]# docker logs -f ef08e800b34e
*** Booting runit daemon...
*** Runit started as PID 5
usermod: UID '0' already exists
usermod: UID '0' already exists
usermod: UID '0' already exists
usermod: UID '0' already exists
.....
Thanks,
Adam