How to reindex when login is blocked?

[arthur karton]

Hi,

We exceeded the number of commiters allowed by our license.

We reduced the number by mapping multiple instances of same committer to one.

But, I think we need to re-index for the above to take effect.

However, I am unable to log in to re-index. Logins appear to be disabled.

What to do?

Thanks,

Arthur

p.s. note we share username/password between jira and fisheye and I am admin on both.

[Caterina Curti]

Hi @arthur karton,

You are correct that a re-index is required after the history has been rewritten. Here is our guide for Mercurial and Git repositories on this topic:

- Git or Hg Repository exceeds number of allowed Committers

Regarding the login, did you already try to use the administrator password?

Note: this is not a username and you can enter this password by browsing to the http://<FECRU_URL>:<FECRU_PORT>/admin/admin.do URL.

If you don't remember it, this is how it can be reset:

- How to reset the Administration Page password in FishEye or Crucible

Cheers,

Caterina - Atlassian