HTTPs not starting after underlying system restart/shutdown

[Dan]

Hi,

I am hosting a containerized Confluence (server) v7.0.1 configured with HTTPs and its own certificate on a server. The Docker image that I am using is atlassian/confluence-server.

All works well until I have to shutdown/restart the server. If one of those 2 operations are required, the HTTPs Confluence is not starting by default - just HTTP. After the server is booting up, Confluence is accessible via HTTP, but not also the HTTPs.

The workaround that I have found was:

- Delete the /var/atlassian/application-data/confluence/lock file;

- Change the port mentioned as "THIS PORT" with a new port in /opt/atlassian/confluence/conf/server.xml row <Server port="<THIS PORT>" shutdown="SHUTDOWN">

- Stop and start again Confluence /opt/atlassian/confluence/bin/stop-confluence.sh && /opt/atlassian/confluence/bin/start-confluence.sh

I would like to avoid this operation in the future as it takes a while until I have Confluence back again with HTTPs enabled.

Is any way that I can solve this issue?

Please let me know if you need any additional information.

Best regards,

Dan

[sukkeong]

You can add Confluence as a service. This is usually done as part on the installation process - there is a prompt if I remember...

Otherwise, you can add the start/stop script in /etc/init.d. Here is an example that was generated as part of the installation process for JIRA. Just change to reflect your installation (I have removed the actual installation path

#!/bin/bash

# JIRA Linux service controller script
cd "/<jira_installation_path>/bin"

case "$1" in
  start)
    ./start-jira.sh
    ;;
  stop)
    ./stop-jira.sh
    ;;
  *)
    echo "Usage: $0 {start|stop}"
    exit 1
    ;;
esac

[Dan]

@sukkeong thanks for your reply. In the containerized version, I have not seen any prompt to select installing Confluence as a service.

I would prefer a fix with a configuration in UI or in some files rather than fixing it with a cronjob. For some reason, if I am doing all these changes from the ticket's description too fast, I am getting this strange error:

23-Feb-2020 09:23:29.122 WARNING [Catalina-utility-4] org.apache.catalina.valves.StuckThreadDetectionValve.notifyStuckThreadDetected Thread [https-jsse-nio-8443-exec-9] (id=[248]) has been active for [69,478] milliseconds (since [2/23/20 9:22 AM]) to serve the same request for [https://localhost:443/plugins/macrobrowser/browse-macros.action?detailed=false&macroMetadataClientCacheKey=1582448914693] and may be stuck (configured threshold for this StuckThreadDetectionValve is [60] seconds). There is/are [3] thread(s) in total that are monitored by this Valve and may be stuck.

Therefore, beside calculating the threshold until I can trigger a cron-job with all those steps inside, I would prefer a fix in UI or in some Confluence files.