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/stop-confluence.sh (code=exited, status=1/FAILURE)
Process: 1917 ExecStart=/confluence/atlassian-confluence-6.9.1/bin/start-confluence.sh (code=exited, status=0/SUCCESS) Main PID: 1958 (code=exited, status=1/FAILURE)
Nov 22 12:39:44 vmanager3045.premium-vserver.net stop-confluence.sh[1961]: If you encounter issues starting up ConfluencNov 22 12:39:44 vmanager3045.premium-vserver.net stop-confluence.sh[1961]: Server startup logs are located in /confluencNov 22 12:39:44 vmanager3045.premium-vserver.net stop-confluence.sh[1961]: ---------------------------------------------Nov 22 12:39:44 vmanager3045.premium-vserver.net stop-confluence.sh[1961]: Using Java: /usr/bin/java
Nov 22 12:39:45 vmanager3045.premium-vserver.net stop-confluence.sh[1961]: 2018-11-22 12:39:45,596 INFO [main] [atlassiaNov 22 12:39:45 vmanager3045.premium-vserver.net stop-confluence.sh[1961]: ---------------------------------------------Nov 22 12:39:45 vmanager3045.premium-vserver.net stop-confluence.sh[1961]: PID file found but either no matching processNov 22 12:39:45 vmanager3045.premium-vserver.net systemd[1]: confluence.service: Control process exited, code=exited staNov 22 12:39:45 vmanager3045.premium-vserver.net systemd[1]: confluence.service: Unit entered failed state.
Nov 22 12:39:45 vmanager3045.premium-vserver.net systemd[1]: confluence.service: Failed with result 'exit-code'.
]
the configuration is as described here:
https://confluence.atlassian.com/confkb/run-confluence-as-a-systemd-service-on-linux-937177781.html
Any suggestion??
Hello Hans-Georg,
this suggestion https://jira.atlassian.com/browse/CONFSERVER-54291 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 ...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.