Bug ID 442535: Time zone changes do not apply to log timestamps without tmm restart

Last Modified: Sep 13, 2023

Affected Product(s):
BIG-IP AFM, LTM(all modules)

Known Affected Versions:
11.5.1 HF1, 11.5.1 HF2, 11.5.1 HF3, 11.5.1 HF4, 11.5.1 HF5, 11.5.1 HF6, 11.5.1 HF7, 11.5.1 HF8, 11.5.1 HF9, 11.5.1 HF10, 11.5.1 HF11, 11.5.2 HF1, 11.5.3 HF1, 11.5.3 HF2, 11.5.4 HF1, 11.5.4 HF2, 11.5.4 HF3, 11.5.4 HF4, 11.4.1, 11.5.0, 11.5.1, 11.6.0, 11.6.1, 11.6.2, 11.6.3,,,,, 11.6.4, 11.6.5,,,, 12.1.0 HF1, 12.1.0 HF2, 12.1.1 HF1, 12.1.1 HF2, 12.1.2 HF1, 12.1.2 HF2

Fixed In:
12.0.0, 11.6.0 HF4, 11.5.2, 11.4.1 HF9

Opened: Jan 09, 2014

Severity: 3-Major

Related Article: K16227


When the timezone of the BIG-IP system changes, logging timestamps are not updated to the new timezone.


/var/log/ltm logs will have the correct time from the other processes that log, but tmm logs will have the incorrect time. The time remains incorrect until tmm or the system is restarted. There are potential issues with processes that depend on correct localtime in tmm.


This occurs when the timezone of the BIG-IP system changes.


In tmsh, run one or both of the following commands: 'restart tmm'. -- bigstart restart tmm.

Fix Information

tmsh modify sys ntp timezone <timezone> will now send a message to TMM so it will reload the timezone.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips