org.eclipse.jgit.errors.RepositoryNotFoundException

repository not found: Cannot open repository x86-km-src

Samebug tips0

There are no available Samebug tips for this exception. If you know how to solve this issue, help other users by writing a short tip.

Don't give up yet. Paste your full stack trace to get a solution.

Solutions on the web44

  • via Google Groups by Cyril Jaquier, 9 months ago
    repository not found: Cannot open repository x86-km-src
  • via Google Groups by funeeldy, 1 year ago
    repository not found: Cannot open repository root
  • via Google Groups by James Mills, 1 year ago
    repository not found: Cannot open repository myrepo
  • Stack trace

    • org.eclipse.jgit.errors.RepositoryNotFoundException: repository not found: Cannot open repository x86-km-src at com.google.gerrit.server.git.LocalDiskRepositoryManager.openRepository(LocalDiskRepositoryManager.java:202) at com.google.gerrit.server.git.LocalDiskRepositoryManager.openRepository(LocalDiskRepositoryManager.java:164) at com.google.gerrit.server.index.change.AllChangesIndexer.indexAll(AllChangesIndexer.java:145) at com.google.gerrit.server.index.change.AllChangesIndexer.indexAll(AllChangesIndexer.java:83) at com.google.gerrit.server.index.OnlineReindexer.reindex(OnlineReindexer.java:81) at com.google.gerrit.server.index.OnlineReindexer.access$000(OnlineReindexer.java:28) at com.google.gerrit.server.index.OnlineReindexer$1.run(OnlineReindexer.java:52) Caused by: org.eclipse.jgit.errors.RepositoryNotFoundException: repository not found: /var/lib/git/repositories/esw_gitrepos/x86-km-src at org.eclipse.jgit.lib.RepositoryCache$FileKey.open(RepositoryCache.java:453) at org.eclipse.jgit.lib.RepositoryCache.openRepository(RepositoryCache.java:274) at org.eclipse.jgit.lib.RepositoryCache.open(RepositoryCache.java:117) at org.eclipse.jgit.lib.RepositoryCache.open(RepositoryCache.java:92) at com.google.gerrit.server.git.LocalDiskRepositoryManager.openRepository(LocalDiskRepositoryManager.java:199) ... 6 more

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    You’re the first here who have seen this exception.