java.io.IOException: Failed to deploy job

[Stephen_Elves1]

Hi,

Trying to run a task on TMC (Remote Engine not Cloud), and I get the above error:

1. it works in the studio
2. Previous versions of the job still work in other workspaces.
3. I've tried uploading new versions they still don't work.
4. What is in the subject line (without the id) is all that is in the logs, normal run, debug run, setting logging to INFO, that's it.

[Stephen_Elves1]

Further update tried directing the task at the artefact from a different workspace: worked fine, but this isn't a proper fix, why does it not work with the new artefact? What does the error message actually mean? Why is the error logging so atrocious?

[Stephen_Elves1]

Another update tried publishing from a different studio, running on a different operating system, in another timezone. Getting the same Failed to deploy job error.

[Stephen_Elves1]

Yet another update: published a different artefact for another task, works perfectly, so clearly it's an issue with one job but without some better error messages from TMC it's impossible to tell what unless anyone else has had and fixed the same issue?

[Anonymous]

Hello,

As your job works well in studio, what does your job design look like?

Did you use any trunjob component in your work flow? If so, please make sure you did tick on "Transmit whole context" option in tRunJob component which could solve the problem and that needs to be done on every child tRunJob component.

Best regards

Sabrina

[Stephen_Elves1]

Unfortunately, Talend's slightly jank forum software doesn't seem to want to let me upload the screenshots of the job because of course it doesn't.

All tRunJobs have "Transmit whole context" ticked.

[Stephen_Elves1]

Clicking "Upload image" in the select Image dialogue does nothing.

[Stephen_Elves1]

Found a workaround.

[Anonymous]

Hello,

What is the Java vendor / Java version used to "run" the Remote Engine?

Is the Engine up and running and showing paired on your end? Could you please try to restart it to see if this issue disappear?

You are able to collect the context information about the Remote Engine issue.

https://help.talend.com/r/en-US/Cloud/use-re-script-for-troubleshooting/use-context-script-for-re-is...

Collecting context information about a Remote Engine issue

It is a good way that using a Remote Engine specific script, talend-re-helper.sh or talend-re-helper.bat, to collect context information about the issues you encountered.

Best regards

Sabrina

[Stephen_Elves1]

>What is the Java vendor / Java version used to "run" the Remote Engine?

2023-05-04 16:39:09:061

* --> java.vm.name : OpenJDK 64-Bit Server VM

Warning

2023-05-04 16:39:09:061

* --> java.vendor.version : Corretto-11.0.11.9.

>Is the Engine up and running and showing paired on your end? Could you please try to restart it to see if this issue disappear?

It is running and paired, it is running jobs from this and other workspaces and almost constantly.

I don't have the access to the remote engine to restart it.

>You are able to collect the context information about the Remote Engine issue.

It doesn't even try and run the job so there is no way to collect any context information for this job.