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

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

Cannot launch Jira in browser


I have issue with Jira since our server has crashed.

We are able to start Jira by using ./ command

But when launch Jira on any browser we have this result 
2019-07-17 14_02_53-Problème d'accès à Jira.png

Into logs/catalina.out 

2019-07-17 13:34:24,367 ThreadPoolAsyncTaskExecutor::Thread 18 ERROR [o.e.g.b.e.i.dependencies.startup.DependencyWaiterApplicationContextExecutor] Unable to create application context for [com.pyxis.greenhopper.jira], unsatisfied dependencies: none
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'greenhopper-launcher': Invocation of init method failed; nested exception is com.opensymphony.module.propertyset.PropertyImplementationException: Failed operation: SetOperation[entityName=GreenHopper.Run.History,entityId=1,propertyKey=lastRunVersion,newType=6,newMapper=TypeMapper[handler=StringPropertyHandler,valueEntity=OSPropertyText]]
at org.springframework.beans.factory.annotation.InitDestroyAnnotationBeanPostProcessor.postProcessBeforeInitialization(
at org.eclipse.gemini.blueprint.util.internal.PrivilegedUtils.executeWithCustomTCCL(
at org.eclipse.gemini.blueprint.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor$
at java.util.concurrent.ThreadPoolExecutor.runWorker(
at java.util.concurrent.ThreadPoolExecutor$
Caused by: com.opensymphony.module.propertyset.PropertyImplementationException: Failed operation: SetOperation[entityName=GreenHopper.Run.History,entityId=1,propertyKey=lastRunVersion,newType=6,newMapper=TypeMapper[handler=StringPropertyHandler,valueEntity=OSPropertyText]]
at com.atlassian.jira.propertyset.CachingOfBizPropertyEntryStore.propEx(
at com.atlassian.jira.propertyset.CachingOfBizPropertyEntryStore.retry(
at com.atlassian.jira.propertyset.CachingOfBizPropertyEntryStore.setEntry(
at com.atlassian.jira.propertyset.CachingOfBizPropertySet.setImpl(
at com.opensymphony.module.propertyset.AbstractPropertySet.set(
at com.atlassian.greenhopper.service.PersistenceServiceImpl.setData(
at com.atlassian.greenhopper.upgrade.UpgradeVersionService.recordPluginStarted(
at com.atlassian.greenhopper.service.logging.LogSupportInfo.logSupportInfoOnStartup(
at com.atlassian.greenhopper.service.logging.LogSupport.onPluginStarting(
at com.atlassian.greenhopper.Launcher.onSpringContextStarted(
... 3 filtered
at java.lang.reflect.Method.invoke(
at org.springframework.beans.factory.annotation.InitDestroyAnnotationBeanPostProcessor$LifecycleElement.invoke(
at org.springframework.beans.factory.annotation.InitDestroyAnnotationBeanPostProcessor$LifecycleMetadata.invokeInitMethods(
at org.springframework.beans.factory.annotation.InitDestroyAnnotationBeanPostProcessor.postProcessBeforeInitialization(
... 18 more
Caused by: com.querydsl.core.QueryException: Caught PSQLException for select, O_S_PROPERTY_ENTRY.propertytype
from public.propertyentry O_S_PROPERTY_ENTRY
where O_S_PROPERTY_ENTRY.entity_name = ? and O_S_PROPERTY_ENTRY.entity_id = ? and O_S_PROPERTY_ENTRY.property_key = ?
order by desc
for update
at com.querydsl.sql.DefaultSQLExceptionTranslator.translate(
at com.querydsl.sql.AbstractSQLQuery.fetch(
at com.atlassian.jira.propertyset.CachingOfBizPropertyEntryStore$SetOperation.upsert(
at com.atlassian.jira.propertyset.CachingOfBizPropertyEntryStore.lambda$tx$6(
at com.atlassian.jira.database.DefaultQueryDslAccessor$1.lambda$executeQuery$0(
at com.atlassian.jira.database.DatabaseAccessorImpl.executeQuery(
at com.atlassian.jira.database.DefaultQueryDslAccessor$1.executeQuery(
at com.atlassian.jira.propertyset.CachingOfBizPropertyEntryStore.query(
at com.atlassian.jira.propertyset.CachingOfBizPropertyEntryStore.tx(
at com.atlassian.jira.propertyset.CachingOfBizPropertyEntryStore.access$300(
at com.atlassian.jira.propertyset.CachingOfBizPropertyEntryStore$SetOperation.perform(
at com.atlassian.jira.propertyset.CachingOfBizPropertyEntryStore.retry(
... 34 more
Caused by: org.postgresql.util.PSQLException: ERROR: could not access status of transaction 25060618
Détail : Could not open file "pg_clog/0017": No such file or directory.
at org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(
at org.postgresql.core.v3.QueryExecutorImpl.processResults(
at org.postgresql.core.v3.QueryExecutorImpl.execute(
at org.postgresql.jdbc.PgStatement.executeInternal(
at org.postgresql.jdbc.PgPreparedStatement.executeWithFlags(
at org.postgresql.jdbc.PgPreparedStatement.executeQuery(
at org.apache.commons.dbcp2.DelegatingPreparedStatement.executeQuery(
at org.apache.commons.dbcp2.DelegatingPreparedStatement.executeQuery(
at com.querydsl.sql.AbstractSQLQuery.fetch(
... 44 more

1 answer

1 accepted

0 votes
Answer accepted
Andy Heinzer Atlassian Team Jul 18, 2019

Hi Sebastien,

Sorry to hear about this problem.  However from your screenshot and the error, I think i can see the problem here. 

It appears that Jira is unable to complete this update because the postgresql database that Jira is using is an older unsupported 9.2.x version.  You can see that current Jira versions deprecated support for this database version a while ago in the supported platforms documentation.

What I would recommend here would be to

  1. install a fresh postgresql 9.6.x version database first. 
  2. Then create a new empty Jira database, and edit your $JIRAHOME/dbconfig.xml file in order use this specific database instead.  (You could also use the Jira Config tool to do this too, if you prefer a graphical user interface.)
  3. Grab a copy of your Jira XML backup file (These are found in the $JIRAHOME/export/ folder by default
  4. Copy that file into the $JIRAHOME/import/ folder
  5. restart Jira (When connected to a new empty database, this will launch the setup wizard)
  6. In the setup wizard, choose the 'import existing data' option and enter the xml backup .zip filename here to both import and upgrade your Jira data here.

This approach tends to be my preferred method, as it gets you on a supported platform and upgrades Jira in what I believe are the fewest number of steps.  It might be possible to upgrade Postgresql as a means to troubleshoot this, but given that you have transactions in SQL that already appear to have failed, I'm not well versed in troubleshooting that database aspect.  Which is why I think it would be better to take a backup and use that here to work past this upgrade problem.

Please let me know if you have any questions or concerns about this approach.


Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Jira Software

How to create Jira issus from Excel file?

When to use CSV importer When managing your processes in Jira, there are many occasions where you need to create a lot of tasks. Creating them one by one will cost you a lot of time and effort and i...

4,349 views 22 31
Read article

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