Subgit fails to work after migrating to a new server

SubGit
#1

We just upgraded to a new EC2 instance on Amazon. Platform is Ubuntu 20.04. I’ve posted a snippet of the log below.

I didn’t post this on the support forum since it contains the names of our files and ports. Can you suggest a solution? Are some specific ciphers needed?

Regards,
Ravindra

…
…
[2022-05-27 05:57:36.730][daemon][19] Closed random access file ‘/home/git/xxx.com.git/subgit/daemon.lock’
[2022-05-27 05:57:36.733][daemon][22] Failed to create SSH agent connector 'connector is not available: ’
com.jcraft.jsch.agentproxy.AgentProxyException: connector is not available:
at com.jcraft.jsch.agentproxy.ConnectorFactory.createConnector(ConnectorFactory.java:111)
at org.tmatesoft.translator.k.a.d.a(SourceFile:151)
at org.tmatesoft.translator.k.a.d.a(SourceFile:71)
at org.tmatesoft.translator.k.d.h.a(SourceFile:113)
at org.tmatesoft.translator.k.d.h.a(SourceFile:232)
at org.tmatesoft.translator.k.d.h.a(SourceFile:148)
at org.tmatesoft.translator.daemon.J.a(SourceFile:526)
at org.tmatesoft.translator.daemon.J.b(SourceFile:524)
at org.tmatesoft.translator.daemon.H.call(SourceFile:502)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at org.tmatesoft.translator.daemon.L.a(SourceFile:436)
at org.tmatesoft.translator.daemon.E.run(SourceFile:261)
[2022-05-27 05:57:36.735][daemon][22] Using Subversion configuration and credentials cache at: /home/git/.subversion
[2022-05-27 05:57:36.761][daemon][22] Checking remote ‘svn+ssh://svn.xxx.com/websites’.
[2022-05-27 05:57:36.789][daemon][26] com.trilead.ssh2.transport.TransportManager : Receive thread: error in receiveLoop: Cannot negotiate, proposals do not match.
[2022-05-27 05:57:36.795][daemon][22] ######### LOCATION STATE REPORT ############
[2022-05-27 05:57:36.795][daemon][22] svn: E210002: There was a problem while connecting to xxxx:NN
org.tmatesoft.translator.util.f: svn: E210002: There was a problem while connecting to svn.xxx.com:NN
at org.tmatesoft.translator.util.f.c(SourceFile:109)
at org.tmatesoft.translator.util.f.b(SourceFile:75)
at org.tmatesoft.translator.k.aj.a(SourceFile:1329)
at org.tmatesoft.translator.k.aj.a(SourceFile:920)
at org.tmatesoft.translator.k.d.h.a(SourceFile:237)
at org.tmatesoft.translator.k.d.h.a(SourceFile:148)
at org.tmatesoft.translator.daemon.J.a(SourceFile:526)
at org.tmatesoft.translator.daemon.J.b(SourceFile:524)

#2

Hello Ravindra,

thank you for reaching out to use on this matter.

Actually, when you send a request through the form on the website, a new forum thread is being opened automatically. I have removed the host name and port from the stack trace manually, so it looks it’s safe now, I suggest to continue here.
The exception looks similar to an issue with SSH library that we fixed recently in v.3.3.14, so as the first step I would recommend upgrading SubGit to the latest version.

#3

I already updated to the latest v3.3.14. Still facing the same error.

#4

Have you run subgit install against the mirrored repository after SubGit upgrade?

#5

Thanks! That fixed it. I couldn’t find any upgrade instructions in the documentation.

#6

Great! Glad to know it is working well now.
The upgrade is pretty simple, actually: first SubGit program binaries should be upgraded, then subgit install should be invoked against all the mirrored repositories to upgrade SubGit “fat” jar in the repositories and start the new daemon, that’s all.