Skip to content
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

Log Parser Input Plugin does not work on RHEL 5 #2805

Closed
sudharani-m opened this issue May 15, 2017 · 5 comments
Closed

Log Parser Input Plugin does not work on RHEL 5 #2805

sudharani-m opened this issue May 15, 2017 · 5 comments
Labels
bug unexpected problem or unintended behavior help wanted Request for community participation, code, contribution

Comments

@sudharani-m
Copy link

Hello Team,

We are running telegraf version v1.2.1 in RHEL 5 server. We are using log parser plugin to send CPU info. However while running the telegraf agent we are getting following error message.
Telegraf.conf file
[inputs.logparser.grok]
    patterns = ["%{DATA:host_name:tag} %{DATA:metric:tag} %{NUMBER:mft_value:float}"] 

Error:
2017-05-15T07:07:00Z I! Started TCP listener service on :8094
2017/05/15 02:07:00 Seeked /opt/mft/shared/logs/cpu.log - &{Offset:0 Whence:0}
2017/05/15 02:07:00 FATAL -- failed to create Watcher
goroutine 47 [running]: 

Do we have RHEL compatibility issue with this plugin?

@danielnelson
Copy link
Contributor

Seems like a compatibility issue, can you add the output of uname -a.

If you are able can you git clone https://github.com/fsnotify/fsnotify and run git test ./...

@sudharani-m
Copy link
Author

Linux *** 2.6.18-417.el5xen #1 SMP Sat Nov 19 14:57:52 EST 2016 x86_64 x86_64 x86_64 GNU/Linux

@danielnelson danielnelson changed the title Log Parser Input Plugin Log Parser Input Plugin does not work on RHEL 5 May 18, 2017
@danielnelson
Copy link
Contributor

To solve this we need someone to check if the fsnotify tests work on RHEL or Centos 5. I'm assuming the tests will fail, and then we can open a ticket upstream.

@danielnelson danielnelson added bug unexpected problem or unintended behavior help wanted Request for community participation, code, contribution labels May 18, 2017
@danielnelson
Copy link
Contributor

danielnelson commented Oct 24, 2017

In version 1.5 we are adding a watch_method = "poll" option which I believe will be a workaround for this issue.

@danielnelson
Copy link
Contributor

Closing, RHEL5 users should use the poll method.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug unexpected problem or unintended behavior help wanted Request for community participation, code, contribution
Projects
None yet
Development

No branches or pull requests

2 participants