# Re: git clone - failing on cygwin with git:// but not with ssh://

3 messages from 2008-12-30 to 2008-12-30. Participants: Joe Casadonte, Junio C Hamano.
Thread: https://gitlist.dev/t/16925

## Joe Casadonte, 2008-12-30 16:40

Subject: Re: git clone - failing on cygwin with git:// but not with ssh://
Message-ID: <u7i5hy5ti.fsf@terrapin.northbound-train.com>
URL: https://gitlist.dev/e/u7i5hy5ti.fsf%40terrapin.northbound-train.com

```
Joe Casadonte <jcasadonte <at> northbound-train.com> writes:

> D:\temp>git clone git://foobar/otminfmyproj.git
> Initialized empty Git repository in /cygdrive/d/temp/foobar/.git/
> fatal: read error (Socket operation on non-socket)
> fatal: early EOF
> fatal: index-pack failed
>
> I've turned on verbose logging in the daemon and I see the following
> messages:
>
> Dec 27 17:31:53 foobar git-daemon: [30327] Connection from 192.168.1.102:2598
> Dec 27 17:31:53 foobar git-daemon: [30327] Extended attributes (16 bytes) exist <host=foobar>
> Dec 27 17:31:53 foobar git-daemon: [30327] Request upload-pack for '/myproj.git'
> Dec 27 17:31:55 foobar git-daemon: [30327] Disconnected (with error)
>
> Running the clone via ssh protocol from test client #2 works, though:
>
> D:\temp>git clone ssh://root <at> foobar/nfs02/git/myproj
> Initialized empty Git repository in /cygdrive/d/temp/myproj/.git/
> remote: Counting objects: 104, done.
> remote: Compressing objects: 100% (72/72), done.
> remote: Total 104 (delta 22), reused 104 (delta 22)
> Receiving objects: 100% (104/104), 76.97 KiB | 9 KiB/s, done.
> Resolving deltas: 100% (22/22), done.
>
> The same test machine has cloned from a different linux server via the
> git protocol just fine.

Looking for a little help, please.  Is this not a legitimate git issue?  Can
anyone at least help me diagnose the issue?  Please?

--
Regards,


joe
Joe Casadonte
jcasadonte@northbound-train.com

------------------------------------------------------------------------------
         Llama Fresh Farms => http://www.northbound-train.com
    Ramblings of a Gay Man => http://www.northbound-train.com/ramblings
               Emacs Stuff => http://www.northbound-train.com/emacs.html
          Music CD Trading => http://www.northbound-train.com/cdr.html
------------------------------------------------------------------------------
                       Live Free, that's the message!
------------------------------------------------------------------------------

```

## Junio C Hamano, 2008-12-30 19:54

Subject: Re: git clone - failing on cygwin with git:// but not with ssh://
Message-ID: <7v1vvp30cq.fsf@gitster.siamese.dyndns.org>
URL: https://gitlist.dev/e/7v1vvp30cq.fsf%40gitster.siamese.dyndns.org
In-Reply-To: <u7i5hy5ti.fsf@terrapin.northbound-train.com>

```
"Joe Casadonte" <jcasadonte@northbound-train.com> writes:

> Looking for a little help, please.  Is this not a legitimate git issue?  Can
> anyone at least help me diagnose the issue?  Please?

I think "git on Cygwin" is as legitimate as git on anything else, but at
the same time my guess is that it is a combination of the fact that
everybody is busy with other things around the end of year , and that
probably there are not many "git on Cygwin" experts monitoring the list to
begin with.

Sorry, I do not work on Cygwin (nor Windows in general).  "fatal: read
error (Socket operation on non-socket)" sounds like it is coming from
pkt-line.c::safe_read() on the downloading side (i.e. git-clone).

Googling for that error message seems to indicate that it seems to a
rather common error message on wide variety of programs running on Cygwin.

C.f.

http://www.google.com/search?&q=%22Socket+operation+on+non-socket%22+site%3Acygwin.com

```

## Joe Casadonte, 2008-12-30 20:01

Subject: Re: git clone - failing on cygwin with git:// but not with ssh://
Message-ID: <ueizpwhxt.fsf@terrapin.northbound-train.com>
URL: https://gitlist.dev/e/ueizpwhxt.fsf%40terrapin.northbound-train.com
In-Reply-To: <u7i5hy5ti.fsf@terrapin.northbound-train.com>

```
On 30 Dec 2008, Joe Casadonte wrote:

> Looking for a little help, please.  Is this not a legitimate git
> issue?  Can anyone at least help me diagnose the issue?  Please?

My apologies to the group -- I wasn't really cognizant of the fact
that its only been 3 days since my first email.  That has now been
made abundantly clear to me :)

I've been working on getting git working full-bore since the middle of
last week, of which this issue is just part of it, and I'm quickly
running out of time (Jan 5 I have to ditch this and go back to my
normal tasks).  All the days are blurring together.....

Anyhow, thanks for *your* patience with me, despite the lack of
manners on my end.  A happy & safe New Years to all!

--
Regards,


joe
Joe Casadonte
jcasadonte@northbound-train.com

------------------------------------------------------------------------------
         Llama Fresh Farms => http://www.northbound-train.com
    Ramblings of a Gay Man => http://www.northbound-train.com/ramblings
               Emacs Stuff => http://www.northbound-train.com/emacs.html
          Music CD Trading => http://www.northbound-train.com/cdr.html
------------------------------------------------------------------------------
                       Live Free, that's the message!
------------------------------------------------------------------------------

```
