VMware Cloud Community
whitetimc
Contributor
Contributor

Leap year bug question

We are in the process of gathering all of the VMware hosts that are impacted by the leap second bug. According to this VMware article (2147498), we must place each impacted host in  Slew mode. This has to be done by switching the ntp daemon to slew mode 24 hours prior to the leap second, continue in slew mode for 48 hours afterwards and then revert to normal operation.

Instead of going through the pain of doing this on all of our impacted servers, can we stop the ntp service prior to midnight, then restart the service a little after midnight? This is the method being done on the Linux servers in our environment and I was hoping that this was an acceptable method of resolution for the VMware hosts as well.

Any thoughts?

Thanks

0 Kudos
2 Replies
a_p_
Leadership
Leadership

I guess you missed

Note: ESXi/ESX are unaffected by the leap second change. For more information, see VMware ESXi and Leap Seconds (2121190)

in the KB article you mentioned!?


André.

0 Kudos
whitetimc
Contributor
Contributor

I should have mentioned that the host that I am referring to are 3.0.1 servers. I believe that these are still affected.

0 Kudos