So I've been running upgrades for jira for a while now and only recently has this issue arose. Whenever I run service jira start or /opt/atlassian/jira/bin/start-jira.sh it immediately fails with the output:
root@jira:/opt/atlassian/jira/bin# ./start-jira.sh
To run JIRA in the foreground, start the server with start-jira.sh -fg
executing using dedicated user: jira
< jira ascii logo>
Atlassian JIRA
Version : 7.11.0
If you encounter issues starting or stopping JIRA, please see the Troubleshooting guide at http://confluence.atlassian.com/display/JIRA/Installation+Troubleshooting+Guide
Server startup logs are located in /opt/atlassian/jira/logs/catalina.out
Using CATALINA_BASE: /opt/atlassian/jira
Using CATALINA_HOME: /opt/atlassian/jira
Using CATALINA_TMPDIR: /opt/atlassian/jira/temp
Using JRE_HOME: /opt/atlassian/jira/jre/
Using CLASSPATH: /opt/atlassian/jira/bin/bootstrap.jar:/opt/atlassian/jira/bin/tomcat-juli.jar
Using CATALINA_PID: /opt/atlassian/jira/work/catalina.pid
Usage: catalina.sh ( commands ... )
commands:
debug Start Catalina in a debugger
debug -security Debug Catalina with a security manager
jpda start Start Catalina under JPDA debugger
run Start Catalina in the current window
run -security Start in the current window with security manager
start Start Catalina in a separate window
start -security Start in a separate window with security manager
stop Stop Catalina, waiting up to 5 seconds for the process to end
stop n Stop Catalina, waiting up to n seconds for the process to end
stop -force Stop Catalina, wait up to 5 seconds and then use kill -KILL if still running
stop n -force Stop Catalina, wait up to n seconds and then use kill -KILL if still running
configtest Run a basic syntax check on server.xml - check exit code for result
version What version of tomcat are you running?
Note: Waiting for the process to end and use of the -force option require that $CATALINA_PID is defined
It doesn't create any logs in /opt/atlassian/jira/logs/* as it doesn't get that far, I've looked at the scripts it invokes and they all seem to be running catalina.sh run. I'm not exactly sure what I might have done as I haven't changed anything while updating. Is my install just broken?
I'm going to start by deleting the /bin folder and upgrading.
Overriding CATALINA_OPTS too early causes this issue
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.