jira startup getting struck at Warmed cache(s) in 12707 ms.

[Ashutosh Mishra]

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

    ___ FAILED PLUGIN REPORT _____________________

    1 plugin failed to load during JIRA startup.

    'com.atlassian.diagnostics.atlassian-diagnostics-plugin' - 'Atlassian Diagnostics - Plugin'  failed to load.

    Application context initialization for 'com.atlassian.diagnostics.atlassian-diagnostics-plugin' has timed out waiting for (|(objectClass=com.atlassian.diagnostics.MonitoringService)(objectClass=com.atlassian.diagnostics.DiagnosticsConfiguration))

    It has the following missing service dependencies :

     &diagnosticsConfiguration of type (objectClass=com.atlassian.diagnostics.DiagnosticsConfiguration)

     &diagnosticsConfiguration of type (objectClass=com.atlassian.diagnostics.DiagnosticsConfiguration)

     &monitoringService of type (objectClass=com.atlassian.diagnostics.MonitoringService)

     &monitoringService of type (objectClass=com.atlassian.diagnostics.MonitoringService)

    It was loaded from /u01/app/atlassian/servicedesk/atlassian-jira/WEB-INF/atlassian-bundled-plugins/atlassian-diagnostics-plugin-1.1.10.jar

    1 plugin are unaccounted for.

    Unaccounted for plugins load as artifacts but fail to resolve into full plugins.

    'com.atlassian.jira.diagnostics' - 'Atlassian Jira - Plugins - Diagnostics Plugin'  is unaccounted for.

    It was loaded from /u01/app/atlassian/servicedesk/atlassian-jira/WEB-INF/atlassian-bundled-plugins/jira-diagnostics-plugin-8.5.8.jar

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

2021-01-06 02:59:18,224+0000 localhost-startStop-1 INFO      [c.a.jira.startup.LauncherContextListener] Memory Usage:

    ---------------------------------------------------------------------------------

      Heap memory     :  Used: 5672 MiB.  Committed: 20480 MiB.  Max: 20480 MiB

      Non-heap memory :  Used:  429 MiB.  Committed:  462 MiB.  Max: 1536 MiB

    ---------------------------------------------------------------------------------

      TOTAL           :  Used: 6101 MiB.  Committed: 20942 MiB.  Max: 22016 MiB

    ---------------------------------------------------------------------------------

2021-01-06 02:59:18,373+0000 Caesium-1-1 INFO      [c.a.jira.upgrade.UpgradeScheduler] Running scheduled upgrades

2021-01-06 02:59:18,384+0000 Caesium-1-1 INFO      [c.a.jira.upgrade.LoggingUpgradeService] run upgrades has started

06-Jan-2021 02:59:18.698 INFO [main] org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler ["http-nio-8080"]

06-Jan-2021 02:59:18.739 INFO [main] org.apache.catalina.startup.Catalina.start Server startup in 834390 ms

2021-01-06 02:59:19,001+0000 Caesium-1-1 INFO      [c.a.j.upgrade.util.BuildNumberDao] Setting current build number to 805008

2021-01-06 02:59:19,039+0000 Caesium-1-1 INFO      [c.a.jira.upgrade.UpgradeIndexManager] There are no reindex requests of type [IMMEDIATE, DELAYED] so none will be run

2021-01-06 02:59:19,039+0000 Caesium-1-1 INFO      [c.a.j.upgrade.util.BuildNumberDao] Setting current version to 8.5.8

2021-01-06 02:59:19,071+0000 Caesium-1-1 INFO      [c.a.j.upgrade.util.BuildNumberDao] Setting downgrade version to 7.1.2

2021-01-06 02:59:19,108+0000 Caesium-1-1 INFO      [c.a.jira.upgrade.LoggingUpgradeService] run upgrades has finished successfully, and took 724 milliseconds to process.

2021-01-06 02:59:19,108+0000 Caesium-1-1 INFO      [c.a.jira.upgrade.UpgradeScheduler] JIRA upgrades completed successfully

2021-01-06 02:59:19,142+0000 Caesium-1-1 INFO      [c.a.jira.upgrade.UpgradeScheduler] Plugins upgrades completed successfully

2021-01-06 02:59:19,145+0000 Caesium-1-1 INFO      [c.a.jira.upgrade.UpgradeIndexManager] Reindexing is not allowed after this upgrade and there is no immediate reindex requests

2021-01-06 02:59:20,510+0000 Caesium-1-2 INFO      [c.a.jira.startup.IndexRecoveryLauncher] Running start-index-recovery on node=node1_4007

2021-01-06 02:59:20,756+0000 Caesium-1-2 INFO      [c.a.jira.startup.IndexRecoveryLauncher] Done running start-index-recovery on node=node1_4007, number of index operations recovered=0

2021-01-06 02:59:20,756+0000 Caesium-1-2 INFO      [c.a.jira.startup.IndexRecoveryLauncher] Finished start-index-recovery on node=node1_4007

2021-01-06 02:59:20,762+0000 Caesium-1-2 INFO      [c.a.jira.startup.CacheWarmerLauncher] Warming up 3 caches.

2021-01-06 02:59:33,469+0000 Caesium-1-2 INFO      [c.a.jira.startup.CacheWarmerLauncher] Warmed cache(s) in 12707 ms.

[Carlos Garcia Navarro]

Hi @Ashutosh Mishra ,

Did you check this document with some troubleshooting tips?

https://confluence.atlassian.com/jirakb/troubleshoot-a-jira-server-startup-failed-error-394464512.html

[Ashutosh Mishra]

This now worked but I am getting another error in Catalina.out

Http error: Unable to tunnel through proxy. Proxy returns "HTTP/1.1 403 DefaultErrorTemplate"

Http error: Unable to tunnel through proxy. Proxy returns "HTTP/1.1 403 DefaultErrorTemplate"

Kindly advice

[Daniel Ebers]

I understand the error message is referring to a proxy. The system seems to reply with error code '403'.

Can you please confirm you use a proxy of whatever sort?

Could you please also describe the setup any further? Is this a single node Confluence installation or there are some specialities we should know about?

Is Jira up - despite the error message or does it refuse to start?
Edit: fixed messed up line above, sorry :)