The host returns esxupdate error codes: -1, Check the update manager log files and esxupdate log files

Problem Description:

When you scan ESXi servers from Update Manager you receive error “esxupdate error codes: -1”
If you check update manager log you will see something like this “VIBs ELX_bootbank_elx-esx-libelxima.so_12.0.1108.0-03 and ELX_bootbank_elx-esx-libelxima.so_12.0.1108.0-03 have unequal values of the ‘payloads’ attribute: ‘[elx-esx-libelxi: 1602.936 KB]’ != ‘[elx-esx-libelxi: 1493.833 KB]’ “. You can see exact similar entry in ESXi server logs also along with other error messages.
In your case name of VIBs could be different, it happens because exact same VIB has a different payload. If you find issue with different VIB, then please use that VIB name in all the commands I mentioned in solution section.

Solution:

First, enable SSH for ESXi host as we have to remove the VIB in question.
Run the following command first, I am trying to filter the result by specifying the name of VIB.
Command –
esxcli software vib list | grep ELX

Command Result –
elx-esx-libelxima.so 12.0.1108.0-03 ELX VMwareCertified 2018-08-23

Now to remove the VIB, use the command mentioned below.
Command –
esxcli software vib remove -n elx-esx-libelxima.so

Command Result –
Removal Result
Message: The update completed successfully, but the system needs to be reboot ed for the changes to be effective.
Reboot Required: true
VIBs Installed:
VIBs Removed: ELX_bootbank_elx-esx-libelxima.so_12.0.1108.0-03
VIBs Skipped:

Restart ESXi host and then you can scan server from Update Manager.

17 Comments

  1. Thank you for psting this issue. This was great, because I had exact the sam. You saved me a lot of time.

  2. Hi Pankaj Patil, I had the same prb and your article was useful, but every time I apply a remediation the issue come back…
    very annoying….

    1. If this is happening for multiple servers connected to same vCeneter then probably you have some kind of customization that keeps on adding the VIB in question when you install the updates. Can you please share the exact error message, ESXi version and server make-model? Also if possible create custom baseline and skip the VIB creating issues.

      1. Hi pankaj… I am having Same issue.. after remediation same error message.. My vcenter server is 6.7 lastest one 15132721 and esxi version is 14320388….first tried in a server it’s worked fine but.. Remaining 18 servers I had error code 1 .. Scanning esxi works fine oly while remediation

  3. i see this problem only with HP G10 servers, i have this VIB running on HP G9 servers and Update manager scan works perfectly on those ?

    Also would like to know what would be impact if we uninstall this VIB and purpose of this VIB

    1. The error message says there is a conflict so when you remove the VIB and next time install the updates it should install all required/missing VIBs. This VIB is for emulex drivers.

  4. Hey Pankaj,

    Thanks for the information. However, in my case, the scan has no issue. Re-mediating the host returns the same error message. This is because the non-critical patches in the Update Manager baseline contain those drivers. Any idea on how to tackle that issue ?

  5. If after remediation returns the same error message, you have to delete the vib :
    esxcli software vib remove -n xxxxxxxxxx.so

    and also CLEAN the VCENTER update manager database as root via CLI :
    service-control –stop vmware-updatemgr
    /usr/lib/vmware-updatemgr/bin/updatemgr-utility.py reset-db
    rm -rf /storage/updatemgr/patch-store/*
    service-control –start vmware-updatemgr

Leave a Reply

Your email address will not be published. Required fields are marked *