Jira 8.5 failed to start - Unable to either create or replace clustered job

[moolahsense_admin]

Hi, 

I'm getting this error when i upgraded to JIRA 8.5.

I tried to resolve by following this but unable to https://community.atlassian.com/t5/Jira-Core-questions/JIRA-Startup-Failed-Unable-to-either-create-or-replace-clustered/qaq-p/686280

Any help would be useful

JIRA-Bootstrap ERROR [c.a.jira.upgrade.PluginSystemLauncher] A fatal error occured during initialisation. JIRA has been locked.
com.atlassian.jira.InfrastructureException: Error occurred while starting component 'com.atlassian.jira.web.action.issue.DefaultTemporaryWebAttachmentsMonitor'.
at com.atlassian.jira.component.pico.ComponentManager.startStartableComponents(ComponentManager.java:339)
at com.atlassian.jira.component.pico.ComponentManager.earlyStartPluginSystem(ComponentManager.java:252)
at com.atlassian.jira.upgrade.PluginSystemLauncher.start(PluginSystemLauncher.java:45)
at com.atlassian.jira.startup.DefaultJiraLauncher.lambda$postDbLaunch$2(DefaultJiraLauncher.java:145)
at com.atlassian.jira.config.database.DatabaseConfigurationManagerImpl.doNowOrEnqueue(DatabaseConfigurationManagerImpl.java:301)
at com.atlassian.jira.config.database.DatabaseConfigurationManagerImpl.doNowOrWhenDatabaseActivated(DatabaseConfigurationManagerImpl.java:196)
at com.atlassian.jira.startup.DefaultJiraLauncher.postDbLaunch(DefaultJiraLauncher.java:137)
at com.atlassian.jira.startup.DefaultJiraLauncher.lambda$start$0(DefaultJiraLauncher.java:104)
at com.atlassian.jira.util.devspeed.JiraDevSpeedTimer.run(JiraDevSpeedTimer.java:31)
at com.atlassian.jira.startup.DefaultJiraLauncher.start(DefaultJiraLauncher.java:102)
at com.atlassian.jira.startup.LauncherContextListener.initSlowStuff(LauncherContextListener.java:154)
at java.lang.Thread.run(Unknown Source)
Caused by: java.lang.RuntimeException: com.atlassian.scheduler.SchedulerServiceException: Unable to either create or replace clustered job: ImmutableClusteredJob[jobId=com.atlassian.jira.web.action.issue.DefaultTemporaryWebAttachmentsMonitor,jobRunnerKey=com.atlassian.jira.web.action.issue.DefaultTemporaryWebAttachmentsMonitor,schedule=Schedule[type=INTERVAL,intervalScheduleInfo=IntervalScheduleInfo[firstRunTime=Mon Dec 09 12:17:57 UTC 2019,intervalInMillis=3600000]],nextRunTime=Mon Dec 09 12:17:57 UTC 2019,version=1,rawParameters=(null)]
at com.atlassian.jira.web.action.issue.DefaultTemporaryWebAttachmentsMonitor.scheduleCleanup(DefaultTemporaryWebAttachmentsMonitor.java:75)
at com.atlassian.jira.web.action.issue.DefaultTemporaryWebAttachmentsMonitor.start(DefaultTemporaryWebAttachmentsMonitor.java:61)
at com.atlassian.jira.component.pico.ComponentManager.startStartableComponents(ComponentManager.java:335)
... 11 more
Caused by: com.atlassian.scheduler.SchedulerServiceException: Unable to either create or replace clustered job: ImmutableClusteredJob[jobId=com.atlassian.jira.web.action.issue.DefaultTemporaryWebAttachmentsMonitor,jobRunnerKey=com.atlassian.jira.web.action.issue.DefaultTemporaryWebAttachmentsMonitor,schedule=Schedule[type=INTERVAL,intervalScheduleInfo=IntervalScheduleInfo[firstRunTime=Mon Dec 09 12:17:57 UTC 2019,intervalInMillis=3600000]],nextRunTime=Mon Dec 09 12:17:57 UTC 2019,version=1,rawParameters=(null)]
at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService.scheduleClusteredJob(CaesiumSchedulerService.java:188)
at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService.scheduleJob(CaesiumSchedulerService.java:136)
at com.atlassian.scheduler.core.DelegatingSchedulerService.scheduleJob(DelegatingSchedulerService.java:62)
at com.atlassian.jira.web.action.issue.DefaultTemporaryWebAttachmentsMonitor.scheduleCleanup(DefaultTemporaryWebAttachmentsMonitor.java:73)
... 13 more
2019-12-09 11:17:59,028 JIRA-Bootstrap ERROR [c.a.jira.startup.DefaultJiraLauncher] JIRA has failed to start because of the following errors: [(Event: Level = (EventLevel: fatal) , Key = (EventType: startup-unexpected) , Desc = We couldn't start JIRA , Exception = An error occurred while trying to start JIRA. We can't give you any more detail right now, we suggest checking the logs for more detail and contacting our support team.<br/>See our documentation for more information on contacting our support team and creating a support zip.)]
2019-12-09 11:17:59,104 JIRA-Bootstrap INFO [c.a.jira.startup.LauncherContextListener] Memory Usage:
---------------------------------------------------------------------------------
Heap memory : Used: 398 MiB. Committed: 736 MiB. Max: 746 MiB
Non-heap memory : Used: 227 MiB. Committed: 250 MiB. Max: 1536 MiB
---------------------------------------------------------------------------------
TOTAL : Used: 625 MiB. Committed: 985 MiB. Max: 2282 MiB
---------------------------------------------------------------------------------

[Andy Heinzer]

Hi,

Sorry to hear that you are seeing this error.  It would appear that Jira is unable to either create a new or replace an existing entry in a table in the Jira database.

I would be interested to see if perhaps there are more than one entry in that table with this job_id.  Could you try to run the following SQL command to see what record(s) are returned?

select * from clusteredjob
where job_id='com.atlassian.jira.web.action.issue.DefaultTemporaryWebAttachmentsMonitor';

I'd also be interested to learn what database Jira is using on the backend (postgres, mysql, MS SQL, oracle, for examples) and what version of that database you are using.  At least one other using in the thread you linked found that the database setup was incorrect for their version, and another found that creating a new database and then importing their data there was a way to get past this problem.

Regards,

Andy