SYSTEM WARNING: 'date_default_timezone_get(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone.' in '/usr/share/mantis/www/core.php' line 264

0004149: monit pool interval - MantisBT Endian Bugtracker
Endian Issue Tracker

Please see now our new Bugtracker system: JIRA

View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0004149Endian FirewallOther Servicespublic2011-09-08 09:572011-09-08 09:57
Assigned To 
PlatformOSOS Version
Product Version2.4.1 
Target VersionFixed in Version 
Summary0004149: monit pool interval
DescriptionI've seen that on new mini monit pool has been increased from 30 to 120 because of the starting up process.

## poll interval of 120 is necessary, because some services take a while to
## start and would be restarted by monit during startup
set daemon 120

Actually IMHO 2 minutes is too much for monit checks on a firewall system some tests are for 5 cycle it means 10 minutes..

There is an interesting feature I've seen on version 5.03 (but it may be supported on earlier versions as well) and is a delay time for the first monit check.
This is really useful to avoid problems and loops in the booting process here is the conf file:

# with start delay 240 # optional: delay the first check by 4-minutes
# # (by default check immediately after monit start)
Attached Files

- Relationships

-  Notes
There are no notes attached to this issue.

- Issue History
Date Modified Username Field Change
2011-09-08 09:57 luca-endian New Issue
2011-09-08 09:57 luca-endian Tag Attached: purple

Copyright © 2005-2008 Endian, SRL. All rights reserved.

Copyright © 2000 - 2012 MantisBT Group
Powered by Mantis Bugtracker