New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

http://localhost:8080 Not responding #135

Open
metzlar opened this Issue May 7, 2013 · 14 comments

Comments

Projects
None yet
@metzlar

metzlar commented May 7, 2013

Hi, I am not very familiar with Node but I downloaded the latest Node pkg (0.10) from the nodejs.org website (I'm on OSX 10.6.8) and installed it and followed the juggernaut installation instructions. Redis is running fine and this is the output from the juggernaut command:

path.existsSync is now called `fs.existsSync`.
    info  - socket.io started

Anyway, now when I try to connect to http://localhost:8080/ or http://localhost:8080/application.js the connection seems to time out/fails after some minutes - so there seems to be something listening on 8080 but I do not get any response.

I tried running juggernaut thru sudo, on different ports and directly thru ./server.js but I just can not get it to work. Any thoughts? Thanks

@xedp3x

This comment has been minimized.

Show comment
Hide comment
@xedp3x

xedp3x May 7, 2013

Do you get any messages from juggernaut on connecting?

Cane you please post the output form the command "netstat -pan | grep node" and "netstat -pan | grep 8080" if the Server are running?

xedp3x commented May 7, 2013

Do you get any messages from juggernaut on connecting?

Cane you please post the output form the command "netstat -pan | grep node" and "netstat -pan | grep 8080" if the Server are running?

@metzlar

This comment has been minimized.

Show comment
Hide comment
@metzlar

metzlar May 8, 2013

I installed socket.io to fool around with it. This did not solve the problem with juggernaut but I am getting more output now:

$ juggernaut
    path.existsSync is now called `fs.existsSync`.
       info  - socket.io started
       debug - client authorized
       info  - handshake authorized 847919531562013476
       debug - client authorized
       info  - handshake authorized 1946779245526333349
       etc...

The output from netstat is:

$ netstat -anp tcp | grep node
    no output...

$ netstat -an | grep node
    Address          Type   Recv-Q Send-Q            Inode  etc...

$ netstat -an | grep 8080
    tcp4       0      0  *.8080                 *.*                    LISTEN

metzlar commented May 8, 2013

I installed socket.io to fool around with it. This did not solve the problem with juggernaut but I am getting more output now:

$ juggernaut
    path.existsSync is now called `fs.existsSync`.
       info  - socket.io started
       debug - client authorized
       info  - handshake authorized 847919531562013476
       debug - client authorized
       info  - handshake authorized 1946779245526333349
       etc...

The output from netstat is:

$ netstat -anp tcp | grep node
    no output...

$ netstat -an | grep node
    Address          Type   Recv-Q Send-Q            Inode  etc...

$ netstat -an | grep 8080
    tcp4       0      0  *.8080                 *.*                    LISTEN
@metzlar

This comment has been minimized.

Show comment
Hide comment
@metzlar

metzlar May 8, 2013

Actually the output client authorized and handshake authorized were from a javascript I wrote earlier and still had open in my browser. I guess juggernaut seems to be connectable by a socket from socket.io but somehow I still can not connect to http://localhost:8080/application.js or any url at localhost:8080.

metzlar commented May 8, 2013

Actually the output client authorized and handshake authorized were from a javascript I wrote earlier and still had open in my browser. I guess juggernaut seems to be connectable by a socket from socket.io but somehow I still can not connect to http://localhost:8080/application.js or any url at localhost:8080.

@malagant

This comment has been minimized.

Show comment
Hide comment
@malagant

malagant May 13, 2013

I have exactly the same problem. I get the same output and get a timeout after certain minutes.
Any progress on this issue?

malagant commented May 13, 2013

I have exactly the same problem. I get the same output and get a timeout after certain minutes.
Any progress on this issue?

@analla

This comment has been minimized.

Show comment
Hide comment
@analla

analla Jun 22, 2013

Same here

analla commented Jun 22, 2013

Same here

@zengjing

This comment has been minimized.

Show comment
Hide comment
@zengjing

zengjing Jul 1, 2013

same... plz

zengjing commented Jul 1, 2013

same... plz

@s-block

This comment has been minimized.

Show comment
Hide comment
@s-block

s-block Jul 21, 2013

same here

s-block commented Jul 21, 2013

same here

@maccman

This comment has been minimized.

Show comment
Hide comment
@maccman

maccman Jul 22, 2013

Owner

Juggernaut is deprecated. Use Server Sent events [1]. If you want a high
abstraction I've written a Sinatra pubsub extension. [2]

[1] - http://blog.alexmaccaw.com/killing-a-library
[2] - https://github.com/maccman/sinatra-pubsub

On Sun, Jul 21, 2013 at 1:46 PM, Josh notifications@github.com wrote:

same here


Reply to this email directly or view it on GitHubhttps://github.com//issues/135#issuecomment-21316731
.

Owner

maccman commented Jul 22, 2013

Juggernaut is deprecated. Use Server Sent events [1]. If you want a high
abstraction I've written a Sinatra pubsub extension. [2]

[1] - http://blog.alexmaccaw.com/killing-a-library
[2] - https://github.com/maccman/sinatra-pubsub

On Sun, Jul 21, 2013 at 1:46 PM, Josh notifications@github.com wrote:

same here


Reply to this email directly or view it on GitHubhttps://github.com//issues/135#issuecomment-21316731
.

@fuzzmonkey

This comment has been minimized.

Show comment
Hide comment
@fuzzmonkey

fuzzmonkey Jul 24, 2013

If anyone else has this problem, install an older version of node. You can use https://github.com/creationix/nvm, juggernaut seems to be working on node v0.6.21-pre.

fuzzmonkey commented Jul 24, 2013

If anyone else has this problem, install an older version of node. You can use https://github.com/creationix/nvm, juggernaut seems to be working on node v0.6.21-pre.

@noahgibbs

This comment has been minimized.

Show comment
Hide comment
@noahgibbs

noahgibbs Sep 10, 2013

@maccman One problem with that "high abstraction", not only your implementation but all of them, is that Rack doesn't really support it. So in Sinatra, Rails and everything else I've seen, there's no way to do it that's portable across app servers.

For instance, yours supports "Evented" servers -- I'm assuming that's Thin and Puma. But no Unicorn, Racer, WEBrick, etc., nor most JRuby servers.

That's a common problem with all the SSE stuff. Again, Rails has basically the same problem. You can support non-evented servers, sort of, but the same code doesn't work. Rails also makes development mode very painful for SSE because of threading/reloading problems -- MRI doesn't support thread-safe code reloading, so Rails won't do multiple threads with code reloading, and SSE requires multiple threads currently (and forever?).

With that said, we now have websocket support in basically all the latest browsers. So they're not a bad choice any more. Better than SSE, probably, at this point -- less browser support, but much less painful framework support.

noahgibbs commented Sep 10, 2013

@maccman One problem with that "high abstraction", not only your implementation but all of them, is that Rack doesn't really support it. So in Sinatra, Rails and everything else I've seen, there's no way to do it that's portable across app servers.

For instance, yours supports "Evented" servers -- I'm assuming that's Thin and Puma. But no Unicorn, Racer, WEBrick, etc., nor most JRuby servers.

That's a common problem with all the SSE stuff. Again, Rails has basically the same problem. You can support non-evented servers, sort of, but the same code doesn't work. Rails also makes development mode very painful for SSE because of threading/reloading problems -- MRI doesn't support thread-safe code reloading, so Rails won't do multiple threads with code reloading, and SSE requires multiple threads currently (and forever?).

With that said, we now have websocket support in basically all the latest browsers. So they're not a bad choice any more. Better than SSE, probably, at this point -- less browser support, but much less painful framework support.

@hgosalia

This comment has been minimized.

Show comment
Hide comment
@hgosalia

hgosalia Jan 20, 2014

@fuzzmonkey - Thanks, that worked for me. I was on node v0.10.21 ... after installing v0.6.21 through nvm, I launched http://localhost:8080 and saw the Juggernaut Hello World page instantly. Thanks again!

hgosalia commented Jan 20, 2014

@fuzzmonkey - Thanks, that worked for me. I was on node v0.10.21 ... after installing v0.6.21 through nvm, I launched http://localhost:8080 and saw the Juggernaut Hello World page instantly. Thanks again!

@fuzzmonkey

This comment has been minimized.

Show comment
Hide comment
@fuzzmonkey

fuzzmonkey Jan 27, 2014

@hgosalia i'd suggest switching to maintained project. You should check out http://faye.jcoglan.com.

fuzzmonkey commented Jan 27, 2014

@hgosalia i'd suggest switching to maintained project. You should check out http://faye.jcoglan.com.

@alexandre-mbm

This comment has been minimized.

Show comment
Hide comment
@alexandre-mbm

alexandre-mbm Mar 11, 2015

I found that I needed specify an old version for the node. And that I must use engines instead engine.

alexandre-mbm commented Mar 11, 2015

I found that I needed specify an old version for the node. And that I must use engines instead engine.

@brendon

This comment has been minimized.

Show comment
Hide comment
@brendon

brendon Aug 12, 2015

I was a bit reluctant at first, but the switch to Faye really was quite easy. The Railscast of Faye is still quite current, and the hardest part was writing a utility method that posted messages to the Faye server from (in my case) a Rails controller. It'd be wise to implement the incoming message security mentioned in the Railscast also.

brendon commented Aug 12, 2015

I was a bit reluctant at first, but the switch to Faye really was quite easy. The Railscast of Faye is still quite current, and the hardest part was writing a utility method that posted messages to the Faye server from (in my case) a Rails controller. It'd be wise to implement the incoming message security mentioned in the Railscast also.

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