Sakai 22 job scheduler trigger error with site stats aggregator

60 views
Skip to first unread message

Austin

unread,
Nov 20, 2023, 3:50:23 PM11/20/23
to sakai-dev
Hello Sakai Devs,

I'm testing a conversion from Sakai 21 to Sakai 22, but I'm seeing the error below.  We are using a separate server and database to process sitestats, but I suspect this error has something to do with the job(s) in qrtz_job_details and/or qrtz_cron_triggers.  Has anyone seen something like this Sakai 22?  Also, in the Admin -> Job Scheduler, I can see 4 out of the jobs that should be there, but the one that's missing 'SiteStats Event Aggregator' is the one that errored below.

Is our data corrupted?  Or was there a change in Sakai 22 with the site stats aggregator job/trigger?

Thanks,

Austin



20-Nov-2023 10:19:30.197 INFO [QuartzScheduler] o.s.c.a.s.SchedulerManagerImpl.lambda$startScheduler$0 Scheduler starting now, after delay of 5 minutes
20-Nov-2023 10:19:30.198 INFO [QuartzScheduler] o.s.c.a.s.SchedulerManagerImpl.cleanUpJobs Checking for existing jobs that need to be cleaned up
20-Nov-2023 10:19:30.218 INFO [QuartzScheduler] o.s.c.a.s.SchedulerManagerImpl.cleanUpJobs Job check completed, 4 jobs found.
Exception in thread "QuartzScheduler" java.lang.RuntimeException: Job Scheduler could not start after delay
at org.sakaiproject.component.app.scheduler.SchedulerManagerImpl.lambda$startScheduler$0(SchedulerManagerImpl.java:679)
at java.base/java.lang.Thread.run(Thread.java:834)
Caused by: org.quartz.SchedulerConfigException: Failure occured during job recovery. [See nested exception: org.quartz.JobPersistenceException: Couldn't store trigger 'DEFAULT.SiteStats Event Aggregator Trigger' for 'DEFAULT.SiteStats Event Aggregator' job:The job (DEFAULT.SiteStats Event Aggregator) referenced by the trigger does not exist. [See nested exception: org.quartz.JobPersistenceException: The job (DEFAULT.SiteStats Event Aggregator) referenced by the trigger does not exist.]]
at org.quartz.impl.jdbcjobstore.JobStoreSupport.schedulerStarted(JobStoreSupport.java:697)
at org.quartz.core.QuartzScheduler.start(QuartzScheduler.java:539)
at org.quartz.impl.StdScheduler.start(StdScheduler.java:142)
at org.sakaiproject.component.app.scheduler.SchedulerManagerImpl.lambda$startScheduler$0(SchedulerManagerImpl.java:677)
... 1 more
Caused by: org.quartz.JobPersistenceException: Couldn't store trigger 'DEFAULT.SiteStats Event Aggregator Trigger' for 'DEFAULT.SiteStats Event Aggregator' job:The job (DEFAULT.SiteStats Event Aggregator) referenced by the trigger does not exist. [See nested exception: org.quartz.JobPersistenceException: The job (DEFAULT.SiteStats Event Aggregator) referenced by the trigger does not exist.]
at org.quartz.impl.jdbcjobstore.JobStoreSupport.storeTrigger(JobStoreSupport.java:1228)
at org.quartz.impl.jdbcjobstore.JobStoreSupport.doUpdateOfMisfiredTrigger(JobStoreSupport.java:1042)
at org.quartz.impl.jdbcjobstore.JobStoreSupport.recoverMisfiredJobs(JobStoreSupport.java:991)
at org.quartz.impl.jdbcjobstore.JobStoreSupporshow .recoverJobs(JobStoreSupport.java:871)
at org.quartz.impl.jdbcjobstore.JobStoreSupport$1.executeVoid(JobStoreSupport.java:843)
at org.quartz.impl.jdbcjobstore.JobStoreSupport$VoidTransactionCallback.execute(JobStoreSupport.java:3780)
at org.quartz.impl.jdbcjobstore.JobStoreSupport$VoidTransactionCallback.execute(JobStoreSupport.java:3778)
at org.quartz.impl.jdbcjobstore.JobStoreSupport.executeInNonManagedTXLock(JobStoreSupport.java:3864)
at org.quartz.impl.jdbcjobstore.JobStoreSupport.recoverJobs(JobStoreSupport.java:839)
at org.quartz.impl.jdbcjobstore.JobStoreSupport.schedulerStarted(JobStoreSupport.java:695)
... 4 more
Caused by: org.quartz.JobPersistenceException: The job (DEFAULT.SiteStats Event Aggregator) referenced by the trigger does not exist.
at org.quartz.impl.jdbcjobstore.JobStoreSupport.storeTrigger(JobStoreSupport.java:1213)
... 13 more

Earle Nietzel

unread,
Nov 21, 2023, 3:40:36 PM11/21/23
to Austin, sakai-dev
Austin,

That error is about a job in recovery that didn't complete and the trigger is now missing for some reason.

Whenever I see these types of issues I simply clean/remove the job and any associated triggers and then restart and recreate them in the ui.

This issue may not be related to the upgrade,

-earle


--
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+...@apereo.org.
To view this discussion on the web visit https://groups.google.com/a/apereo.org/d/msgid/sakai-dev/CAKL84%3DkWf8tw5TWyn_37Lf-9towf7oDZm1%2B0HDei%3DQBnYHp51A%40mail.gmail.com.
Reply all
Reply to author
Forward
0 new messages