On 04/15/2010 05:24 PM, Jeremy wrote: > > I know I really should get around to upgrading to Nagios 3.x but no time for > that yet and it's going to be a pain to upgrade them all at once without > being blind for a little bit, so pretend Nagios 3.x isn't an option just > yet. >
The truth of the matter though is that noone really cares about fixing a problem in 2.12 unless it's also a problem in 3.2.1, and especially if it's a bug as hard to debug as this one. Insofar as I know, configuration files are compatible between those two revisions, so you could just use 3.2.1 as a drop-in replacement for 2.12. Some minor things have to be changed in nagios.cfg (and possibly cgi.cfg), but the bulk of the configuration should be ok the way it is. Since this is an otherwise intermittent error which may well depend on other variables (such as pthread library version, glibc library version or any other system library), it's well nigh impossible to debug without having you run Nagios through valgrind until it crashes due to lack of memory. Rest assured that that will keep your Nagios running crippled longer than an upgrade would If the problem persists with Nagios 3.2.1, you should look into upgrading the rest of your system. If that doesn't help either, it's time to report it as a bug. -- Andreas Ericsson [email protected] OP5 AB www.op5.se Tel: +46 8-230225 Fax: +46 8-230231 Considering the successes of the wars on alcohol, poverty, drugs and terror, I think we should give some serious thought to declaring war on peace. ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Nagios-users mailing list [email protected] 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
