# ECE Allocator install with new data directory

**URL:** <https://discuss.elastic.co/t/ece-allocator-install-with-new-data-directory/85304>\
**Category:** Elastic Cloud Enterprise (ECE)\
**Created:** [May 10, 2017, 8:43pm UTC](https://discuss.elastic.co/t/ece-allocator-install-with-new-data-directory/85304 "2017-05-10T20:43:15Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![tarp](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tarp/32/51884_2.png) [@tarp](https://discuss.elastic.co/u/tarp)\
**Post date:** [May 10, 2017, 8:43pm UTC](https://discuss.elastic.co/t/ece-allocator-install-with-new-data-directory/85304/1 "2017-05-10T20:43:15Z")

</div>

I'm building a ECE cluster at AWS. I'm using the AMIs provided by Elastic.

I'm trying to create my allocator EC2 instances with 4TB of disk. I have done this in cloud formation, with the following parameters.  
BlockDeviceMappings:  
-  
DeviceName: /dev/sdb  
Ebs:  
VolumeSize: 4000  
VolumeType: gp2  
DeleteOnTermination: true

In the OS userdata I run the following commands.  
"mkfs -t xfs /dev/xvdb\n",  
"mkdir /data\n",  
"mount /dev/xvdb /data\n",  
"chown elastic.elastic /data\n",  
"echo '/dev/xvdb /data ext4 defaults,nofail 0 2' \>\> /etc/fstab\n",

OS looks like this,  
[elastic@ip-10-212-98-233 mapper]$ df -h  
Filesystem Size Used Avail Use% Mounted on  
devtmpfs 16G 0 16G 0% /dev  
tmpfs 16G 0 16G 0% /dev/shm  
tmpfs 16G 8.3M 16G 1% /run  
tmpfs 16G 0 16G 0% /sys/fs/cgroup  
/dev/xvda3 19G 1.7G 17G 10% /  
/dev/xvda1 1014M 209M 806M 21% /boot  
/dev/mapper/lxc-data 19G 1.1G 18G 6% /mnt/data  
/dev/xvdb 4.0T 33M 4.0T 1% /data  
tmpfs 3.2G 0 3.2G 0% /run/user/1000

I try to install ECE with the following command  
./elastic-cloud-enterprise-installer.sh --coordinator-host 10.212.97.168 --host-storage-path /data --debug

This errors out, with nothing useful, debug output is below.  
-- Debug Info --  
NODE\_TYPE - additional  
REPOSITORY - [docker.elastic.co/cloud-enterprise](http://docker.elastic.co/cloud-enterprise)  
RUNNER\_REGION - ece-region  
RUNNER\_HOST\_IP - 10.212.98.233  
ELASTIC\_UID - 1000  
NODE\_TYPE - additional  
RUNNER\_AVAILABILITY\_ZONE - ece-region-1b  
HOST\_STORAGE\_ROOT\_VOLUME\_PATH - /  
MEMORY\_SETTINGS - {}  
COORDINATOR\_HOST - 10.212.97.168  
RUNNER\_ID - 10.212.98.233  
HOST\_STORAGE\_PATH - /data  
RUNNER\_CAPACITY - 26971  
CLOUD\_ENTERPRISE\_VERSION - 1.0.0-beta2  
HOST\_STORAGE\_DEVICE\_PATH - /dev/mapper/lxc-data  
ELASTIC\_GID - 1000

-- Verifying Prerequisites --  
Checking host storage path... PASSED  
Checking docker version... PASSED  
Checking internal ip connectivity... PASSED  
Checking coordinator 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

```auto
Errors have caused Elastic Cloud Enterprise installation to fail

I believe the problem is how I'm creating the filesystem or mounting it. The install worked fine before I started trying to add the large filesystem. Am I doing this the proper way? Can someone help?
```

---

<div class="post-metadata">

**Author:** ![cstrzadala](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/cstrzadala/32/8211_2.png) [@cstrzadala](https://discuss.elastic.co/u/cstrzadala)\
**Post date:** [May 12, 2017, 2:03am UTC](https://discuss.elastic.co/t/ece-allocator-install-with-new-data-directory/85304/2 "2017-05-12T02:03:33Z")

</div>

Hi @tarp,

Does this install fail constantly? When it fails, can you run the following commands to try and get some more info out of the issue.

- `docker ps -a`
- `docker logs elastic-cloud-enterprise-bootstrap-1.0.0-beta2`

If you can give us the output of those two commands, that would help us diagnose the issue here.

Thanks,

Christian

---

<div class="post-metadata">

**Author:** ![tarp](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tarp/32/51884_2.png) [@tarp](https://discuss.elastic.co/u/tarp)\
**Post date:** [May 12, 2017, 3:30pm UTC](https://discuss.elastic.co/t/ece-allocator-install-with-new-data-directory/85304/3 "2017-05-12T15:30:33Z")

</div>

Hi Christian,

I'm out of the office for about a week, so I can't test this right now.

Can you look at my filesystem creation process and tell me if this is sound? Is there a better way to be doing this with EC2 at AWS using the provided AMIs?

Thanks,  
Tim

---

<div class="post-metadata">

**Author:** ![tarp](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tarp/32/51884_2.png) [@tarp](https://discuss.elastic.co/u/tarp)\
**Post date:** [May 22, 2017, 3:50pm UTC](https://discuss.elastic.co/t/ece-allocator-install-with-new-data-directory/85304/4 "2017-05-22T15:50:14Z")

</div>

Hi Christian,

Sorry for getting back to you so late, I was on vacation. Yes this happens everytime I try to build the allocator with the larger disk.

Output you requested is here.  
[root@ip-10-212-101-176 ~]# docker ps -a  
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES  
d3f0aa5746ae [docker.elastic.co/cloud-enterprise/elastic-cloud-enterprise:1.0.0-beta2](http://docker.elastic.co/cloud-enterprise/elastic-cloud-enterprise:1.0.0-beta2) "/sbin/my\_init" 17 minutes ago Exited (0) 17 minutes ago elastic-cloud-enterprise-bootstrap-1.0.0-beta2

\*\*\* /elastic\_cloud\_apps/bootstrap/bootstrap-additional exited with status 1.  
\*\*\* Killing all processes...  
\*\*\* Runit exited with status 0  
fail: /etc/service/docker-socket-proxy: runsv not running  
fail: /etc/service/entry-point: runsv not running  
\*\*\* Killing all processes...

---

<div class="post-metadata">

**Author:** ![tarp](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tarp/32/51884_2.png) [@tarp](https://discuss.elastic.co/u/tarp)\
**Post date:** [May 23, 2017, 7:41pm UTC](https://discuss.elastic.co/t/ece-allocator-install-with-new-data-directory/85304/5 "2017-05-23T19:41:07Z")

</div>

Hi,  
I have corrected this issue with the following steps  
shutdown docker service  
I copied the existing /mnt/data/\* to /data  
updated permissions  
remounted /data as /mnt/data  
updated the /etc/fstab  
remount  
startup docker

This gave me my 4TB partition and I didn't have to run the installer with any special data flags.

---

<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:** [June 6, 2017, 7:41pm UTC](https://discuss.elastic.co/t/ece-allocator-install-with-new-data-directory/85304/6 "2017-06-06T19:41:19Z")

</div>

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