Scott, I have the same issue here. The MySQL tuning has helped the situation, but hasn¹t completely eliminated it. After I get up to 3.3.x I am going to look at it more to see what else I can optimize.
Mike Mike Dorman Lead Systems Engineer Latisys-Denver, LLC (303) 268-1504 direct [email protected] www.latisys.com From: Ton Voon <[email protected]> Reply-To: Opsview Users <[email protected]> Date: Tue, 3 Nov 2009 13:42:00 +0000 To: Opsview Users <[email protected]> Subject: Re: [opsview-users] (no subject) On 3 Nov 2009, at 13:33, Scott Simecek wrote: > For the past few nights around 3:30AM I get an alert like this one. > > NDO CRITICAL - oldest ndo file is 92 seconds old, 19 ndo files backlogged > > In five or ten minutes I get a recovery message and all is well until the next > night. Any idea why this just started happening and how I can fix it? I > recently increased the number of hosts we have but it is still small (122) and > the number of checks is also low (865). I just upgraded last night to 3.3.2 on > my master server. The housekeeping is kicked off in the early hours, so it is probably database cleanup activity that is causing slow responses. See the mysql tuning documentation and see if that helps: http://docs.opsview.org/doku.php?id=opsview3.3:mysql#mysql_tuning Ton _______________________________________________ Opsview-users mailing list [email protected] http://lists.opsview.org/lists/listinfo/opsview-users
<<image.png>>
_______________________________________________ Opsview-users mailing list [email protected] http://lists.opsview.org/lists/listinfo/opsview-users
