Validate time synchronization in VMware vRealize Log Insight
search cancel

Validate time synchronization in VMware vRealize Log Insight

book

Article ID: 342120

calendar_today

Updated On:

Products

VMware Aria Suite

Issue/Introduction

Time is critical to the core functionality of VMware vRealize Log Insight. You must synchronize the time on the Log Insight virtual appliance with an NTP server or with the ESX/ESXi host on which you deployed the virtual appliance. This article provide steps to manually validate that time is correctly synchronized within the cluster.


Symptoms:
  • A VMware vRealize Log Insight cluster-wide operation fails.
  • The runtime.log file within the Log Insight virtual appliance contains an entry similar to:

    com.vmware.loginsight.api.ApiException: Request failed. 440: Client Error (440)



Environment

VMware vRealize Log Insight 3.3.x
VMware vRealize Log Insight 3.0.x
VMware vRealize Log Insight 2.5.x

Resolution

Validate time configuration using the vRealize Log Insight user interface and validate time is successfully synchronized using a console or SSH connection to each virtual appliance.

Verify Configuration

  1. Log in to the vRealize Log Insight web user interface as a user with the Edit Admin permission.
  2. Click the configuration drop-down menu icon and select Administration.
  3. Under Configuration, click Time.
  4. There are two options available, NTP server (recommended) and ESX/ESXi host.

    • If Log Insight is synchronizing time with an ESX/ESXi host, validate that the time is consistently synchronized on all ESX/ESXi hosts on which the Log Insight cluster virtual machines are running. For more information, see Troubleshooting NTP on ESX and ESXi 4.x / 5.x (1005092).

    • If Log Insight is synchronizing time with an NTP server, verify that the time server is correct and that the time is successfully synchronizing by clicking the Test button. This updates the ntpd configuration and waits for successful synchronization.

Manually Validate Successful NTP Synchronization

If the NTP servers are correct but time synchronization issues are suspected, time synchronization may be verified manually. Perform these steps on each node in the Log Insight cluster.
  1. Open a console or SSH connection to the Log Insight appliance and login as root.
  2. Verify the current date and time in UTC by running this command:

    date -u

    Example output:

    Thu Jul 9 22:31:05 UTC 2015

  3. Query the current status of the configured NTP servers by running this command:

    ntpq -p

    Example output showing two configured NTP servers, one initializing and one synchronized:

    remote refid st t when poll reach delay offset jitter
    ==============================================================================
    1.vmware.pool.n .INIT. 16 u - 64 0 0.000 0.000 0.000
    *2.vmware.pool.n 10.11.12.13 2 u 1 64 1 32.565 0.702 0.968


  4. Review the output from ntpq -p. Each row of output from ntpq corresponds to one of the NTP servers configured in the Log Insight administration user interface.

    • Tally code character in first column: * indicates the source this system is synchronized with the remote and blank indicates that the source has been rejected as not valid.
    • remote: The hostname or IP address of the configured upstream NTP server.
    • refid: Identification of the time stream to which the remote NTP server is synchronized. If you receive a refid of .INIT. Log Insight's ntpd has not received a response from the configured NTP server.
    • reach: An 8-bit shift register in octal (base 8), with each bit representing success (1) or failure (0) in contacting the configured NTP server. A value of 377 is 11111111 (base 2), which indicates that every query was successful during the last 8 poll intervals.
    • delay: Round trip delay (in milliseconds) for communication between the remtote NTP server and the Log Insight node.
    • offset: The offset (in milliseconds) between the time on the remote NTP server and the Log Insight node. A value closer to 0 is ideal.
    • jitter: The observed timing jitter or variation between clock pulses of time with the remote NTP server. A value closer to 0 is ideal.



Additional Information

For more information, see the NTP.org Troubleshooting documentation and the NTP Query Program documentation.

The preceding links were correct as of September 16, 2015. If you find a link is broken, provide feedback and a VMware employee will update the link.

Troubleshooting NTP on ESX and ESXi 4.x / 5.x / 6.x