Details
-
Type:
Task
-
Status: Closed (View Workflow)
-
Priority:
Major
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: None
-
Labels:None
-
Story Points:3
-
Epic Link:
-
Sprint:Fall 4 2022 Oct 10, Fall 5 2022 Oct 24, Spring 6 2023 Mar 20
Description
Situation: Jira keeps going down with a 503.
Task: Determine why Jira is going down.
Note:
To restart the Jira server:
- log into the jira host using ssh as user "ec2-user"
- change to root user (sudo su)
- change to the "bin" directory, located here: /home/ec2-user/jira/atlassian-jira-software-7.0.11-standalone/bin
- let the server shut down properly, just in case it is still running, by executing the "stop jira" script: stop-jira.sh
Note that if the server has crashed, probably there is still a "stale" PID file. If so, when you attempt to stop jira, the script will print that there is a stale PID file.
- Restart jira by running the "start jira" script: start-jira.sh
To enable Nowlan Freese to carry out the above workflow I did this:
- Added his public key to the authorized hosts on jira.bioviz.org
- Modifed the EC2 and its attached security group "jira3" to enable him to restart the the EC2 and also modify its security group
- Used the IAM policy simulator on AWS to check if his user name can edit the security group, which confirmed that he can do it.
Attachments
Activity
| Field | Original Value | New Value |
|---|---|---|
| Epic Link | IGBF-2323 [ 18477 ] |
| Status | To-Do [ 10305 ] | In Progress [ 3 ] |
| Description |
Situation: Jira keeps going down with a 503.
Task: Determine why Jira is going down. |
Situation: Jira keeps going down with a 503.
Task: Determine why Jira is going down. Note: To restart the Jira server: * log into the jira host using ssh as user "ec2-user" * change to root user (sudo su) * change to the "bin" directory, located here: /home/ec2-user/jira/atlassian-jira-software-7.0.11-standalone/bin * let the server shut down properly, just in case it is still running, by executing the "stop jira" script: stop-jira.sh Note that if the server has crashed, probably there is still a "stale" PID file. If so, when you attempt to stop jira, the script will print that there is a stale PID file. * Restart jira by running the "start jira" script: start-jira.sh |
| Status | In Progress [ 3 ] | Needs 1st Level Review [ 10005 ] |
| Assignee | Ann Loraine [ aloraine ] |
| Assignee | Ann Loraine [ aloraine ] |
| Status | Needs 1st Level Review [ 10005 ] | First Level Review in Progress [ 10301 ] |
| Status | First Level Review in Progress [ 10301 ] | To-Do [ 10305 ] |
| Status | To-Do [ 10305 ] | In Progress [ 3 ] |
| Description |
Situation: Jira keeps going down with a 503.
Task: Determine why Jira is going down. Note: To restart the Jira server: * log into the jira host using ssh as user "ec2-user" * change to root user (sudo su) * change to the "bin" directory, located here: /home/ec2-user/jira/atlassian-jira-software-7.0.11-standalone/bin * let the server shut down properly, just in case it is still running, by executing the "stop jira" script: stop-jira.sh Note that if the server has crashed, probably there is still a "stale" PID file. If so, when you attempt to stop jira, the script will print that there is a stale PID file. * Restart jira by running the "start jira" script: start-jira.sh |
Situation: Jira keeps going down with a 503.
Task: Determine why Jira is going down. Note: To restart the Jira server: * log into the jira host using ssh as user "ec2-user" * change to root user (sudo su) * change to the "bin" directory, located here: /home/ec2-user/jira/atlassian-jira-software-7.0.11-standalone/bin * let the server shut down properly, just in case it is still running, by executing the "stop jira" script: stop-jira.sh Note that if the server has crashed, probably there is still a "stale" PID file. If so, when you attempt to stop jira, the script will print that there is a stale PID file. * Restart jira by running the "start jira" script: start-jira.sh To enable [~nfreese] to carry out the above workflow I did this: * Added his public key to the authorized hosts on jira.bioviz.org * Modifed the EC2 and its attached security group "jira3" to enable him to restart the the EC2 and also modify its security group * Used the IAM policy simulator on AWS to check if his user name can edit the security group, which confirmed that he can do it. |
| Status | In Progress [ 3 ] | Needs 1st Level Review [ 10005 ] |
| Assignee | Ann Loraine [ aloraine ] |
| Assignee | Nowlan Freese [ nfreese ] |
| Sprint | Fall 4 2022 Oct 10 [ 156 ] | Fall 4 2022 Oct 10, Fall 5 2022 Oct 24 [ 156, 157 ] |
| Rank | Ranked higher |
| Assignee | Nowlan Freese [ nfreese ] | Ann Loraine [ aloraine ] |
| Status | Needs 1st Level Review [ 10005 ] | First Level Review in Progress [ 10301 ] |
| Status | First Level Review in Progress [ 10301 ] | Ready for Pull Request [ 10304 ] |
| Status | Ready for Pull Request [ 10304 ] | Pull Request Submitted [ 10101 ] |
| Status | Pull Request Submitted [ 10101 ] | Reviewing Pull Request [ 10303 ] |
| Status | Reviewing Pull Request [ 10303 ] | Merged Needs Testing [ 10002 ] |
| Status | Merged Needs Testing [ 10002 ] | Post-merge Testing In Progress [ 10003 ] |
| Resolution | Done [ 10000 ] | |
| Status | Post-merge Testing In Progress [ 10003 ] | Closed [ 6 ] |
| Resolution | Done [ 10000 ] | |
| Status | Closed [ 6 ] | To-Do [ 10305 ] |
| Sprint | Fall 4 2022 Oct 10, Fall 5 2022 Oct 24 [ 156, 157 ] | Fall 4 2022 Oct 10, Fall 5 2022 Oct 24, Spring 6 2023 Mar 20 [ 156, 157, 166 ] |
| Status | To-Do [ 10305 ] | In Progress [ 3 ] |
| Status | In Progress [ 3 ] | Needs 1st Level Review [ 10005 ] |
| Status | Needs 1st Level Review [ 10005 ] | First Level Review in Progress [ 10301 ] |
| Status | First Level Review in Progress [ 10301 ] | Ready for Pull Request [ 10304 ] |
| Status | Ready for Pull Request [ 10304 ] | Pull Request Submitted [ 10101 ] |
| Status | Pull Request Submitted [ 10101 ] | Reviewing Pull Request [ 10303 ] |
| Status | Reviewing Pull Request [ 10303 ] | Merged Needs Testing [ 10002 ] |
| Status | Merged Needs Testing [ 10002 ] | Post-merge Testing In Progress [ 10003 ] |
| Resolution | Done [ 10000 ] | |
| Status | Post-merge Testing In Progress [ 10003 ] | Closed [ 6 ] |