AskF5 Knowledge Base
- Home
- SOL14113
Applies To:
Show Versions
sol14113: Cron job date/time may not be updated when system timezone is changed
Known Issue
Original Publication Date: 01/07/2013
Updated Date: 06/18/2013
Description
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:
- There were cron jobs configured in the BIG-IP system.
- The BIG-IP system timezone was changed, with at least a difference of one hour.
Impact
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.
Symptoms
As a result of this issue, you may encounter the following symptoms:
- The cron jobs that you expected to run at the date or time that is based on the newly-updated timezone did not occur.
For example:
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.
Status
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 |
Versions Fixed |
Related Articles |
| Release | None | None |
| Hotfix | None | None |
Workaround
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.
- Log in to the BIG-IP command line.
- Restart the cron daemon using the following command:
bigstart restart crond
Supplemental Information
