DeadLocks on Gerrit SSH_Daemon?

70 views
Skip to first unread message

程洋

unread,
Mar 25, 2022, 9:27:00 AM3/25/22
to Repo and Gerrit Discussion
I found a lots of "git clone" stuck at client.
After debugging the server i found "git-upload-pack" and "ssh-daemon" locks each other
Here is the jstack. Is there anyone who knows why?

jstack

Matthias Sohn

unread,
Mar 25, 2022, 10:03:16 AM3/25/22
to 程洋, Repo and Gerrit Discussion
Which Gerrit version do you use and how is it configured ?

-Matthias

程洋

unread,
Mar 25, 2022, 11:09:40 PM3/25/22
to Repo and Gerrit Discussion

3.2.3. And here is the config
config

程洋

unread,
Mar 27, 2022, 10:20:59 PM3/27/22
to Repo and Gerrit Discussion
Any idea. It's really strange to me.

程洋

unread,
Mar 27, 2022, 11:31:12 PM3/27/22
to Repo and Gerrit Discussion
It seems a known issue of org.apache.sshd. But still not fixed yet

Thomas Wolf

unread,
Mar 29, 2022, 4:36:31 PM3/29/22
to Repo and Gerrit Discussion
On Monday, March 28, 2022 at 5:31:12 AM UTC+2 d171...@gmail.com wrote:
It seems a known issue of org.apache.sshd. But still not fixed yet
A pity the stack trace doesn't show the exception. There is a fair chance that this problem in org.apache.sshd is fixed in 2.8.0, but I can't be sure from these stack traces.

The daemon gets an exception at the end of KEX, while trying to install new keys.

Gerrit 3.2 used org.apache.sshd 2.4.0 according to https://www.gerritcodereview.com/3.2.html .

There was a change for SSHD-966 in 2.5.0, there was a race condition in KEX fixed in 2.8.0, and 2.8.0 also changed the way new keys are installed in KEX.

Would be really interesting to know whether this still occurs with the most recent Gerrit. If so, having such a stack trace and possibly debug logging switched on for org.apache.sshd might help to track this down for good.

程洋

unread,
Mar 31, 2022, 12:15:32 AM3/31/22
to Repo and Gerrit Discussion
I also noticed that latest sshd changed a lots of related codes.
Thanks i will try latest Gerrit and if we still have the problem. we will try back

Reply all
Reply to author
Forward
0 new messages