bugzilla-daemon at bugzilla.mindrot.org
2018-Apr-16 17:13 UTC
[Bug 2859] New: git stopped to work when gitlab is running on nonstandard port
https://bugzilla.mindrot.org/show_bug.cgi?id=2859 Bug ID: 2859 Summary: git stopped to work when gitlab is running on nonstandard port Product: Portable OpenSSH Version: 7.7p1 Hardware: amd64 OS: Linux Status: NEW Severity: major Priority: P5 Component: ssh Assignee: unassigned-bugs at mindrot.org Reporter: gglater62 at gmail.com After upgrade to openssh-7.7 git stopped to work. url to git repository is something like: ssh://git at gitlab.example.com:7456/something/something.git Result of git pull: bash: git-upload-pack: command not found fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists. -- You are receiving this mail because: You are watching the assignee of the bug.
bugzilla-daemon at bugzilla.mindrot.org
2018-Apr-16 21:58 UTC
[Bug 2859] git stopped to work when gitlab is running on nonstandard port
https://bugzilla.mindrot.org/show_bug.cgi?id=2859 Darren Tucker <dtucker at dtucker.net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dtucker at dtucker.net --- Comment #1 from Darren Tucker <dtucker at dtucker.net> --- The error message seems to indicate that git-upload-pack is not in the $PATH on the server. Could you please attach the ssh debug output? Assuming a Bourne-ish shell, something like: $ GIT_SSH_COMMAND='echo ssh $@ 1>&2; ssh -vvv' git pull then attach the resulting log using "Add an attachment"? -- You are receiving this mail because: You are watching someone on the CC list of the bug. You are watching the assignee of the bug.
bugzilla-daemon at bugzilla.mindrot.org
2018-Apr-17 09:55 UTC
[Bug 2859] git stopped to work when gitlab is running on nonstandard port
https://bugzilla.mindrot.org/show_bug.cgi?id=2859 --- Comment #2 from tester <gglater62 at gmail.com> --- Hm, when I set GIT_COMMAND_SSH=ssh it works, but when GIT_COMMAND_SSH is unset it does not. For 7.6 it worked even when GIT_COMMAND_SSH was unset. -- You are receiving this mail because: You are watching the assignee of the bug. You are watching someone on the CC list of the bug.
bugzilla-daemon at bugzilla.mindrot.org
2018-Apr-17 10:29 UTC
[Bug 2859] git stopped to work when gitlab is running on nonstandard port
https://bugzilla.mindrot.org/show_bug.cgi?id=2859 --- Comment #3 from Darren Tucker <dtucker at dtucker.net> --- OK, how about strace, eg: $ strace -f -e trace=process git clone ssh://git at gitlab.example.com:7456/something/something.git There should be a line something like [pid 20798] execve("/usr/local/bin/ssh", ["/usr/local/bin/ssh", "-p", "7456", "git at gitlab.example.com", "git-upload-pack '/something/some"...], 0x561bec622a50 /* 43 vars */) = 0 which will show the arguments given to the ssh command. -- You are receiving this mail because: You are watching the assignee of the bug. You are watching someone on the CC list of the bug.
bugzilla-daemon at bugzilla.mindrot.org
2018-Apr-17 13:46 UTC
[Bug 2859] git stopped to work when gitlab is running on nonstandard port
https://bugzilla.mindrot.org/show_bug.cgi?id=2859 --- Comment #4 from tester <gglater62 at gmail.com> --- Created attachment 3143 --> https://bugzilla.mindrot.org/attachment.cgi?id=3143&action=edit Log of git pull It is a bit "obfuscated". -- You are receiving this mail because: You are watching the assignee of the bug. You are watching someone on the CC list of the bug.
bugzilla-daemon at bugzilla.mindrot.org
2018-Apr-17 13:58 UTC
[Bug 2859] git stopped to work when gitlab is running on nonstandard port
https://bugzilla.mindrot.org/show_bug.cgi?id=2859 --- Comment #5 from Darren Tucker <dtucker at dtucker.net> --- (In reply to tester from comment #4)> Created attachment 3143 [details] > Log of git pull > > It is a bit "obfuscated".>From the log: > 17825 execve("/usr/bin/ssh-user", ["/usr/bin/ssh-user", "-G", "-p", > "7456", "git at gitlab.example.com"], 0x14c30c0 /* 75 vars */) = 0What's ssh-user and where does it come from? It's being invoked by git before ssh. It seems to end up running /usr/bin/ssh -x -a -oClearAllForwardings=yes -l tester -p 7456 git at gitlab.example.com which specifies contradictory usernames "tester" and "git". The option parsing changed in 7.7 and now uses the first match, same as the rest of the config parsing. -- You are receiving this mail because: You are watching someone on the CC list of the bug. You are watching the assignee of the bug.
bugzilla-daemon at bugzilla.mindrot.org
2018-Apr-17 15:37 UTC
[Bug 2859] git stopped to work when gitlab is running on nonstandard port
https://bugzilla.mindrot.org/show_bug.cgi?id=2859 --- Comment #6 from tester <gglater62 at gmail.com> --- Sorry, for noise. I uninstalled ssh-user (okas) package. It was set via GIT_SSH and now git works. Sorry, and thanks for help. -- You are receiving this mail because: You are watching the assignee of the bug. You are watching someone on the CC list of the bug.
bugzilla-daemon at bugzilla.mindrot.org
2018-Apr-17 15:39 UTC
[Bug 2859] git stopped to work when gitlab is running on nonstandard port
https://bugzilla.mindrot.org/show_bug.cgi?id=2859 tester <gglater62 at gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |INVALID -- You are receiving this mail because: You are watching someone on the CC list of the bug. You are watching the assignee of the bug.
bugzilla-daemon at bugzilla.mindrot.org
2018-Oct-19 06:17 UTC
[Bug 2859] git stopped to work when gitlab is running on nonstandard port
https://bugzilla.mindrot.org/show_bug.cgi?id=2859 Damien Miller <djm at mindrot.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #7 from Damien Miller <djm at mindrot.org> --- Close RESOLVED bugs with the release of openssh-8.0 -- You are receiving this mail because: You are watching someone on the CC list of the bug. You are watching the assignee of the bug.