Service JIRA

Location

• Staging: djoum/XSEDE
• Production: batouri/XSEDE

Description of the service

Issue tracker.

How to access it

• http://issues.openmrs.org/
• http://issues-stg.openmrs.org/

How to restart it

sudo service jira restart

Logs location

sudo su -

su - jira

tail -f /opt/jira/logs/catalina.out

tail -f /opt/jira-data/logs/atlassian*.log

#Backup Jira using the GUI

Create a maintenance outage in status.io and announce the outage in talk.

sudo su -

su - jira

vim /opt/jira/conf/setenv.sh
change JVM_MINIMUM_MEMORY="4g"
change JVM_MAXIMUM_MEMORY="5g"
Jira needs at least this much JVM to successfully run the GUI xml backup.

vim /opt/confluence/conf/server.xml #and look for this line <Context path="" docBase="${catalina.home}/atlassian-jira" reloadable="false" useHttpOnly="true">
change path="" to path="/jira" #this will make sure nobody can access jira and only you can.

/opt/jira/bin/.stop-jira.sh

/opt/jira/bin/.start-jira.sh

After jira starts again, go to https://issues.openmrs.org/jira and log-in go to Systems in the wrench on the right and log-in once again. Look for backup on the left and click on it. use filename "jira-backup-YYYY-MM-DD" and click backup. you can tail the logs to see how it goes but, the GUI does not give you a status, so you will have to watch it until its done. once its done you will need to change the JVM to the original values and change setenv.sh PATH="" and restart jira.