git clone problem

654 views
Skip to first unread message

peng

unread,
May 8, 2014, 3:04:49 PM5/8/14
to moose-users
Hello Everyone,

I'm a moose beginner, and embarrassed to bother you about the git clone problems.

After this command prompt in my opensuse, linux:/home/peng/projects # git clone https://github.com/idaholab/moose.git, it shows that :
"
Initialized empty Git repository in /home/peng/projects/moose/.git/
error: The requested URL returned error: 403 while accessing https://github.com/idaholab/moose.git/info/refs
fatal: HTTP request failed
"
What should I do with the git clone to install the moose?
Thank you very much.

Best,
Peng
------------------
make it happen :-)
 

Peterson, JW

unread,
May 8, 2014, 3:16:10 PM5/8/14
to peng, moose-users


On Thu, May 8, 2014 at 1:04 PM, peng <peng...@gmail.com> wrote:
Hello Everyone,

I'm a moose beginner, and embarrassed to bother you about the git clone problems.

After this command prompt in my opensuse, linux:/home/peng/projects # git clone https://github.com/idaholab/moose.git, it shows that :
"
Initialized empty Git repository in /home/peng/projects/moose/.git/
error: The requested URL returned error: 403 while accessing https://github.com/idaholab/moose.git/info/refs
fatal: HTTP request failed
"
What should I do with the git clone to install the moose?
 
You seem to be doing the right thing here, I'm not sure why it doesn't work.

Is it a temporary network connectivity issue?  Have you tried it again?

--
John

Wang (Non-US), Yaqi

unread,
May 8, 2014, 3:20:06 PM5/8/14
to peng, moose-users
Are you able to fork the repo at github.com?


On Thu, May 8, 2014 at 1:04 PM, peng <peng...@gmail.com> wrote:
 

--
You received this message because you are subscribed to the Google Groups "moose-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to moose-users...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

peng

unread,
May 8, 2014, 3:58:49 PM5/8/14
to Wang (Non-US), Yaqi, moose-users
Thanks for reminding that.
It looks my account is in the member list of the network.
However, when git clone again, the error is still there,

"
"
Initialized empty Git repository in /home/peng/projects/moose/.git/
error: The requested URL returned error: 403 while accessing https://github.com/idaholab/moose.git/info/refs
fatal: HTTP request failed
"
I'll try it once again later.
Thanks a lot.

------------------
make it happen :-)
 


------------------ Original ------------------
From:  "Wang (Non-US), Yaqi";<yaqi...@inl.gov>;
Date:  Fri, May 9, 2014 03:20 AM
To:  "peng"<peng...@gmail.com>;
Cc:  "moose-users"<moose...@googlegroups.com>;
Subject:  Re: git clone problem

Permann, Cody J

unread,
May 8, 2014, 4:06:58 PM5/8/14
to peng, Wang (Non-US), Yaqi, moose-users
Peng,

Are you on a network behind a firewall?  One way to verify that you can connect from the command line is to try other command line utilities like "curl" or "wget".

Cody

Andrew....@csiro.au

unread,
May 8, 2014, 4:56:06 PM5/8/14
to cody.p...@inl.gov, peng...@gmail.com, yaqi...@inl.gov, moose...@googlegroups.com
Hey Peng,

Welcome to the marvellous moose multiverse.  I get similar errors because I am behind some firewall or something.  Instead of https://blah  I use git://blah .  For this to work you first have to set up a github passphrase - search on google and you’ll find a nice page on doing that.  If you have any problems at all please just ask and I can give you more info, but not for a couple of hours since I’m not at work yet (it’s before breakfast time here).

a

Gaston, Derek R

unread,
May 8, 2014, 5:00:20 PM5/8/14
to Andy Wilkins, Cody Permann (INL), peng...@gmail.com, Yaqi Wang (Non-US), moose-users
If you're having trouble with firewalls you need to set the https_proxy environment variable.

If you don't want to / don't know how to do that I recommend using SSH with GitHub... it will go through any firewall... https://help.github.com/articles/generating-ssh-keys

Derek

peng

unread,
May 9, 2014, 11:58:18 AM5/9/14
to Gaston, Derek R, Andy Wilkins, Cody Permann (INL), Wang (Non-US), Yaqi, moose-users
Dear all, 
Thank you for all your kind help.
But I still donot get it by clone.
Here is what I've tried and the response.
At last, I'm going to get one copy by download the ZIP file of master version through the webpage. Is it the same, right?
Thank you again for the warm response.

Best,
Peng

Appended:

1. I added ssh key successfully.
peng@linux-5y30:~> ssh -T git@github.com
The authenticity of host 'github.com (192.30.252.129)' can't be established.
RSA key fingerprint is 16:27:ac:a5:76:28:2d:36:63:1b:56:4d:eb:df:a6:48.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added 'github.com,192.30.252.129' (RSA) to the list of known hosts.
Hi peng029! You've successfully authenticated, but GitHub does not provide shell access.

2. failed to git clone by https after the ssh work
peng@linux-5y30:~> git clone https://github.com/idaholab/moose.git
Initialized empty Git repository in /home/peng/moose/.git/

error: The requested URL returned error: 403 while accessing https://github.com/idaholab/moose.git/info/refs
fatal: HTTP request failed

3. failed to use the ssh method
peng@linux-5y30:~> ssh git@github.com:idaholab/moose.git
ssh: Could not resolve hostname github.com:idaholab/moose.git: Name or service not known


4. tested the firewall issue by curl
peng@linux-5y30:~/projects> curl https://github.com/idaholab/moose.git
<html>
<head><title>301 Moved Permanently</title></head>
<body bgcolor="white">
<center><h1>301 Moved Permanently</h1></center>
<hr><center>nginx</center>
</body>
</html>


5. tested the firewall issue by wget
peng@linux-5y30:~/projects> wget https://github.com/idaholab/moose.git
--2014-05-09 11:49:37--  https://github.com/idaholab/moose.git
Resolving github.com... 192.30.252.130
Connecting to github.com|192.30.252.130|:443... connected.
HTTP request sent, awaiting response... 301 Moved Permanently
Location: https://github.com/idaholab/moose [following]
--2014-05-09 11:49:37--  https://github.com/idaholab/moose
Reusing existing connection to github.com:443.
HTTP request sent, awaiting response... 200 OK
Length: 50322 (49K) [text/html]
Saving to: `moose'

100%[===================================================>] 50,322      --.-K/s   in 0.1s

2014-05-09 11:49:37 (512 KB/s) - `moose' saved [50322/50322]


------------------
make it happen :-)
 


------------------ Original ------------------
From:  "Gaston, Derek R";<derek....@inl.gov>;
Date:  Fri, May 9, 2014 05:00 AM
To:  "Andy Wilkins"<Andrew....@csiro.au>;
Cc:  "Cody Permann (INL)"<cody.p...@inl.gov>; "peng.029"<peng...@gmail.com>; "Yaqi Wang (Non-US)"<yaqi...@inl.gov>; "moose-users"<moose...@googlegroups.com>;

Andrs, David

unread,
May 9, 2014, 12:02:21 PM5/9/14
to moose-users
​To use git clone over SSH:​
 git clone g...@github.com:idaholab/moose.git
 
​--
David​

Gaston, Derek R

unread,
May 9, 2014, 12:06:49 PM5/9/14
to Andrs, David, moose-users
To get GitHub to tell you this information go to a repository on GitHub ( like http://github.com/idaholab/moose ) and on the right side there is a little box with the "clone" URL in it... click "SSH" there and the link will change to show you the SSH URL to use in your clone statement.

Like David mentions the correct URL for MOOSE is: g...@github.com:idaholab/moose.git

Derek

Wang (Non-US), Yaqi

unread,
May 9, 2014, 12:46:48 PM5/9/14
to peng, Gaston, Derek R, Andy Wilkins, Cody Permann (INL), moose-users
You should do: git clone git@github.com:idaholab/moose.git
instead of: ssh git@github.com:idaholab/moose.git


On Fri, May 9, 2014 at 9:58 AM, peng <peng...@gmail.com> wrote:

Wang (Non-US), Yaqi

unread,
May 9, 2014, 12:48:05 PM5/9/14
to peng, Gaston, Derek R, Andy Wilkins, Cody Permann (INL), moose-users
I did not refresh my inbox. David has pointed it out. ;-)

Peng Zhang

unread,
May 12, 2014, 11:01:56 AM5/12/14
to moose...@googlegroups.com
Hello Everyone,
Thanks a lot for all your suggestions.

Finally, I upgraded my opensuse from 11.2 to 13.1 and followed the instructions on the www.mooseframework.org including the MOOSE environment setting.

One more thing, I fixed the error by "zypper install m4" when updating the libmesh. I hope it(installing the m4 package) can be added in the prereqs section. 

Now the test running is working and I'm already engaged in MOOSE.
Great MOOSE.

Thank you all again.

Best,
Peng

Miller, Jason M

unread,
May 12, 2014, 11:18:18 AM5/12/14
to Peng Zhang, moose...@googlegroups.com
I went ahead and added it. The reason for it not being there, is not everyone appears to need it. For example, I did not need it when I first created the OpenSUSE instructions :)

I do not see a problem with having everyone install it, so... its there now.
Jason 


--
Reply all
Reply to author
Forward
0 new messages