nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

No job runner registered for job runner key 'com.atlassian.confluence.extra.team-calendars:reminderJ

Jiri Pik

how to fix this? I have updated today the Confluence Questions and it may have caused this

2018-02-26 18:07:33,849 ERROR [Caesium-1-4] [scheduler.caesium.impl.CaesiumSchedulerService] executeClusteredJobWithRecoveryGuard Unhandled exception during the attempt to execute job 'reminderTrigger'; will attempt recovery in 60 seconds
com.atlassian.scheduler.SchedulerRuntimeException: The parameters cannot be accessed: com.atlassian.scheduler.core.JobRunnerNotRegisteredException: No job runner registered for job runner key 'com.atlassian.confluence.extra.team-calendars:reminderJob'
 at com.atlassian.scheduler.core.status.UnusableJobDetails.getParameters(UnusableJobDetails.java:48)
 at com.atlassian.scheduler.core.status.LazyJobDetails.getParameters(LazyJobDetails.java:82)
 at com.atlassian.confluence.impl.schedule.caesium.ConfluenceSchedulerService.enqueueJob(ConfluenceSchedulerService.java:136)
 at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService.executeClusteredJob(CaesiumSchedulerService.java:437)
 at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService.executeClusteredJobWithRecoveryGuard(CaesiumSchedulerService.java:462)
 at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService.executeQueuedJob(CaesiumSchedulerService.java:390)
 at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService$1.consume(CaesiumSchedulerService.java:285)
 at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService$1.consume(CaesiumSchedulerService.java:282)
 at com.atlassian.scheduler.caesium.impl.SchedulerQueueWorker.executeJob(SchedulerQueueWorker.java:65)
 at com.atlassian.scheduler.caesium.impl.SchedulerQueueWorker.executeNextJob(SchedulerQueueWorker.java:59)
 at com.atlassian.scheduler.caesium.impl.SchedulerQueueWorker.run(SchedulerQueueWorker.java:34)
 at java.lang.Thread.run(Thread.java:748)
Caused by: com.atlassian.scheduler.core.JobRunnerNotRegisteredException: No job runner registered for job runner key 'com.atlassian.confluence.extra.team-calendars:reminderJob'
 at com.atlassian.scheduler.core.status.UnusableJobDetails.<init>(UnusableJobDetails.java:34)
 at com.atlassian.scheduler.core.status.LazyJobDetails$1.create(LazyJobDetails.java:74)
 at com.atlassian.scheduler.core.status.LazyJobDetails$1.create(LazyJobDetails.java:54)
 at com.atlassian.util.concurrent.LazyReference$Sync.run(LazyReference.java:325)
 at com.atlassian.util.concurrent.LazyReference.getInterruptibly(LazyReference.java:143)
 at com.atlassian.util.concurrent.LazyReference.get(LazyReference.java:112)
 at com.atlassian.scheduler.core.status.LazyJobDetails.getDelegate(LazyJobDetails.java:103)
 ... 11 more
2

Accepted answers

AnnWorley

In case the Questions update somehow corrupted the plugins cache, please clear it as described in How to clear Confluence plugins cache.

Another possible solution is more heavy handed, it's to truncate a related table in the Confluence database. Of course it is important to back up the database first. Please see: There are many errors "executeClusteredJobWithRecoveryGuard Unhandled exception" in atlassian-confluence.log after migrating from Cloud to Server.

All comments

AnnWorley

In case the Questions update somehow corrupted the plugins cache, please clear it as described in How to clear Confluence plugins cache.

Kavirajacholan Selvaraj

Hi,

We are also facing same issue but we migrate from data center to aws cloud. Below is the error message for your reference.

We need to migrate environment right away, since we already out of time. Could you please advise us with urgency.

ERROR [Caesium-1-2] [scheduler.caesium.impl.CaesiumSchedulerService] executeClusteredJobWithRecoveryGuard Unhandled exception during the attempt to execute job 'migration-plugin:analytics-events-consumer-job-id'; will attempt recovery in 60 seconds
com.atlassian.scheduler.SchedulerRuntimeException: The parameters cannot be accessed: com.atlassian.scheduler.core.JobRunnerNotRegisteredException: No job runner registered for job runner key 'migration-plugin:analytics-events-consumer-runner-key'

Thanks,
Kavi

James Brown_wkdbt3

Is it possible to diagnose which plugin is causing the issue through a threaddump?