Skip to main content
All CollectionsDecember 31, 2023Data CollectionTroubleshooting data collection
Troubleshooting "Clock skew is detected between the OneIQ Pulse clock and remote clock" error.
Troubleshooting "Clock skew is detected between the OneIQ Pulse clock and remote clock" error.

Learn how to troubleshoot local time being out of sync between OneIQ Pulse and VMware® endpoints.

Alpha Team avatar
Written by Alpha Team
Updated over 4 months ago

Prerequisites

You must have access to VMware vCenter.

You must have access to Windows Server where OneIQ Pulse is installed.

Overview

OneIQ Pulse will collect data only if the local time on the machine hosting it is synchronized with the time on discovered VMware endpoints. Otherwise, a "Clock skew is detected" error will be displayed during endpoint discovery:

Even if NTP is used, VMware ESXi™ hosts may not synchronize with the NTP server without appropriate patches/updates.

Troubleshooting

Use the VMware vSphere Client to determine the current time on VMware vCenter/ESXi Servers under the System Information section. To edit the Time Configuration of an ESXi Host in the VMware Host Client, see this VMware article.

Example

  1. VMware vCenter/ESXi Server time is 6:30 UTC.

  2. The OneIQ Pulse machine's local time is also 6:30, but the time zone is set to UTC+1.

In this situation, OneIQ Pulse would not be able to collect data from VMware vCenter/ESXi Server due to a time difference of one hour.

Resolution

Adjust the time on the OneIQ Pulse machine to match the time on the VMware vCenter/ESXi Server.

Did this answer your question?