JIRA Startup Failed - Unable to either create or replace clustered job

[Lukasz Zalewski]

Hi,

I have run JIRA using docker image ahaasler/jira:7.3.5 together with PostgresDB.
After crash of one machnie I have problem with JIRA Startup.

on WebGUI i received

Error occurred while starting component 'com.atlassian.jira.web.action.issue.DefaultTemporaryWebAttachmentsMonitor'. 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=Fri Dec 08 22:49:34 GMT 2017,intervalInMillis=3600000]],nextRunTime=Fri Dec 08 22:49:34 GMT 2017,version=1,rawParameters=(null)] 

in atlassian-jira.log

    ___ FAILED PLUGIN REPORT _____________________

    1 plugin failed to load during JIRA startup.

        'com.atlassian.plugins.authentication.atlassian-authentication-plugin' - 'SAML for Atlassian Data Center'  failed to load.
                Error creating bean with name 'statisticsCollectionService': Invocation of init method failed; nested exception is com.atlassian.scheduler.SchedulerServiceException: Unable to either create or replace clustered job: ImmutableClusteredJob[jobId=analytics-collection,jobRunnerKey=com.atlassian.plugins.authentication.impl.analytics.StatisticsCollectionService,schedule=Schedule[type=CRON_EXPRESSION,cronScheduleInfo=CronScheduleInfo[cronExpression='0 0 23 * * ?',timeZone=null]],nextRunTime=Fri Dec 08 23:00:00 GMT 2017,version=1,rawParameters=(null)]
                        Unable to either create or replace clustered job: ImmutableClusteredJob[jobId=analytics-collection,jobRunnerKey=com.atlassian.plugins.authentication.impl.analytics.StatisticsCollectionService,schedule=Schedule[type=CRON_EXPRESSION,cronScheduleInfo=CronScheduleInfo[cronExpression='0 0 23 * * ?',timeZone=null]],nextRunTime=Fri Dec 08 23:00:00 GMT 2017,version=1,rawParameters=(null)]

                It was loaded from /opt/jira/atlassian-jira/WEB-INF/atlassian-bundled-plugins/atlassian-authentication-plugin-2.0.3.jar

    ********************************************************************************************************************************************************************************************************

 Even I disabled atlassian-authentication-plugin by sql on SB

INSERT into pluginstate (pluginkey, pluginenabled) VALUES ('com.atlassian.plugins.authentication.atlassian-authentication-plugin','false');

I got:

    ___ Plugin System Started _________________

2017-12-08 22:17:23,107 JIRA-Bootstrap ERROR      [c.a.jira.upgrade.UpgradeLauncher] Skipping, JIRA is locked.
2017-12-08 22:17:23,107 JIRA-Bootstrap INFO      [c.a.jira.scheduler.JiraSchedulerLauncher] JIRA Scheduler not started: JIRA startup checklist failed.
2017-12-08 22:17:23,188 JIRA-Bootstrap ERROR      [c.a.jira.startup.AnalyticsLauncher] Start analytics not scheduled
com.atlassian.scheduler.SchedulerServiceException: Unable to either create or replace clustered job: ImmutableClusteredJob[jobId=c3cb8b50-4fb3-4f7b-a2a1-9928cb5e9198,jobRunnerKey=com.atlassian.jira.startup.AnalyticsLauncher.Start,schedule=Schedule[type=INTERVAL,intervalScheduleInfo=IntervalScheduleInfo[firstRunTime=Fri Dec 08 22:20:23 GMT 2017,intervalInMillis=0]],nextRunTime=Fri Dec 08 22:20:23 GMT 2017,version=1,rawParameters=(null)]
        at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService.createOrReplaceWithRetry(CaesiumSchedulerService.java:202)
        at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService.scheduleClusteredJob(CaesiumSchedulerService.java:189)
        at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService.scheduleJob(CaesiumSchedulerService.java:137)
        at com.atlassian.scheduler.core.AbstractSchedulerService.scheduleJobWithGeneratedId(AbstractSchedulerService.java:114)
        at com.atlassian.scheduler.core.DelegatingSchedulerService.scheduleJobWithGeneratedId(DelegatingSchedulerService.java:77)
        at com.atlassian.jira.startup.AnalyticsLauncher.runStartAnalyticsJob(AnalyticsLauncher.java:72)
        at com.atlassian.jira.startup.AnalyticsLauncher.start(AnalyticsLauncher.java:40)
        at com.atlassian.jira.startup.ActiveServicesLauncher.start(ActiveServicesLauncher.java:56)
        at com.atlassian.jira.startup.DefaultJiraLauncher.lambda$postTenantArrived$4(DefaultJiraLauncher.java:184)
        at com.atlassian.jira.startup.DefaultInstantUpgradeManager$StartupTask.run(DefaultInstantUpgradeManager.java:139)
        at com.atlassian.jira.startup.DefaultInstantUpgradeManager.runTask(DefaultInstantUpgradeManager.java:55)
        at com.atlassian.jira.startup.DefaultInstantUpgradeManager.doNowOrWhenInstanceBecomesActive(DefaultInstantUpgradeManager.java:42)
        at com.atlassian.jira.startup.DefaultJiraLauncher.postTenantArrived(DefaultJiraLauncher.java:177)
        at com.atlassian.jira.startup.DefaultJiraLauncher.lambda$postDBActivated$3(DefaultJiraLauncher.java:165)
        at com.atlassian.jira.tenancy.DefaultTenantManager.doNowOrWhenTenantArrives(DefaultTenantManager.java:55)
        at com.atlassian.jira.startup.DefaultJiraLauncher.postDBActivated(DefaultJiraLauncher.java:162)
        at com.atlassian.jira.startup.DefaultJiraLauncher.lambda$postDbLaunch$2(DefaultJiraLauncher.java:151)
        at com.atlassian.jira.config.database.DatabaseConfigurationManagerImpl.doNowOrEnqueue(DatabaseConfigurationManagerImpl.java:298)
        at com.atlassian.jira.config.database.DatabaseConfigurationManagerImpl.doNowOrWhenDatabaseActivated(DatabaseConfigurationManagerImpl.java:194)
        at com.atlassian.jira.startup.DefaultJiraLauncher.postDbLaunch(DefaultJiraLauncher.java:141)
        at com.atlassian.jira.startup.DefaultJiraLauncher.lambda$start$0(DefaultJiraLauncher.java:103)
        at com.atlassian.jira.util.devspeed.JiraDevSpeedTimer.run(JiraDevSpeedTimer.java:31)
        at com.atlassian.jira.startup.DefaultJiraLauncher.start(DefaultJiraLauncher.java:101)
        at com.atlassian.jira.startup.LauncherContextListener.initSlowStuff(LauncherContextListener.java:149)
        at java.lang.Thread.run(Thread.java:745)
2017-12-08 22:17:23,256 JIRA-Bootstrap ERROR      [c.a.jira.startup.IndexRecoveryLauncher] Index recovery not scheduled
com.atlassian.scheduler.SchedulerServiceException: Unable to either create or replace clustered job: ImmutableClusteredJob[jobId=fe6042ca-eadc-4b92-804d-a945d3e45b4f,jobRunnerKey=com.atlassian.jira.DefaultJiraLauncher.IndexRecovery,schedule=Schedule[type=INTERVAL,intervalScheduleInfo=IntervalScheduleInfo[firstRunTime=Fri Dec 08 22:17:23 GMT 2017,intervalInMillis=0]],nextRunTime=Fri Dec 08 22:17:23 GMT 2017,version=1,rawParameters=(null)]
        at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService.createOrReplaceWithRetry(CaesiumSchedulerService.java:202)
        at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService.scheduleClusteredJob(CaesiumSchedulerService.java:189)
        at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService.scheduleJob(CaesiumSchedulerService.java:137)
        at com.atlassian.scheduler.core.AbstractSchedulerService.scheduleJobWithGeneratedId(AbstractSchedulerService.java:114)
        at com.atlassian.scheduler.core.DelegatingSchedulerService.scheduleJobWithGeneratedId(DelegatingSchedulerService.java:77)
        at com.atlassian.jira.startup.IndexRecoveryLauncher.runIndexRecoveryJob(IndexRecoveryLauncher.java:102)
        at com.atlassian.jira.startup.IndexRecoveryLauncher.start(IndexRecoveryLauncher.java:49)
        at com.atlassian.jira.startup.DefaultJiraLauncher.lambda$postTenantArrived$4(DefaultJiraLauncher.java:187)
        at com.atlassian.jira.startup.DefaultInstantUpgradeManager$StartupTask.run(DefaultInstantUpgradeManager.java:139)
        at com.atlassian.jira.startup.DefaultInstantUpgradeManager.runTask(DefaultInstantUpgradeManager.java:55)
        at com.atlassian.jira.startup.DefaultInstantUpgradeManager.doNowOrWhenInstanceBecomesActive(DefaultInstantUpgradeManager.java:42)
        at com.atlassian.jira.startup.DefaultJiraLauncher.postTenantArrived(DefaultJiraLauncher.java:177)
        at com.atlassian.jira.startup.DefaultJiraLauncher.lambda$postDBActivated$3(DefaultJiraLauncher.java:165)
        at com.atlassian.jira.tenancy.DefaultTenantManager.doNowOrWhenTenantArrives(DefaultTenantManager.java:55)
        at com.atlassian.jira.startup.DefaultJiraLauncher.postDBActivated(DefaultJiraLauncher.java:162)
        at com.atlassian.jira.startup.DefaultJiraLauncher.lambda$postDbLaunch$2(DefaultJiraLauncher.java:151)
        at com.atlassian.jira.config.database.DatabaseConfigurationManagerImpl.doNowOrEnqueue(DatabaseConfigurationManagerImpl.java:298)
        at com.atlassian.jira.config.database.DatabaseConfigurationManagerImpl.doNowOrWhenDatabaseActivated(DatabaseConfigurationManagerImpl.java:194)
        at com.atlassian.jira.startup.DefaultJiraLauncher.postDbLaunch(DefaultJiraLauncher.java:141)
        at com.atlassian.jira.startup.DefaultJiraLauncher.lambda$start$0(DefaultJiraLauncher.java:103)
        at com.atlassian.jira.util.devspeed.JiraDevSpeedTimer.run(JiraDevSpeedTimer.java:31)
        at com.atlassian.jira.startup.DefaultJiraLauncher.start(DefaultJiraLauncher.java:101)
        at com.atlassian.jira.startup.LauncherContextListener.initSlowStuff(LauncherContextListener.java:149)
        at java.lang.Thread.run(Thread.java:745)
2017-12-08 22:17:23,263 JIRA-Bootstrap INFO      [c.a.jira.startup.DefaultInstantUpgradeManager] Late startup launchers took 0s
2017-12-08 22:17:23,274 JIRA-Bootstrap ERROR      [c.a.jira.startup.LauncherContextListener] Unable to start JIRA.
java.lang.IllegalStateException: Abnormal system startup detected
        at com.atlassian.jira.startup.LauncherContextListener.initDone(LauncherContextListener.java:180)
        at com.atlassian.jira.startup.LauncherContextListener.initSlowStuff(LauncherContextListener.java:162)
        at java.lang.Thread.run(Thread.java:745)
2017-12-08 22:17:23,281 JIRA-Bootstrap INFO      [c.a.jira.startup.LauncherContextListener] Memory Usage:
    ---------------------------------------------------------------------------------
      Heap memory     :  Used:  328 MiB.  Committed:  638 MiB.  Max:  747 MiB
      Non-heap memory :  Used:  189 MiB.  Committed:  206 MiB.  Max: 1264 MiB
    ---------------------------------------------------------------------------------
      TOTAL           :  Used:  516 MiB.  Committed:  844 MiB.  Max: 2011 MiB
    ---------------------------------------------------------------------------------
2017-12-08 22:17:28,111 Modification Check:thread-1 INFO      [c.a.jira.startup.JiraStartupLogger]

    ___ Modifications ___________________________

         Modified Files                                : None
         Removed Files                                 : None

Eny sugestions?

[Bryan McMillan]

Zawistowski,

Application Links are designed to be used to setup communications (incoming/outgoing) between tools.  In my environment we have Jira, Confluence, Crucible, and FishEye.  All Atlassian tools.  I setup application links from the screen you've attached here to your question.  In the case of our setup we wanted JIRA to be able to see the code and reviews that are related to JIRA issues.  Moreover, we have also been working on adding a link to Jenkins so we can also see what builds that code was included into.  So, for any given approved Change Request (CR) , a specific JIRA issue type, we can see from the approved CR down to the code that was changed, what changed, what build or builds it went into, etc.  Now Jenkins is not an Atlassian tool obviously but there is an integration for it that exists we are also using which require plug-ins to extended Jira's & Jenkins functionality as plug-ins are needed in both tools.

Regards,

Bryan

[Bharadwaj Jannu]

Hi Zawistowski Grzegorz,

The following links gives an idea of adding an application link in jira.

https://confluence.atlassian.com/display/JIRA060/Adding+an+Application+Link

https://confluence.atlassian.com/jira/linking-to-another-application-357335370.html

It is a two-way adding application link meant you need to add JIRA application and url in the target application also.

Hope this helps!!

[Nic Brough -Adaptavist-]

You do what it says - add the url of the application you want to link to.  Have a look through https://confluence.atlassian.com/jira/linking-to-another-application-357335370.html