Host time and XOA time are not consistent with each other
-
I installed the pool patches and updated the host, rebooted and this is the error I get in XO now beside each VM. I have checked the time and it seems to be the same in both. What to check next?
-
@olivierlambert Sorry for the noise. The issue turned out to be a DNS issue. The IT guys nightmare is when a client says "I didn't touch it"! Ha! well, I didn't! Yet somehow DNS stopped working during the update and left the host and xoa in a strange state and of course NTP could not update. I fixed the resolve.conf and 99 patches showed up in the pool. I will install those after hours and I hope all will be well after that.
Thank you for the response.
-
That you have NTP correctly configured/enabled everywhere
-
@olivierlambert I have never had to do anything with NTP on my xcp-ng installs in the past. This is a system that has been up for a couple years and now it decides this after an update. I did check NTP on both the host and the XO vm and both "seem" to be working.
-
If the message is displayed, there is a reason. Please do a
timdatectl statuson your XOA -
@olivierlambert Sorry for the noise. The issue turned out to be a DNS issue. The IT guys nightmare is when a client says "I didn't touch it"! Ha! well, I didn't! Yet somehow DNS stopped working during the update and left the host and xoa in a strange state and of course NTP could not update. I fixed the resolve.conf and 99 patches showed up in the pool. I will install those after hours and I hope all will be well after that.
Thank you for the response.
-
@edisoninfo Great!
This warning is a life saver and did perfectly its job, allowing you to discover a hidden issue
Glad you found the root cause! -
O olivierlambert marked this topic as a question
-
O olivierlambert has marked this topic as solved