Windows Evenlog Monitoring Issues

[[email protected]]

I'm looking in purchasing Nagios XI for our Unversity and I'm running into an issue trying to monitor a Windows 2008 R2 server's eventlogs. Which method does the Nagios support team recommend and can support? I've tried two differant methods and I couldn't get either one to work. I really like the NagEventLog method, with the client configuration gui and genterate tests from it. But it appears not to be supported?

1. Used the Windows Eventlog wizard and ran into the same regedit32 error that the other posts have experience during the install and the services sends out errors to App event log with no description. I also download the x64 binary files and copied over the 32 versions. No firewalls are turned on attempted to configure based on several docs and forum suggestions. Using the same increption method on both sides. Tried 3DES and NONE. Verified host server is listening on port 5667, but don't have a method to test it for Passive checks. Plus it looks like Nagios support team doesn't support the plugin and have referances to a 3rd party website? The service also spits out errors to the eventlog when you restart the services, but no details on the Event ID 0 error.

http://exchange.nagios.org/directory/Ad ... rd/details
http://exchange.nagios.org/directory/Ad ... og/details

2. I tried the following plugin and couldn't get it to work.
http://exchange.nagios.org/directory/Ad ... on/details

If you need any additional information, current settings, debug logs, etc... just let me know.

Thanks
Don

[slansing]

Currently we do not know the status of support for the NagEventLog. It is managed by a third party and so far we have seen no bug fixes related to these installation and service start errors. We have ran through this quite a few times in the office here and even after those unknown errors it does seem to monitor the Event Logs properly. Did you follow our documentation for integrating it?

http://assets.nagios.com/downloads/nagi ... entLog.pdf

[[email protected]]

I did go through all the steps again and where I thought I had modified the "only_from" setting in the /etc/xinetd.d/nsca on the Nagios server. It was set to only allow the localhost. Once that was set correctly, it started working. The errors in the client's event logs after the service started, stopped as well, I assume they were generated when it couldn't connect to the host server. That would had been very helpful info. The NatEventLog is nice, but it does need a little polishing if its going to be part of the commercial product.

Thank you very much for the quick response. It's much apperciated!!

Don