job scheduler stuck - help!
1,184 views
Skip to first unread message
Adam Marshall
Aug 30, 2016, 10:44:19 AM8/30/16
to saka...@apereo.org
Our job scheduler is showing every job is failing.
We see ERROR: "Trigger Misfired" in every row of the Event Log since the middle of last week. Any idea what we can do to kick it into working again?
It's only on a staging server so we can afford to do naughty things to the DB if necessary.
adam
We see ERROR: "Trigger Misfired" in every row of the Event Log since the middle of last week. Any idea what we can do to kick it into working again?
It's only on a staging server so we can afford to do naughty things to the DB if necessary.
adam
Brian Jones
Aug 30, 2016, 11:37:59 AM8/30/16
to Adam Marshall, saka...@apereo.org
We sometimes have 'stuck' quartz jobs. This is the process we use to
'unstuck' them:
1) Check the QRTZ_FIRED_TRIGGERS table to determine the cause
2) Remove the row(s) via SQL
3) After the row(s) is/are deleted, record the CRON expression for the
job's trigger
4) Delete and recreate the trigger
5) Check the next fired time and verify that it does get fired
Hope this helps!
Brian Jones
Programmer/Analyst
Information Technology Services
Support Services Building, Suite 4300
Western University
(519) 661-2111 x86969
bjon...@uwo.ca
'unstuck' them:
1) Check the QRTZ_FIRED_TRIGGERS table to determine the cause
2) Remove the row(s) via SQL
3) After the row(s) is/are deleted, record the CRON expression for the
job's trigger
4) Delete and recreate the trigger
5) Check the next fired time and verify that it does get fired
Hope this helps!
Brian Jones
Programmer/Analyst
Information Technology Services
Support Services Building, Suite 4300
Western University
(519) 661-2111 x86969
bjon...@uwo.ca
Brian Jones
Aug 30, 2016, 11:39:29 AM8/30/16
to Adam Marshall, saka...@apereo.org
Also FYI: the column STATE in table QRTZ_TRIGGERS will show the value
'BLOCKED' for any jobs that are currently executing. This could be a
false positive if the job was interrupted and it never reverted to the
completion state.
Brian Jones
Programmer/Analyst
Information Technology Services
Support Services Building, Suite 4300
Western University
(519) 661-2111 x86969
bjon...@uwo.ca
'BLOCKED' for any jobs that are currently executing. This could be a
false positive if the job was interrupted and it never reverted to the
completion state.
Brian Jones
Programmer/Analyst
Information Technology Services
Support Services Building, Suite 4300
Western University
(519) 661-2111 x86969
bjon...@uwo.ca
Adam Marshall
Aug 30, 2016, 11:56:11 AM8/30/16
to Brian Jones, saka...@apereo.org
Thanks Brian. FYI it is every single job that is stuck and reporting an ERROR.
adam
adam
Adam Marshall
Sep 1, 2016, 10:47:55 AM9/1/16
to Brian Jones, saka...@apereo.org
Our QRTZ_FIRED_TRIGGERS table is empty. Any more ideas?
adam
-----Original Message-----
From: Brian Jones [mailto:bjon...@uwo.ca]
Sent: 30 August 2016 16:38
To: Adam Marshall <adam.m...@it.ox.ac.uk>; saka...@apereo.org
Subject: Re: [sakai-dev] job scheduler stuck - help!
adam
-----Original Message-----
From: Brian Jones [mailto:bjon...@uwo.ca]
Sent: 30 August 2016 16:38
To: Adam Marshall <adam.m...@it.ox.ac.uk>; saka...@apereo.org
Subject: Re: [sakai-dev] job scheduler stuck - help!
Jaco Gillman
Dec 13, 2017, 9:18:12 AM12/13/17
to Adam Marshall, Brian Jones, saka...@apereo.org
Hi Adam
We experience this issue in a Sakai 11.4 installation... all the scheduled jobs misfires.. Did you perhaps find an answer or solution for this?
--
You received this message because you are subscribed to the Google Groups "Sakai Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sakai-dev+unsubscribe@apereo.org.
To post to this group, send email to saka...@apereo.org.
Visit this group at https://groups.google.com/a/apereo.org/group/sakai-dev/.
Reply all
Reply to author
Forward
0 new messages