[GH-ISSUE #199] Bug when try to read log on network drive #167

New issue

Closed

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

kerem commented

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

Owner

Originally created by @azertyii on GitHub (Jul 31, 2018).
Original GitHub issue: https://github.com/NarrativeScience-old/log.io/issues/199

Hello,
I'm on ubuntu 16.04. When i read a log file dpkg.log on my own virtual machine it works. But when i create a network drive to read a log file on another server it doesn't work.
There are my harvester "application_server" but no log in log.io.
My harvester.conf :
exports.config = {
nodeName: "application_server",
logStreams:{
message:[
"/media/configuration/idsQueue.log" //This is my log file
]
},
server: {
host '127.0.0.1',
port: 28777
}
}

Thx,

Originally created by @azertyii on GitHub (Jul 31, 2018). Original GitHub issue: https://github.com/NarrativeScience-old/log.io/issues/199 Hello, I'm on ubuntu 16.04. When i read a log file dpkg.log on my own virtual machine it works. But when i create a network drive to read a log file on another server it doesn't work. There are my harvester "application_server" but no log in log.io. My harvester.conf : exports.config = { nodeName: "application_server", logStreams:{ message:[ "/media/configuration/idsQueue.log" //This is my log file ] }, server: { host '127.0.0.1', port: 28777 } } Thx,

kerem closed this issue

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

kerem commented

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

Author

Owner

@jnovack commented on GitHub (Oct 5, 2018):

This does not work with Node v8. This project was last alive in 2014. You are advised to seek an alternate project.

@jnovack commented on GitHub (Oct 5, 2018): This does not work with Node v8. This project was last alive in 2014. You are advised to seek an alternate project.

kerem commented

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

Author

Owner

@msmathers commented on GitHub (Jan 12, 2020):

This issue is being caused by something below the application stack. log.io uses node.js' native fs.watch() to detect file changes, which uses inotify on linux. There's a known issue with inotify & NFS: https://stackoverflow.com/a/4231277

@msmathers commented on GitHub (Jan 12, 2020): This issue is being caused by something below the application stack. log.io uses node.js' native `fs.watch()` to detect file changes, which uses `inotify` on linux. There's a known issue with inotify & NFS: https://stackoverflow.com/a/4231277