Tom cat restarted but application won't start Jira

Bongani Hermans_2opknp

I am new in linux so not sure what to do, was running some tests and had to restart Tom cat for the changes to take place.

$CATALINA_PID was set but the specified file does not exist. Is Tomcat running? Stop aborted

I then removed the file catalina and tom cat started but now application hasn't started.

logs:

[mcaadmin@uatjrap1v logs]$ tail catalina.out
2020-04-11 14:46:34,055 Caesium-1-4 INFO [c.a.jira.upgrade.UpgradeScheduler] Running scheduled upgrades
2020-04-11 14:46:34,079 Caesium-1-4 INFO [c.a.jira.upgrade.LoggingUpgradeService] run upgrades has started
2020-04-11 14:46:34,575 Caesium-1-4 INFO [c.a.j.upgrade.util.BuildNumberDao] Setting current build number to 8010002020-04-11 14:46:34,590 Caesium-1-4 INFO [c.a.jira.upgrade.UpgradeIndexManager] There is no reindex requests of type [IMMEDIATE, DELAYED] so none will be run
2020-04-11 14:46:34,590 Caesium-1-4 INFO [c.a.j.upgrade.util.BuildNumberDao] Setting current version to 8.1.0
2020-04-11 14:46:34,596 Caesium-1-4 INFO [c.a.j.upgrade.util.BuildNumberDao] Setting downgrade version to 7.1.2
2020-04-11 14:46:34,603 Caesium-1-4 INFO [c.a.jira.upgrade.LoggingUpgradeService] run upgrades has finished successfully, and took 524 milliseconds to process.
2020-04-11 14:46:34,603 Caesium-1-4 INFO [c.a.jira.upgrade.UpgradeScheduler] JIRA upgrades completed successfully
2020-04-11 14:46:34,608 Caesium-1-4 INFO [c.a.jira.upgrade.UpgradeScheduler] Plugins upgrades completed successfully
2020-04-11 14:46:34,609 Caesium-1-4 INFO [c.a.jira.upgrade.UpgradeIndexManager] Reindexing is not allowed after this upgrade and there is no immediate reindex requests
[mcaadmin@uatjrap1v logs]$ tail catalina.out -f
2020-04-11 14:46:34,055 Caesium-1-4 INFO [c.a.jira.upgrade.UpgradeScheduler] Running scheduled upgrades
2020-04-11 14:46:34,079 Caesium-1-4 INFO [c.a.jira.upgrade.LoggingUpgradeService] run upgrades has started
2020-04-11 14:46:34,575 Caesium-1-4 INFO [c.a.j.upgrade.util.BuildNumberDao] Setting current build number to 801000
2020-04-11 14:46:34,590 Caesium-1-4 INFO [c.a.jira.upgrade.UpgradeIndexManager] There is no reindex requests of type [IMMEDIATE, DELAYED] so none will be run
2020-04-11 14:46:34,590 Caesium-1-4 INFO [c.a.j.upgrade.util.BuildNumberDao] Setting current version to 8.1.0
2020-04-11 14:46:34,596 Caesium-1-4 INFO [c.a.j.upgrade.util.BuildNumberDao] Setting downgrade version to 7.1.2
2020-04-11 14:46:34,603 Caesium-1-4 INFO [c.a.jira.upgrade.LoggingUpgradeService] run upgrades has finished successfully, and took 524 milliseconds to process.
2020-04-11 14:46:34,603 Caesium-1-4 INFO [c.a.jira.upgrade.UpgradeScheduler] JIRA upgrades completed successfully
2020-04-11 14:46:34,608 Caesium-1-4 INFO [c.a.jira.upgrade.UpgradeScheduler] Plugins upgrades completed successfully
2020-04-11 14:46:34,609 Caesium-1-4 INFO [c.a.jira.upgrade.UpgradeIndexManager] Reindexing is not allowed after this upgrade and there is no immediate reindex requests

 

When attempting to start I get :

Server startup logs are located in /opt/mcaadmin/atlassian-jira-software-8.1.0-standalone/logs/catalina.out
Using CATALINA_BASE: /opt/mcaadmin/atlassian-jira-software-8.1.0-standalone
Using CATALINA_HOME: /opt/mcaadmin/atlassian-jira-software-8.1.0-standalone
Using CATALINA_TMPDIR: /opt/mcaadmin/atlassian-jira-software-8.1.0-standalone/temp
Using JRE_HOME: /usr/lib/jvm/java
Using CLASSPATH: /opt/mcaadmin/atlassian-jira-software-8.1.0-standalone/bin/bootstrap.jar:/opt/mcaadmin/atlassian-jira-software-8.1.0-standalone/bin/tomcat-juli.jar
Using CATALINA_PID: /opt/mcaadmin/atlassian-jira-software-8.1.0-standalone/work/catalina.pid
Existing PID file found during start.
Unable to read PID file. Start aborted.
[mcaadmin@uatjrap1v bin]$

 

When I stop I get : 

If you encounter issues starting or stopping JIRA, please see the Troubleshooting guide at https://docs.atlassian.com/jira/jadm-docs-081/Troubleshooting+installation

Server startup logs are located in /opt/mcaadmin/atlassian-jira-software-8.1.0-standalone/logs/catalina.out
Using CATALINA_BASE: /opt/mcaadmin/atlassian-jira-software-8.1.0-standalone
Using CATALINA_HOME: /opt/mcaadmin/atlassian-jira-software-8.1.0-standalone
Using CATALINA_TMPDIR: /opt/mcaadmin/atlassian-jira-software-8.1.0-standalone/temp
Using JRE_HOME: /usr/lib/jvm/java
Using CLASSPATH: /opt/mcaadmin/atlassian-jira-software-8.1.0-standalone/bin/bootstrap.jar:/opt/mcaadmin/atlassian-jira-software-8.1.0-standalone/bin/tomcat-juli.jar
Using CATALINA_PID: /opt/mcaadmin/atlassian-jira-software-8.1.0-standalone/work/catalina.pid
cat: /opt/mcaadmin/atlassian-jira-software-8.1.0-standalone/work/catalina.pid: Permission denied
PID file found but either no matching process was found or the current user does not have permission to stop the process. Stop aborted.
[mcaadmin@uatjrap1v bin]$

 

I am still new in linux not sure what I did wrong. Please advise

Mehmet A _Bloompeak_

Hi @Bongani Hermans ,

The line below is the reason. The user starting the tomcat does not have permission to access the pid file. You can give permission for the user or you can try deleting the pid file and then start tomcat.

/opt/mcaadmin/atlassian-jira-software-8.1.0-standalone/work/catalina.pid