I haven't tried it myself but running "cmd /c" should kick off another process.
Thanks, earlier for log file monitoring we used the .exe plugin. In ncpa.cfg we tried with cmd but it didnt worked and I believe we were not aware of the syntax "cmd /c". After thats we installed perl on windows used the perl plugin. But I am going to check this if this works.
balothia wrote:We got the error message when we tried running the check_winevent plugin. I am attaching the screen shot.
Thanks,
Gautam
I am able to resolve the issue, now plugin is running. But i am not able to pass the arguments to plugin using -a option. "-a --window "10 minutes" -a --type "audit failure""
I am confirm that there is a problem with parsing the arguments. Our NCPA developer is looking at this as we speak. We will post a possible solution/workaround as soon as we have one.
Be sure to check out our Knowledgebase for helpful articles and solutions!
lmiltchev wrote:I am confirm that there is a problem with parsing the arguments. Our NCPA developer is looking at this as we speak. We will post a possible solution/workaround as soon as we have one.
Thanks lmiltchev, as of now i am using the batch file with ncpa agent to run the plugin with parameters but thats not helping at all. Just for example if there 5 audit failures and critical threshold is set 4. The plugin output should be Critical as well but on Nagios its coming as green(OK) an"Event Critical event 5".
nscott wrote:I am working on this and there is a bug where the plugins aren't getting passed properly. I'm working on a fix now.
Hi Scott & Team,
Do we have any updates on this issue? I know it might take sometime but we have to golive with our systems. If you suggest we can move to NSClient++, but really I want to use NCPA on all our servers. As it supported most of available OS platforms.
Just wanted to give you heads up. Nick Scott is off today but he will be in the office tomorrow afternoon, and will follow up with you on the development. Unfortunately, I don't know how much he's done on fixing the bug.
Be sure to check out our Knowledgebase for helpful articles and solutions!