Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Unable to start JIRA

Daniel Darnbrough February 13, 2018

Hello,

We have had to restore Jira from recovery after corruption, all files were successfully restored apart from files residing in - application-data/plugins/.osgi-plugins/felix/ and application-data/export/

Should we cut our losses and assume all data is lost, or is there a chance that Jira can start without these files?

Thanks

 

 

1 answer

1 accepted

0 votes
Answer accepted
Fazila Ashraf
Community Champion
February 13, 2018

Hi Daniel

  • application-data/plugins/.osgi-plugins/felix/ => will rebuild on startup of JIRA
  • application-data/export/ => Will have the auto xml exports of JIRA.

If you do not need the old xml exports any more then you can just move on..

JIRA can start with out these files

Thanks and regards,

Fazila

Daniel Darnbrough February 14, 2018

Hi Fazila,

Ok this is positive. Jira currently fails to start, which log should i be looking in and what should i be looking for?

 

Currently the web page says:

An unexpected error has occurred during startup: we couldn't start Jira

Thanks

Dan

Fazila Ashraf
Community Champion
February 14, 2018

Look for /application-data/log/atlassian-jira.log for the errors.

That should hint you on what you should check further

Daniel Darnbrough February 15, 2018

And in Linux this would be Catalina.out?

 

if so we see the first errors when initialising the plugins:

 

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=Tue Feb 13 23:00:00 GMT 2018,version=1,rawParameters=(null)]

Nic Brough -Adaptavist-
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
February 15, 2018

No, you need to read <jira-home>/log/atlassian-jira.log as Fazila said.

Daniel Darnbrough February 15, 2018

Thanks Nic, that log doesn't exist. theres a <jira-home>/logs/

atlassian-jira-gc-<date>.log.0.current -- EDIT looks like Jira Home was in a different local found the log now.

 

But i have now resolved the issue:

Running 

reindex database "jiradb";

And restarting

 

Allowed Jira to start and we are seeing no further errors.

Nic Brough -Adaptavist-
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
February 15, 2018

There is an atlassian-jira.log somewhere, although you may have renamed it.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events