[GH-ISSUE #23] cannot get / #19

New issue

Closed

opened 2026-02-26 05:31:05 +03:00 by kerem · 2 comments

kerem commented

2026-02-26 05:31:05 +03:00

Owner

Originally created by @ckrimmel on GitHub (Mar 2, 2012).
Original GitHub issue: https://github.com/NarrativeScience-old/log.io/issues/23

I followed the latest Ubuntu build recipe step by step with no known issues. When I attempt to access the log.io interface at http://servername:8998 I get "cannot get /"

When starting server --

Starting Log.io server...
Launching forever process...
info: Forever processing file: /usr/local/bin/log.io-server
Done.
Done.

When starting harvester --
Starting Log.io harvester...
Launching forever process...
info: Forever processing file: /usr/local/bin/log.io-harvester
Done.
Done.

Nothing is appearing in the system logs, log.io harvester or server logs.

If I start log.io via "/usr/local/bin/log.io-server start" I get "info - socket.io started". It doesn't appear that the server is listening on the port. If I start the server, then start the harvester via command "log.io-harvester start" it tells me that it's trying to find the server repeatedly.

Originally created by @ckrimmel on GitHub (Mar 2, 2012). Original GitHub issue: https://github.com/NarrativeScience-old/log.io/issues/23 I followed the latest Ubuntu build recipe step by step with no known issues. When I attempt to access the log.io interface at http://servername:8998 I get "cannot get /" When starting server -- Starting Log.io server... Launching forever process... info: Forever processing file: /usr/local/bin/log.io-server Done. Done. When starting harvester -- Starting Log.io harvester... Launching forever process... info: Forever processing file: /usr/local/bin/log.io-harvester Done. Done. Nothing is appearing in the system logs, log.io harvester or server logs. If I start log.io via "/usr/local/bin/log.io-server start" I get "info - socket.io started". It doesn't appear that the server is listening on the port. If I start the server, then start the harvester via command "log.io-harvester start" it tells me that it's trying to find the server repeatedly.

kerem closed this issue

2026-02-26 05:31:05 +03:00

kerem commented

2026-02-26 05:31:05 +03:00

Author

Owner

@msmathers commented on GitHub (Mar 2, 2012):

Turns out the connect.js dependency just released v2.0, which has some backwards-incompatible changes. I just committed a package.json update that forces an install of <=1.8.4, which fixes the problem for now until we have time to update the connect calls. I've republished the npm so it should work if you do a fresh install.

@msmathers commented on GitHub (Mar 2, 2012): Turns out the connect.js dependency just released v2.0, which has some backwards-incompatible changes. I just committed a package.json update that forces an install of <=1.8.4, which fixes the problem for now until we have time to update the connect calls. I've republished the npm so it should work if you do a fresh install.

kerem commented

2026-02-26 05:31:05 +03:00

Author

Owner

@ckrimmel commented on GitHub (Mar 2, 2012):

That did the trick! Thank you very much Mike!

Cliff

On Fri, Mar 2, 2012 at 2:21 PM, Mike Smathers <
reply@reply.github.com

wrote:

Turns out the connect.js dependency just released v2.0, which has some
backwards-incompatible changes. I just committed a package.json update
that forces an install of <=1.8.4, which fixes the problem for now until we
have time to update the connect calls. I've republished the npm so it
should work if you do a fresh install.

Reply to this email directly or view it on GitHub:
https://github.com/NarrativeScience/Log.io/issues/23#issuecomment-4292244

@ckrimmel commented on GitHub (Mar 2, 2012): That did the trick! Thank you very much Mike! Cliff On Fri, Mar 2, 2012 at 2:21 PM, Mike Smathers < reply@reply.github.com > wrote: > > Turns out the connect.js dependency just released v2.0, which has some > backwards-incompatible changes. I just committed a package.json update > that forces an install of <=1.8.4, which fixes the problem for now until we > have time to update the connect calls. I've republished the npm so it > should work if you do a fresh install. > > --- > > Reply to this email directly or view it on GitHub: > https://github.com/NarrativeScience/Log.io/issues/23#issuecomment-4292244