When scheduling a pipeline task on the Remote Engine Gen2 in Talend Cloud Management Console, you might not see the corresponding logs.
The logs might not have been enabled.
Run the following command to stop the Remote Engine Gen2:
remote-engine.bat stopif you are on a Windows system
./remote-engine.sh stopif you are on a Unix system
Open the following file to edit it:
<engine_directory>/default/.env if you are using the engine in the AWS USA, AWS Europe, AWS Asia-Pacific or Azure regions.
<engine_directory>/eap/.env if you are using the engine as part of the Early Adopter Program.
- Set the LIVY_JOB_LOG_PERSISTENCE_ENABLE parameter to true.
- Save your changes and restart the Remote Engine Gen2.