Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Jira datacenter- Can't login after a database failover or backup xml restore

Hello Jira users, 

Wanted to share my experience with one particular behavior of Jira that I have encountered multiple times and was able to fix with the same steps.

Problem: 

After a database failover(due to production database crash or not an unplanned failover), users even Jira-administrators, can't log into Jira. Error: Sorry username or password incorrect.

This error also occurs when you restore from backup xml from one Jira instance to another(where the cluster nodes are different)

Solution:

Check clusternode database table. When you restore from backup XML, it includes the entries of  clusternode table which has hostnames and status(OFFLINE/ACTIVE) of the source Jira instance. They do not match the cluster or node hostnames on the destination Jira instance.

select * from clusternode

When you can't log in: 

NODEID, STATUS, TIMESTAMP, IP, CACHE_LISTENER_PORT, NODE_BUILD_NUMBER, NODE_VERSION

node1 OFFLINE 1621274609792 destinationnode01  40001 805004 8.5.4
node2 ACTIVE 1622135262959   sourcenodejiradc01 40001 805004 8.5.4

What to rectify?

  •  Make sure the status of the node match the actual status in Jira cluster. If a node says active, it needs to be up and running in the cluster. If its not up and running change the status to OFFLINE.
  • Make sure the IP matches to that of the destination Jira instance(or where you are hosted). Remove the ones which show source node hostnames or different hosts not belonging to the cluster.
  • During an unplanned failover, the correct status of clusternodes don't copy over correctly, in that case the hostnames might be correct but check their status.

You can use simple update SQLs to do that.

Restart your Jira instance or in some cases no need to restart as well, you will be able to log into Jira.

When you CAN log in, the entries must look this way:

NODEID, STATUS, TIMESTAMP, IP, CACHE_LISTENER_PORT, NODE_BUILD_NUMBER, NODE_VERSION

node1 OFFLINE 1621274609792 destinationnode01  40001 805004 8.5.4
node2 ACTIVE 1622135262959  destinationnode02  40001 805004 8.5.4

node2 or destinationnode02  - is up and running .

node1 or destinationnode01 - is not yet started.

 

Please let me know if you have tried other ways to solve this mystery.

Thank you for reading.

Regards,

Divya TV

 

 

 

0 comments

Comment

Log in or Sign up to comment
TAGS
Community showcase
Published in Confluence

Introducing External Collaboration for Confluence

We’re excited to introduce external collaboration for Confluence, now available in early access. It is available to preview for Confluence Cloud Premium and Enterprise customers. (If you're not on ...

230 views 0 8
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you