[GH-ISSUE #12] Unable to show anything on web. #9

New issue

Closed

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

kerem commented

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

Owner

Originally created by @murvinlai on GitHub (Sep 27, 2011).
Original GitHub issue: https://github.com/NarrativeScience-old/log.io/issues/12

I have installed and "sudo ./install/server" and "sudo /etc/init.d/log.io-harvester start" but I don't see the left menu as in the sample (http://logio.org:8998/). my thing has only empty menu

Result of cat /var/log/log.io/server.log

info - 14:40:09 - Nodes: 0, WebClients: 0, Messages Sent: 0

Result of /var/log/log.io/harvester.log

14:40:19 - Watching: /var/log/log.io/harvester.log (logio_harvester)

ps -A | grep log:
1906 ? 00:00:00 log-server

the configuration is:
cat /etc/log.io/server.conf
/* Log.io log server configuration */

exports.config = {

// Log server port
port: 8998,

// Uncomment to enable basic HTTP authentication
/*
basic_auth: {
username: "foo",
password: "bar"
}
*/
}

cat /etc/log.io/harvester.conf
/* Log.io log harvester configuration */

exports.config = {

// Log server host & port
server: {
host: '127.0.0.1',
port: 8998,
},

// Watch the following log files, defined by label:path mappings
log_file_paths: {
logio_harvester: '/var/log/log.io/harvester.log'
},

// Define name of current machine.
// Alternatively, you can set this name in /etc/profile:
// export LOGIO_HARVESTER_INSTANCE_NAME='my_log_machine'
// If so, comment out the line below
instance_name : 'log_node_1'

}

any idea?

Originally created by @murvinlai on GitHub (Sep 27, 2011). Original GitHub issue: https://github.com/NarrativeScience-old/log.io/issues/12 I have installed and "sudo ./install/server" and "sudo /etc/init.d/log.io-harvester start" but I don't see the left menu as in the sample (http://logio.org:8998/). my thing has only empty menu Result of cat /var/log/log.io/server.log info - 14:40:09 - Nodes: 0, WebClients: 0, Messages Sent: 0 Result of /var/log/log.io/harvester.log 14:40:19 - Watching: /var/log/log.io/harvester.log (logio_harvester) ps -A | grep log: 1906 ? 00:00:00 log-server the configuration is: cat /etc/log.io/server.conf /\* Log.io log server configuration */ exports.config = { // Log server port port: 8998, // Uncomment to enable basic HTTP authentication /* basic_auth: { username: "foo", password: "bar" } */ } cat /etc/log.io/harvester.conf /\* Log.io log harvester configuration */ exports.config = { // Log server host & port server: { host: '127.0.0.1', port: 8998, }, // Watch the following log files, defined by label:path mappings log_file_paths: { logio_harvester: '/var/log/log.io/harvester.log' }, // Define name of current machine. // Alternatively, you can set this name in /etc/profile: // export LOGIO_HARVESTER_INSTANCE_NAME='my_log_machine' // If so, comment out the line below instance_name : 'log_node_1' } any idea?

kerem closed this issue

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

kerem commented

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

Author

Owner

@mingfai commented on GitHub (Sep 29, 2011):

I just tried to run Log.io with the current git snapshot and it doesn't work for me. The installation is successful, the web server is up and running and the harvester is monitoring a nginx log that I have specified (according to /var/log/log.io/harvester.log), but on the web screen, the log file name isn't shown on the left hand side panel. It would be great if the dev could tag a stable version. thx

@mingfai commented on GitHub (Sep 29, 2011): I just tried to run Log.io with the current git snapshot and it doesn't work for me. The installation is successful, the web server is up and running and the harvester is monitoring a nginx log that I have specified (according to /var/log/log.io/harvester.log), but on the web screen, the log file name isn't shown on the left hand side panel. It would be great if the dev could tag a stable version. thx

kerem commented

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

Author

Owner

@msmathers commented on GitHub (Jan 9, 2012):

I'm going to close this issue, as it was likely caused by the new websockets spec that went into effect at the end of September for the latest versions of Chrome & Firefox. This "tricked" earlier versions of socket.io into thinking that the websockets protocol was available and functional, preventing fallback transports. Log.io 0.2.x uses socket.io v0.8.4, which resolved this issue.

@msmathers commented on GitHub (Jan 9, 2012): I'm going to close this issue, as it was likely caused by the new websockets spec that went into effect at the end of September for the latest versions of Chrome & Firefox. This "tricked" earlier versions of socket.io into thinking that the websockets protocol was available and functional, preventing fallback transports. Log.io 0.2.x uses socket.io v0.8.4, which resolved this issue.