Skip to main content

'esxupdate' errors 10 & 99

Update:  8GB flash drive does not actually fix this, so don't go out and buy!  You need to get the hosts patched.

  1. Running ESXi
  2. No local storage (using USB stick)
You attach an Update Manager baseline and 'scan'.
First you get:
'The host returns esxupdate error codes: 10. Check the Update Manager log files and esxupdate log files for more details.'
So you reconfigure the /etc/vmware/esxupdate/esxupdate.conf file by adding in a path for the log file (/var/tmp/esxupdate.debug).
Then you get:
'The host returns esxupdate error codes: 99. Check the Update Manager log files and esxupdate log files for more details.'
So as per here ( you check that all the paths are correct. /var/tmp/ does not exist. It is actually a link to /scratch/var/tmp, and /scratch doesn't even exist.
As per here ( I created the dir using 'mkdir -p /tmp/scratch/var/tmp'. Success.
Note that this issue is resolved as of 4.1U1.

Original post:
This applies if you are running the following:
* ESXi installable on a flash drive
* No permanent local storage (i.e. no local SATA/SAS drive)
* Flash drive is 4GB or smaller

I'd been getting errors using Update Manager and Host Profiles with my ESXi hosts (with above config).  When trying to scan for updates I would get esxupdate error 10 (I think), and when trying to remediate updates I would get esxupdate error 99.  Most patches would install, but one would not, failing with that error.

"The host returns esxupdate error codes: 99.Check the Update Manager log files and esxupdate log files for more details."

Using host profiles, I would see silly things like 'Option Mem.VMOverheadGrowthLimit doesn't match the specified criteria'.  Even after successfully applying a profile, still issues.  

Anyways, after much Googling, I found this:

After 4.1 Update 1, it seems flash drives 4GB and smaller are no longer enough without additional local storage.  People have reported success with 8GB drives, so that's what I've ordered.  Not a huge cost, just a hassle trying to figure this out.  

Thank you, Filbo.

Hope this helps the Google results.


Popular posts from this blog

DFSR - eventid 4312 - replication just won't work

This warning isn't documented that well on the googles, so here's some google fodder:

You are trying to set up replication for a DFS folder (no existing replication)Source server is 2008R2, 'branch office' server is 2012R2 (I'm moving all our infra to 2012R2)You have no issues getting replication configuredYou see the DFSR folders get created on the other end, but nothing stagesFinally you get EventID 4312:
The DFS Replication service failed to get folder information when walking the file system on a journal wrap or loss recovery due to repeated sharing violations encountered on a folder. The service cannot replicate the folder and files in that folder until the sharing violation is resolved.  Additional Information:  Folder: F:\Users$\\Desktop\Random Folder Name\  Replicated Folder Root: F:\Users$  File ID: {00000000-0000-0000-0000-000000000000}-v0  Replicated Folder Name: Users  Replicated Folder ID: 33F0449D-5E67-4DA1-99AC-681B5BACC7E5  Replication Group…

Fixing duplicate SPNs (service principal name)

This is a pretty handy thing to know:

SPNs are used when a specific service/daemon uses Kerberos to authenticate against AD. They map a specific service, port, and object together with this convention: class/host:port/name

If you use a computer object to auth (such as local service):

If you use a user object to auth (such as a service account, or admin account):

Why do we care about duplicate SPNs? If you have two entries trying to auth using the same Kerberos ticket (I think that's right...), they will conflict, and cause errors and service failures.

To check for duplicate SPNs:
The command "setspn.exe -X

C:\Windows\system32>setspn -X
Processing entry 7
MSSQLSvc/ is registered on these accounts:
CN=SQL Admin,OU=service accounts,OU=resources,DC=company,DC=local

found 1 groups of duplicate SPNs. (truncated/sanitized)

Note that y…

Logstash to Nagios - alerting based on Windows Event ID

This took way longer than it should have to get here's a config and brain dump...

You want to have a central place to analyze Windows Event/IIS/local application logs, alert off specific events, alert off specific situations.  You don't have the budget for a boxed solution.  You want pretty graphs.  You don't particularly care about individual server states.  (see rationale below - although you certainly have all the tools here to care, I haven't provided that configuration)

ELK stack, OMD, NXlog agent, and Rsyslog.  The premise here is as follows:

Event generated on server into EventLogNXlog ships to Logstash inputLogstash filter adds fields and tags to specified eventsLogstash output sends to a passive Nagios service via the Nagios NSCA outputThe passive service on Nagios (Check_MK c/o OMD) does its thing w. alerting
Open Monitoring Distribution, but the real point here is Check_MK (IIRC Icinga uses this...).  It makes Nagios easy to use and main…