We are on Tidal Version 6.2.1.54 and Tidal is installed on Windows and our agent server is on Linux. We have set up default runtime job limit to 50.
Issue is that whenever the job reaches this 50 limit, instead of having a status of waiting on resource, job simply errors out with status as Error Occured, and this happens adhoc. Tried to increase the ulimit for the user id on our application server from 1024 to 4096 and also haven't seen any application server CPU being heavily utilized during this error time. Application server logs doesn't show any error, where as Tidal side we see the job status as Error Occured with message as : Launcher Error: setuid error: Resource Temporarily unavailable.
Any ideas on what could have been causing this issue?
