Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
See why IDC MarketScape names Qlik a 2025 Leader! Read more
cancel
Showing results for 
Search instead for 
Did you mean: 
sushantk19
Creator
Creator

Talend job failed to trigger

Hello All,

I am facing a strange issue. One of my talend job fails to trigger from TMC and it gives the below error:

Remote server has encountered an error:

, messageType=SERVER_ERROR, idRequestResponsePair=null, message=java.io.FileNotFoundException: /opt/talend/ipaas/remote-engine-client/./TalendJobServersFiles/repository/XXXX_job_000_DW_Adtriba_Load_f04666fe14c72d6977133/job_000_DW_Adtriba_Load/

job_000_DW_Adtriba_Load_run.sh (No such file or directory).

The strange thing is that this job doesnt refer/use any source file at all. This issue might happen say once in 15 days.When i run the same job through talend studio 7.3, it works fine. but it fails to trigger from TMC every now and then. Anyone faced this issue before? any suggestions.

Labels (2)
8 Replies
Anonymous
Not applicable

This is the job executable file, not source file, go to check if the file do still exist, and check the owner of remote-engine if it has permission to run this file.

 

Regards

Shong

 

 

sushantk19
Creator
Creator
Author

@shong: I checked with my IT team. The executable file still exists on remote engine. Also, it has the same permissions to run like the other jobs which are running fine so far. Please find the screenshot attached.

Any other reasons why this could be happening?

Anonymous
Not applicable

From your screenshot, it seems there is no execute permission to the file?

sushantk19
Creator
Creator
Author

yes. even i thought so. But the job is running fine for 15 days. On 16th day, it fails to trigger with the above error. any idea why this could be happening and how to resolve this?

Anonymous
Not applicable

@Sushant Kapoor​ , I have no idea why this happens, check other tasks whether they have the same issue. Add execute permission to the file to see whether it can be triggered to run again, or redeploy the task.

 

Regards

Shong

sushantk19
Creator
Creator
Author

@Shicong Hong​ : yes, all the tasks have the same issue. they seem to run fine for 15 days. on 16th day, they would fail with the above issue. so we are redploying all our tasks before 16th day. but i guess this is not the root cause, its a temporary fix.

Anonymous
Not applicable

so keep monitoring the job execution, if the problem occurs again, it is better to open a ticket to our Support team, our colleague will check the execution environment and logs with you together.

 

 

sushantk19
Creator
Creator
Author

@shong: now the jobs are failing even before 15 days with same error. This issue seems to be really wierd.