[GIT] fatal: git fetch_pack: expected ACK/NAK, got 'ERR want 1f1d62db763e1b6e92ce54cfbf2d7db16ff34f38 not valid'

2,883 views
Skip to first unread message

joseph M

unread,
Aug 6, 2015, 5:02:16 AM8/6/15
to Repo and Gerrit Discussion
i got this error , how we can solve this issue 
Message has been deleted

Quentin Neill

unread,
May 19, 2016, 9:36:51 AM5/19/16
to Repo and Gerrit Discussion
The problem with researching this particular issue is when you search for the terms you get hits in all kinds of tools and projects where people report derivatives of this bug: debian, eclipse, nginx, scm-manager, etc.

As far as I can tell, it is an underlying git issue which is exposed by gerrit, and I think it is this one:
The fix for that one is to restart gerrit periodically, or upgrade to 2.10.7 or 2.11.4 or 2.12 (2.12 does not have the issue

Richard Christie

unread,
May 24, 2016, 7:17:19 AM5/24/16
to Repo and Gerrit Discussion


On Thursday, 19 May 2016 14:36:51 UTC+1, Quentin Neill wrote:
The fix for that one is to restart gerrit periodically, or upgrade to 2.10.7 or 2.11.4 or 2.12 (2.12 does not have the issue

For what it is worth, we do see this problem semi-frequently on larger repositories hosted by gerrit 2.12.2 (sometimes once a week)

As you say, restarting gerrit makes it go away, but sooner or later one pops up again.

We do run periodic c-git "git gc" on the repositories due to having had that before gerrit offered its own, and have not yet changed over due to FUD on people complaining in older gerrit versions of issues with gerrit's implementation.

To try and avoid any concurrency issues (again FUD about jgit and cgit running in the same repo at the same time) our integration marks the repository read-only to gerrit and waits to make sure there are no gerrit receive-pack processes on the repository running before starting gc. It then flushes gerrit's caches on finish.
Reply all
Reply to author
Forward
0 new messages