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.
Turned out to be an issue with the database connector (swapping localhost to 127.0.0.1 fixed the issue) - why this suddenly happened when no updates or changes were made is confusing
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?
Cheers,
Michael
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Michael,
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Turned out to be an issue with the database connector (swapping localhost to 127.0.0.1 fixed the issue) - why this suddenly happened when no updates or changes were made is confusing
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.