The command displays the ID, release date, vendor, summary, severity, category,
installation date, description, knowledge base URL, contact, and list of
constituent VIBs for each bulletin.
The update command installs selected bulletins and VIBs on the host. The
command requires at least one of the -m|--meta option or the
--bundle option.
If specified with -m|--meta or --bundle, the command installs
all bulletins within the meta-data or offline bundle ZIP that are applicable to
the host. (A bulletin is applicable if it contains one or more applicable VIBs;
a VIB is applicable if it matches the host's platform, version and locale.)
The update command automatically downloads VIBs from a remote location
if necessary, unless they have been previously downloaded using the stage
command.
Installing a bulletin results in the VIBs contained in the bulletin being
installed, unless they are obsoleted or already installed. If all of the VIBs in
a bulletin are already installed or obsoleted by other VIBs installed on the
host, the bulletin is marked as installed in the esxupdate database without any
additional installation of VIBs.
The -b option may be combined with -m|--meta or --bundle
to restrict installation to specific bulletins.
The update command will attempt to resolve any missing dependencies, and
prompt for their installation.
REMOVE
-
esxupdate remove
[-b bulletin-id]
The remove command removes a selected bulletin from the host, by removing
the VIBs contained in it. It is designed for removing extensions which were
added after the initial install, but not for removing ESX patch and update bulletins.
The remove command does not roll back patches, rather it completely removes VIB packages from the system.
A bulletin can not be removed if any of the VIBs
in the bulletin are obsoleted by another bulletin installed on the host. A
bulletin can also not be removed if the removal would break any dependencies
for other VIBs or packages installed on the host.
STAGE
-
esxupdate stage
[-m meta-url|--meta=meta-url]
[--bundle=bundle-url]
[-b bulletin-id]
[--nocache]
The stage command downloads and prepares selected VIBs and bulletins for
installation. It performs all of the functions of update, except that it
does not call the underlying package manager (RPM or ipkg) to install VIBs on
the host system. The stage command can be used to download VIBs and
meta-data or offline bundle ZIPs, and to check for dependency, conflict or
obsoletion before attempting to run the update command.
SCAN
-
esxupdate scan
[-m meta-url|--meta=meta-url]
[--bundle=bundle-url]
[-a|--all]
The scan command reads meta-data or an offline bundle ZIP and displays
information on the bulletins they contain. The command produces a list of
bulletin IDs, their release dates, and their summaries. The scan
command can be used to determine what bulletins are available in a given
meta-data or offline bundle ZIP, as well as which bulletins the host does not
comply with.
EXIT VALUES
In addition to error messages and logging, esxupdate uses various exit
values to denote different error conditions:
- 0
-
Success. No error.
- 2
-
The command-line syntax was not valid.
- 3
-
esxupdate could not get an exclusive lock on its lock file. Another
instance of esxupdate is running.
- 4
-
esxupdate failed to download meta-data.
- 5
-
The meta-data format could not be un-archived or could not be parsed. The
meta-data format is invalid.
- 7
-
One or more VIBs could not be downloaded or copied.
- 8
-
The VIB could not be un-archived, or the VIB XML data could not be parsed. The
format of the VIB is invalid.
- 9
-
An error occurred reading or writing VIB data.
- 10
-
A general error occurred reading or writing to or from a file.
- 11
-
The esxupdate database could not be parsed. The database format is invalid.
- 12
-
An error occurred reading or writing to the esxupdate database.
- 13
-
The requested bulletin (specified with -b) could not be found in the
meta-data, or no bulletin exists in the meta-data that matches this platform,
version, and locale.
- 14
-
An error occurred checking dependencies. One or more VIBs can not be installed
due to a conflict, obsoletion, or because it requires another VIB that could
not be located in meta-data or on the host.
- 15
-
The underlying package manager returned an error.
- 16
-
esxupdate was unable to parse its configuration file.
- 18
-
One or more VIBs require the host to be in maintenance mode, but the host is
not currently in maintenance mode.
- 19
-
One or more post-installation scripts (specified in esxupdate.conf) failed to
complete successfully.
- 20
-
A VIB did not contain signed hash data.
- 21
-
A VIB contained signed hash data with an unrecognized or unsupported version.
- 22
-
A VIB contained invalid signed hash data.
- 23
-
The VIB's hash data was signed with an expired or untrusted key.
- 24
-
The VIB's signed hash does not match the hash calculated from VIB data.
- 25
-
Additional dependencies are available in the meta-data, and must be specified
in order to resolve requirements.
- 26
-
The offline bundle could not be downloaded.
- 27
-
The offline bundle could not be un-archived, or contained invalid data.
- 80
-
One or more updated VIBs require the host to be rebooted (not an indication of
failure).
- 81
-
One or more updated VIBs require the mgmt-vmware service (hostd) to be restarted
(using the command "service mgmt-vmware restart"). This exit value does not
indicate an error.
FILES
- Configuration file:
-
/etc/vmware/esxupdate/esxupdate.conf
- Database files:
-
/etc/vmware/esxupdate/bulletins.zip
/etc/vmware/esxupdate/vibs.xml
- Log file:
-
/var/log/vmware/esxupdate.log
Index
- NAME
-
- SYNOPSIS
-
- DESCRIPTION
-
- OPTIONS
-
- GLOBAL OPTIONS
-
- COMMAND OPTIONS
-
- COMMANDS
-
- QUERY
-
- INFO
-
- UPDATE
-
- REMOVE
-
- STAGE
-
- SCAN
-
- EXIT VALUES
-
- FILES
-
This document was created by
man2html,
using the manual pages. Brought to you by Bouke Groenescheij, www.jume.nl
Time: 15:25:08 GMT, May 26, 2009