Setup: JIRA couldn't create the jira.home directory

[Mocospace]

We're migrating from one server to another server, following the confluence article.

On start, we get a fatal error in catalina.out:

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

When hitting the web page, we get this error.

Setup: JIRA couldn't create the jira.home directory

It's quite obvious that jira has full access to jira.home.

Where else can I look to diagnose what's going on?

Additional Error log:

14-Nov-2022 17:57:01.362 INFO [main] org.apache.catalina.startup.Catalina.start Server startup in 8431 ms
2022-11-14 17:57:01,384+0000 JIRA-Bootstrap INFO [c.a.j.config.database.SystemDatabaseConfigurationLoader] Reading database configuration from /home/ec2-user/atlassian/jira_home/dbconfig.xml
2022-11-14 17:57:01,434+0000 JIRA-Bootstrap INFO [c.a.j.config.database.DatabaseConfigHandler] Trying to get encrypted password from xml and decrypt it
2022-11-14 17:57:01,436+0000 JIRA-Bootstrap INFO [c.a.j.config.database.DatabaseConfigHandler] Database password decryption not performed.
2022-11-14 17:57:01,686+0000 JIRA-Bootstrap INFO [c.a.jira.startup.JiraStartupLogger] Running Jira startup checks.
2022-11-14 17:57:01,687+0000 JIRA-Bootstrap FATAL [c.a.jira.startup.JiraStartupLogger] Startup check failed. Jira will be locked.
2022-11-14 17:57:01,769+0000 JIRA-Bootstrap INFO [c.a.jira.startup.LauncherContextListener] Startup is complete. Jira is ready to serve.

[Mocospace · Accepted solution]

To answer my own question:

On the original (old) server, the jira_home/data/attachment directory was changed to a symlink pointing to a new directory (as the hard drive was filling).

When jira_home was copied over to the new server, the symlink failed, but the link still existed. When comparing directories (from old to new) this made things look fine, however there was no 'attachment' directory (no destination for the link).

This was causing Jira to fail to start, with no other error message.

[Hieu]

Hi @Mocospace might be the permission to access the folder.

Create and point Jira home folder
https://confluence.atlassian.com/adminjiraserver/setting-your-jira-application-home-directory-938847747.html

chmod 755 for unix
grant access permision via UI if you are using windows

[Mocospace]

Yes, that has already been done.

Jira says this on start:

Upgrade: Custom changes have not been carried over

The listed configuration files contain custom changes. To keep your current configuration, re-apply these custom changes to the new version of the files during upgrade.

• atlassian-jira/WEB-INF/classes/jira-application.properties

Note: Make sure you only copy over the changes not the entire files.

Which is odd as we aren't upgrading. It's a version to version copy.

[Hieu]

Can you try to: 

1. stop jira service
2. delete jira_home/plugins/.bundled-plugins
3. delete jira_home/plugins/.osgi-plugins
4. start jira service

[Mocospace]

Sorry for the delay.

I get the same messages.

If I move jira_home and make a blank directory in it's place, jira starts normally and takes me into the "Jira Setup" as if it's a new, blank install.

[Mocospace]

14-Nov-2022 21:10:51.151 INFO [main] org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler ["http-nio-1080"]
14-Nov-2022 21:10:51.287 INFO [main] org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler ["http-nio-8082"]
2022-11-14 21:10:51,314+0000 JIRA-Bootstrap INFO [c.a.j.config.database.SystemDatabaseConfigurationLoader] Reading database configuration from /home/ec2-user/atlassian/jira_home/dbconfig.xml
2022-11-14 21:10:51,383+0000 JIRA-Bootstrap INFO [c.a.j.config.database.DatabaseConfigHandler] Trying to get encrypted password from xml and decrypt it
2022-11-14 21:10:51,387+0000 JIRA-Bootstrap INFO [c.a.j.config.database.DatabaseConfigHandler] Database password decryption not performed.
14-Nov-2022 21:10:51.438 INFO [main] org.apache.catalina.startup.Catalina.start Server startup in 7981 ms
2022-11-14 21:10:51,656+0000 JIRA-Bootstrap INFO [c.a.jira.startup.JiraStartupLogger] Running Jira startup checks.
2022-11-14 21:10:51,656+0000 JIRA-Bootstrap FATAL [c.a.jira.startup.JiraStartupLogger] Startup check failed. Jira will be locked.
2022-11-14 21:10:51,722+0000 JIRA-Bootstrap INFO [c.a.jira.startup.LauncherContextListener] Startup is complete. Jira is ready to serve.
2022-11-14 21:10:51,724+0000 JIRA-Bootstrap INFO [c.a.jira.startup.LauncherContextListener] Memory Usage:
---------------------------------------------------------------------------------
Heap memory : Used: 424 MiB. Committed: 900 MiB. Max: 2011 MiB
Non-heap memory : Used: 43 MiB. Committed: 66 MiB. Max: 1536 MiB
---------------------------------------------------------------------------------
TOTAL : Used: 468 MiB. Committed: 966 MiB. Max: 3547 MiB
---------------------------------------------------------------------------------