Page 2 of 6
Re: Command to check Windows logs
Posted: Tue Sep 22, 2015 4:08 pm
by tgriep
Thanks eloyd. 8)
Re: Command to check Windows logs
Posted: Tue Sep 22, 2015 10:41 pm
by jamesc23
Looks like this is not going anywhere. Thanks for the input. will have to find help from elsewhere.
Re: Command to check Windows logs
Posted: Wed Sep 23, 2015 9:10 am
by hsmith
tgriep wrote:If they are in the Unconfigured Objects, you would click on them to import them into XI and that is how the service checks will be setup for you.
Is this step not working for you? Generally we wait for feedback after a post to see if further troubleshooting needs to be done.
Re: Command to check Windows logs
Posted: Wed Sep 23, 2015 3:56 pm
by tmcdonald
I have to agree with
@hsmith here - the quoted post from
@tgriep is the next step in getting passive results to work. If that step is not working for you, please tell us otherwise we have no way of knowing.
Re: Command to check Windows logs
Posted: Wed Sep 23, 2015 7:13 pm
by jamesc23
My apologies for jumping the gun.
So, the server I'm wanting to create the service on isn't appearing in the unconfigured objects. I was trying to create the service using traditional way but I don't have the syntax (if there's one) for this. I did find an article here -
https://kb.op5.com/display/HOWTOs/How+t ... ventlog+ID but it didn't work for me. as I got the unknown error message as mentioned earlier.
Thanks guys.
Re: Command to check Windows logs
Posted: Wed Sep 23, 2015 9:23 pm
by eloyd
op5 is not a Nagios Enterprise product. Are you using op5 or actually using Nagios?
Re: Command to check Windows logs
Posted: Wed Sep 23, 2015 10:21 pm
by jamesc23
Nagios. I was referring to the command line, not the product. I found something similar to the command lines from op5 site but I couldn't get the service to work.
Re: Command to check Windows logs
Posted: Thu Sep 24, 2015 9:33 am
by tmcdonald
jamesc23 wrote:I was referring to the command line, not the product.
I'm a little confused by this, can you clarify?
Also, just so you know, the passive results come in including a host name and a service description for a service check, or just a host name if it is a host check. If there is a matching host/service in the running configuration, it will be updated with this information. If not, it will show in Unconfigured Objects. Are you sure you do not already have a host/service set up?
Re: Command to check Windows logs
Posted: Thu Sep 24, 2015 9:00 pm
by jamesc23
We're obviously not on the same page.
Let's start again. I'm quite new to Nagios and am working on setting up/standardising Nagios that I've picked up from previous employee. I want to set up a service that can monitor an event and alert us when there's an error. I tried to create a service using check_mrpe but I couldn't get it to work. Then you mentioend NSCA so I configured this and I think it's enabled. I just couldn't get NSCA to report on an event log.
The host I was working on was already setup in Nagios and I believe that's why it doesn't appear in the unconfigured objects. Now I'm under the impression that if a host isn't configured with anything it should show up under unconfigured objects. So, I deleted all services that's associated to this host but I still don't see this host under unconfigured objects.
All I'm trying to achieve is to set up a service using whatever module that will give me a report on windows event ID.
Hope this clarifies a few things?
Thanks.
Re: Command to check Windows logs
Posted: Fri Sep 25, 2015 2:04 pm
by jdalrymple
By default debugging isn't enabled in nsca. Edit /usr/local/nagios/etc/nsca.cfg to turn debugging on:
Code: Select all
# DEBUGGING OPTION
# This option determines whether or not debugging
# messages are logged to the syslog facility.
# Values: 0 = debugging off, 1 = debugging on
debug=1
As noted, if things are working at all - debug logging will start rolling into your /var/log/messages.
Example:
Code: Select all
Sep 25 14:03:38 nagiosserver nsca[10605]: SERVICE CHECK -> Host Name: 'monitoredserver', Service Description: 'IMAP Service', Return Code: '0', Output: 'IMAP OK - 0.086 second response time on port 143 [* OK monitoredserver.domain.net Cyrus IMAP4 v2.2.13 server ready]|time=0.086065s;;;0.000000;10.000000'