<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1"> <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> <HTML> <HEAD> <META NAME="Generator" CONTENT="MS Exchange Server version 6.5.6944.0"> <TITLE>RE: [Nagios-users] Nagios 2.0b3 still buggy?</TITLE> </HEAD> <BODY> <DIV id=idOWAReplyText10164 dir=ltr> <DIV dir=ltr>I have to agree that Nagios 2.0b3 is reasonably stable.</DIV> <DIV dir=ltr>I am currently monitoring 5 different customers sites with a nagios 2.0b3 box at each site and a central nagios 2.0b3 box. I have over 70 remote hosts being monitored and over 250 services without problem... I am using NRPE_NT on each windows server, which is working great on servers ranging from NT 4 to Server 2003, NSCA to pass back passive checks to the central box, service escalations and dependencies on the central box as well... I know that there are people that are watching alot more than me and are running fine.. while I have experienced some hardships getting everything configured I do not believe that nagios 2.0b3 is a buggy program... at least any more than most programs are... </DIV></DIV> <DIV dir=ltr> <HR tabIndex=-1> From: nagios-users-admin@lists.sourceforge.net on behalf of Dave Augustus Sent: Thu 7/28/2005 11:51 AM To: nagios-users@lists.sourceforge.net Subject: RE: [Nagios-users] Nagios 2.0b3 still buggy? </DIV> <DIV> This is a test subject just chiming in here that we are using v2.03b3 and it is working great. We are monitoring about 10 servers/141 services using both network connections and nrpe. All on linux. Also, the NagiosQL is a great app for setting up and configuring. It covers most of the functionality and has helped tremendously in deploying Nagios. As a n00b to nagios, I would say we are NOT using the advanced features of Service Groups, escalations and such. However, our Windows admins are happy to get a glimpse of what Nagios can do. They are sold on it and we will deploying a larger Nagios install for monitoring our Windows and VmWare servers. *test subject* Dave Augustus Kenneth Copeland Ministries On Thu, 2005-07-28 at 10:00 -0500, Marc Powell wrote: > > > -----Original Message----- > > From: nagios-users-admin@lists.sourceforge.net [<A href="mailto:nagios-users-">mailto:nagios-users-</A> > > admin@lists.sourceforge.net] On Behalf Of Ralph.Grothe@itdz-berlin.de > > Sent: Thursday, July 28, 2005 4:12 AM > > To: nagios-users@lists.sourceforge.net > > Subject: [Nagios-users] Nagios 2.0b3 still buggy? > > > > Hello, > > > > recently I noticed a minor "flame" between Nagios > > hackers/patchers going on here > > where one party raised concerns that release 2.X not being fit > > for production usage yet? > > It's still beta. Ethan has indicated on numerous occasions that if you > run 2.0, expect problems. Quoting an e-mail from Ethan on 3/23/2005 -- > > "First, I would still consider 2.0 as being beta software - that's why > its labeled as such. While no major changes will be made to either > the configuration files or functionality before a "stable" 2.0 is > released, I do expect that a few major nasty bugs will be discovered > within the current code. If you're running the 2.0 code while its in > beta, consider yourself a test subject. :-)" > > As of that e-mail it was expected that it might be out of beta by the > end of June. Obviously we're past that but there hasn't been an official > release yet so we're still in beta mode. Many people have successfully > been running 2.x in production environments for some time. Others have > experienced problems. YMMV. > > > As I'm experiencing quite some bizarre behaviour of my Nagios > > setup, > > that I rather blamed on my lack of Nagios configuration skills, > > I now wonder if it couldn't also be at least partly based on the > > release 2.0b3 I am using. > > > > Could it be this one is still a bit "immature" or buggy, and > > would it be advisable to downgrade to a > > "stable" release until I've got my basic stuff working as > > desired? > > That's what _I_ would do but to each his own. Do what you're comfortable > with. If you're monitoring mission critical applications and you > absolutely can't deal with bugs in your monitoring software, use 1.x. > > > For instance, did I alway wonder why my running nagios daemon > > didn't continue processing > > after it caught a SIGHUP. > > It reported to nagios.log that it caught the signal and was > > reinitializing, > > but then no more appeared nor happened. > > That sounds like it might be a bug. Maybe someone else running 2.x can > reproduce it? > > -- > Marc > > > ------------------------------------------------------- > SF.Net email is Sponsored by the Better Software Conference & EXPO September > 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices > Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA > Security * Process Improvement & Measurement * <A href="http://www.sqe.com/bsce5sf">http://www.sqe.com/bsce5sf</A> > _______________________________________________ > Nagios-users mailing list > Nagios-users@lists.sourceforge.net > <A href="https://lists.sourceforge.net/lists/listinfo/nagios-users">https://lists.sourceforge.net/lists/listinfo/nagios-users</A> > ::: 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 the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * <A href="http://www.sqe.com/bsce5sf">http://www.sqe.com/bsce5sf</A> _______________________________________________ Nagios-users mailing list Nagios-users@lists.sourceforge.net <A href="https://lists.sourceforge.net/lists/listinfo/nagios-users">https://lists.sourceforge.net/lists/listinfo/nagios-users</A> ::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. ::: Messages without supporting info will risk being sent to /dev/null </DIV> </BODY> </HTML>