| Git clone/pull with SSH from Azure DevOps repositories fails frequently [message #1831933] |
Thu, 03 September 2020 04:21  |
Eclipse User |
|
|
|
Hello,
we recently moved our git repositories to Azure DevOps and since then we are having issues accessing them with git clone/pull.
Error "remote end hung up unexpectedly"
This error usually occurs on the first clone/pull on a specific repository. If the clone/pull is executed immediately after the failure, then the clone/pull usually succeeds.
If the SSH client is changed to JSch then the problem also occurs with the error "session is down"
If we use the plain old command line git executable (2.17.1.windows.2) then everything works as expected.
Eclipse Version: Eclipse 2020-06
EGit/JGit Version: 5.8.0
Backend: Apache MINA
Any help provided would be much appreciated.
Thanks
Corny
|
|
|
|
|
|
|
|
|
|
|
|
| Re: Git clone/pull with SSH from Azure DevOps repositories fails frequently [message #1832952 is a reply to message #1832911] |
Tue, 29 September 2020 17:42  |
| Eclipse User |
|
|
|
Unfortunately getting a log from Eclipse with these Apache MINA sshd messages is indeed hard. With JGit, it should be possible in the way I wrote above, but if you can't reproduce with JGit, that won't help.
With Eclipse, you have to figure out which logging back-end, if any, is installed. My normal "Eclipse for Committers" apparently has none; so to get logging output I have to download one, for instance org.slf4j.impl.log4j12, and then copy that into my Eclipse's "dropins" folder. Then write a log4j configuration and pass that via a Java system property defined via the _JAVA_OPTIONS environment variable to Eclipse.
Here's a way to get DEBUG logging for Apache MINA sshd from the Eclipse for Java Developers package that you appear to be using. That one includes a logback logging back-end (via m2e), so write a config for logback:
<?xml version="1.0" encoding="UTF-8"?>
<configuration scan="true" scanPeriod="5 seconds">
<appender name="STDOUT" class="ch.qos.logback.core.ConsoleAppender">
<encoder>
<pattern>%d{HH:mm:ss.SSS} [%thread] %-5level %logger{40} - %msg%n</pattern>
</encoder>
</appender>
<logger name="org.apache.sshd" level="DEBUG" additivity="false">
<appender-ref ref="STDOUT" />
</logger>
<root level="WARN">
<appender-ref ref="STDOUT" />
</root>
</configuration>
Save it as file "logback-debug.xml" somewhere.
Then set the environment variable and start Eclipse from the command line. Then pull from your repo on Azure DevOps. You should get a lot of DEBUG logging in the terminal.
On my OS X machine, I just start
$ _JAVA_OPTIONS='-Dlogback.configurationFile=file:///absolute/path/to/logback-debug.xml' ./eclipse &
With some luck, such a log will perhaps show something that can give me a clue as to what might be going on.
|
|
|
|
Powered by
FUDForum. Page generated in 0.78119 seconds
Home