Qlik Talend Management Console logs do not show anything for the job, even though the job is finished.
Resolution
Potential Checklist
If the remote engine may be facing issues, please try restarting the remote engine and seeing if the Talend Management Console logs will appear after re-executing the task.
This may be due to high usage of memory, so check the statistics.csv file located in the following directory: <Talend Remote Engine Installation>/data/log
Check the following columns and compare the usage for both the usage in the remote engine and disk.
memory-used and memory-max
disk-used and disk-max
Ensure the <Remote Engine>/etc/org.ops4j.pax.logging.cfg file is not corrupted by comparing with a fresh Remote Engine container.
And inside the <Remote Engine>/etc/org.talend.ipaas.rt.logs.cfg, ensure this parameter is NOT set to:
active = false
Cause
The Remote Engine will be the one to handle sending the logs to Talend Management Console to show in the Talend Management Console logs. There may be problems with the remote engine that affected it to not handle the logs appropriately. For example, there may be a high usage of memory for the remote engine or in the environment where the remote engine is being used.
Related Content
For more information about how to prevent sending logs to Talend Management Console, please refer to