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

0000964: cron does not start any job after huge time changes - MantisBT
MantisBT - Endian Firewall
View Issue Details
0000964Endian FirewallOther Servicespublic2008-06-16 20:542008-09-10 15:44
0000964: cron does not start any job after huge time changes
fcron stores for each job the timestamp when the respective job is expected to run in its persistent crontab.

whenever the system clock will be changed backwards, fcron will not start any job until the saved timestamp is reached. this may take a very long time when fcron first started with a wrong date far in the future and ntpd set it back afterwards.
No tags attached.
Issue History
2008-06-16 20:54peter-endianNew Issue
2008-06-16 20:55peter-endianNote Added: 0001319
2008-06-17 10:35peter-endianStatusnew => resolved
2008-06-17 10:35peter-endianFixed in Version => 2.2-rc2
2008-06-17 10:35peter-endianResolutionopen => fixed
2008-06-17 10:35peter-endianAssigned To => peter-endian
2008-07-27 20:18peter-endianStatusresolved => closed
2008-09-10 15:44chris-endianTarget Version2.2 => 2.2-rc3

2008-06-16 20:55   
possible solution:
remove /var/spool/cron/root before the crontab will be installed during startup