Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal

Recognition

  • Give kudos
  • Received
  • Given

Leaderboard

  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Error after upgrading jira from 7.2 to 8.10.1 Edited

I have upgraded the jira 7.2 to 8.10.1, but when i tried to start the jira service.

Its throwing the error as below :

 

Server startup logs are located in /opt/atlassian/jiranew/atlassian-jira-software-8.10.1-standalone/logs/catalina.out
Using CATALINA_BASE: /opt/atlassian/jiranew/atlassian-jira-software-8.10.1-standalone
Using CATALINA_HOME: /opt/atlassian/jiranew/atlassian-jira-software-8.10.1-standalone
Using CATALINA_TMPDIR: /opt/atlassian/jiranew/atlassian-jira-software-8.10.1-standalone/temp
Using JRE_HOME: /usr
Using CLASSPATH: /opt/atlassian/jiranew/atlassian-jira-software-8.10.1-standalone/bin/bootstrap.jar:/opt/atlassian/jiranew/atlassian-jira-software-8.10.1-standalone/bin/tomcat-juli.jar
Using CATALINA_PID: /opt/atlassian/jiranew/atlassian-jira-software-8.10.1-standalone/work/catalina.pid
Existing PID file found during start.
Removing/clearing stale PID file.
Tomcat started.
root@XXX:/var/atlassian/application-data/jira/plugins# systemctl start jira.service
Job for jira.service failed because the control process exited with error code. See "systemctl status jira.service" and "journalctl -xe" for details.
root@XXXX:/var/atlassian/application-data/jira/plugins#

 

I can able to find the below error in catalina.out  and atlassian.jira log

 

catalina.out 

___ Starting the JIRA Plugin System _________________

2020-08-06 09:45:26,280+0000 ThreadPoolAsyncTaskExecutor::Thread 11 INFO [c.a.ratelimiting.internal.RateLimitingConfiguration] Rate Limited Request Handler ENABLED
Security framework of XStream not initialized, XStream is probably vulnerable.
2020-08-06 09:45:40 localhost-startStop-1 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.cluster.DefaultClusterServicesManager'.

2020-08-06 09:45:42 localhost-startStop-1 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.)]

 

atlassian.jira log

"errors":0,"period":"5.085 min","compactInMillis":{},"compactBeforeCounter":{},"compactAfterCounter":{},"compactVersionedCounter":{},"compactUnVersionedCounter":{},"filterOutAlreadyIndexedInMillis":{},"filterOutAlreadyIndexedBeforeCounter":{},"filterOutAlreadyIndexedAfterCounter":{},"updateIndexInMillis":{},"updateIndexCounter":{},"updateIndexBatchCounter":{}}

2020-08-06 10:00:22,pool-27-thread-1 ERROR [c.a.j.config.properties.PropertiesUtil] Exception whilst trying to find value for property 'jira.diagnostics.threshold.database-pool-utilization'. Defaulting to 100. java.lang.NumberFormatException: null
2020-08-06 09:55:51,localhost-startStop-1 ERROR [c.a.jira.health.HealthChecks] We couldn't start JIRA
2020-08-06 09:55:51, localhost-startStop-1 ERROR [c.a.jira.health.HealthChecks] 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.
See our documentation for more information on contacting our support team and creating a support zip.
2020-08-06 09:55:51,327+0000 localhost-startStop-1 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.cluster.DefaultClusterServicesManager'.

2020-08-06 09:55:29,660+0000 localhost-startStop-1 ERROR [c.a.p.osgi.factory.OsgiPlugin] Detected an error (BundleException) enabling the plugin 'com.atlassian.servicedesk.public-rest-api' : Unable to resolve com.atlassian.servicedesk.public-rest-api [202](R 202.0): missing requirement [com.atlassian.servicedesk.public-rest-api [202](R 202.0)] osgi.wiring.package; (osgi.wiring.package=com.atlassian.servicedesk.api.comment) [caused by: Unable to resolve com.atlassian.servicedesk [194](R 194.0): missing requirement [com.atlassian.servicedesk [194](R 194.0)] osgi.wiring.package; (osgi.wiring.package=com.atlassian.jira.plugins.workinghours.api.calendar) [caused by: Unable to resolve com.atlassian.jira.plugins.workinghours [134](R 134.0): missing requirement [com.atlassian.jira.plugins.workinghours [134](R 134.0)] osgi.wiring.package; (&(osgi.wiring.package=com.atlassian.activeobjects.external)(version>=0.19.0)(!(version>=3.0.0)))]] Unresolved requirements: [[com.atlassian.servicedesk.public-rest-api [202](R 202.0)] osgi.wiring.package; (osgi.wiring.package=com.atlassian.servicedesk.api.comment)]. This error usually occurs when your plugin imports a package from another bundle with a specific version constraint and either the bundle providing that package doesn't meet those version constraints, or there is no bundle available that provides the specified package. For more details on how to fix this, see https://developer.atlassian.com/x/mQAN
2020-08-06 09:55:29,662+0000 localhost-startStop-1 ERROR [c.a.p.osgi.factory.OsgiPlugin] Detected an error (BundleException) enablin

 

3 answers

0 votes

@aynes Varghese  

Try start Jira  in a safe mode then enable one by one from the manage apps > user installed, to fine  the plugin that can be causing the problem

Add ability to disable Jira add-ons at start time 

 

Kind regards,

Moses

yes i removed the plugins and tried to start. but automatically plugins folder gets created and can see all required plugin inside it.

But the service came up and still the jira UI throws errow as mentioned below 

I found the below error in catalina.out log file 

06-Aug-2020 14:58:37.385 INFO [main] org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler ["http-nio-8080"]
06-Aug-2020 14:58:37.390 SEVERE [main] org.apache.catalina.core.StandardService.startInternal Failed to start connector [Connector[HTTP/1.1-8080]]
org.apache.catalina.LifecycleException: Protocol handler start failed

 

Jira.atalassian.log file 

06-Aug-2020 14:58:37.393 INFO [main] org.apache.catalina.startup.Catalina.start Server startup in 4127 ms
06-Aug-2020 14:58:37.394 SEVERE [main] org.apache.catalina.core.StandardServer.await StandardServer.await: create[localhost:8005]:
java.net.BindException: Address already in use (Bind failed)
decrypt it
2020-08-06 14:58:37,468+0000 JIRA-Bootstrap INFO [c.a.j.config.database.DatabaseConfigHandler] Database password decryption not performed.
2020-08-06 14:58:37,626+0000 JIRA-Bootstrap INFO [c.a.jira.startup.JiraStartupLogger] Running Jira startup checks.
2020-08-06 14:58:37,626+0000 JIRA-Bootstrap FATAL [c.a.jira.startup.JiraStartupLogger] Startup check failed. Jira will be locked.
2020-08-06 14:58:37,678+0000 JIRA-Bootstrap INFO [c.a.jira.startup.LauncherContextListener] Memory Usage:

Recommend you remove add-on's from the installed plugin's directory in Jira home. Start Jira and if it comes up you can re-install you add-on's.

What database and version of db are you using?

yes i did the same and made few more changes. that made jira service to come up.

 

My SQL version 5.6.44

But while trying to start jira in the UI, it throws me error.

I found the below error in catalina.out log file 

06-Aug-2020 14:58:37.385 INFO [main] org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler ["http-nio-8080"]
06-Aug-2020 14:58:37.390 SEVERE [main] org.apache.catalina.core.StandardService.startInternal Failed to start connector [Connector[HTTP/1.1-8080]]
org.apache.catalina.LifecycleException: Protocol handler start failed

 

Jira.atalassian.log file 

06-Aug-2020 14:58:37.393 INFO [main] org.apache.catalina.startup.Catalina.start Server startup in 4127 ms
06-Aug-2020 14:58:37.394 SEVERE [main] org.apache.catalina.core.StandardServer.await StandardServer.await: create[localhost:8005]:
java.net.BindException: Address already in use (Bind failed)
decrypt it
2020-08-06 14:58:37,468+0000 JIRA-Bootstrap INFO [c.a.j.config.database.DatabaseConfigHandler] Database password decryption not performed.
2020-08-06 14:58:37,626+0000 JIRA-Bootstrap INFO [c.a.jira.startup.JiraStartupLogger] Running Jira startup checks.
2020-08-06 14:58:37,626+0000 JIRA-Bootstrap FATAL [c.a.jira.startup.JiraStartupLogger] Startup check failed. Jira will be locked.
2020-08-06 14:58:37,678+0000 JIRA-Bootstrap INFO [c.a.jira.startup.LauncherContextListener] Memory Usage:

I would review the docs about the database closely. We upgraded to 5.7 before going from 7.x to 8.x.

https://confluence.atlassian.com/adminjiraserver0810/supported-platforms-1014673441.html

Like aynes Varghese likes this

Yes i have reviewed the doc. Jira 8.10.1 will support my sql 5.6 utf 8 but it wont support my sql 5.6 4 byte character.

2020-08-07 10:04:05,121+0000 localhost-startStop-1 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.cluster.DefaultClusterServicesManager'.
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

Hi there,

Did you manage to fix this? I have the same issue upgrading from 7.11.0 to 8.13.1

Suggest an answer

Log in or Sign up to answer
TAGS

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you