Nagios 2.0b3 still buggy?

[Marc Powell]

> -----Original Message-----
> From: nagios-users-admin at lists.sourceforge.net [mailto:nagios-users-
> admin at lists.sourceforge.net] On Behalf Of Ralph.Grothe at itdz-berlin.de
> Sent: Thursday, July 28, 2005 4:12 AM
> To: nagios-users at 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 * http://www.sqe.com/bsce5sf
_______________________________________________
Nagios-users mailing list
Nagios-users at 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