It is hard to say why the applications were both unavailable after you installed Confluence on the server you already had Service Desk on.
If I had to guess I would say perhaps there were not enough resources for both to run. The system requirements for Atlassian applications are linked on the bottom of: Server: Installing multiple applications on a single server
For next steps, it doesn't sound like we have logs from when the applications wouldn't start but we will need to examine logs to know what happened. If you do have logs, please look for error messages. I start at the Starting Confluence line in the atlassian-confluence.log and check any errors in the Tomcat logs located in the installation directory. The log locations are:
- <confluence_install>/logs/ (anything recent in this directory)
- <confluence_home>/logs/atlassian-confluence.log
Note: The <confluence_home> directory is the path defined in the following file: <confluence_install>/confluence/WEB-INF/classes/confluence-init.properties
Please create a test server that is a clone of your production Service Desk server and try the Confluence installation there. We will be able to check for out of memory and other errors in the logs, and do tests such as starting from a script in the bin directory instead of the service and starting one application at a time to isolate and eventually resolve the issue.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.