[GH-ISSUE #147] Cannot connect to server on a Windows system #120

New issue

Closed

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

kerem commented

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

Owner

Originally created by @ZaLiTHkA on GitHub (Jan 24, 2015).
Original GitHub issue: https://github.com/NarrativeScience-old/log.io/issues/147

I'm currently doing some research into real-time log file viewers to bundle with a couple corporate level software packages; the app suites in question are either desktop or web based Java based systems running locally with bundled Java and Tomcat on the target installation machine. So including something like Log.io would be dead simple from my side.

So far I've had no issues installing Log.io, but running it seems to be a different story.. After installing, I start the server with log.io-server with no issues and set the paths to my log files in harvester.conf, but when I try run log.io-harvester, I get a message stating error: Unable to connect server, trying again... over and over.

At first I thought it was my log files path, but I've tried the typical E:\\path to\\log file.log and E:/path to/log file.log path definitions, which made no difference. When I deliberately use an invalid path, log.io-harvester complains that the file cannot be found, but still no server connection.

I should note, the web server side is starting up correctly and I can access the UI through localhost:28778, which shows "0 streams, 0 nodes, 0 messages.." etc, with no errors or warnings shown in the browser console. Running curl http://localhost:28777 from another prompt shows a response in the log.io-server window, but that's all I can do with it.

Am I being silly here? What am I missing? Is there any way to run Log.io with verbose output to see more detail?

Originally created by @ZaLiTHkA on GitHub (Jan 24, 2015). Original GitHub issue: https://github.com/NarrativeScience-old/log.io/issues/147 I'm currently doing some research into real-time log file viewers to bundle with a couple corporate level software packages; the app suites in question are either desktop or web based Java based systems running locally with bundled Java and Tomcat on the target installation machine. So including something like Log.io would be dead simple from my side. So far I've had no issues installing Log.io, but running it seems to be a different story.. After installing, I start the server with `log.io-server` with no issues and set the paths to my log files in `harvester.conf`, but when I try run `log.io-harvester`, I get a message stating `error: Unable to connect server, trying again...` over and over. At first I thought it was my log files path, but I've tried the typical `E:\\path to\\log file.log` and `E:/path to/log file.log` path definitions, which made no difference. When I deliberately use an invalid path, `log.io-harvester` complains that the file cannot be found, but still no server connection. I should note, the web server side is starting up correctly and I can access the UI through `localhost:28778`, which shows "0 streams, 0 nodes, 0 messages.." etc, with no errors or warnings shown in the browser console. Running `curl http://localhost:28777` from another prompt shows a response in the `log.io-server` window, but that's all I can do with it. Am I being silly here? What am I missing? Is there any way to run Log.io with verbose output to see more detail?

kerem closed this issue

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

kerem commented

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

Author

Owner

@Deadarius commented on GitHub (Apr 23, 2015):

Try to set server.host to 127.0.0.1 instead of default 0.0.0.0. It worked for me.

@Deadarius commented on GitHub (Apr 23, 2015): Try to set server.host to 127.0.0.1 instead of default 0.0.0.0. It worked for me.

kerem commented

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

Author

Owner

@ZaLiTHkA commented on GitHub (Apr 24, 2015):

Thanks for the tip. I've been swamped with other work since I posted this, but hopefully I'll get a chance to look into this again soon.

@ZaLiTHkA commented on GitHub (Apr 24, 2015): Thanks for the tip. I've been swamped with other work since I posted this, but hopefully I'll get a chance to look into this again soon.

kerem commented

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

Author

Owner

@ZaLiTHkA commented on GitHub (May 14, 2015):

I've spent most of my free time the last couple weeks working out the finer details of environment configuration for development in Windows with NodeJS. Finally got to the point where I can get native libraries to compile reliably on three different Windows machines (yay).

However, I'm still not having any joy with getting this to run under Windows. I got it running fine in my Ubuntu VM though, and then I found issue #76 which stated (semi-recently) that there are issues with Log.io and Windows. There are one or two personal projects where this would be useful to me, but I'll have to carry on looking for a real-time log tail system that doesn't commit suicide when it enters the same room as a Microsoft OS...

@ZaLiTHkA commented on GitHub (May 14, 2015): I've spent most of my free time the last couple weeks working out the finer details of environment configuration for development in Windows with NodeJS. Finally got to the point where I can get native libraries to compile reliably on three different Windows machines (yay). However, I'm still not having any joy with getting this to run under Windows. I got it running fine in my Ubuntu VM though, and then I found issue #76 which stated (semi-recently) that there are issues with Log.io and Windows. There are one or two personal projects where this would be useful to me, but I'll have to carry on looking for a real-time log tail system that doesn't commit suicide when it enters the same room as a Microsoft OS...

kerem referenced this issue

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

[PR #122] [MERGED] Fixes harvester durability issues, addresses #70, #85, #114, #120 #248