[Building Sakai] anybody know how to clear a stuck quartz job? [EVALSYS]

[Maurer, Christopher Wayne]

If it's something big that we know about ahead of time, we just remove the
triggers so the jobs no longer run and then re-add them when the
maintenance is complete.

Chris


On 6/28/12 12:36 PM, "Shawn Foster" <sfoster9 at uwo.ca> wrote:

>Hi,
>
>We realized yesterday that our TurnItIn sync and Sakora jobs (two jobs
>total) were interrupted during recent system maintenance. Their "Next
>Run" dates and times were set to the next date and time following the
>failed run, which is now in the past. These jobs were interrupted but
>would never finish.
>
>So we decided to delete the two jobs that were stuck in "EXECUTING" from
>the "QRTZ_FIRED_TRIGGERS" table. That didn't set the jobs' status from
>"BLOCKED" back to "WAITING" in the "QRTZ_TRIGGERS" table, so I manually
>ran the jobs through Job Scheduler. Once the jobs had finished, the
>"QRTZ_TRIGGERS" table status for the jobs had returned to "WAITING" and
>the "Next Run" date had been reset to the next proper run date and time.
>No server or database restart required.
>
>Thanks for the suggestions. I hope this will help others.
>
>Is there a way to pause jobs when we know that system maintenance will
>interrupt a job from completing?
>
>-Shawn
>
>-- 
>Shawn Foster
>Instructional Technology Support and Application Development
>Western University
>
>On 12-06-18 1:48 PM, Paul Dagnall wrote:
>> Sorry...must have hit a hot key to send. Wasn't done yet.
>>
>> Similar to what Chris posted, changing the state to WAITING might
>>possibly
>> "wake" it up. Deleting it and letting it get scheduled again should work
>> but I'd be a little worried about things suddenly getting unstuck and
>> sending two emails.
>>
>>
>> On Mon, Jun 18, 2012 at 1:46 PM, Paul Dagnall <pdagnall1 at udayton.edu>
>>wrote:
>>
>>> Similar to what Chris posted, changing the state to WAITING
>>>
>>>
>>>
>>> On Mon, Jun 18, 2012 at 1:41 PM, Charles Hedrick
>>><hedrick at rutgers.edu>wrote:
>>>
>>>> executing
>>>>
>>>> On Jun 18, 2012, at 1:39 PM, Paul Dagnall <pdagnall1 at udayton.edu>
>>>>wrote:
>>>>
>>>> For stuck Turn-It-In issues, I have just deleted the record from
>>>> QRTZ_FIRED_TRIGGERS, but in that case I wasn't as concerned with
>>>>duplicity
>>>> if that didn't really kill it. What is in the STATE column in the
>>>>offending
>>>> record?
>>>>
>>>> Paul Dagnall
>>>> Application Developer & Administrator
>>>> University of Dayton
>>>>
>>>>
>>>> On Mon, Jun 18, 2012 at 1:27 PM, Maurer, Christopher Wayne <
>>>> chmaurer at iupui.edu> wrote:
>>>>
>>>>> This doesn't really help with your immediate problem, but I'll
>>>>>probably
>>>>> try to get this applied in trunk sometime soon.
>>>>> https://jira.sakaiproject.org/browse/SAK-21425 (Need a way to see
>>>>> running
>>>>> jobs and have ability to kill them.)
>>>>>
>>>>> Chris
>>>>>
>>>>> On 6/18/12 1:23 PM, "Bryan Holladay" <holladay at longsight.com> wrote:
>>>>>
>>>>>> I will defer this to someone else on the list then since I haven't
>>>>>> done this w/o restarting (or even know if it's possible).
>>>>>>
>>>>>> -Bryan
>>>>>>
>>>>>> On Mon, Jun 18, 2012 at 1:21 PM, Charles Hedrick
>>>>>><hedrick at rutgers.edu>
>>>>>> wrote:
>>>>>>> yes. restarting would be really hard at the moment.
>>>>>>>
>>>>>>> On Jun 18, 2012, at 1:19 PM, Bryan Holladay
>>>>>>><holladay at longsight.com>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> I thought it requires clearing the fired triggers and any other
>>>>>>>> references in the DB to that running job, then restarting.  Are
>>>>>>>>you
>>>>>>>> trying to do this w/o restarting?
>>>>>>>>
>>>>>>>> On Mon, Jun 18, 2012 at 12:59 PM, Charles Hedrick
>>>>>>>> <hedrick at rutgers.edu> wrote:
>>>>>>>>> We're not getting emails sent by EVALSYS. I believe the problem
>>>>>>>>>is
>>>>>>>>> that Quartz is stuck. QRTZ_FIRED_TRIGGERS shows
>>>>>
>>>>>>>>> 
>>>>>>>>>org.sakaiproject.component.app.scheduler.ScheduledInvocationManage
>>>>>>>>>rImpl
>>>>>>>>> .runner executing, with the fired time not changing. Is there a
>>>>>>>>>way
>>>>> to
>>>>>>>>> clear this? Can I just clear the fired triggers table, or do we
>>>>>>>>>need
>>>>>>>>> something more?
>>>>>>>>>
>>>>>>>>> _______________________________________________
>>>>>>>>> sakai-dev mailing list
>>>>>>>>> sakai-dev at collab.sakaiproject.org
>>>>>>>>> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>>>>>>>>>
>>>>>>>>> TO UNSUBSCRIBE: send email to
>>>>>>>>> sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of
>>>>>>>>> "unsubscribe"
>>>>>>>
>>>>>> _______________________________________________
>>>>>> sakai-dev mailing list
>>>>>> sakai-dev at collab.sakaiproject.org
>>>>>> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>>>>>>
>>>>>> TO UNSUBSCRIBE: send email to
>>>>>> sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of
>>>>>> "unsubscribe"
>>>>>
>>>>> _______________________________________________
>>>>> sakai-dev mailing list
>>>>> sakai-dev at collab.sakaiproject.org
>>>>> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>>>>>
>>>>> TO UNSUBSCRIBE: send email to
>>>>> sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of
>>>>> "unsubscribe"
>>>>>
>>>>
>>>>
>>>>
>>>
>>
>>
>>
>> _______________________________________________
>> sakai-dev mailing list
>> sakai-dev at collab.sakaiproject.org
>> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>>
>> TO UNSUBSCRIBE: send email to
>>sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of
>>"unsubscribe"
>>
>
>_______________________________________________
>sakai-dev mailing list
>sakai-dev at collab.sakaiproject.org
>http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>
>TO UNSUBSCRIBE: send email to
>sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of
>"unsubscribe"