From: "Jason Pyeron" <jpyeron@pdinc.us>
To: <git@vger.kernel.org>
Subject: git push hung?
Date: Sun, 7 Dec 2014 09:24:09 -0500 [thread overview]
Message-ID: <F818AFA80A5F46BBA007F6EB102A75C5@black> (raw)
I am trying to push to our local intranet git (smart https behind apache), and it has been at this point for 10+ hours.
jpyeron@black /projects/git/git
$ GIT_TRACE=1 git push
09:08:45.662902 git.c:349 trace: built-in: git 'push'
09:08:45.662902 run-command.c:341 trace: run_command: 'git-remote-https' 'origin' 'https://intranet.pdinc.us/git/git/'
09:08:46.225700 run-command.c:341 trace: run_command: 'git credential-cache --timeout=99999999999 get'
09:08:46.256967 run-command.c:192 trace: exec: '/bin/sh' '-c' 'git credential-cache --timeout=99999999999 get' 'git credential-cache --timeout=99999999999 get'
09:08:46.366400 git.c:554 trace: exec: 'git-credential-cache' '--timeout=99999999999' 'get'
09:08:46.366400 run-command.c:341 trace: run_command: 'git-credential-cache' '--timeout=99999999999' 'get'
09:08:47.022999 run-command.c:341 trace: run_command: 'git credential-cache --timeout=99999999999 store'
09:08:47.038632 run-command.c:192 trace: exec: '/bin/sh' '-c' 'git credential-cache --timeout=99999999999 store' 'git credential-cache --timeout=99999999999 store'
09:08:47.116799 git.c:554 trace: exec: 'git-credential-cache' '--timeout=99999999999' 'store'
09:08:47.116799 run-command.c:341 trace: run_command: 'git-credential-cache' '--timeout=99999999999' 'store'
09:08:47.366931 run-command.c:341 trace: run_command: 'send-pack' '--stateless-rpc' '--helper-status' '--thin' '--progress' 'https://intranet.pdinc.us/git/git/' 'refs/heads/master:refs/heads/master'
09:08:47.382565 exec_cmd.c:134 trace: exec: 'git' 'send-pack' '--stateless-rpc' '--helper-status' '--thin' '--progress' 'https://intranet.pdinc.us/git/git/' 'refs/heads/master:refs/heads/master'
09:08:47.429465 git.c:349 trace: built-in: git 'send-pack' '--stateless-rpc' '--helper-status' '--thin' '--progress' 'https://intranet.pdinc.us/git/git/' 'refs/heads/master:refs/heads/master'
09:08:47.538898 run-command.c:341 trace: run_command: 'pack-objects' '--all-progress-implied' '--revs' '--stdout' '--thin' '--delta-base-offset' '--progress'
09:08:47.695231 exec_cmd.c:134 trace: exec: 'git' 'pack-objects' '--all-progress-implied' '--revs' '--stdout' '--thin' '--delta-base-offset' '--progress'
09:08:47.742131 git.c:349 trace: built-in: git 'pack-objects' '--all-progress-implied' '--revs' '--stdout' '--thin' '--delta-base-offset' '--progress'
Counting objects: 18734, done.
Delta compression using up to 2 threads.
Compressing objects: 100% (5707/5707), done.
Writing objects: 100% (18734/18734), 9.37 MiB | 0 bytes/s, done.
Total 18734 (delta 14519), reused 17108 (delta 12968)
Servier died, this is in the log:
fatal: protocol error: expected old/new/ref, got 'shallow 3339e9f686bd4c17e3575c71327c4ccf1e8e077b'
What steps can I take to debug this hang in the client?
Git fetch hangs the same way with a server exit of fatal: did not find object for shallow 3339e9f686bd4c17e3575c71327c4ccf1e8e077b
Note: I fixed the underlying problem with a git fetch --unshallow upstream
--
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
- -
- Jason Pyeron PD Inc. http://www.pdinc.us -
- Principal Consultant 10 West 24th Street #100 -
- +1 (443) 269-1555 x333 Baltimore, Maryland 21218 -
- -
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
This message is copyright PD Inc, subject to license 20080407P00.
next reply other threads:[~2014-12-07 14:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-07 14:24 Jason Pyeron [this message]
2014-12-07 17:57 ` git push hung? Torsten Bögershausen
2014-12-07 19:14 ` Jason Pyeron
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=F818AFA80A5F46BBA007F6EB102A75C5@black \
--to=jpyeron@pdinc.us \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox