My current setup is on all one server instance:
- Standalone Linux Server - CentOS Linux release 7.5.1804 (Core)
- Standalone JIRA Service Desk v3.11.1 (installed w/provided .bin file)
- Standalone Confluence v6.10.0 (installed w/provided .bin)
- Standalone Postgres DB Server (on the same host)
My Issue:
During the "Setup" process (via the browser on port 8090), I chose the following steps:
- Production Installation
- No Add-ons
- My own database (connection successful !)
- Load Content -> "Example Site"
- Configure User Management -> (Have tried both options)
CRASH - my confluence instance crashes.
I can repeat the process by deleting the "confluence.cfg.xml" file and restarting confluence, then browsing to my server at port 8090. This step was determined by resolution 10 on the following URL (after a proper google search):
https://confluence.atlassian.com/confkb/confluence-does-not-start-due-to-spring-application-context-has-not-been-set-218278311.html
After each crash, my confluence.cfg.xml file size is the same and only the "confluence.setup.server.id", "jwt.private.key", and "jwt.public.key" property values are changed.
What are my next steps here?
I would like to get confluence up and running.
If you need to see anything else, then please let me know and I will share it with you.
Many Thanks.
Hi there,
Thank you for all the information! Would you be able to have a look at your Confluence server logs in order to see exactly which error is causing Confluence to crash?
I think that would help the most in this situation.
Regards,
Shannon
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.