ECE Installation Issue

Hi folks. Attempting to install ECE on prem using a medium installation guide. Was able to get the first 3 servers up and running no issue. When I attempt to install the 3 allocator servers, I am getting an error with the bootstrap.conf missing a paren. This happens on all 3 allocator servers.

I have search around and cant seem to find an answer. Can anyone assist?

bash <(curl -fsSL https://download.elastic.co/cloud/elastic-cloud-enterprise.sh) install --coordinator-host 10.150.1.147 --roles-token 'eyJ0eXAiOiJKV1QiLCJhbGc...redacted.....' --roles "allocator" --availability-zone US_East_AZ2 --memory-settings '{"runner":{"xms":"1G","xmx":"1G"}, "allocator":{"xms":"4G","xmx":"4G"}}'

Elastic Cloud Enterprise Installer

Install Elastic Cloud Enterprise on this host to add its resources to an existing installation.
After installation is complete, the host becomes a runner that you can assign a role to in the Cloud UI.
To learn more about the options you can specify, see the documentation.

-- Verifying Prerequisites --
Checking runner container does not exist... PASSED
Checking host storage root volume path is not root... PASSED
Checking host storage path is accessible... PASSED
Checking host storage path contents matches whitelist... PASSED
Checking Docker version... PASSED
Checking Docker file system... PASSED
Checking Docker network settings... PASSED
Checking Docker storage driver... PASSED
Checking whether 'setuser' works inside a Docker container... PASSED
Checking memory settings... PASSED
Checking runner ip connectivity... PASSED
Checking coordinator connectivity... PASSED
Checking OS IPv4 IP forward setting... PASSED
Checking metadata endpoint protection... PASSED

  • The installation can proceed with 169.254.169.254 accessible; however we consider this a SSRF risk and recommend adjusting your firewall rules to prevent access from docker containers.
    Checking OS max map count setting... PASSED
    Checking OS kernel version... PASSED
    Checking minimum required memory... PASSED
    Checking OS kernel cgroup.memory... PASSED
    Checking OS minimum ephemeral port... PASSED
    Checking OS max open file descriptors per process... PASSED
    Checking OS max open file descriptors system-wide... PASSED
    Checking OS file system and Docker storage driver compatibility... PASSED
    Checking OS file system storage driver permissions... PASSED
    Checking OS AppArmor status... PASSED
    -- Completed Verifying Prerequisites --

  • Running Bootstrap container

  • Monitoring bootstrap process

  Errors have caused Elastic Cloud Enterprise installation to fail - Please check logs
  Node type - additional
  • Waiting for bootstrap monitor process to exit

elastic@~$ cat /mnt/data/elastic/logs/bootstrap-logs/bootstrap.log
[2021-08-04 12:13:05,441][ERROR][scala.Predef$ ] Uncaught throwable occurred on thread: [main], calling System.exit(1) {}
com.typesafe.config.ConfigException$Parse: /elastic_cloud_apps/bootstrap/bootstrap.conf: 59: expecting a close parentheses ')' here, not: end of file
at com.typesafe.config.impl.ConfigDocumentParser$ParseContext.parseError(ConfigDocumentParser.java:201)
at com.typesafe.config.impl.ConfigDocumentParser$ParseContext.parseError(ConfigDocumentParser.java:197)
at com.typesafe.config.impl.ConfigDocumentParser$ParseContext.parseKey(ConfigDocumentParser.java:279)
at com.typesafe.config.impl.ConfigDocumentParser$ParseContext.parseObject(ConfigDocumentParser.java:450)
at com.typesafe.config.impl.ConfigDocumentParser$ParseContext.parseValue(ConfigDocumentParser.java:247)
at com.typesafe.config.impl.ConfigDocumentParser$ParseContext.parseObject(ConfigDocumentParser.java:458)
at com.typesafe.config.impl.ConfigDocumentParser$ParseContext.parse(ConfigDocumentParser.java:648)
at com.typesafe.config.impl.ConfigDocumentParser.parse(ConfigDocumentParser.java:14)
at com.typesafe.config.impl.Parseable.rawParseValue(Parseable.java:260)
at com.typesafe.config.impl.Parseable.rawParseValue(Parseable.java:248)
at com.typesafe.config.impl.Parseable.parseValue(Parseable.java:180)
at com.typesafe.config.impl.Parseable.parseValue(Parseable.java:174)
at com.typesafe.config.impl.Parseable.parse(Parseable.java:299)
at com.typesafe.config.ConfigFactory.parseFile(ConfigFactory.java:689)
at no.found.bootstrap.shared.ConfigurationLoader$.loadDefault(ConfigurationLoader.scala:60)
at no.found.bootstrap.BootstrapAdditional$.delayedEndpoint$no$found$bootstrap$BootstrapAdditional$1(BootstrapAdditional.scala:375)
at no.found.bootstrap.BootstrapAdditional$delayedInit$body.apply(BootstrapAdditional.scala:373)
at scala.Function0.apply$mcV$sp(Function0.scala:39)
at scala.Function0.apply$mcV$sp$(Function0.scala:39)
at scala.runtime.AbstractFunction0.apply$mcV$sp(AbstractFunction0.scala:17)
at scala.App.$anonfun$main$1$adapted(App.scala:80)
at scala.collection.immutable.List.foreach(List.scala:431)
at scala.App.main(App.scala:80)
at scala.App.main$(App.scala:78)
at no.found.util.ElasticCloudApp.main(ElasticCloudApp.scala:23)
at no.found.bootstrap.BootstrapAdditional.main(BootstrapAdditional.scala)
[2021-08-04 12:13:05,449][INFO ][no.found.util.LogApplicationExit$] Application is exiting {}

This one we've seen before when that --memory-settings includes newlines or is otherwise malformed, but that's not the case here it seems (and I think I remember fixing the docs for exactly that reason, and sure enough: Deploy a medium installation | Elastic Cloud Enterprise Reference [2.10] | Elastic)

Is that --memory-settings definitely the one you used?

Alex. Thank you! It was the memory settings. There was a space after the comma that was causing the issue.

1 Like

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