From: Jakub Narebski <jnareb@gmail.com>
To: Joshua Stoutenburg <jehoshua02@gmail.com>
Cc: Git List <git@vger.kernel.org>
Subject: Re: New setup, trying to clone . . .
Date: Fri, 16 Sep 2011 01:29:07 -0700 (PDT) [thread overview]
Message-ID: <m3pqj0sxfy.fsf@localhost.localdomain> (raw)
In-Reply-To: <CAOZxsToJk45UHGAuno-r=B76+SUg5icbYvUsY5EfgcGv_UkxHg@mail.gmail.com>
Joshua Stoutenburg <jehoshua02@gmail.com> writes:
> I'm following these instructions: http://progit.org/book/ch4-4.html
>
> Everything has gone fine up until about halfway down the page, where it says:
>
> > At this point, the others can clone it down and push changes back up just as easily:
> > $ git clone git@gitserver:/opt/git/project.git
>
> Of course, replacing [git@gitserver:/opt/git/project.git] according to
> my setup, and I change directory to an empty directory apart from the
> original project, then I try the command, I get the following output:
>
> At this point, the others can clone it down and push changes back up
> just as easily:
>
> $ git clone gituser@192.168.1.102:/git/project.git
> Cloning into project...
> Connection closed by 192.168.1.102
> fatal: The remote end hung up unexpectedly
>
> Any ideas what's going on here?
Note that 'gituser@192.168.1.102:/git/project.git' is an SSH URL.
There are two possible issues:
1. The path to repository is incorrect.
If you are on the same machine as server, you can try cloning (or
just 'git ls-remote') with a local path:
git clone /git/project.git
or
git clone file:///git/project.git
2. The SSH setup is not correct: either SSH daemon is not started, or
there is no 'gituser' account, or 'gituser' account doesn't have
access to /git/project.git
You can check first two with
ssh gituser@192.168.1.102 echo Hello
HTH
--
Jakub Narębski
prev parent reply other threads:[~2011-09-16 8:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-16 6:59 New setup, trying to clone . . Joshua Stoutenburg
2011-09-16 8:29 ` Jakub Narebski [this message]
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=m3pqj0sxfy.fsf@localhost.localdomain \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
--cc=jehoshua02@gmail.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).