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
After upgrading Crowd 2.0.7 to 2.5.1 yesterday I've seen a SQL error a couple times in atlassian-crowd.log. See attached stack trace. (actually seen it twice, ~24hrs between.)
Looks like a uniqe constraint violation in table cwd_token.
Can this be fixed easily in a nice way?
(Or hacker-style: Stop crowd & clear table?)
Otherwise Crowd seems to be working fine after the upgrade. But it would be nice to not have this error in logfile.
I would suggest the SQL approach, unless you can find the row in question that is causing the violation, and removing just that record.
Removing all tokens would logout all sessions for all users + applications currently using Crowd for authentication.