semaphore icon indicating copy to clipboard operation
semaphore copied to clipboard

Console is stuck in "Running" state

Open ocafebabe opened this issue 3 years ago • 6 comments

I'm experiencing an issue with Semaphore where the console is stuck in "Running" state indefinitely even though the playbook has failed (exit code 1): Screenshot from 2022-02-22 13-05-06

This is happening only when the playbook is generating a lot of output (+1000 lines) on an error and it seems to be similar to this issue: #642

For reference, I'm using the latest released version: 2.8.53 and it's a major show stopper for us.

ocafebabe avatar Feb 22 '22 18:02 ocafebabe

I did another test with the same playbook to reproduce the same behaviour and I discovered something interesting, while the console is still showing a "Running" state, the task is correctly shown with a "Failed" status under _Task Templates: Screenshot from 2022-02-22 13-41-50

ocafebabe avatar Feb 22 '22 20:02 ocafebabe

Thank you, I will try to reproduce the issue.

fiftin avatar Mar 06 '22 07:03 fiftin

Thanks a lot and please let me know if you need additional details or testing from my part.

ocafebabe avatar Mar 07 '22 15:03 ocafebabe

My issue is not 100% the same but the browser hangs up especially when checking "Debug" checkbox and/or using -vvv / -vvvv as arg. This is not an issue when not using Debug or not using -vvv args. it just happens when a LOT of output is coming in. when I am able to stop the task (it keeps running forever here) it stays in "stopping" state forever, blocking any other tasks ofc (no parallel runs allowed)..

steadfasterX avatar Aug 19 '22 11:08 steadfasterX

I got the same error. Ansible semaphore version 2.9.37. It happens only in debug mode and when output is really long. Bez tytułu

However, in task history it is showed as ended image

piotrszczypta-a4bee avatar Oct 26 '23 13:10 piotrszczypta-a4bee