HTTP 500 : An error has occurred: {"code":"ECONNREFUSED","errno":"ECONNREFUSED","syscall":"connect"} #266

Closed
tamsler opened this Issue Jul 8, 2012 · 11 comments

Projects

None yet

8 participants

@tamsler
tamsler commented Jul 8, 2012

I am getting the following error after deploying my app today:

HTTP 500:
An error has occurred: {"code":"ECONNREFUSED","errno":"ECONNREFUSED","syscall":"connect"}

It looks like this happened before: #215 ...

I have tried to deploy my app several times with "jitsu deploy" but am getting the same error over and over.

@tamsler
tamsler commented Jul 8, 2012

I just received help in the IRC channel. The issues was that my node app was using 127.0.0.1/localhost instead of 0.0.0.0. Changing that and a redeploy fixed the issue.

@tamsler
tamsler commented Jul 8, 2012

I looked for this in the docs but didn't find anything. Actually, the handbook's (https://github.com/nodejitsu/handbook) example shows using port 80, which is not allowed. You have to use a port > 1024. I would recommend that the docs are updated outlining the correct use of port and IP.

@jfhbrook
jfhbrook commented Jul 8, 2012

This >1024 behavior is new, and as far as I know not permanent. In addition, I was under the impression that "localhost" would also magically work as-expected. @mmalecki You wouldn't happen to know if anything changed here during the migration, eh?

@mmalecki
mmalecki commented Jul 8, 2012

localhost won't work and didn't ever work - we don't monkey-punch it in carapace. Closing.

@mmalecki mmalecki closed this Jul 8, 2012
@indexzero
Member

@mmalecki We do monkey punch it now in carapace and I believe @bmeck deployed the hotfix last night so localhost shouldn't be an issue anymore.

nodejitsu/haibu-carapace@a6a6a1f

@mmalecki
mmalecki commented Jul 8, 2012

Oh, I didn't notice that commit. Nice.

@craigcosmo

I have the issue too. Just re-deploy, it will disappear. No need to make change to your code

@joshuairl

+1 This is still happening to me with latest versions of everything...

@mmalecki

@joshuairl you should drop by #nodejitsu on Freenode IRC. It's most likely your application crashing.

@thalesfsp

"+1 This is still happening to me with latest versions of everything..."

"@joshuairl you should drop by #nodejitsu on Freenode IRC. It's most likely your application crashing." <- its not what the logs say

Whats the SOLUTION?

@dscape
Member
dscape commented Dec 15, 2012

There's a variety of reason why this can happen, it basically means our load balancers failed to connect to one of the upstream services.

In your case @thalesfsp it seems like it was a bug in CouchDB, which I have patched just 5 minutes ago.

If you read it as "upstream connection failed" I'm pretty sure you can understand this is an umbrela error and it doesnt mean much. If you go to irc however we can investigate in our logs what might have gone wrong, and fix it asap. That's why @mmalecki suggested you should do that.

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