"fatal: remote error: want 123xyz not valid" happens from time to time by fetching

586 views
Skip to first unread message

Yan

unread,
May 18, 2022, 3:55:24 AM5/18/22
to Repo and Gerrit Discussion
Hi all, 
Our gerrit server has already been updated to v3.4.4. By fetching some repositories, we faced this problem from time to time.

The user got:
               Fetching gerrit 
               fatal: remote error: want 123xyz not valid 
               fatal: internal server error 
               error: could not fetch gerrit

On the server, the error log was:
 [2022-05-18T08:59:47.754+02:00] [SSH git-upload-pack /abc_test (userid)] ERROR com.google.gerrit.sshd.BaseCommand : Internal server error (user userid account 1) during git-upload-pack '/abc_test
org.eclipse.jgit.transport.UploadPackInternalServerErrorException
        at org.eclipse.jgit.transport.UploadPack.upload(UploadPack.java:775)
        at com.google.gerrit.sshd.commands.Upload.runImpl(Upload.java:101)
        at com.google.gerrit.sshd.AbstractGitCommand.service(AbstractGitCommand.java:109)
        at com.google.gerrit.sshd.AbstractGitCommand$1.run(AbstractGitCommand.java:74)
        at com.google.gerrit.sshd.BaseCommand$TaskThunk.run(BaseCommand.java:490)
        at com.google.gerrit.server.logging.LoggingContextAwareRunnable.run(LoggingContextAwareRunnable.java:113)
        at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
        at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
        at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304)
        at com.google.gerrit.server.git.WorkQueue$Task.run(WorkQueue.java:612)
        at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
        at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
        at java.base/java.lang.Thread.run(Thread.java:829)
Caused by: org.eclipse.jgit.transport.WantNotValidException: want 123xyz not valid
        at org.eclipse.jgit.transport.UploadPack$AdvertisedRequestValidator.checkWants(UploadPack.java:1856)
        at org.eclipse.jgit.transport.UploadPack.parseWants(UploadPack.java:1807)
        at org.eclipse.jgit.transport.UploadPack.processHaveLines(UploadPack.java:1696)
        at org.eclipse.jgit.transport.UploadPack.fetchV2(UploadPack.java:1207)
        at org.eclipse.jgit.transport.UploadPack.serveOneCommandV2(UploadPack.java:1294)
        at org.eclipse.jgit.transport.UploadPack.serviceV2(UploadPack.java:1334)
        at org.eclipse.jgit.transport.UploadPack.uploadWithExceptionPropagation(UploadPack.java:836)
        at org.eclipse.jgit.transport.UploadPack.upload(UploadPack.java:752)
        ... 12 more


It happens not by each fetch activity, and usually works by another try or multi attempts.  But it still bothers the users. Any idea why it happens and how to solve it?

Thanks!
Yan


Nasser Grainawi

unread,
May 19, 2022, 12:40:47 PM5/19/22
to Yan, Repo and Gerrit Discussion
On Wed, May 18, 2022 at 1:55 AM Yan <biya...@gmail.com> wrote:
Hi all, 
Our gerrit server has already been updated to v3.4.4. By fetching some repositories, we faced this problem from time to time.

The user got:
               Fetching gerrit 
               fatal: remote error: want 123xyz not valid 
               fatal: internal server error 
               error: could not fetch gerrit


Hi Yan,

Is '123xyz' a valid object in that repository? i.e. can you run something like 'git cat-file -t 123xyz' in the bare repo on the server and it works?
 
--
--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/repo-discuss/074dc571-d4ea-4b90-8b1d-0b502088aeefn%40googlegroups.com.
Reply all
Reply to author
Forward
0 new messages