Original Publication Date: 01/07/2013
Updated Date: 03/01/2016
After you change the BIG-IP system time zone, 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 runs at the date and time that is based on the previous time zone, and not based on the updated time zone.
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 time zone, the log may be rotated at a different time.
F5 Product Development has assigned ID 384208 to this issue. F5 has confirmed that this issue exists in the products listed in the Applies To box, located in the upper-right corner of this article. For information about releases or hotfixes that resolve this issue, refer to the following table:
|Type of Fix||Versions Fixed||Related Articles|
To work around this issue, you can restart the cron daemon after you change the time zone of the BIG-IP system. To do so, perform the following procedure:
Impact of workaround: Performing the following procedure should not have a negative impact on your system.
bigstart restart crond