Embedded Files
Jira Directory Structure
Jira Directory Structure
/var/atlassian/application-data/jira/
/var/atlassian/application-data/jira/
cluster.properties
dbconfig.xml
log
monitor
plugins
caches/indexesV1
caches/insight_indexes
customisations/conf
customisations/bin
customisations/atlassian-jira/WEB-INF
customisations/baseline-hash-registry.properties
/opt/atlassian/jira-servicedesk/current/logs
/opt/atlassian/jira-servicedesk/current/logs
All files are suffixed with a date. Older files may also be compressed using gzip (.gz suffix)
access_log.YYY-MM-DD
atlassian-jira-gc-YYYY-MM-DD_HH24-MI-SS.log
catalina.YY-MM-DD.log
/media/atl/jira/shared
/media/atl/jira/shared
jira-servicedesk.version
jira-config.properties
export
import
caches
data/assets
data/attachments
data/avatars
data/insight
log
logos
node-status
plugins/installed_plugins
scriptrunner
CloudFormation Stack UPDATE_FAILED
CloudFormation Stack UPDATE_FAILED
Export EXPORT_NAME cannot be updated as it is in use by STACK_NAME
Export EXPORT_NAME cannot be updated as it is in use by STACK_NAME
Tentative working theory: the AMI ID of the Bastion Host is a different AMI ID to all other Bastion Hosts built by the Quickstart template over the last three years (all others match).. so Cloudformation is not recognising that it needs to update the existing Bastion and is, instead, creating another (which then fails to be terminated as part of the rollback steps).
Irrespective of whether this working theory is right or wrong, what we do know is that Cloudformation appears to be updating the Bastion in the VPCStack when we wouldn't expect it to.
In this case, the error was preventing a Jira Upgrade.
Irrespective of whether this working theory is right or wrong, what we do know is that Cloudformation appears to be updating the Bastion in the VPCStack when we wouldn't expect it to.
In this case, the error was preventing a Jira Upgrade.
Workaround
Workaround
In the AWS console...
Services - CloudFormation
Find the nested stack for the Jira Service Desk nodes and click Update (and confirm you wish to update the nested stack)
Use current template
Set Use Bastion host to false
Click through the following pages then Update
According to the Atlassian docs, this will remove the ability to connect to the Jira nodes via the Bastion host, but will allow you to continue with your initial task (i.e a Jira Upgrade). In my testing, I was still able to ssh tunnel via the Bastion to the new Jira nodes.
To reinstate Bastion access...
TODO
Bibliography
Bibliography
https://confluence.atlassian.com/adminjiraserver/jira-application-home-directory-938847746.htmlhttps://community.atlassian.com/t5/Jira-Software-questions/remove-growing-log-files/qaq-p/1647356https://confluence.atlassian.com/support/create-a-support-zip-790796819.htmlhttps://www.epochconverter.com/
Performancehttps://confluence.atlassian.com/enterprise/jira-data-center-size-profiles-955171062.htmlhttps://confluence.atlassian.com/adminjiraserver/performance-and-scale-testing-965568707.htmlhttps://confluence.atlassian.com/kb/performance-troubleshooting-tools-best-practice-652444218.htmlhttps://confluence.atlassian.com/jirakb/using-jvmtop-to-analyze-jira-performance-740098869.html
https://confluence.atlassian.com/enterprise/performance-testing-framework-for-confluence-935577039.htmlhttps://confluence.atlassian.com/enterprise/confluence-data-center-sample-performance-test-946041232.htmlhttps://confluence.atlassian.com/enterprise/data-center-performance-monitoring-946040739.html
https://www.adaptavist.com/blog/performance-tuning-atlassian-3-use-a-reverse-proxy/https://www.adaptavist.com/blog/monitoring-atlassian-performance-tuning-4/
Monitoringhttps://confluence.atlassian.com/enterprise/jira-data-center-sample-deployment-and-monitoring-strategy-953148860.htmlhttps://confluence.atlassian.com/enterprise/getting-started-with-data-center-monitoring-946040846.htmlhttps://confluence.atlassian.com/enterprise/tools-for-monitoring-your-data-center-application-942851919.htmlhttps://confluence.atlassian.com/enterprise/data-center-performance-monitoring-946040739.html
JMX/Zabbixhttps://confluence.atlassian.com/doc/live-monitoring-using-the-jmx-interface-150274182.htmlhttps://confluence.atlassian.com/adminjiraserver/live-monitoring-using-the-jmx-interface-939707304.htmlhttps://docs.oracle.com/javase/7/docs/technotes/guides/management/agent.html
HealthCheckhttps://confluence.atlassian.com/enterprise/jira-data-center-health-check-tools-644580752.html
HealthCheck: Shared Homehttps://confluence.atlassian.com/jirakb/healthcheck-shared-home-738722489.html
CloudFormationhttps://confluence.atlassian.com/jirakb/how-to-remove-the-bastion-host-from-an-existing-aws-quick-start-deployment-1005337522.htmlhttps://aws.amazon.com/premiumsupport/knowledge-center/cloudformation-stack-export-name-error/
504 Gateway Time-outhttps://community.atlassian.com/t5/Jira-questions/504-Gateway-Time-out-when-logging-into-to-JIRA/qaq-p/1204291
Performancehttps://confluence.atlassian.com/enterprise/jira-data-center-size-profiles-955171062.htmlhttps://confluence.atlassian.com/adminjiraserver/performance-and-scale-testing-965568707.htmlhttps://confluence.atlassian.com/kb/performance-troubleshooting-tools-best-practice-652444218.htmlhttps://confluence.atlassian.com/jirakb/using-jvmtop-to-analyze-jira-performance-740098869.html
https://confluence.atlassian.com/enterprise/performance-testing-framework-for-confluence-935577039.htmlhttps://confluence.atlassian.com/enterprise/confluence-data-center-sample-performance-test-946041232.htmlhttps://confluence.atlassian.com/enterprise/data-center-performance-monitoring-946040739.html
https://www.adaptavist.com/blog/performance-tuning-atlassian-3-use-a-reverse-proxy/https://www.adaptavist.com/blog/monitoring-atlassian-performance-tuning-4/
Monitoringhttps://confluence.atlassian.com/enterprise/jira-data-center-sample-deployment-and-monitoring-strategy-953148860.htmlhttps://confluence.atlassian.com/enterprise/getting-started-with-data-center-monitoring-946040846.htmlhttps://confluence.atlassian.com/enterprise/tools-for-monitoring-your-data-center-application-942851919.htmlhttps://confluence.atlassian.com/enterprise/data-center-performance-monitoring-946040739.html
JMX/Zabbixhttps://confluence.atlassian.com/doc/live-monitoring-using-the-jmx-interface-150274182.htmlhttps://confluence.atlassian.com/adminjiraserver/live-monitoring-using-the-jmx-interface-939707304.htmlhttps://docs.oracle.com/javase/7/docs/technotes/guides/management/agent.html
HealthCheckhttps://confluence.atlassian.com/enterprise/jira-data-center-health-check-tools-644580752.html
HealthCheck: Shared Homehttps://confluence.atlassian.com/jirakb/healthcheck-shared-home-738722489.html
CloudFormationhttps://confluence.atlassian.com/jirakb/how-to-remove-the-bastion-host-from-an-existing-aws-quick-start-deployment-1005337522.htmlhttps://aws.amazon.com/premiumsupport/knowledge-center/cloudformation-stack-export-name-error/
504 Gateway Time-outhttps://community.atlassian.com/t5/Jira-questions/504-Gateway-Time-out-when-logging-into-to-JIRA/qaq-p/1204291
Page updated
Google Sites
Report abuse