From: Jonathan Nieder <jrnieder@gmail.com>
To: John Griessen <john@ecosensory.com>
Cc: git@vger.kernel.org
Subject: Re: git-daemon serving repos with repo.git/git-daemon-export-ok
Date: Mon, 3 Jan 2011 17:11:53 -0600 [thread overview]
Message-ID: <20110103231153.GA10733@burratino> (raw)
In-Reply-To: <4D224475.1090805@ecosensory.com>
Hi John,
John Griessen wrote:
> john@toolbench:~/EEProjects/test$ git clone git://ecosensory.com/tek_7k_ext.git
> Cloning into tek_7k_ext...
> fatal: protocol error: bad line length character: fata
[...]
> Next I tried changing my command that runs git-daemon
> from
>
> exec 2>&1
> echo 'git-daemon starting.'
> exec chpst -ugitdaemon \
> "$(git --exec-path)"/git-daemon --verbose --base-path=/var/cache /var/cache/git
Worrisome. Based on /usr/share/doc/git-daemon-run/README.Debian,
I would be interested in:
git --version
dpkg -l git-daemon-run
sv stat git-daemon
cat /var/log/git-daemon/current
It looks like the daemon is sending a malformed reply starting with
"fatal: ", similar to the bug fixed by v1.7.0.3~7 (daemon:
parse_host_and_port SIGSEGV if port is specified, 2010-03-20).
It the error message does not provide any insight, I'd also suggest
using strace or ltrace to attach to the running git-daemon process to
see what's going on.
Thanks for reporting,
Jonathan
next prev parent reply other threads:[~2011-01-03 23:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <S1751603Ab1ACU6e/20110103205834Z+1762@vger.kernel.org>
2011-01-03 21:49 ` git-daemon serving repos with repo.git/git-daemon-export-ok John Griessen
2011-01-03 22:47 ` John Griessen
2011-01-03 23:11 ` Jonathan Nieder [this message]
2011-01-03 23:38 ` John Griessen
2011-01-03 23:55 ` Jonathan Nieder
2011-01-04 1:58 ` John Griessen
2011-01-04 2:11 ` Jonathan Nieder
2011-01-04 3:09 ` Jonathan Nieder
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=20110103231153.GA10733@burratino \
--to=jrnieder@gmail.com \
--cc=git@vger.kernel.org \
--cc=john@ecosensory.com \
/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;
as well as URLs for NNTP newsgroup(s).