Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,467,417
Community Members
 
Community Events
177
Community Groups

Unable to login to Crowd after migrating to new server

I'm setting up a mirror image for Crowd on a separate server for testing the upgrade from 2.0.7 to 2.4.1. I've created a separate MySQL database and imported the data. Initially, I'm able to login using the authentication with the production server, but once I follow the instructions in the link below and modify the crowd.properties file on the test Crowd server and remove the IP address from the production Crowd for the test Crowd server, I can no longer login. when I look at the tables in my test Crowd db, I see my user account name in the listing but it just doesn't let me in. I don't even get anything in the catalina.out file saying it fails or that there was even a warning or error. it simply just doesn't work. Any ideas?

https://confluence.atlassian.com/display/CROWD023/Migrating+Crowd+between+Servers

2 answers

1 accepted

0 votes
Answer accepted

Found that this was an issue with the version we were trying to upgrade to on that particular server. Whatever the cause was exactly I'm not sure, but I chose to upgrade to a different version and that seemed to "unlock" whatever was causing the problem.

0 votes

So this is logging in via the crowd web application you are refering to?

The Crowd web application (console) is actually a crowd client registered with the crowd server (i.e. under the Application tab)

If you look on your production server, Applications->Crowd->Remote Addresses you will probably find it has your production IP in there.

When you migrated crowd server (staging) is seeing you attempt to log in from another crowd console that it doesn't have the IP configured under that Remote Address.

So can you confirm that you indeed DID add the new server's IP to the remote addresses on the production server BEFORE migrating the data. (Under the Preparation section in that link you posted)

Yes, I did add the new server's IP address to the remote addresses on the production server prior to migrating. The IP address was/is showing up on the new server's remote IP address listing after I did the migration and brought it up. But once I go back to the production system and remove the new server's IP address I can no longer log in with the same credentials that work on production.

Another thing to check, your new server's install isn't pointing at the production crowd's home directory is it? and therefore picking up the old crowd.properties file?

No, it is looking at it's own home location. They are very different locations just to ensure that doesn't happen. I recently did another installation and export to ensure that the steps were performed exactly as required and I'm still having the same problem.

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events