Print View

Pegasus service fails to start after upgrade or installation of ESX 3.5 Update 1


After installing or upgrading to ESX 3.5 Update 1 the pegasus install queues fail to complete delaying the start of the VirtualCenter Agent (vmware-vpxa) on reboot.

The failure can be seen by restarting the service:

# service pegasus restart
Processing /var/pegasus/vmware/install_queue/3             [FAILED]
ERROR: See log - /var/pegasus/vmware/install_queue/3.log
Processing /var/pegasus/vmware/install_queue/3             [FAILED]
ERROR: See log - /var/pegasus/vmware/install_queue/3.log
Pegasus CIMOM (cimserver) is already stopped.
Starting Pegasus CIMOM (cimserver)...                      [  OK  ]

And also in the log /var/pegasus/vmware/install_queue/3.log:

Compiling roleauth-schema.mof into root/PG_Interop
Parsing error: parse error: Error adding class VMware_IdentityMemberOfCollection to the repository: CIM_ERR_NOT_FOUND: The requested object could not be found: "VMware_Identity"

Note that the queue number can vary. It would appear to be 1 for a clean install, or 3 for an upgrade


The following script automates the original fix by Mike La Spina:

The script searches all of the queue directories and implements the fixes, then restarts the pegasus service.

Create the script and make it executable:

touch pegasusFix
chmod +x pegasusFix

Edit the script with vi or nano, and then run the script with:


The pegasusFix script is available from:


Pegasus Error Message During Upgrade from ESX Server 2.x to ESX Server 3.5 Update 1


VMware ESX 3.5 Update 1

Created: 17th June 2008
Updated: 8th July 2008

Print View

© 2005-2024 Jamie Morrison