[GH-ISSUE #96] Conflict with 2 same harvester.conf on 2 different serveurs

kerem commented

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

Owner

Originally created by @Dual-Boot on GitHub (Oct 28, 2013).
Original GitHub issue: https://github.com/NarrativeScience-old/log.io/issues/96

Hi,

I have just discovered that could be an indesign bug. Here the problem :
I have 2 serveurs running 2 havresters and every harvester are collecting Apache logs.
If I launch one harvester then the second, the second only appears once then disappears.
The harvester configuration files are like these :

first harvester :
exports.config = {
nodeName: "srv-proxy01",
logStreams: {
apache: [
"/var/log/apache2/access.log",
"/var/log/apache2/error.log"
],
apache_mail_freesquare_org_ssl: [
"/var/log/apache2/mail.freesquare.org-ssl_access.log",
"/var/log/apache2/mail.freesquare.org-ssl.error.log"
],
auth: [
"/var/log/auth.log"
],
kernel: [
"/var/log/kern.log"
],
syslog: [
"/var/log/syslog"
],
fail2ban: [
"/var/log/fail2ban.log"
]
},
server: {
host: '192.168.0.8',
port: 28777
}
}
the second one :
exports.config = {
nodeName: "srv-octo01",
logStreams: {
apache: [
"/var/log/apache2/access.log",
"/var/log/apache2/error.log"
],
apache_octopussy: [
"/var/log/apache2/octopussy.log",
"/var/log/apache2/octopussy-error.log"
]
},
server: {
host: '192.168.0.8',
port: 28777
}
}

In the second one if I change those lines :
apache: [
"/var/log/apache2/access.log",
"/var/log/apache2/error.log"
],
by :
apache_srv_octo01: [
"/var/log/apache2/access.log",
"/var/log/apache2/error.log"
],

And restart the harvester, everything is OK. It seems that writting the same configuration logStreams caused the problem.

Best regards,

Originally created by @Dual-Boot on GitHub (Oct 28, 2013). Original GitHub issue: https://github.com/NarrativeScience-old/log.io/issues/96 Hi, I have just discovered that could be an indesign bug. Here the problem : I have 2 serveurs running 2 havresters and every harvester are collecting Apache logs. If I launch one harvester then the second, the second only appears once then disappears. The harvester configuration files are like these : - first harvester : exports.config = { nodeName: "srv-proxy01", logStreams: { apache: [ "/var/log/apache2/access.log", "/var/log/apache2/error.log" ], apache_mail_freesquare_org_ssl: [ "/var/log/apache2/mail.freesquare.org-ssl_access.log", "/var/log/apache2/mail.freesquare.org-ssl.error.log" ], auth: [ "/var/log/auth.log" ], kernel: [ "/var/log/kern.log" ], syslog: [ "/var/log/syslog" ], fail2ban: [ "/var/log/fail2ban.log" ] }, server: { host: '192.168.0.8', port: 28777 } } - the second one : exports.config = { nodeName: "srv-octo01", logStreams: { apache: [ "/var/log/apache2/access.log", "/var/log/apache2/error.log" ], apache_octopussy: [ "/var/log/apache2/octopussy.log", "/var/log/apache2/octopussy-error.log" ] }, server: { host: '192.168.0.8', port: 28777 } } In the second one if I change those lines : apache: [ "/var/log/apache2/access.log", "/var/log/apache2/error.log" ], by : apache_srv_octo01: [ "/var/log/apache2/access.log", "/var/log/apache2/error.log" ], And restart the harvester, everything is OK. It seems that writting the same configuration logStreams caused the problem. Best regards,

kerem closed this issue

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

kerem commented

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

Author

Owner

@Dual-Boot commented on GitHub (Oct 28, 2013):

So I think the solution is link to the server log.io process.
When modifying a harvester (not creating a new one), we have to stop the harvester and stop server log.io then start again the server log.io then the the harvester process. Quiet strange. But I did see something about that. Maybe a cache problem from the serveur ?

@Dual-Boot commented on GitHub (Oct 28, 2013): So I think the solution is link to the server log.io process. When modifying a harvester (not creating a new one), we have to stop the harvester and stop server log.io then start again the server log.io then the the harvester process. Quiet strange. But I did see something about that. Maybe a cache problem from the serveur ?

kerem commented

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

Author

Owner

@msmathers commented on GitHub (Nov 5, 2013):

I'm not entirely sure I understand the problem you're having here. If you see a new node or stream appear in the list on the left, and then suddenly disappear, it means the harvester process associated with that node and stream went down. So either the harvester process was terminated, or the node went offline.

The harvester is actually designed to allow the same logStream name across multiple nodes, that's one of its features. We encourage people to use the same logStream name, actually.

@msmathers commented on GitHub (Nov 5, 2013): I'm not entirely sure I understand the problem you're having here. If you see a new node or stream appear in the list on the left, and then suddenly disappear, it means the harvester process associated with that node and stream went down. So either the harvester process was terminated, or the node went offline. The harvester is actually designed to allow the same logStream name across multiple nodes, that's one of its features. We encourage people to use the same logStream name, actually.

kerem commented

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

Author

Owner

@Dual-Boot commented on GitHub (Nov 6, 2013):

Hi,

Sorry for the convenience, it was a mistake from me.
I also think I am not running the lastest version, I have installed it from npm.

Best regards

/
/-------------------------------------
| Guy CARRÉ |
| ************* |
| PostMaster - SysAdmin |
| |
| "Free Your Mind. Think Open Source" |
| april.org |
| |
|_____________________________________|

----- Mail original -----
De: "Mike Smathers" notifications@github.com
À: "NarrativeScience/Log.io" Log.io@noreply.github.com
Cc: "Dual-Boot" guycarre@free.fr
Envoyé: Mardi 5 Novembre 2013 23:35:35
Objet: Re: [Log.io] Conflict with 2 same harvester.conf on 2 different serveurs (#96)

I'm not entirely sure I understand the problem you're having here. If you see a new node or stream appear in the list on the left, and then suddenly disappear, it means the harvester process associated with that node and stream went down. So either the harvester process was terminated, or the node went offline.

The harvester is actually designed to allow the same logStream name across multiple nodes, that's one of its features. We encourage people to use the same logStream name, actually.

—
Reply to this email directly or view it on GitHub .

@Dual-Boot commented on GitHub (Nov 6, 2013): Hi, Sorry for the convenience, it was a mistake from me. I also think I am not running the lastest version, I have installed it from npm. Best regards --- / \ /-------------------------------------\ | Guy CARRÉ | | ************\* | | PostMaster - SysAdmin | | | | "Free Your Mind. Think Open Source" | | april.org | | | |_____________________________________| ----- Mail original ----- De: "Mike Smathers" notifications@github.com À: "NarrativeScience/Log.io" Log.io@noreply.github.com Cc: "Dual-Boot" guycarre@free.fr Envoyé: Mardi 5 Novembre 2013 23:35:35 Objet: Re: [Log.io] Conflict with 2 same harvester.conf on 2 different serveurs (#96) I'm not entirely sure I understand the problem you're having here. If you see a new node or stream appear in the list on the left, and then suddenly disappear, it means the harvester process associated with that node and stream went down. So either the harvester process was terminated, or the node went offline. The harvester is actually designed to allow the same logStream name across multiple nodes, that's one of its features. We encourage people to use the same logStream name, actually. — Reply to this email directly or view it on GitHub .

Rows
Columns

[GH-ISSUE #96] Conflict with 2 same harvester.conf on 2 different serveurs #75