Original Publication Date: 01/07/2013
Updated Date: 06/18/2013
When you have changed the BIG-IP system timezone, the cron daemon may not update the effective change of date and time to the existing cron jobs.
This issue occurs when all of the following conditions are met:
A scheduled cron job will run at the date and time that is based on the previous timezone, and not based on the updated timezone.
As a result of this issue, you may encounter the following symptoms:
The BIG-IP system has a log rotation cron job configured, by default, to start daily at 4:02 a.m. However, when you change the system timezone, the log may be rotated at a different time.
F5 Product Development has assigned ID 384208 to this issue, and has confirmed that this issue exists in the products listed in the Applies To box. For information about releases or hotfixes that resolve this issue, refer to the following table:
|Type of Fix
To work around this issue, you can restart the cron daemon after changing the timezone of the BIG-IP system. To do so, perform the following procedure:
Impact of workaround: None.
bigstart restart crond