You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
Hi I am using jira and confluence datacenters in aws cloud.i wanted to make some configaration changes in log4j.properties and web.xml files.we are usng autosacling groups for the both datacenters as well,after i make the necessary changes in the nodes and restart the confluence the node which i made changes is getting terminated whwnever i restart the confluence service and its been hard.Please let me know whats the reason is there any feature like the nodes get destroyed when ever we restart the confluence service and spins up a new node
You could try reverting the changes in the config files and see if you can restart Jira and Confluence. If that works, I suspect a bad file edit. If it doesn't work then you can start debugging the real problem
Greetings for the day !
Please provide more datails. e.g. product version, logs, changes which you are doing.. etc.
Please raise ticket with Atlassian Support as well.
We will revert you soon.