-
Notifications
You must be signed in to change notification settings - Fork 19
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
Windows service restart hagning with windows_eventlog2 #59
Comments
Isn't this same as #57 with your AV. Tell the AV to exclude the file. |
Yeah, this issue should be the same root of cause. |
@flurreN and @cosmo0920 thanks for the help, however i tried the exclusion like before and then even turning off the AV agent completely and still had the issue. It turned out my Config Management code (Puppet) was broken (not idempotent) and it was trying to delete the service definition then recreate it, then restart it. When this happened the service would fail to stop, probably something to do with the service definition being deleted and recreated. Fixing the idempotency in my Puppet code solved the issue and Puppet can now successfully manage the service, restart it with config changes, etc. Here is the PR with the fix: https://github.com/EncoreTechnologies/puppet-fluentd/pull/5/files |
@flurreN and @cosmo0920 as a side note... FluentD on Windows is working AMAZING compared to NXLog! We've also been using the client-side parsing and filtering capabilities to take a TON of load off of our central logging servers (Graylog). Thank you very much for your help, i'm really excited about FluentD!!! |
Direct Hash object mapping is very helpful to reduce resource usage. This is Ruby's magic! 😄 ... And tons of hand writing code here: https://github.com/fluent-plugins-nursery/winevt_c/blob/master/ext/winevt/winevt_utils.cpp 💪 |
Hello, i just recently deployed FluentD on Windows to all of our DEV machines and am noticing that when trying to restart the FluentD service, that it is failing to stop the underlying ruby processes causing the restart to hang and eventually fail.
Here is our config:
I don't see anything obvious in the logs other than the worker says it has stopped but the process keeps on running:
Anything that i can check or try to help debug and fix this?
The text was updated successfully, but these errors were encountered: