show's these error on sudo systemctl start jira.service
Job for jira.service failed because the control process exited with error code. See "systemctl status jira.service" and "journalctl -xe" for details.
Hello @Shivaji Pawar
Welcome to Atlassian Community!
The error message you shared is not very meaningful. We need more logs details from INSTALLATION_PATH/logs/catalina.out file.
But you can try the following steps. (Pleaze make sure that you don't have an other service, not Jira, runnig under the same server)
check if there is a jira job that is up via this command
#ps v -C java
If you have results you need to kill manually the job via this command and using the PID shown in previous command
#kill -9 PID
Then you can try to start jira.
Regards,
Seif,
Hello @Shivaji Pawar ! Welcome to the Atlassian Community!
A few questions I have to ask:
1. What happens when you start Jira manually?
2. What does the Catalina.out and the Jira logs show?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
i have the same issue. I have two servers in a cluster.
Alpha node works perfectly.
Omega node is not starting with "systemctl" command. It works only with basic "service jira start" option.
LOGS are pointing to "Connect timed out" , "Host unreachable" errors.
I am also getting Cluster Cache Replication errors. I tried all the documents but not helping.
Kindly help.
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.