Solved: RME 4, How to purge jobs in "Stop Initiated" state?

Jason Fraioli · ‎08-17-2010

I had a couple of jobs that are in "Stop Initiated" state, but they never actually stop. If I try to delete the job, I'll get: RMEJOB0004: Could not delete following jobs: 1634 This is because these jobs may be running.

Can anyone shed some light on how to purge these jobs out of RME?

Joe Clarke · ‎08-17-2010

Try starting the job's daemon with the pdexec command to see if that kick starts it into cycling out of the system. If not, then manually unregister it with:

pdreg -u 1608

Then see if you can delete it.

View solution in original post

Joe Clarke · ‎08-17-2010

Check the output of pdshow to see if there is a daemon running for the job ID. If so, run pdterm on that job ID to kill it. Then see if the job stops in the GUI.

Jason Fraioli · ‎08-17-2010

Process= 1608
State = Administrator has shut down this server
Pid    = 0
RC     = 0
Signo = 0
Start = N/A
Stop   = Not applicable
Core   = Not applicable
Info   = Not applicable

The job remains in "Stop Initiated" state in the GUI. If I try to delete it, I'll get:

RMEJOB0004: Could not delete following jobs: 1608
This is because these jobs may be running.

The hung netconfig job gives this error:

CFG0012: Failed while deleting job(s)
Possible Cause: Could not delete job in JRM:1634

Joe Clarke · ‎08-17-2010

Try starting the job's daemon with the pdexec command to see if that kick starts it into cycling out of the system. If not, then manually unregister it with:

pdreg -u 1608

Then see if you can delete it.