JIRA shows fatal error after moving to a new server

[LEM]

We moved our JIRA-, Confluence- and Crowd-starter instances to a new server (applications only, DB remainded the same).

We copied all install- and home-folders with the correct users and started the applications. Crowd and Confluence started up with no problems.

But JIRA had this entry in the startup logs and didn't start:

JIRA-Bootstrap FATAL [c.a.jira.startup.JiraStartupLogger] Startup check failed. Jira will be locked.

I found this in the Knowledge base, but the home-directory is still the same /atlassian/application-data/jira as on the previous server.

[Daniel Ebers · Accepted solution]

Hi Werner,

the FATAL-error you cites is a generic one - the truth is also in the logs, but somewhere else. Could you please check if you see more errors except from the one you posted - then somebody here might be able to say more.
A relevant info should be in atlassian-jira.log and/or catalina.out

Thanks in advance!
Regards,
Daniel

[LEM]

Hi Daniel,

thanks for your quick response.

You were right, there was another issue responsible for the problem: the path for the backup-files wasn't accessible for Jira.

This seems to be checked during startup, and if it doesn't work it leaves no error in the catalina.out...

Either way, JIRA is up and running now. Thanks for your input that it might have nothing to do with the actual error :-)

Best regards,

Werner