Depending on how/where you installed the Remote Engine Gen2, the procedure to restart it might differ slightly.
on Unix systems
on Windows systems
The Remote Engine Gen2 Docker containers are configured to automatically restart when they were not properly stopped in the first place and the Docker daemon starts again. This case occurs especially when the engine is installed on an virtual machine (like an EC2 machine) and the VM is shut down and restarted again.
In this situation Docker containers will be restarted automatically but this might not bring services up correctly, preventing the engine from reconnecting to Talend Cloud.
- Make sure the remote-engine.sh|bat file is configured as a
service of the Operating System so that the
remote-engine.sh|bat stopcommand is executed when the Operating System is shutting down and
./remote-engine.sh start -r <region> -k <pair_key>(Unix) or
remote-engine.bat start -r <region> -k <pair_key>(Windows) is executed when the Operating System is starting.