SEVERE: Unable to create directory for deployment: /opt/atlassian/jira/conf/Catalina/localhost
Thought it might have to do with no DB being established yet, but I see the comments in the server.xml file that DB is set up the first time you log in to jira.
Installed jira 6.1 on CentOS server. The installer didn't indicate any errors. No errors indicated when I run "service jira start" but I just cannot connect to the instance via browser. I've tried both the express setup and the custom setup.
Looks like a permissions issue, but I installed as root, changed owner to jira, set the appropriate execute permissions...
It looks you haven't give permissions to the jira user that is starting JIRA to the JIRA folders. This documentation might help: https://confluence.atlassian.com/display/JIRAKB/JIRA+Generates+a+FileNotFoundException+due+to+Permission+denied
Hope it helps,
There's a known bug in the 6.1 Linux installer causing the "SEVERE: Unable to create directory for deployment: /opt/atlassian/jira/conf/Catalina/localhost" message in catalina.out.
If you've run the installer as "root",
/opt/atlassian/jira/conf is owned by root:root with 755 permissions.
chown -R jira:root /opt/atlassian/jira/conf/
This allows the "jira" user to populate the Catalina tree. No more SEVERE errors are logged.
Atlassian acknowledged this is a problem with 6.1 installer which should be fixed in 6.2 (which I have not yet tested).
Hey Brian - curious what you mean by "set my.conf to localhost"
I'm guessing you meant my.cnf? Even then, what config variable do you set to localhost within my.cnf? The bind-address? (bind-address = 127.0.0.1 is what I currently have there)
I'm having the same issue you describe.
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot