Jog failed and the execution log could not be found

[Tomas Valenta]

Hello,

we are using Rundeck 5.4.0 and every day are failing several different jobs after 1s execution and detail is showing message: The Execution Log could not be found. No output. Not all jobs on this Rundeck have this problem and the next several run of failed jobs are running OK. All jobs are scheduled and they are invoking Powershell script written inline in Rundeck on the Windows node. Do you anybody have the same issue, please?

Regards

Tomas

[James F.]

I cannot speak to why your executions are failing, but consider Rundeck 5.5.0. The developers recently announced bug fixes to missing execution history in 5.4.0

[rac...@rundeck.com]

Aditionally, test your script directly (running the .ps1 file in a test environment) to discard any script-related issues. Probably you're facing this.

[Tomas Valenta]

Thank you for your information. I will ask for the upgrade. When the job is failing there is no remote connection on the node

from the Rundeck server and next job execution is running OK, so I do not suppose the problem could be in the Powershell script.

Dne pondělí 19. srpna 2024 v 15:21:21 UTC+2 uživatel James F. napsal:

[James F.]

The error sounds like the credentials - or node tags - may be wrong? What is your default node executor? Is that the node executor set for all of your projects? What is your node source? What hard-coded properties are you defining in your inventory file / group_vars (ansible)?