About repo sync -j32 -c

665 views
Skip to first unread message

vista...@gmail.com

unread,
Feb 27, 2017, 2:56:25 AM2/27/17
to Repo and Gerrit Discussion
When repo sync -j32 -c ,I got the error.      Repo sync -j32 is ok.  


Disconnecting: Protocol error: expected packet type 31, got 94
mux_client_request_session: read from master failed: Broken pipe
mux_client_request_session: read from master failed: Broken pipe
mux_client_request_session: read from master failed: Broken pipe
fatal: The remote end hung up unexpectedly
fatal: The remote end hung up unexpectedly
fatal: early EOF
fatal: The remote end hung up unexpectedly
fatal: The remote end hung up unexpectedly
fatal: early EOF
fatal: early EOF
fatal: The remote end hung up unexpectedly
fatal: early EOF
fatal: The remote end hung up unexpectedly

Gustaf Lundh

unread,
Feb 27, 2017, 7:33:21 AM2/27/17
to vista...@gmail.com, Repo and Gerrit Discussion
Check out sshd.{rekeyTimeLimit,rekeyByteLimit} configuration values.

The change that introduced them have some more information in the commit message:

https://gerrit-review.googlesource.com/#/c/60574/
-------------------

Allow configuration of SSH rekey values

A long standing bug in SSHD Mina where packets gets out of
order during the rekey phase, will force the ControlMaster
to disconnect during high load (repo -jxx):

Protocol error: expected packet type 31, got 94

This fix allows us to change the trigger limits for rekeying:

rekeyTimeLimit - Default value 1h
rekeyBytesLimit - Default value 1073741824 (bytes, 1GB)

The rekeyTimeLimit can be set to 0 to disable the trigger.

The rekeyBytesLimit can never be set to lower than 32, (Mina
will automatically raise the value to 32 if lower).

To get rid of the Protocol error by using these configuration
values, you can set rekeyTimeLimit to 0 (disables it) and also
set a very high rekeyBytesLimit. This will ensure that the bug
prone rekeying logic in SSHD Mina will never be executed.

Change-Id: Ic196c99266252f47659b26af645b26f77fc15ebd

-------------------

--
--
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.
For more options, visit https://groups.google.com/d/optout.

Nasser Grainawi

unread,
Mar 3, 2017, 3:10:22 PM3/3/17
to Gustaf Lundh, vista...@gmail.com, Repo and Gerrit Discussion
On Feb 27, 2017, at 5:33 AM, Gustaf Lundh <gustaf...@axis.com> wrote:

Check out sshd.{rekeyTimeLimit,rekeyByteLimit} configuration values.

Or use GIT_SSH to disable repo's use of ControlMaster.

-- 
Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum, 
a Linux Foundation Collaborative Project

vista...@gmail.com

unread,
Mar 3, 2017, 10:52:14 PM3/3/17
to Repo and Gerrit Discussion, gustaf...@axis.com, vista...@gmail.com
Thank you!

I change the value like that.

rekeyTimeLimit = 0 
rekeyBytesLimit = 107374182400

And the error never occur, but other error came.

org.apache.sshd.common.SshException: Received 97 on unknown channel 0
Reply all
Reply to author
Forward
0 new messages