We are running JIRA/Stash on CentOS 7 behind an Apache (2.4) proxy (SSL enabled). This morning I was able to connect to the JIRA instance but noticed the Stash instance was returning a 502 Proxy Error.
Rebooting the server lead to both JIRA and Stash returning errors relating to the database:
(Stash) The database, as currently configured, is not accessible.
(JIRA) HTTP Status 500 - Could not determine database type.
After inspecting the logs, the JIRA ones point to a database issue, while the Stash logs say the "No Spring WebApplicationContext is available"
Nothing has changed on these boxes since they were working - we have even rolled the server back to a previous backup of when it was working and it still produces the same errors.
Any insight to why this might be occuring or how we can better debug it would be greatly appreciated - thanks.
It sounds like both Stash and JIRA cannot connect to the configured database. I'd check whether the database server is up and running and whether the JIRA/Stash server can connect to the database. Perhaps the database server is down or the hostname/ip (if you've configured your database connection based on an IP) has changed or perhaps a firewall configuration has changed somewhere?
The database is running and it can be connected to on the box. It's hosted on the same machine and the IP or host hasn't changed as they are accessing it through localhost.
It was working perfectly fine this morning until we rebooted the server.
Thanks for your reply
Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...
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