Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal


  • Give kudos
  • Received
  • Given


  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Failure when starting confluence service on vServer with systemctl

Starting and stopping confluence service on my vServer works perfect manually.

Now I wanted to start the service when the system starts and using systemctl

[systemctl status confluence
● confluence.service - Confluence
   Loaded: loaded (/etc/systemd/system/confluence.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Do 2018-11-22 12:39:45 CET; 1s ago
  Process: 1961 ExecStop=/confluence/atlassian-confluence-6.9.1/bin/ (code=exited, status=1/FAILURE)
  Process: 1917 ExecStart=/confluence/atlassian-confluence-6.9.1/bin/ (code=exited, status=0/SUCCESS) Main PID: 1958 (code=exited, status=1/FAILURE)

Nov 22 12:39:44[1961]: If you encounter issues starting up ConfluencNov 22 12:39:44[1961]: Server startup logs are located in /confluencNov 22 12:39:44[1961]: ---------------------------------------------Nov 22 12:39:44[1961]: Using Java: /usr/bin/java
Nov 22 12:39:45[1961]: 2018-11-22 12:39:45,596 INFO [main] [atlassiaNov 22 12:39:45[1961]: ---------------------------------------------Nov 22 12:39:45[1961]: PID file found but either no matching processNov 22 12:39:45 systemd[1]: confluence.service: Control process exited, code=exited staNov 22 12:39:45 systemd[1]: confluence.service: Unit entered failed state.
Nov 22 12:39:45 systemd[1]: confluence.service: Failed with result 'exit-code'.

the configuration is as described here:

Any suggestion??


1 answer

Hello Hans-Georg,

this suggestion might be helpful.

Hi Johan, thank you for the link. I followed this already, but did not provide any improvement.It seems that the ExecStop is the issue ...

Problem solved:

In the connector block for https, I forgot to move the /> to the end of the keystore file path. 

Port 8443 is now open.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Confluence

Announcing Team Calendars in Confluence Data Center

Hi Community! We're thrilled to share that Team Calendars for Confluence is now a built-in feature for Confluence Data Center releases 7.11 and beyond.  A long time favorite,  Team Cale...

199 views 0 6
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you