Issue

• Build agents report Clock Difference not being in sync
• If the clock is not correctly synchronized, you could experience network and authentication issues
• Build logs report incorrect timestamps

Environment

• CloudBees CI (CloudBees Core)
• CloudBees CI (CloudBees Core) on traditional platforms - Client controller
• CloudBees CI (CloudBees Core) on traditional platforms - Operations Center
• CloudBees Jenkins Platform - Client controller
• CloudBees Jenkins Platform - Operations Center
• CloudBees Jenkins Distribution
• Jenkins LTS

Description

When accessing Manage Jenkins > Manage Node page, or JENKINS_URL/computer it may happen that some nodes are not In sync in the Clock Difference column

Resolution

In order to fix the time drift issue, we recommend to enable clock synchronization for all Jenkins hosts on your network.

Linux

Install and enable NTP service.

RHEL/CentOS

sudo yum install ntp

Debian/Ubuntu

sudo apt-get install ntp

Start the service, and enable NTP to start at boot

sudo systemctl start ntpd
sudo systemctl enable ntpd

Windows

Left-click on the time in the bottom-right of the screen, then follow Change date and time settings…

You can synchronize the clock from the command line, navigate to an elevated command prompt, then enter

net time \\time.windows.com /set /y

References:

• Accurate Time for Windows Server 2016
• How the Windows Time Service Works

Validate

Once you adjust the time on the remote host, validate Clock Difference for the questioned node