do you enable retention? On Tue, Jul 26, 2011 at 8:33 PM, Jindrich Nemec <jindrich.ne...@fsit.cz> wrote: > I've found a similar thread, linked below. It seems the problem it is still > unsolved. > > ----- > > http://www.mail-archive.com/nagios-users@lists.sourceforge.net/msg24816.html > > > For example a check that runs today will have a next scheduled check date of > 05/03/2010 instead of 05/03/2009. There is no real connection between the > checks, it's like a random problem. Some checks have it, others don't. a > manual > reschedule of the check does solve the problem but sometimes only temporary. > > > http://article.gmane.org/gmane.network.nagios.devel/5554/match=next+year > > ------------------------------------------------------------------------------ > Magic Quadrant for Content-Aware Data Loss Prevention > Research study explores the data loss prevention market. Includes in-depth > analysis on the changes within the DLP market, and the criteria used to > evaluate the strengths and weaknesses of these DLP solutions. > http://www.accelacomm.com/jaw/sfnl/114/51385063/ > _______________________________________________ > 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 >
------------------------------------------------------------------------------ Magic Quadrant for Content-Aware Data Loss Prevention Research study explores the data loss prevention market. Includes in-depth analysis on the changes within the DLP market, and the criteria used to evaluate the strengths and weaknesses of these DLP solutions. http://www.accelacomm.com/jaw/sfnl/114/51385063/ _______________________________________________ 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
