-
Notifications
You must be signed in to change notification settings - Fork 56
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Restart of collector sidecar causes Graylog server to reprocess all messages #46
Comments
@hryzec: Which sidecar version do you use? |
@mariussturm Currently using 2x 0.0.9 (sidecar) and one 0.5.0 (deprecated collector) |
Ok, there was a similar issue please check if it's the same problem for you: #40 Especially the configcache.dat file in the CacheDir is important, if that file is missing NXlog has no idea where to start and ingest the whole file on every run. |
@mariussturm I am using Windows VMs for collectors, nxLog creates log file in the same dir .../data as CacheDir points to but I cannot see any configcache.dat there. nxLog version nxlog-ce-2.9.1716 and collector-sidecar download from 27/7/2016. I have not disabled tthe snippet and distribute to collector hosts using tag 'default'.
|
@mariussturm I played a little with CahceDir setting, used "" and '' t enclose got these errors in nxLog:
I believe the path is ok, also permission should be fine only nxLog does not create the configcache.dat file. |
I think this is kind of a bug in NXLog. The Sidecar is executing NXlog in foreground mode but on a Windows system NXLog never saves the file position when it runs in foreground. Not sure how to solve this :/ |
Yeah, the same behavior when I remove collector-sidecar from the equation and just run nxLog with generated configuration. But what now - their forum sucks :\ As soon as this is only a Windows issue it should not matter that much once I deploy this into production as we have only Linux machines (SLES). But still it is a little awkward. When would new release of GL Server and Collector Sidecar v. 1 eventually be? |
I looked a little bit more into this. To work around this NXlog limitation I have to do a bigger change in the way the collector is started and executed. For now you can switch to Filebeat instead, the binary is included in the Sidecar packages. I will fix the issue around 0.10 I guess. |
Ok, thank you for your prompt help @mariussturm! I will have a look on that. |
Hi, just to update the actual cause... I have reply from nxLog support:
So just to clarify... The .dat and .pid files are created only when nxLog is running as service. As soon as nxLog runs with -f it does not creates neither .dat or .pid file?
|
Thanks for the update! |
@mariussturm Sorry, just one more thing little bit outside of this actual nxLog issue... I cannot really find any filebeat Collector Configuration Input/Output examples or description on web. I have downloaded 2.1.0 Beta 4-1 Server now but ave no idea how to create working configuration that collector sidecar would download and create local filebeat.conf. Currently it just creates file with empty prospector and says:
|
It works basically like the nxlog configuration but on the 'Beats'-tab. Here is a step-by-step guide how to create a configuration: http://docs.graylog.org/en/2.1/pages/collector_sidecar.html#step-by-step-guide |
Thanks @mariussturm ! I will have a look on it. |
@mariussturm i'm trying to configure filebeat, but when i'm creating new collector configuration, i cannot see 'Beats" tab. |
@tennaen you have to upgrade to Graylog 2.1 for that feature. |
@mariussturm i have updated Graylog to 2.1, but still can't see any tabs. |
@tennaen which OS and browser version do you use? Do you see a javascript error in the developer console of your browser? |
Now it is working. Problem was with firefox cache. Thanks. |
@hryzec in 0.1.0-alpha.1 is a fix for this issue, could you please test that version? |
Closing this, please open a new ticket if there are more problems with nxlog on Windows hosts. |
From graylog-labs/graylog2-web-interface#1734.
@hryzec wrote:
The text was updated successfully, but these errors were encountered: