VMware Communities > VMTN > VMware Infrastructure™ > VI: ESX 3.5 > Discussions
Up to Discussions in VI: ESX 3.5

This Question is Answered

2 "helpful" answers available (6 pts)
1 2 3 ... 5 Previous Next
61 Replies Last post: May 6, 2009 2:14 PM by CarboCrux777
Reply

errors after upgrade 3.5.0 to 3.5.0 Upgrade 1

Apr 11, 2008 3:39 AM

Click to view Fredzone's profile Novice Fredzone 11 posts since
Jan 2, 2006
Hello,

I upgraded two servers from 3.5.0 to 3.5.0 upgrade 1 from the CD.
Everything was fine during the upgrade process but at the boot procedure, I had errors at the end with the last script "/var/pegasus/vmware/install_queue/3".

Error from the log file /var/pegasus/vmware/install_queue/3.log"
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"

I had the same errors on both servers. If I reboot the servers "/var/pegasus/vmware/install_queue/3" re-tries each time but failed.
Everything seems right on the servers but I'm not confident about that.

What can I do to fix that?

Thank you in advance,

Frédéric

Reply Re: errors after upgrade 3.5.0 to 3.5.0 Upgrade 1 Apr 11, 2008 5:36 AM
Click to view kucharski's profile Master kucharski 982 posts since
Sep 13, 2004

Did you actually download the correct file from VMware. There are actually 3 files you can download:

1. A straight iso image for a brand new build of ESX 3.5 w/ Update 1 (which you probably downloaded and don't want)

2. An upgrade package from ESX 2.x to ESX 3.5 w/ Update 1

3. An upgrade package from ESX 3.5 to ESX 3.5 w/ Update 1 (this is the one that you should have downloaded)

Michael

Reply Re: errors after upgrade 3.5.0 to 3.5.0 Upgrade 1 Apr 11, 2008 6:32 AM
Click to view bkhowson's profile Novice bkhowson 14 posts since
Dec 2, 2005
I believe pegasus is part of the IBM Director client. You would have to talk to IBM about it. If you can experiment (test lab...) you could try removing and reinstalling Director.
Reply Re: errors after upgrade 3.5.0 to 3.5.0 Upgrade 1 Apr 11, 2008 6:37 AM
in response to: kucharski
Click to view Fredzone's profile Novice Fredzone 11 posts since
Jan 2, 2006

I downloaded the correct file (the servers have the related build). I took the ISO file and I burn it on a CD.
I wanted to be sure of my media so I run the media test of the installation CD. The check was ok on both servers. So I'm pretty sure that the ISO/media is not the source of the problem.

Frédéric


Reply Re: errors after upgrade 3.5.0 to 3.5.0 Upgrade 1 Apr 11, 2008 6:38 AM
in response to: bkhowson
Click to view Fredzone's profile Novice Fredzone 11 posts since
Jan 2, 2006
The servers are HP ML570. IBM director is not installed on the servers.
Reply Re: errors after upgrade 3.5.0 to 3.5.0 Upgrade 1 Apr 13, 2008 2:38 PM
Click to view Dram's profile Novice Dram 5 posts since
Nov 19, 2004

I have the exact problem of FredZone, same error, same erro in logfile, upgrade from 3.5 to 3.5.0 upgrade 1, upgrade from downloaded iso (verified).

The only difference is that the server is a hp proliant DL380 G5

What happen?????


Reply Re: errors after upgrade 3.5.0 to 3.5.0 Upgrade 1 Apr 13, 2008 3:15 PM
Click to view mike.laspina's profile Virtuoso mike.laspina 2,251 posts since
May 26, 2006

Hi,

Your installation/upgrade is just fine. Pegasus is an opensource Common Information Model management tool. The error you received is very minor.

The pegasus engine was trying to compile the list of MOF files in the /var/pegasus/vmware/install_queue/3

Unfortunately there appears to be a miss match for only the VMware_Identity class object.

I am working this issue myself and hope to have to time to clean up the error'd MOF repository.

It will not cause any problems for VC but could have minor impact on any CIM based management apps for the server which most shops don't use.


Reply Re: errors after upgrade 3.5.0 to 3.5.0 Upgrade 1 Apr 14, 2008 1:35 AM
in response to: mike.laspina
Click to view supersonic!'s profile Novice supersonic! 11 posts since
Mar 5, 2007

Hi,

I'm running into the same issue on all servers (4 x 3.5 -> 3.5-U1).

When rebooting a server "/var/pegasus/vmware/install_queue/3" starts again.

Hoping this issue - minor or not - will be solved shortly...

Bye

Martin


Reply Re: errors after upgrade 3.5.0 to 3.5.0 Upgrade 1 Apr 14, 2008 6:58 AM
in response to: supersonic!
Click to view bkhowson's profile Novice bkhowson 14 posts since
Dec 2, 2005

Has anyone done the upgrade on IBM? Are all the complaints on HP? Do the people reporting issues have Insight Manager installed, or are these 'pristine' systems?


Reply Re: errors after upgrade 3.5.0 to 3.5.0 Upgrade 1 Apr 14, 2008 7:51 AM
in response to: bkhowson
Click to view mike.laspina's profile Virtuoso mike.laspina 2,251 posts since
May 26, 2006

Hi,

I have IBM servers and yes it occurs on a clean install as well.

Reply Re: errors after upgrade 3.5.0 to 3.5.0 Upgrade 1 Apr 14, 2008 2:38 PM
in response to: Fredzone
Click to view mike.laspina's profile Virtuoso mike.laspina 2,251 posts since
May 26, 2006

Ok,

I have solved this issue.
There are a couple of errors in the MOF compiler directives and a file is missing from the shared provider components.
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.

Enjoy!

Reply Re: errors after upgrade 3.5.0 to 3.5.0 Upgrade 1 Apr 14, 2008 11:32 PM
in response to: mike.laspina
Click to view Dram's profile Novice Dram 5 posts since
Nov 19, 2004

Seems that everything go OK, Tanks!!!
Reply Re: errors after upgrade 3.5.0 to 3.5.0 Upgrade 1 Apr 15, 2008 6:12 AM
in response to: mike.laspina
Click to view daniel337's profile Novice daniel337 16 posts since
Oct 26, 2005
@mike.laspina:

Thank you very much for this helful answer! I had exact this problem after the update of five servers (Dell PowerEdge 2900 III) from version 3.5.0 to 3.5.0 Update 1 using the CD.

Thumps up!

Daniel
Reply Re: errors after upgrade 3.5.0 to 3.5.0 Upgrade 1 Apr 15, 2008 11:51 AM
in response to: mike.laspina
Click to view mjcb's profile Enthusiast mjcb 146 posts since
Sep 16, 2005
Hello,

After I do this, what log do I check to ensure the error is fixed.

Thanks,
Reply Re: errors after upgrade 3.5.0 to 3.5.0 Upgrade 1 Apr 15, 2008 2:04 PM
in response to: mjcb
Click to view mike.laspina's profile Virtuoso mike.laspina 2,251 posts since
May 26, 2006

Hi,

The pegasus log entries are mostly in /var/messages and maybe some in /var/boot.log.


1 2 3 ... 5 Previous Next
Actions
Up to Discussions in VI: ESX 3.5