Weird error message when trying to update ESXi


I’m trying to update an ESXi host:

# uname -a
VMkernel esxihostname.somedomain.com 6.7.0 #1 SMP Release build-14320388 Aug 5 2019 02:37:06 x86_64 x86_64 x86_64 ESXi

The command I am invoking is from [https://esxi-patches.v-front.de/ESXi-6.7.0.html](https://esxi-patches.v-front.de/ESXi-6.7.0.html) (while firewall port 443 open)

# esxcli software profile update -p ESXi-6.7.0-20191204001-standard
-d https://hostupdate.vmware.com/software/VUM/PRODUCTION/main/vmw-depot-index.xml

to which I receive this error:

unorderable types: datetime.datetime() < NoneType()
Please refer to the log file for more details.

I thought it might have to do with time sync – hosts are all set to UTC in BIOS and in web client, I’ve tried setting VCSA both to host, or using domain controllers as NTP sources – neither appear to have any impact.

ntpd appears to be behaving normally:

# ntpd -q
27 Dec 06:40:57 ntpd[2206256]: ntpd 4.2.8p13+vmware@1.3847-o Mon May 20 19:29:19 UTC 2019 (1): Starting
27 Dec 06:40:57 ntpd[2206256]: Command line: ntpd -q
27 Dec 06:40:57 ntpd[2206256]: proto: precision = 0.323 usec (-21)
27 Dec 06:40:57 ntpd[2206256]: basedate set to 2019-05-08
27 Dec 06:40:57 ntpd[2206256]: gps base set to 2019-05-12 (week 2053)
27 Dec 06:40:57 ntpd[2206256]: unable to bind to wildcard address :: – another process may be running – EXITING

# ntpq -p
remote refid st t when poll reach delay offset jitter
somedc01.somedom 4 u 20 64 3 0.465 0.482 0.247
somedc02.somedom .LOCL. 1 u 20 64 3 0.698 72478.7 10.249

Anyone ever seen this before? Any ideas about what I could do?

Thinking about trying a fresh install of 6.7U3 but would like to avoid if possible.


View Reddit by AveryFreemanView Source


To see the full content, share this page by clicking one of the buttons below

Related Articles

One Comment

Leave a Reply