K10095: Error Message: Clock advanced by ticks

K10095: Error Message: Clock advanced by ticks

https://my.f5.com/manage/s/article/K10095

Published Date: Sep 21, 2018Updated Date: Oct 13, 2025 Download Article Show social share buttons AI Recommended Content

Toggle showing the products this articleApplies to: BIG-IP AAM 15.1.10, 15.1.9, 15.1.8, 15.1.7, 15.1.6, 15.1.5, 15.1.4, 15.1.3, 15.1.2, 15.1.1, 15.1.0, 15.1.X, 15.0.1, 15.0.0, 15.0.X, 15.X.X, 14.1.5, 14.1.4, 14.1.3, 14.1.2, 14.1.0, 14.1.X, 14.0.1, 14.0.0, 14.0.X, 14.X.X, 13.1.5, 13.1.4, 13.1.3, 13.1.1, 13.1.0, 13.1.X, 13.0.1, 13.0.0, 13.0.X, 13.X.X, 12.1.6, 12.1.5, 12.1.4, 12.1.3, 12.1.2, 12.1.1, 12.1.0, 12.1.X, 12.0.0, 12.0.X, 12.X.X BIG-IP AFM 17.5.1, 17.5.0, 17.5.X, 17.1.3, 17.1.2, 17.1.1, 17.1.0, 17.1.X, 17.0.0, 17.0.X, 17.X.X, 16.1.6, 16.1.5, 16.1.4, 16.1.3, 16.1.2, 16.1.1, 16.1.0, 16.1.X, 16.0.1, 16.0.0, 16.0.X, 16.X.X, 15.1.10, 15.1.9, 15.1.8, 15.1.7, 15.1.6, 15.1.5, 15.1.4, 15.1.3, 15.1.2, 15.1.1, 15.1.0, 15.1.X, 15.0.1, 15.0.0, 15.0.X, 15.X.X, 14.1.5, 14.1.4, 14.1.3, 14.1.2, 14.1.0, 14.1.X, 14.0.1, 14.0.0, 14.0.X, 14.X.X, 13.1.5, 13.1.4, 13.1.3, 13.1.1, 13.1.0, 13.1.X, 13.0.1, 13.0.0, 13.0.X, 13.X.X, 12.1.6, 12.1.5, 12.1.4, 12.1.3, 12.1.2, 12.1.1, 12.1.0, 12.1.X, 12.0.0, 12.0.X, 12.X.X, 11.6.5, 11.6.4, 11.6.3, 11.6.2, 11.6.1, 11.6.0, 11.6.X, 11.5.10, 11.5.9, 11.5.8, 11.5.7, 11.5.6, 11.5.5, 11.5.4, 11.5.3, 11.5.2, 11.5.1, 11.5.0, 11.5.X, 11.4.1, 11.4.0, 11.4.X, 11.3.0, 11.3.X, 11.X.X BIG-IP APM 17.5.1, 17.5.0, 17.5.X, 17.1.3, 17.1.2, 17.1.1, 17.1.0, 17.1.X, 17.0.0, 17.0.X, 17.X.X, 16.1.6, 16.1.5, 16.1.4, 16.1.3, 16.1.2, 16.1.1, 16.1.0, 16.1.X, 16.0.1, 16.0.0, 16.0.X, 16.X.X, 15.1.10, 15.1.9, 15.1.8, 15.1.7, 15.1.6, 15.1.5, 15.1.4, 15.1.3, 15.1.2, 15.1.1, 15.1.0, 15.1.X, 15.0.1, 15.0.0, 15.0.X, 15.X.X, 14.1.5, 14.1.4, 14.1.3, 14.1.2, 14.1.0, 14.1.X, 14.0.1, 14.0.0, 14.0.X, 14.X.X, 13.1.5, 13.1.4, 13.1.3, 13.1.1, 13.1.0, 13.1.X, 13.0.1, 13.0.0, 13.0.X, 13.X.X, 12.1.6, 12.1.5, 12.1.4, 12.1.3, 12.1.2, 12.1.1, 12.1.0, 12.1.X, 12.0.0, 12.0.X, 12.X.X, 11.6.5, 11.6.4, 11.6.3, 11.6.2, 11.6.1, 11.6.0, 11.6.X, 11.5.10, 11.5.9, 11.5.8, 11.5.7, 11.5.6, 11.5.5, 11.5.4, 11.5.3, 11.5.2, 11.5.1, 11.5.0, 11.5.X, 11.4.1, 11.4.0, 11.4.X, 11.3.0, 11.3.X, 11.2.1, 11.2.0, 11.2.X, 11.1.0, 11.1.X, 11.0.0, 11.0.X, 11.X.X, 10.2.4, 10.2.3, 10.2.2, 10.2.1, 10.2.0, 10.2.X, 10.1.0, 10.1.X, 10.X.X BIG-IP ASM 17.5.1, 17.5.0, 17.5.X, 17.1.3, 17.1.2, 17.1.1, 17.1.0, 17.1.X, 17.0.0, 17.0.X, 17.X.X, 16.1.6, 16.1.5, 16.1.4, 16.1.3, 16.1.2, 16.1.1, 16.1.0, 16.1.X, 16.0.1, 16.0.0, 16.0.X, 16.X.X, 15.1.10, 15.1.9, 15.1.8, 15.1.7, 15.1.6, 15.1.5, 15.1.4, 15.1.3, 15.1.2, 15.1.1, 15.1.0, 15.1.X, 15.0.1, 15.0.0, 15.0.X, 15.X.X, 14.1.5, 14.1.4, 14.1.3, 14.1.2, 14.1.0, 14.1.X, 14.0.1, 14.0.0, 14.0.X, 14.X.X, 13.1.5, 13.1.4, 13.1.3, 13.1.1, 13.1.0, 13.1.X, 13.0.1, 13.0.0, 13.0.X, 13.X.X, 12.1.6, 12.1.5, 12.1.4, 12.1.3, 12.1.2, 12.1.1, 12.1.0, 12.1.X, 12.0.0, 12.0.X, 12.X.X, 11.6.5, 11.6.4, 11.6.3, 11.6.2, 11.6.1, 11.6.0, 11.6.X, 11.5.10, 11.5.9, 11.5.8, 11.5.7, 11.5.6, 11.5.5, 11.5.4, 11.5.3, 11.5.2, 11.5.1, 11.5.0, 11.5.X, 11.4.1, 11.4.0, 11.4.X, 11.3.0, 11.3.X, 11.2.1, 11.2.0, 11.2.X, 11.1.0, 11.1.X, 11.0.0, 11.0.X, 11.X.X, 10.2.4, 10.2.3, 10.2.2, 10.2.1, 10.2.0, 10.2.X, 10.1.0, 10.1.X, 10.0.1, 10.0.0, 10.0.X, 10.X.X BIG-IP GTM 11.6.5, 11.6.4, 11.6.3, 11.6.2, 11.6.1, 11.6.0, 11.6.X, 11.5.10, 11.5.9, 11.5.8, 11.5.7, 11.5.6, 11.5.5, 11.5.4, 11.5.3, 11.5.2, 11.5.1, 11.5.0, 11.5.X, 11.4.1, 11.4.0, 11.4.X, 11.3.0, 11.3.X, 11.2.1, 11.2.0, 11.2.X, 11.1.0, 11.1.X, 11.0.0, 11.0.X, 11.X.X, 10.2.4, 10.2.3, 10.2.2, 10.2.1, 10.2.0, 10.2.X, 10.1.0, 10.1.X, 10.0.1, 10.0.0, 10.0.X, 10.X.X BIG-IP Link Controller 17.5.1, 17.5.0, 17.5.X, 17.1.3, 17.1.2, 17.1.1, 17.1.0, 17.1.X, 17.0.0, 17.0.X, 17.X.X, 16.1.6, 16.1.5, 16.1.4, 16.1.3, 16.1.2, 16.1.1, 16.1.0, 16.1.X, 16.0.1, 16.0.0, 16.0.X, 16.X.X, 15.1.10, 15.1.9, 15.1.8, 15.1.7, 15.1.6, 15.1.5, 15.1.4, 15.1.3, 15.1.2, 15.1.1, 15.1.0, 15.1.X, 15.0.1, 15.0.0, 15.0.X, 15.X.X, 14.1.5, 14.1.4, 14.1.3, 14.1.2, 14.1.0, 14.1.X, 14.0.1, 14.0.0, 14.0.X, 14.X.X, 13.1.5, 13.1.4, 13.1.3, 13.1.1, 13.1.0, 13.1.X, 13.0.1, 13.0.0, 13.0.X, 13.X.X, 12.1.6, 12.1.5, 12.1.4, 12.1.3, 12.1.2, 12.1.1, 12.1.0, 12.1.X, 12.0.0, 12.0.X, 12.X.X, 11.6.5, 11.6.4, 11.6.3, 11.6.2, 11.6.1, 11.6.0, 11.6.X, 11.5.10, 11.5.9, 11.5.8, 11.5.7, 11.5.6, 11.5.5, 11.5.4, 11.5.3, 11.5.2, 11.5.1, 11.5.0, 11.5.X, 11.4.1, 11.4.0, 11.4.X, 11.3.0, 11.3.X, 11.2.1, 11.2.0, 11.2.X, 11.1.0, 11.1.X, 11.0.0, 11.0.X, 11.X.X, 10.2.4, 10.2.3, 10.2.2, 10.2.1, 10.2.0, 10.2.X, 10.1.0, 10.1.X, 10.0.1, 10.0.0, 10.0.X, 10.X.X BIG-IP LTM 17.5.1, 17.5.0, 17.5.X, 17.1.3, 17.1.2, 17.1.1, 17.1.0, 17.1.X, 17.0.0, 17.0.X, 17.X.X, 16.1.6, 16.1.5, 16.1.4, 16.1.3, 16.1.2, 16.1.1, 16.1.0, 16.1.X, 16.0.1, 16.0.0, 16.0.X, 16.X.X, 15.1.10, 15.1.9, 15.1.8, 15.1.7, 15.1.6, 15.1.5, 15.1.4, 15.1.3, 15.1.2, 15.1.1, 15.1.0, 15.1.X, 15.0.1, 15.0.0, 15.0.X, 15.X.X, 14.1.5, 14.1.4, 14.1.3, 14.1.2, 14.1.0, 14.1.X, 14.0.1, 14.0.0, 14.0.X, 14.X.X, 13.1.5, 13.1.4, 13.1.3, 13.1.1, 13.1.0, 13.1.X, 13.0.1, 13.0.0, 13.0.X, 13.X.X, 12.1.6, 12.1.5, 12.1.4, 12.1.3, 12.1.2, 12.1.1, 12.1.0, 12.1.X, 12.0.0, 12.0.X, 12.X.X, 11.6.5, 11.6.4, 11.6.3, 11.6.2, 11.6.1, 11.6.0, 11.6.X, 11.5.10, 11.5.9, 11.5.8, 11.5.7, 11.5.6, 11.5.5, 11.5.4, 11.5.3, 11.5.2, 11.5.1, 11.5.0, 11.5.X, 11.4.1, 11.4.0, 11.4.X, 11.3.0, 11.3.X, 11.2.1, 11.2.0, 11.2.X, 11.1.0, 11.1.X, 11.0.0, 11.0.X, 11.X.X, 10.2.4, 10.2.3, 10.2.2, 10.2.1, 10.2.0, 10.2.X, 10.1.0, 10.1.X, 10.0.1, 10.0.0, 10.0.X, 10.X.X BIG-IP PEM 17.5.1, 17.5.0, 17.5.X, 17.1.3, 17.1.2, 17.1.1, 17.1.0, 17.1.X, 17.0.0, 17.0.X, 17.X.X, 16.1.6, 16.1.5, 16.1.4, 16.1.3, 16.1.2, 16.1.1, 16.1.0, 16.1.X, 16.0.1, 16.0.0, 16.0.X, 16.X.X, 15.1.10, 15.1.9, 15.1.8, 15.1.7, 15.1.6, 15.1.5, 15.1.4, 15.1.3, 15.1.2, 15.1.1, 15.1.0, 15.1.X, 15.0.1, 15.0.0, 15.0.X, 15.X.X, 14.1.5, 14.1.4, 14.1.3, 14.1.2, 14.1.0, 14.1.X, 14.0.1, 14.0.0, 14.0.X, 14.X.X, 13.1.5, 13.1.4, 13.1.3, 13.1.1, 13.1.0, 13.1.X, 13.0.1, 13.0.0, 13.0.X, 13.X.X, 12.1.6, 12.1.5, 12.1.4, 12.1.3, 12.1.2, 12.1.1, 12.1.0, 12.1.X, 12.0.0, 12.0.X, 12.X.X, 11.6.5, 11.6.4, 11.6.3, 11.6.2, 11.6.1, 11.6.0, 11.6.X, 11.5.10, 11.5.9, 11.5.8, 11.5.7, 11.5.6, 11.5.5, 11.5.4, 11.5.3, 11.5.2, 11.5.1, 11.5.0, 11.5.X, 11.4.1, 11.4.0, 11.4.X, 11.3.0, 11.3.X, 11.X.X Issue Error Message

01010029:5: Clock advanced by ticks

In this error message, note the following:

is the number of milliseconds the Traffic Management Microkernel (TMM) clock is behind by. For example: 01010029:5: Clock advanced by 518 ticks 01010029:5: Clock advanced by 505 ticks 01010029:5: Clock advanced by 590 ticks The BIG-IP system daemon heartbeat is a recurring signal generated by a service. The BIG-IP system continually monitors daemon heartbeat signals for certain daemons, such as TMM, to determine whether the service is running. The BIG-IP system logs this type of message when TMM fails to complete its polling loop and update its heartbeat signal within the threshold period. Message Location You may encounter this message in the following location: The /var/log/ltm file Description Each TMM thread has its own timekeeping mechanism that is regularly checked against the system clock and updated. If the TMM thread notices that it is behind the system clock by more than a set threshold, the system displays this error message. These threshold periods are 100 milliseconds (ticks) for BIG-IP hardware platforms and 300 milliseconds (ticks) for BIG-IP Virtual Edition (VE) running on a hypervisor. This message occurs when one of the following conditions is met: TMM is very busy TMM is stalled TMM is very busy Examples of this may include: Protracted iRules processing due to unexpected data input. Modifying large complex configurations, such as those containing numerous SSL profiles with SSL certificates or keys. Certain administrative operations, such as displaying large numbers of connections, persistence entries, or large ARP tables through the command line. Loading large databases into TMM, such as IpRep or GeoIP. A configuration that results in large volumes of traffic processed by a single TMM instance. TMM is stalled Examples of this may include: Memory paging, I/O operations, or other events that cause TMM to lose CPU time. A hypervisor not resourcing a BIG-IP VE guest adequately, leading to vCPU stalls. This can often happen when an administrator takes a hypervisor-level snapshot of a running BIG-IP VE guest. The snapshot process freezes the BIG-IP VE system at points, including TMM, so no traffic passes through at that time. When TMM starts running again, the system sees that it has essentially jumped to some point in the future, so the clock advances. For more information, refer to K00421514: Periodic failover while taking BIG-IP VE snapshots from hypervisor. For example, in the following BIG-IP system entries, TMM failed to update its heartbeat signal for over 10 seconds. This event caused the HA daemon to terminate, produce a core file, and cause a failover. 01010029:5: Clock advanced by 518 ticks 01010029:5: Clock advanced by 505 ticks 01010029:5: Clock advanced by 590 ticks 01010029:5: Clock advanced by 568 ticks 01010029:5: Clock advanced by 1681 ticks 01010029:5: Clock advanced by 6584 ticks 01140029:4: HA daemon_heartbeat tmm fails action is go offline down links and restart. Note: The expected message showing a clock advanced of over 10000 ticks (10 seconds) may not be displayed because the HA daemon will have performed the action before logging has occurred. Other considerations When troubleshooting clock advances, if the split planes (HTSplit) feature is enabled, clock advances are usually a symptom of a TMM issue, as TMM cannot be stalled by processes running on control plane cores. On Virtual Clustered Multiprocessing (vCMP) guests, hypervisor issues such as severe memory leaks may be able to stall a vCPU running a TMM thread on the guest. For more information about this feature, refer to K23505424: Overview of the HTSplit feature. When large clock advances occur on one of the members of a high availability (HA) pair that uses network failover, that traffic is also disrupted on HA connections that pass through this TMM. If there is no alternate connection path via management IP addresses and TMM is unresponsive due to clock advance for an amount of time greater than the network failover timeout (typically defaults to 3 seconds), but less than the TMM heartbeat timeout (10 seconds), both systems become active, and stay active, until the system restores network failover traffic or the TMM heartbeat expires. Important: As a best practice, for robust HA configurations, include failover communication paths between both TMM self IP addresses and between management IP addresses. BIG-IP VE BIG-IP VE systems running on a hypervisor may log clock advanced messages on idle BIG-IP VE instances due to the way some hypervisors resource idle BIG-IP VE guests. To reduce the amount of messages logged on a specific BIG-IP VE system, configure the hypervisor to grant additional resources to the BIG-IP VE system; for example, increasing instance priority or shares and lock guest memory in RAM. For more information about this feature, refer to K22658205: Unexpected failover or other instability in BIG-IP VE due to CPU starvation by hypervisor. Impact This message may appear intermittently depending on system load, and it does not necessarily indicate system instability or a cause for concern unless accompanied with another error message or at the time of a serious event. If this message appears regularly, you can use it to help diagnose underlying performance or configuration issues. Recommended Actions If this message appears in or around critical events in the log file, you can use the message as a diagnostic clue to determine the cause using other diagnostic messages before and after the events. Typically, you must investigate possible resource-related issues on the device and work to resolve them. The following articles may help resolve known causes of Clock advanced messages. Article Title K15950 TMM may log 'Clock advanced by' messages and possibly restart when loading many FIPS keys on BIG-IP 11050 platforms K09247330 Clock advanced messages may be triggered when a large amount of data is maintained in DNS Express zones K34554754 A ConfigSync operation with a large number of Client SSL profiles may increase TMM CPU usage K14330 vCMP hosts with high disk I/O may experience instability K14701 The BIG-IP system may not count HTTP persistent requests toward the Maximum Requests setting K20100613 An enabled sFlow receiver causes poor TMM performance on certain BIG-IP platforms K15431 Manually starting the BIG-IP APM websso service may trigger 100 percent CPU utilisation K24036315 Hardware crypto queues may erroneously become unavailable under heavy load K17554 Hardware SSL acceleration may cause the BIG-IP system to become unresponsive K00421514 Periodic failover while taking BIG-IP VE snapshots from hypervisor Related Content K9231: Overview of BIG-IP daemon heartbeat failsafe K9233: Overview of daemon heartbeat failover for VIPRION systems K95002127: Troubleshooting BIG-IP failover events K16739: Understanding 'top' output on the BIG-IP system K16419: Overview of BIG-IP memory usage AI Recommended Content Security Advisory - K000159546: Python vulnerability CVE-2024-5642 Knowledge - K000135931: Contact F5 Support Security Advisory - K000157317: BIND vulnerability CVE-2025-8677 Security Advisory - K000157334: BIND vulnerability CVE-2025-40778 F5 support engineers who work directly with customers write Support Solution and Knowledge articles, which give you immediate access to mitigation, workaround, or troubleshooting suggestions.