Bug ID 1039041: Log Message: Clock advanced by <number> ticks

Last Modified: Dec 07, 2023

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

Fixed In:
17.0.0, 16.1.2

Opened: Aug 06, 2021

Severity: 1-Blocking


<ticks> is the number of milliseconds the Traffic Management Microkernel (TMM) clock is out of sync (behind) the system clock because the TMM thread is waiting for a response. Logs are similar to below. bigip1 notice tmm15[46856]: 01010029:5: Clock advanced by 103 ticks bigip1 notice tmm7[46855]: 01010029:5: Clock advanced by 106 ticks bigip1 notice tmm10[46855]: 01010029:5: Clock advanced by 107 ticks bigip1 notice tmm25[46856]: 01010029:5: Clock advanced by 113 ticks bigip1 notice tmm15[46856]: 01010029:5: Clock advanced by 121 ticks bigip1 notice tmm5[46855]: 01010029:5: Clock advanced by 106 ticks


This message may appear intermittently depending on system load and conditions mentioned above, and it does not necessarily indicate system instability or a cause for concern unless accompanied by another error message or at the time of a serious event. In all the above conditions, clock advance ticks are in the range of 100 - 170.


These logs are seen more frequently in i15820-DF platforms with FIPS enabled, in comparison to other FIPS platforms. The messages are observed during FIPS key lookup in the HSM. These lookups occur either during TMM start/restart or during SSL profile configuration modification.



Fix Information


Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips