Re: [Nagios-users] nsclient, is it still an acceptable method to monitor nt
Michael Medin wrote: > Rui Miguel Silva Seabra skrev: >> Sex, 2007-11-09 às 11:35 +0100, Andreas Ericsson escreveu: >> >> NSClient++ has a nasty bug on the option to check services. It can't >> handle services that contain white space in their names. >> > Humm... > Is this true? > Not that I know of, and I certainly didn't write that. > [EMAIL PROTECTED]:~/src$ check_nrpe -H 192.168.0.147 -c CheckServiceState -a > ShowAll "COM+ Event System" > OK: COM+ Event System: started > > [EMAIL PROTECTED]:~/src$ check_nt -H 192.168.0.147 -p 12489 -v SERVICESTATE > "-lCOM+ Event System" -d SHOWALL > COM+ Event System: Started > > But maybe I missunderstood what did not work? > In that case we misunderstood it the same way. Otoh, if you ever find a service with a vertical tab in its name, that might not work ;-) Rui, could it be that you're checking something using the wrong language for the check, or that you're using the wrong name for the service, or are there perhaps other characters in the service-name that aren't part of the us ascii character set (ñ et al comes to mind)? -- Andreas Ericsson [EMAIL PROTECTED] OP5 AB www.op5.se Tel: +46 8-230225 Fax: +46 8-230231 - SF.Net email is sponsored by: Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ Nagios-users mailing list Nagios-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nagios-users ::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. ::: Messages without supporting info will risk being sent to /dev/null
Re: [Nagios-users] nsclient, is it still an acceptable method to monitor nt
Rui Miguel Silva Seabra skrev: > Sex, 2007-11-09 às 11:35 +0100, Andreas Ericsson escreveu: > > NSClient++ has a nasty bug on the option to check services. It can't > handle services that contain white space in their names. > Humm... Is this true? [EMAIL PROTECTED]:~/src$ check_nrpe -H 192.168.0.147 -c CheckServiceState -a ShowAll "COM+ Event System" OK: COM+ Event System: started [EMAIL PROTECTED]:~/src$ check_nt -H 192.168.0.147 -p 12489 -v SERVICESTATE "-lCOM+ Event System" -d SHOWALL COM+ Event System: Started But maybe I missunderstood what did not work? // Michael Medin > Rui > > All Hail Discordia! > Today is Pungenday, the 21st day of The Aftermath in the YOLD 3173 > + No matter how much you do, you never do enough -- unknown > + Whatever you do will be insignificant, > | but it is very important that you do it -- Gandhi > + So let's do it...? > > > - > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > ___ > Nagios-users mailing list > Nagios-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/nagios-users > ::: Please include Nagios version, plugin version (-v) and OS when reporting > any issue. > ::: Messages without supporting info will risk being sent to /dev/null - SF.Net email is sponsored by: Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ Nagios-users mailing list Nagios-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nagios-users ::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. ::: Messages without supporting info will risk being sent to /dev/null
Re: [Nagios-users] nsclient, is it still an acceptable method to monitor nt
Hi NRPE NT seems to me the best way to monitor windows services. since there are alot of plug ins available at nagiosexchange and around the web. it support windows NT/2000/2003/vista. also 32 and 64 bit. And the biggest advantage it consume little resources compare to the other solutions NRPE NT http://www.nagiosexchange.org/Windows.49.0.html?&tx_netnagext_pi1[p_view]=64 Some basic plugins http://www.nagiosexchange.org/Windows_NRPE.66.0.html?&tx_netnagext_pi1[p_view]=62 Hope it helped Moshe Sharon http://www.centerity.com - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/___ Nagios-users mailing list Nagios-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nagios-users ::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. ::: Messages without supporting info will risk being sent to /dev/null
Re: [Nagios-users] nsclient, is it still an acceptable method to monitor nt
Thanks Andreas, Good Description of the differences, However, you forgot to mension NC_Net also supports NSCA for Passive checks. So in my eyes, each flavor of the current Windows Plugins offers a different set of enhancements, NSCLIENT++ has NRPE and some other enhancements NC_NET has NSCA, event logs, RunScripts,WMI,... (And supports Whitespace in Service names) OpMon - may be introducing NRPE soon? and hopefully other enhancements All three are compatible to the Check_NT from the official Plugins and should return similar results. Tony (Author of NC_Net) On Nov 9, 2007 5:35 AM, Andreas Ericsson <[EMAIL PROTECTED]> wrote: > Giles Coochey wrote: > >> Steve Ensley wrote: > >>> I'm upgrading another departments Nagios 1.3 instance to Nagios 2.9. > >> they > >>> are using nsclient to get some info from some nt servers. Most of > > my > >> Nagios > >>> experience has been monitoring Unix servers. > >>> > >>> The website at http://nsclient.ready2run.nl/ for nsclient doesnt > > seem to > >>> have been touched since 2004. Is it still a viable method to > > monitor nt > >>> servers or is there somthing else I should be looking into to > > replace > >> it. > >> Try NSClient++ instead. It's at sourceforge somewhere, and is quite a > > lot > >> fresher. NSClient might work, but it's getting rather ancient. > >> > > > > I had this same quandary sometime back. > > > > Options were > > > > NSClient (seems too old, not being developed) > > NSClient++ (presumably enhanced in some way) > > OpServices version of NSClient (still being developed) > > NC_Net (still being developed) > > > > In the end I simply went with NC_Net and it appears to work for us just > > fine, and I often see the author on this list, which tells me that he's > > still involved with Nagios in some way. > > > > It would be nice if all the different people who independently developed > > all the different versions 'unforked' their efforts though :-), it would > > make the decision on which one to use much easier, by having a lack of > > choice!! > > They aren't really forks. OpServices have simply taken over maintainership > of NSClient (more or less, as the original author seems to have vanished). > NSClient++ is a re-implementation in C++, with support for NRPE style > script > based checks as well. NC_Net does things through dot net stuff and some m$ > voodoo, but incorporates the NSClient mode of address since that's what > the > official plugins support. > > So it's really three different agents. > > -- > Andreas Ericsson [EMAIL PROTECTED] > OP5 AB www.op5.se > Tel: +46 8-230225 Fax: +46 8-230231 > > - > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > ___ > Nagios-users mailing list > Nagios-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/nagios-users > ::: Please include Nagios version, plugin version (-v) and OS when > reporting any issue. > ::: Messages without supporting info will risk being sent to /dev/null > - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/___ Nagios-users mailing list Nagios-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nagios-users ::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. ::: Messages without supporting info will risk being sent to /dev/null
Re: [Nagios-users] nsclient, is it still an acceptable method to monitor nt
Sex, 2007-11-09 às 11:35 +0100, Andreas Ericsson escreveu: > > NSClient (seems too old, not being developed) > > NSClient++ (presumably enhanced in some way) > > OpServices version of NSClient (still being developed) > > NC_Net (still being developed) > > > > In the end I simply went with NC_Net and it appears to work for us just > > fine, and I often see the author on this list, which tells me that he's > > still involved with Nagios in some way. > > > > It would be nice if all the different people who independently developed > > all the different versions 'unforked' their efforts though :-), it would > > make the decision on which one to use much easier, by having a lack of > > choice!! > > They aren't really forks. OpServices have simply taken over maintainership > of NSClient (more or less, as the original author seems to have vanished). > NSClient++ is a re-implementation in C++, with support for NRPE style script > based checks as well. NC_Net does things through dot net stuff and some m$ > voodoo, but incorporates the NSClient mode of address since that's what the > official plugins support. > > So it's really three different agents. NSClient++ has a nasty bug on the option to check services. It can't handle services that contain white space in their names. Rui All Hail Discordia! Today is Pungenday, the 21st day of The Aftermath in the YOLD 3173 + No matter how much you do, you never do enough -- unknown + Whatever you do will be insignificant, | but it is very important that you do it -- Gandhi + So let's do it...? - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ ___ Nagios-users mailing list Nagios-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nagios-users ::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. ::: Messages without supporting info will risk being sent to /dev/null
Re: [Nagios-users] nsclient, is it still an acceptable method to monitor nt
Giles Coochey wrote: >> Steve Ensley wrote: >>> I'm upgrading another departments Nagios 1.3 instance to Nagios 2.9. >> they >>> are using nsclient to get some info from some nt servers. Most of > my >> Nagios >>> experience has been monitoring Unix servers. >>> >>> The website at http://nsclient.ready2run.nl/ for nsclient doesnt > seem to >>> have been touched since 2004. Is it still a viable method to > monitor nt >>> servers or is there somthing else I should be looking into to > replace >> it. >> Try NSClient++ instead. It's at sourceforge somewhere, and is quite a > lot >> fresher. NSClient might work, but it's getting rather ancient. >> > > I had this same quandary sometime back. > > Options were > > NSClient (seems too old, not being developed) > NSClient++ (presumably enhanced in some way) > OpServices version of NSClient (still being developed) > NC_Net (still being developed) > > In the end I simply went with NC_Net and it appears to work for us just > fine, and I often see the author on this list, which tells me that he's > still involved with Nagios in some way. > > It would be nice if all the different people who independently developed > all the different versions 'unforked' their efforts though :-), it would > make the decision on which one to use much easier, by having a lack of > choice!! They aren't really forks. OpServices have simply taken over maintainership of NSClient (more or less, as the original author seems to have vanished). NSClient++ is a re-implementation in C++, with support for NRPE style script based checks as well. NC_Net does things through dot net stuff and some m$ voodoo, but incorporates the NSClient mode of address since that's what the official plugins support. So it's really three different agents. -- Andreas Ericsson [EMAIL PROTECTED] OP5 AB www.op5.se Tel: +46 8-230225 Fax: +46 8-230231 - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ ___ Nagios-users mailing list Nagios-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nagios-users ::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. ::: Messages without supporting info will risk being sent to /dev/null
Re: [Nagios-users] nsclient, is it still an acceptable method to monitor nt
> > Steve Ensley wrote: > > I'm upgrading another departments Nagios 1.3 instance to Nagios 2.9. > they > > are using nsclient to get some info from some nt servers. Most of my > Nagios > > experience has been monitoring Unix servers. > > > > The website at http://nsclient.ready2run.nl/ for nsclient doesnt seem to > > have been touched since 2004. Is it still a viable method to monitor nt > > servers or is there somthing else I should be looking into to replace > it. > > > > Try NSClient++ instead. It's at sourceforge somewhere, and is quite a lot > fresher. NSClient might work, but it's getting rather ancient. > I had this same quandary sometime back. Options were NSClient (seems too old, not being developed) NSClient++ (presumably enhanced in some way) OpServices version of NSClient (still being developed) NC_Net (still being developed) In the end I simply went with NC_Net and it appears to work for us just fine, and I often see the author on this list, which tells me that he's still involved with Nagios in some way. It would be nice if all the different people who independently developed all the different versions 'unforked' their efforts though :-), it would make the decision on which one to use much easier, by having a lack of choice!! - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ ___ Nagios-users mailing list Nagios-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nagios-users ::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. ::: Messages without supporting info will risk being sent to /dev/null
Re: [Nagios-users] nsclient, is it still an acceptable method to monitor nt
Steve Ensley wrote: > I'm upgrading another departments Nagios 1.3 instance to Nagios 2.9. they > are using nsclient to get some info from some nt servers. Most of my Nagios > experience has been monitoring Unix servers. > > The website at http://nsclient.ready2run.nl/ for nsclient doesnt seem to > have been touched since 2004. Is it still a viable method to monitor nt > servers or is there somthing else I should be looking into to replace it. > Try NSClient++ instead. It's at sourceforge somewhere, and is quite a lot fresher. NSClient might work, but it's getting rather ancient. -- Andreas Ericsson [EMAIL PROTECTED] OP5 AB www.op5.se Tel: +46 8-230225 Fax: +46 8-230231 - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ ___ Nagios-users mailing list Nagios-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nagios-users ::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. ::: Messages without supporting info will risk being sent to /dev/null