Cannot find a duplicate user

[Robert Egan]

After the last upgrade (JIRA 8.20.3) health check reported a duplicate user account. The problem is, I have only been able to find one account, in the Crowd directory. Any ideas for finding the duplicate, or is the Duplicate Users health check broken?

[Alexis Robert · Accepted solution]

Hi @Robert Egan ,

what I usually do in this case is go to the database and get the entire directory information : 

select * from cwd_user

And import the result (simple copy and paste) in Excel. Then you can just use the "Duplicates" function to get the duplicate user.

Let me know if this helps, 

--Alexis

[Robert Egan]

Not sure why it did not show in the UI, but a SQL query did find the duplicate user. It was in local directory and the Crowd directory.

[Tim Perrault]

Good to hear. Also check out this link to use the REST API. Forgot to add that to my answer on how I found the duplicate users.

[Tim Perrault]

Hi @Robert Egan 

I had this same issue. I fixed the duplicate users but the warning still showed up until I restarted the application.

Please be mindful that even after deleting the duplicate user accounts, the health check will still show as failing as it runs only once a week. If you'd like a quicker update, please restart JIRA for a faster update

Thanks,

Tim

[Mike DESILE Positive]

Hi, same issue for me (8.20.5). I reset cache by adding and removing a new directory, use the link provide upper and check in database with this SQL :

select count(user_key), user_key from app_user group by user_key having count(user_key)>0

But the error still there...

@atlassian , is there an issue here ?

[Tim Perrault]

Did you restart the Jira application after you did the fix?

[Mike DESILE Positive]

Of course not, this is a Production instance. We'll se after the next maintenance operation.

But in TEST environement YES, but error still there...

[Tim Perrault]

Do you know the last time the application was restarted?

Basically the check happens weekly. So let's say the server was restarted Monday at 3:30pm. It will run the check then, but then it won't run again until the following Monday or if you restart before then.