Redwood Job stuck running every 20 seconds
We have a job in our production redwood box running every 20 seconds. We cannot kill, or cancel it. Every 20 seconds it restarts and creates a new jobid. It leads to an out of memory error, eventually redwood crashes again. We would like to delete this job in its entirety, but cannot..
Does anyone know how to get this job to stop running in its loop long enough to delete it entirely? We can't even determine the origins of this job.
I have read that some have used a submit System_ForceJobStatusUnknown using script, but I am not good with scripting. Would anyone out there be able to help me set up a script and correct parameters that would give us the new job id, and set status to unknown for each new id created ? Maybe that would enable us to delete it ? I'm just spinning my wheels here, cause we are out of idea's