Medium Today I was updating my Bitbucket Server from 4.3.0 to 4.5.1
Everything went fine, until a user wanted to push a git lfs file.
Here is what my logs are saying:
Git Repo:
vagrant@tp64:/var/www/foo.local$ GIT_TRACE=1 git push 18:05:36.634627 git.c:344 trace: built-in: git 'push' 18:05:36.636284 run-command.c:334 trace: run_command: 'ssh' '-p' '7999' 'git@bitbucket.mybitbucket.example' 'git-receive-pack '\''/bar/foo.com.git'\''' 18:06:06.209979 run-command.c:334 trace: run_command: '.git/hooks/pre-push' 'origin' 'ssh://git@bitbucket.mybitbucket.example:7999/bar/foo.com.git' 18:06:06.219723 git.c:561 trace: exec: 'git-lfs' 'pre-push' 'origin' 'ssh://git@bitbucket.mybitbucket.example:7999/bar/foo.com.git' 18:06:06.219774 run-command.c:334 trace: run_command: 'git-lfs' 'pre-push' 'origin' 'ssh://git@bitbucket.mybitbucket.example:7999/bar/foo.com.git' trace git-lfs: run_command: git rev-list --objects 6d24f6230dabbadb35b397bf1e990ddbfb02754b --not --remotes=origin trace git-lfs: run_command: git cat-file --batch-check trace git-lfs: run_command: git cat-file --batch trace git-lfs: run_command: 'git' config -l trace git-lfs: tq: starting 3 transfer workers trace git-lfs: tq: running as batched queue, batch size of 100 trace git-lfs: tq: sending batch of size 1 trace git-lfs: ssh: git@bitbucket.mybitbucket.example git-lfs-authenticate bar/foo.com.git upload trace git-lfs: ssh: upload attempted with git@bitbucket.mybitbucket.example. Error: exit status 1 Git LFS: (0 of 1 files) 0 B / 756.23 KB exit status 1 error: failed to push some refs to 'ssh://git@bitbucket.mybitbucket.example:7999/bar/foo.com.git'
My Bitbucket logs are showing this:
2016-04-07 20:38:52,394 WARN [ssh-scm-request-handler] me xxxxx xxxxx 127.0.0.1 SSH - git-lfs-authenticate bar/foo.com.git download c.a.b.i.ssh.server.SshCommandAdapter git-lfs-authenticate ic/foo.com.git download : Command is not supported; no handler is available
I downgraded back again to 4.3.0 and the errors where gone (database + application directory)
Greetings Jan
