The execution script fails on CentOS distributions
When trying to launch the execution script, it might fail if you are using a CentOS distribution with a Minimal installation.
Symptom 1: cannot find host
On a Minimal version of CentOS, you may not have all the DNS-related commands
(host, dig, nslookup, etc.).
The execution script needs the host command to be present on the OS,
otherwise it will fail and you will get the following
error:
[centos@ip-XXX-XX-X-XX remote-engine]$ ./remote-engine.sh start -r eu -k <YourKey>
Checking docker status
Docker is up and running now!
############################################################################################################
To run the Remote Engine Gen2 on your machine, your Docker environment needs at least 8GB of memory
############################################################################################################
Starting the Remote Engine Gen2
./remote-engine.sh: ligne229: host : command not found
Dns name 'pair.us/eu/ap.cloud.talend.com' is invalid
Unable to start the Remote Engine Gen2Those commands are part of a package called bind-utils that may not be installed by default on the OS.
Symptom 2: cannot find region
The execution script also needs to find the region value corresponding to your Talend Cloud account, otherwise it will fail. The available regions are listed in the regions.txt file located in your Remote Engine Gen2 installation directory.
Solution for both symptoms: Intall bind-utils
Procedure
Alternative solution for symptom 2: Add region to regions.txt
Procedure
- Go to the Remote Engine Gen2 installation directory.
- Check if your region is listed, If not then add it to the file.
- Save your changes.
- Launch the execution script again.