ssh_exchange_identification: Connection closed by remote host #346

Open
raqqa opened this Issue Mar 19, 2012 · 24 comments

Projects

None yet
@raqqa
raqqa commented Mar 19, 2012

Worked just fine yesterday, but now I get this problem.

$ git push nodester master
ssh_exchange_identification: Connection closed by remote host
fatal: The remote end hung up unexpectedly

So I tried setting my key again,

$ nodester user setkey
nodester info sending sshkey: \id_rsa.pub
nodester info ssh key successfully sent

But still doesn't work.

I don't know if related, but I also get

$ nodester npm list
nodester info list npm packages for app:
nodester /usr/bin/n: line 38: /dev/null: Permission denied
nodester /usr/bin/n: line 41: /dev/null: Permission denied

EDIT;
I'm stupid, didn't see the previous issue on the same subject.

@nodester
Owner

Hi Mikael,

We are currently running extremely low on disk space which is causing this
issue. We are in the process of adding more resources to the platform as
we speak.

Thanks,
Chris

On Mon, Mar 19, 2012 at 11:18 AM, Mikael Emilsson <
reply@reply.github.com

wrote:

Worked just fine yesterday, but now I get this problem.

$ git push nodester master
ssh_exchange_identification: Connection closed by remote host
fatal: The remote end hung up unexpectedly

So I tried setting my key again,

$ nodester user setkey
nodester info sending sshkey: \id_rsa.pub
nodester info ssh key successfully sent

But still doesn't work.

I don't know if related, but I also get

$ nodester npm list
nodester info list npm packages for app:
nodester /usr/bin/n: line 38: /dev/null: Permission denied
nodester /usr/bin/n: line 41: /dev/null: Permission denied


Reply to this email directly or view it on GitHub:
#346

@raqqa
raqqa commented Mar 19, 2012

Yeah, saw the other issue.

Is this what's causing the npm list issue as well?

@nodester
Owner

yes :(

On Mon, Mar 19, 2012 at 12:39 PM, Mikael Emilsson <
reply@reply.github.com

wrote:

Yeah, saw the other issue.

Is this what's causing the npm list issue as well?


Reply to this email directly or view it on GitHub:
#346 (comment)

@alejandro
Collaborator

@raqqa can you try again please? So we can close this issue :)

@raqqa
raqqa commented Mar 20, 2012

Works fine now, thanks guys!

@raqqa raqqa closed this Mar 20, 2012
@Domiii
Domiii commented May 30, 2012

I am having this issue now, too.

@alejandro
Collaborator

Hey @Domiii what's your problem? THe ssh stuff? Try to restart your rsa keys.

@Domiii
Domiii commented May 30, 2012

Ok I just tried it again 5 minutes later and it just works. Thanks for the quick response anyway :)

@alejandro
Collaborator

No problem :)! Sometimes is because the internet connection.

Hack the planet \m/

@ghost
ghost commented Jul 24, 2012

it seems this same issue is back

@alejandro alejandro reopened this Jul 24, 2012
@ctm
ctm commented Jul 25, 2012

It's happening a bunch to us (Jackrabbit Systems), too. It is intermittent, but it interferes with doing deploys. We may have six servers all pulling from github successfully with one failing. I just had it happen minutes ago.

@bubba-h57

Indeed. We have been seeing it for the past day or so. I initially thought it was our server, but I have now attempted it on enough different machines to be fairly certain it is not. It is always intermittent as well, a few additional manual attempts will eventually yield a good pull or push.

@alejandro
Collaborator

I was holding my voice here because I actually don't know what's the origin of this problem. I'd like to believe that it's caused because our instance. ssh stuff is a OS based system. Well if you the process fails on a push there is nothing to do with "nodester" itself. So we don't have too much to do there.

Checking the logs and everything looks fine. Probably is a thing with aws.

What you guys can try is to reset your rsa keys, maybe that help.

@ctm Jackrabbit is hosted on nodester? Or you have installed the nodester server?.

Cheers.

@kensmith
kensmith commented Apr 4, 2013

This is happening again today. Is it a low disk space issue again? Is there an ETA to resolution?

@wapcaplet

+1, I'm seeing this today when trying to push or pull in a repository that was working fine before:

$ git pull origin develop
ssh_exchange_identification: Connection closed by remote host
fatal: The remote end hung up unexpectedly
$ git push origin develop
ssh_exchange_identification: Connection closed by remote host
fatal: The remote end hung up unexpectedly

Edit: It's working OK now.

@kcantwel
kcantwel commented Apr 4, 2013

+1: Seeing this as well.

% git push origin master
ssh_exchange_identification: Connection closed by remote host
fatal: The remote end hung up unexpectedly

@brasten
brasten commented Apr 4, 2013

Same here, started this morning.

@alejandro
Collaborator
@chrismatthieu
Collaborator

AppFog is supporting the Nodester platform now. Please send emails to support@appfog.com. Thanks.

@klasekwall

I'm also getting this message when doing pull. Trying from multiple computers.
ssh_exchange_identification: Connection closed by remote host

@klasekwall

...and now it suddenly works to pull again. What is happening??! Can you please try to find the underlying cause for this?

@mikelyons

Had this issue, kept trying, worked on the 8th try ...

Trying to git pull --rebase

@ihoneymon

@mikelyons Thanks. I solved problem. ^^

@alexpogrebnyak

@ihoneymon Hi, what did you do to solve problem? I have the same:(

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment