Gerrit - failed to sign in: Cannot assign external ID

[Mark Derricutt]

Hi all,

One of our gerrit users seems to be able to login anymore, I see in the error log file:

INFO  com.google.gerrit.httpd.auth.ldap.LdapLoginServlet : 'abhishekr' failed to sign in: Cannot assign external ID "gerrit:abhishekr" to account 1000017; external ID already in use."

this entry repeats about 10 times with different (consecutively increaseing) account ids mentioned, none of them in the account reviewdb table.

This is with Gerrit 2.13.8 ( have been holding off upgrading til 2.15's out ).

Has anyone seen this before or explain what may have happened? Earlier in the week we had some issues with connections to the postgresql db and restarted the server, and everything seems good for all users expect this one.

Cheers,
Mark

---

"The ease with which a change can be implemented has no relevance at all to whether it is the right change for the (Java) Platform for all time." — Mark Reinhold.

Mark Derricutt
http://www.theoryinpractice.net
http://www.chaliceofblood.net
http://plus.google.com/+MarkDerricutt
http://twitter.com/talios
http://facebook.com/mderricutt

[Björn Pedersen]

Hi,

this seems like a know problem:
https://bugs.chromium.org/p/gerrit/issues/detail?id=5090

Mostly, this has to do with case-mismatches (the logins are case-sensitive)

Björn

[thomasmu...@yahoo.com]

Hi, please try gerrit 2.13.9 please.

This includes a fix so it dosent read from the index rather it reads from the db now.

[Mark Derricutt]

On 25 Jan 2018, at 20:35, 'Björn Pedersen' via Repo and Gerrit Discussion wrote:

this seems like a know problem: 
https://bugs.chromium.org/p/gerrit/issues/detail?id=5090

Resolved. Upgrading to 2.13.9 didn't help, but re-running the account reindex did after upgrading to .9. Strange that this issue cropped up over the Christmas break with no changes in the servers.

All sorted now tho :)

Cheers

[David Ostrovsky]

On Wednesday, January 31, 2018 at 12:11:18 AM UTC+1, Mark Derricutt wrote:

On 25 Jan 2018, at 20:35, 'Björn Pedersen' via Repo and Gerrit Discussion wrote:

this seems like a know problem: 
https://bugs.chromium.org/p/gerrit/issues/detail?id=5090

Resolved. Upgrading to 2.13.9 didn't help, but re-running the account reindex did after upgrading to .9. Strange that this issue cropped up over the Christmas break with no changes in the servers.

This resembles me this issue, that was fixed on stable-2.14,

and even applied to stable-2.13 too, but there was not official

release any more that included this change: [1].

Another important fix is: [2]. That why I would suggest to use

gerrit.war from GerritFroge CI instead, that includes all outstanding

fixes on stable-2.13 branch: [3]:

  $ git log --oneline v2.13.9..stable-2.13 | wc -l

  17

[1] https://gerrit-review.googlesource.com/#/c/gerrit/+/138775

[2] https://gerrit-review.googlesource.com/#/c/gerrit/+/133235

[3] https://gerrit-ci.gerritforge.com/view/Gerrit/job/Gerrit-buck-stable-2.13/166

[David Pursehouse]

On Sun, Feb 4, 2018 at 6:19 PM David Ostrovsky <david.o...@gmail.com> wrote:

On Wednesday, January 31, 2018 at 12:11:18 AM UTC+1, Mark Derricutt wrote:

On 25 Jan 2018, at 20:35, 'Björn Pedersen' via Repo and Gerrit Discussion wrote:

this seems like a know problem: 
https://bugs.chromium.org/p/gerrit/issues/detail?id=5090

Resolved. Upgrading to 2.13.9 didn't help, but re-running the account reindex did after upgrading to .9. Strange that this issue cropped up over the Christmas break with no changes in the servers.

This resembles me this issue, that was fixed on stable-2.14,

and even applied to stable-2.13 too, but there was not official

release any more that included this change: [1].

I'm in the process of fixing a couple of issues with 2.13.x and when they are done I'm planning to release 2.13.10 which will include that fix and a few others that have been submitted on stable-2.13 following 2.13.9

 

Another important fix is: [2]. That why I would suggest to use

gerrit.war from GerritFroge CI instead, that includes all outstanding

fixes on stable-2.13 branch: [3]:

  $ git log --oneline v2.13.9..stable-2.13 | wc -l

  17

[1] https://gerrit-review.googlesource.com/#/c/gerrit/+/138775

[2] https://gerrit-review.googlesource.com/#/c/gerrit/+/133235

[3] https://gerrit-ci.gerritforge.com/view/Gerrit/job/Gerrit-buck-stable-2.13/166

--
--
To unsubscribe, email repo-discuss...@googlegroups.com
More info at http://groups.google.com/group/repo-discuss?hl=en

---
You received this message because you are subscribed to the Google Groups "Repo and Gerrit Discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to repo-discuss...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Luca Milanesio]

On 5 Feb 2018, at 01:56, David Pursehouse <david.pu...@gmail.com> wrote:

On Sun, Feb 4, 2018 at 6:19 PM David Ostrovsky <david.o...@gmail.com> wrote:

On Wednesday, January 31, 2018 at 12:11:18 AM UTC+1, Mark Derricutt wrote:

On 25 Jan 2018, at 20:35, 'Björn Pedersen' via Repo and Gerrit Discussion wrote:

this seems like a know problem: 
https://bugs.chromium.org/p/gerrit/issues/detail?id=5090

Resolved. Upgrading to 2.13.9 didn't help, but re-running the account reindex did after upgrading to .9. Strange that this issue cropped up over the Christmas break with no changes in the servers.

This resembles me this issue, that was fixed on stable-2.14,

and even applied to stable-2.13 too, but there was not official

release any more that included this change: [1].

I'm in the process of fixing a couple of issues with 2.13.x and when they are done I'm planning to release 2.13.10 which will include that fix and a few others that have been submitted on stable-2.13 following 2.13.9

+1, thanks David.

[Krešimir Tonković]

I had the same message in the log, but just reindexing didn't help. Ultimately this resolved my issue: https://groups.google.com/forum/#!topic/repo-discuss/wCt_ePUoKg4

--

Regards,

Kresimir