After installing ESX 3.5 update 1 an error occurs during the boot proces:
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”
Compiling omc-smash-interop-schema.mof into root/PG_Interop
A quick search on the VMTN forum revealed that I wasn’t the only one experiencing these problems. Luckily Mike Laspina already discovered how to fix this problem:
Here is what you will need to do.
Edit the roleauth-schema compiler directive to include the VMware_Identity class definition using nano /var/pegasus/vmware/install_queue/3_files/mofs/root/PG_Interop/roleauth-schema.mof
Add the bolded line above the pre-existing member directive.
#pragma include (“VMware_Identity.mof”)
#pragma include (“VMware_IdentityMemberOfCollection.mof”)It also needs to be added in the standard cimv2 path.
nano /var/pegasus/vmware/install_queue/3_files/mofs/root/cimv2/roleauth-schema.mof
#pragma include (“VMware_Identity.mof”)
#pragma include (“VMware_IdentityMemberOfCollection.mof”)Copy the missing file from the stardard cimv2 path to the shared path.
cp /var/pegasus/vmware/install_queue/3_files/mofs/root/cimv2/VMware_Identity.mof /var/pegasus/vmware/install_queue/3_files/mofs/root/PG_Interop/
Stop and start the service with these commands.
/etc/init.d/pegasus stop
/etc/init.d/pegasus start
Once the scripts completes the install_queues will be empty and the service will start much more quickly.
And according to the user mjilin VMware support is also aware and this issue will be addressed soon:
Dear ESX users,
Thanks for your timely feedback regarding upgrading to ESX/ESXi 3.5 Update 1.
As one user correctly pointed out, we use Pegasus to provide system management information, which third-party vendors can incorporate into their management applications.
We have identified the root cause of the issue and will provide fixes in an upcoming patch release. More information can be found in the Knowledge Base article 1004257.
Thanks for your information sharing in the community forum and keeping the discussion lively. We appreciate your support and feedback.
Best regards,
VMware ESX Product Tea
Michael says
Thanks guy,
This fixed all my issues!
Lars says
Thx 🙂
Jan says
Thanks a lot. This fixed the issues…
Kevin says
you’re a legend. thanks for this.
i’m finding on the esx3.5 installations i’m doing, the directory I need to go to is 1_files, rather than 3_files as mentioned above, but otherwise it works perfectly 🙂
Scott Lowe says
I’ll echo Kevin’s comment above. The process works perfectly, but I’m needing to modify the 1_files directory instead of the 3_files directory. Anyone have any idea why that’s the case?
John Eckard says
This worked. I had to use the 1_files as well.
FYI Doing it in 3.5 esx u1 as well says
Thanks for the patch lines! In ESX 3.5 U1 still after patching the 1_files instead of the 3_ in your example I am still getting the pegasus start error.
But I figured it was worth a shot…thanks for your info!
Regards,
Paul Bounds
Houston,TX
FYI Doing it in 3.5 esx u1 as well says
I found what the problem was, in the cut and paste, the quotes got chenged somehow to . instead of ” I went back into the two role schema files, made the substitution, restarted pegasus, and it came right.
Thanks Again!
Paul Bounds
Houston, TX
Jamie Morrison says
I have implemented Mike La Spina’s solution as a script that will handle queue directories 1-9 to automate the resolution.
Pegasus service fails to start after upgrade or installation of ESX 3.5 Update 1
http://theether.net/kb/100083
Duncan Epping says
Thanks for the script! Nice solution.
Brian Wing says
Sweet! U Rock.
mikemcs says
thanks for offering this info, but i am a newbie…
1. If my esx hangs on the pegasus thing, how do i get to a shell prompt
2. how do i transfer your fix script so i can run it?
mikemcs says
OR better yet, i understand that can be disabled…how do i disable the pegasus thing?
Duncan says
Just wait until it’s finished, it can take up to 10 / 15 minutes but you will get a prompt in the end. I use FASTSCP or WinSCP for copying files. Don’t forget to make the script executable with “chmod 755 “
mikemcs says
it never finishes, it POSD during the pegasus thing…happens same way after 4 attempted installs.
I would like to just disable it for now to see if that gets me by my POSD…can you tell me how i disable it?
Its been awhile since I played with unix….i am sure it is in a startup file somewhere, and then I can just REM that line that starts the pegasus?
Do i have to install the tools for winscp to work?
Duncan Epping says
Yeah you can disable it if you can login, try ALT F2 to login. I don’t have access to a 3.5 system at the moment but the pegasus start up can be disabled via chkconfig i guess.
Joaquin Avellan says
ESX 3.5 Update 2 will fix the pegasus provider, released July 25th.
Andres Martinez says
I applied the fix also and after some time the CPU utilization of the service console peaks at 100% all the time.. if I restart the pegasus service it goes back to normal.
I’m still running update 1.. not planning to upgrade to update 2 in the near term
anybody experiencing the same ?
this is the script that I used:
PEGASUS_PATH=/var/pegasus/vmware/install_queue/
cd $PEGASUS_PATH
for queue in `ls ?`
do
echo $queue
CURRENT_FILE=$PEGASUS_PATH$queue’_files/mofs/root/PG_Interop/roleauth-schema.mof’
if [ -f $CURRENT_FILE ] ; then
echo $CURRENT_FILE
sed ‘/#pragma include (“VMware_IdentityMemberOfCollection.mof”)/i\#pragma include (“VMware_Identity.mof”)’ $CURRENT_FILE > /tmp/roleauth-schema.mof
mv /tmp/roleauth-schema.mof $CURRENT_FILE -f
fi
CURRENT_FILE=$PEGASUS_PATH$queue’_files/mofs/root/cimv2/roleauth-schema.mof’
if [ -f $CURRENT_FILE ] ; then
echo $CURRENT_FILE
sed ‘/#pragma include (“VMware_IdentityMemberOfCollection.mof”)/i\#pragma include (“VMware_Identity.mof”)’ $CURRENT_FILE > /tmp/roleauth-schema.mof
mv /tmp/roleauth-schema.mof $CURRENT_FILE -f
fi
CURRENT_FILE=$PEGASUS_PATH$queue’_files/mofs/root/cimv2/VMware_Identity.mof’
if [ -f $CURRENT_FILE ] ; then
echo $CURRENT_FILE
cp $CURRENT_FILE $PEGASUS_PATH$queue’_files/mofs/root/PG_Interop/’
fi
done
#service pegasus restart
Duncan says
haven’t seen this happening but can you check which process is causing this?