Confluence currently works as a service with System V's init.d . With more and more OS slowly moving to the more modern systemd approach (see: https://blog.ambientia.fi/2014/06/09/managing-confluence-as-a-service-with-systemd/ ), we need to also cater for this change.

As a workaround, you can follow the instructions written by Jussi Haaja here:

My solution can be downloaded from: http://jussiha.staff.ambientia.fi/downloads/confluence-tomcat-systemd.zip , place files in directory libexec to /usr/libexec/ambtomcat, the sysconfig/confluence file to /etc/sysconfig and system/confluence.service to /etc/systemd/system. All configuration related to service (JAVA_OPTS etc.) is done in /etc/sysconfig/confluence, which means that the traditional way of configuring Tomcat startup parameters via setenv.sh is not utilized at all. If you are not using Fedora 20, you also need the file /usr/share/java-utils/java-functions from package javapackages-tools to use this solution. To get the file, see the Fedora package sources here.

Review both the sysconfig and the service file so that the file paths reflect your installation. After you are done, Confluence can be started by invoking systemctl start confluence. Review that the startup works by using journalctl –f –u confluence.service