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.
For JSM June Challenge #2, share how your non-technical teams like HR, legal, marketing, finance, and beyond started using Jira Service Management! Tell us: Did they ask to start using it or...
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