Bootstrap monitoring process did not exit as expected - Again

I am asking to reopen this ticket. I need some kind of resolution on how to fix it. I have 7 deployments to do in the next 6 months. I had no issues with doing the install on Centos 7 but when I tried in RHEL 7.5 Maipo - with Docker 1.13 I am getting the error. Could someone please put in the commands for how they fixed it.
Also, where does the IP address come into play with the services? Why is it used in the /mnt/data/elastic/xxx.xxx.1.187/services. Is there somewhere in the configuration that I should have made a change so that the IP address is not the point for services. I am asking as one of the errors that shows up when I am not directly in that network, I get a message that it is on the whitelist and I should change it.

Any help would be greatly appreciated.
Linda Carr

Dear Linda,

As we've described, the installer yields false negative message, which means that it should
be ignored by user, who should instead refer to bootstrap/upgrade log. If you don't see errors there, that means the relevant processes has completed successfully (see ECE documentation here).

Although problem has been resolved at our end, we need to release new ECE version which will contain the fix.

This issue occurs on your environment only if Docker daemon logging driver is set to journald. If changing it to json-file would be an option for you, this could act as a workaround.

Could you please send me where I would do that? How to and where the files live.

Thanks
Linda

Also, where does the IP address come into play with the services? Why is it used in the /mnt/data/elastic/xxx.xxx.1.187/services.

Regarding the path you're mentioning - yes, it's configurable upon ECE installation. This path contains runner ID of the node. There's --runner-id option in our installation script you can use to specify a custom value.

Default runner ID is always the IP address of the host, so that's why you're seeing xxx.xxx.1.187 subdirectory there.

You can find those logs in either /mnt/data/elastic/logs/bootstrap-logs or /mnt/data/elastic/logs/upgrader-logs directory, depending on task you're actually doing.

For Docker daemon configuration please refer to the official documentation https://docs.docker.com/config/containers/logging/configure/

Ok – so where do I change the timeout setting? That is what I am looking for.

I am doing the initial build on 7.5. If I run into the same issue with the 7.4 I want to know exactly where I need make those changes based on the ECE 2.4 build details.

https://www.elastic.co/guide/en/cloud-enterprise/current/ece-configure-hosts-rhel-centos.html

Thanks very much!!

Linda Carr

571-437-6540

Telegraph: https://t.me/Lcarr_P

Always show up to the problem looking like a solution” - Marquis Phifer

So in the elastic-cloud-enterprise.sh file? Is this where you are talking about? I have that open in Notepad ++ -

Would you have time to review it with me and make changes as needed?

Thanks!

Linda Carr

571-437-6540

Telegraph: https://t.me/Lcarr_P

Always show up to the problem looking like a solution” - Marquis Phifer

How do I change the services directory that is pointing to the IP of the machine? Would there be a better place that is more generic so that if the system is built in a lab and then has a NAT to the outside world the files can be reached? Where is that detail in the script please.

Thanks,

Linda Carr

571-437-6540

Telegraph: https://t.me/Lcarr_P

Always show up to the problem looking like a solution” - Marquis Phifer

Also – reran it after removing the previous build and got this again –

image003.jpg

Please assist..

Linda Carr

571-437-6540

Telegraph: https://t.me/Lcarr_P

Always show up to the problem looking like a solution” - Marquis Phifer

Is there a team who can work with me on troubleshooting? Please let me know as soon as you can.

Linda Carr

571-437-6540

Telegraph: https://t.me/Lcarr_P

Always show up to the problem looking like a solution” - Marquis Phifer