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,463,666
Community Members
 
Community Events
176
Community Groups

very slow authentication to Crowd 2.7.2

Hi, I have crowd 2.7.2 and mysql 5.1 on the same linux (rhel6) server. We have several applications linking to it just fine. In the past year or so, I noticed authentication to the crowd gui itself with my admin credentials take 1-5 minutes... and if I am inactive for 30 seconds or so, I have to repeat this hellish login. Had the same issue with crowd 2.6 - though it hasn't always been this bad. I haven't upgraded the mysql DB. Note: I thought it might me a reverse dns lookup issue . But nope , mysql is not performing reverse dns lookup. Heap settings look good on crowd application . Mysql user grants are not using hostnames..but localhost or specific up addresses. I'm stumped . Is this some mysql issue? We have several directories , only one is ldap though... an active directory connection to an ADAM server .. which has worked fine for years. Our user base, including disabled users, is under 4000. Any tips much appreciated . Makes admin tasks in crowd a nightmare.

2 answers

1 accepted

0 votes
Answer accepted

Please raise a support case at https://support.atlassian.comand our friendly support team will help you collect information and troubleshoot based on your configuration and logs. (This QA site isn't well suited to back and forth troubleshooting due to its public nature.)

Thanks - I did. I will post if anything interesting comes out of it.
0 votes

This is a provisional answer: When I granted all privileges on the crowd mysql user, the problem went away. Perhaps I was missing a necessary permission. Still need to see how it plays out though. :)

actually -- scratch that. Still encountering issue.

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events