VMware Communities: Message List - errors after upgrade 3.5.0 to 3.5.0 Upgrade 1

Re: errors after upgrade 3.5.0 to 3.5.0 Upgrade 1

CarboCrux777 — Wed, 06 May 2009 21:14:19 GMT

Just to let you know that the Pegasus error still occurs when upgrading from the HP downloaded version of ESX 3.5 U3 to the Vmware Version of ESX 3.5 U4.

I had the error today where the system hung after trying to do something in the Pegasus startup.

Re: errors after upgrade 3.5.0 to 3.5.0 Upgrade 1

Schorschi — Fri, 15 Aug 2008 19:24:57 GMT

Good. We stop services, run the script, then explicit start services. Seems to be fine. However, it just so happens that we reboot shortly after, since the fix script is run per our automated build process. So that is why we may not be seeing the same results initially as you did.

Re: errors after upgrade 3.5.0 to 3.5.0 Upgrade 1

prefixed — Fri, 15 Aug 2008 19:12:14 GMT

Actually I just checked it now and it appears to be working. I did restart the esx host a few more times. It didn't seem to fix the first time I restarted though.

Re: errors after upgrade 3.5.0 to 3.5.0 Upgrade 1

Schorschi — Fri, 15 Aug 2008 19:05:06 GMT

Really? Humm. Has worked for us. Is it the very latest script?

Re: errors after upgrade 3.5.0 to 3.5.0 Upgrade 1

prefixed — Wed, 13 Aug 2008 04:58:41 GMT

I'm still having this issue after performing the required steps. I even tried running the script in case I made typos or something. Still a no go, any ideas why the steps wouldn't work?

Re: errors after upgrade 3.5.0 to 3.5.0 Upgrade 1

Schorschi — Wed, 13 Aug 2008 01:20:50 GMT

We have a standing policy that we never recommend a version of ESX to our clients until at least 90 days after GA code release. We learned this with ESX 2.5.0 moving from 2.1.2. This is for two reasons, both related to quality. First, hardware vendors, IBM, Dell, HP, at times, have significant issues with their respective hardware agents and new media releases from VMware. VMware does not have a great track record on testing even the third party components they recommend. Until the given hardware vendors recommend their agents have been fully vetted, they are not vetted by VMware. Second, VMware continues to prove that major releases just are not well vetted internally by VMware. We waited for more than 6 months on ESx 3.0 and we were still nailed on a numbe of issues. ESX 3.0.1 was better but not wonderful. ESX 3.5.0 we never recommended, this was per VMware recommendation to wait for 3.5 Update1, thus we only recently started recommending ESX 3.5 Update 1, again more than 90 days from GA release. This latest issue, unfortunate, for VMware, has proven to us, that we are justified in being late rather than early adoptors. We are very seriouosly waiting at least 6 months again, before recommending ESX 4, when it is released as GA.

Re: errors after upgrade 3.5.0 to 3.5.0 Upgrade 1

Engelsman — Tue, 12 Aug 2008 19:01:14 GMT

Yeah, Shouldn't install Update 2 (wasn't aware of that by the time).
Luckely for us, we don't have Update 2 running in production.
We 'll just sit back and wait I guess...

Re: errors after upgrade 3.5.0 to 3.5.0 Upgrade 1

Gerry.Deutsch — Tue, 12 Aug 2008 16:01:54 GMT

This problem appears to be fixed in Update2. However, the August 12th date problem is preventing me from doing a fresh ESX V3.50 Update2 installation. The documented fix about editing the MOF files worked perfeectly for me to correct the pegasus install errors.........

Re: errors after upgrade 3.5.0 to 3.5.0 Upgrade 1

williamarrata — Thu, 17 Jul 2008 21:31:55 GMT

I just did two fresh ESX 3.5 Update 1 installations on HP DL585 G5 128GB 4 4x4 quad processors and the same issue happened. I did the Mike Laspina fix and all is good. Just an FYI 3_files did not exist but 1_files did and changes were made there. After editing and copying files, I restarted service and good to go.

Hope that helped.

Re: errors after upgrade 3.5.0 to 3.5.0 Upgrade 1

Oswulf — Thu, 17 Jul 2008 21:09:21 GMT

Not resolved yet. Fresh install of ESX 3.5 Update 1 followed by Update Manager patches to build 98103. Issue still remains...

Re: errors after upgrade 3.5.0 to 3.5.0 Upgrade 1

mjlin — Thu, 10 Jul 2008 07:38:12 GMT

Dear ESX users,

A solution to this issue has been developed and will be available in the next Update release, which will be released shortly.

Best regards,

VMware ESX Product Team

Re: errors after upgrade 3.5.0 to 3.5.0 Upgrade 1

The Ether — Fri, 04 Jul 2008 04:10:28 GMT

Yep, I believe it is the same thing.

I have seen it on pretty much every server I have installed or upgraded on (Dell/IBM)

I believe the queue numbers change depending on whether it is an install or an upgrade.

Cheers,

Jamie.

Re: errors after upgrade 3.5.0 to 3.5.0 Upgrade 1

Schorschi — Fri, 04 Jul 2008 03:41:07 GMT

Just about every IBM server we install 3.5 U1 on, does something like this as well, but even install_queue 1 and 2 tasks error out. It does not appear to be the same issue, or is it?

Re: errors after upgrade 3.5.0 to 3.5.0 Upgrade 1

glynnd1 — Mon, 30 Jun 2008 16:26:51 GMT

Ugh!

Has VMware published a date on when they expect to have this resolved by? As much as I appricate the work Mike and others have put into the solution it is not something I'll get sign off from my boss on.

Re: errors after upgrade 3.5.0 to 3.5.0 Upgrade 1

The Ether — Tue, 17 Jun 2008 06:40:26 GMT

Hi,

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

Regards,

Jamie.

Re: errors after upgrade 3.5.0 to 3.5.0 Upgrade 1

mike.laspina — Wed, 11 Jun 2008 13:53:00 GMT

Ok,

Just want to make sure you were OK.

I noticed it is still an issue in 3.5.0u1.

Re: errors after upgrade 3.5.0 to 3.5.0 Upgrade 1

jason.vitanza@sequeldata.com — Wed, 11 Jun 2008 13:36:11 GMT

Mike,

I did get this to work, I just had to modify the files under"1_files" sorry about not posting this sooner, I was off for a week or so. Also, this is hapening on every install of 3.5 update 1, at least with HP Blades

Re: errors after upgrade 3.5.0 to 3.5.0 Upgrade 1

mike.laspina — Wed, 11 Jun 2008 12:22:07 GMT

If you disable the service you will not have the ability to used third party management products like System Center, HP Openview and any thing else that depends on a Common Interface Model/Web Enterprise Manager service.

As well the service was not functionally impacted by the MOF compiler scripts. It was still working but could not be correctly updated using the error'd script.

In Jason's case he indicated it was still not resolved with the corrected script directives and file copy.

Re: errors after upgrade 3.5.0 to 3.5.0 Upgrade 1

Engelsman — Wed, 11 Jun 2008 07:12:50 GMT

Hey Mike,

The issue can be resolved with your fix, but I still wonder what happens when you disable the pegasus service.

What would be affected by this?

Regards

Re: errors after upgrade 3.5.0 to 3.5.0 Upgrade 1

tom howarth — Wed, 11 Jun 2008 06:18:49 GMT

Thread moved to the VI: ESX 3.5 forum

Tom Howarth
VMware Communities User Moderator

Re: errors after upgrade 3.5.0 to 3.5.0 Upgrade 1

mike.laspina — Tue, 10 Jun 2008 23:18:18 GMT

HI Bill,

Jason noted he was still having an issue with pegasus but he has not indicated any resolve, so I was checking if he needed a hand with it.

Re: errors after upgrade 3.5.0 to 3.5.0 Upgrade 1

Kahonu84 — Tue, 10 Jun 2008 20:05:12 GMT

Me??? If so, not really. ESX1 was flawless. ESX2 - I ran into the issue and your fix took care of it. ESX3 - I won't be doing for another week or two.

Bill

Re: errors after upgrade 3.5.0 to 3.5.0 Upgrade 1

mike.laspina — Tue, 10 Jun 2008 19:59:56 GMT

Hi,

Are you still having an issue with this?

Re: errors after upgrade 3.5.0 to 3.5.0 Upgrade 1

mike.laspina — Fri, 06 Jun 2008 19:26:17 GMT

I don't know what the root cause is. I would have to be intimate with the build process to know. I just understand the pegasus components and am able to correct the scripts so they install correctly.

I suspect that it was a good code distro up until 3.0.1 and then the issue surfaced. It not a serious problem since it is not used by very many shops. However it does make you wait longer for a system to come up.

Re: errors after upgrade 3.5.0 to 3.5.0 Upgrade 1

Kahonu84 — Fri, 06 Jun 2008 18:12:09 GMT

A question in retrospect if I may. Thusfar I have upgraded two (of three) hosts. The hosts are the same, the media is the same and I am the same. Why would this error come up on ESX2 and not ESX1??

Mahalo, Bill

Re: errors after upgrade 3.5.0 to 3.5.0 Upgrade 1

Kahonu84 — Fri, 06 Jun 2008 06:38:05 GMT

Mahalo Mike for your contributions. This worked for me also.

Bill

Re: errors after upgrade 3.5.0 to 3.5.0 Upgrade 1

Bastien_P — Thu, 05 Jun 2008 18:41:22 GMT

Same here. 2 new fresh install and i have the error msg. But for now it seems ok and for what i read here.. The error is not a critical one. So i guess i'll wait and see. Tks for the solution and the confirmation that this solution is a correct workaround.

Re: errors after upgrade 3.5.0 to 3.5.0 Upgrade 1

raoulst — Mon, 02 Jun 2008 15:03:48 GMT

I did a fresh install of 3.5 U1 and do also have this problem.
Is there anybody out there running 3.5 U1 and not having this problem?

raoulst

Re: errors after upgrade 3.5.0 to 3.5.0 Upgrade 1

jason.vitanza@sequeldata.com — Mon, 02 Jun 2008 14:57:30 GMT

After my install, I do not have a "/var/pegasus/vmware/install_queue/3_files" directory. All I have is a 1_Files, and 2_Files directory. I made the changes to 1_files and 2_files. I am still getting this error.

Any thoughts?

Re: errors after upgrade 3.5.0 to 3.5.0 Upgrade 1

joanwhit — Mon, 19 May 2008 18:40:13 GMT

We only had 2 files - do you create 3_files file?

Re: errors after upgrade 3.5.0 to 3.5.0 Upgrade 1

jnickel — Wed, 14 May 2008 18:13:37 GMT

I had the same error after upgrading a couple 3.0.2 boxes to 3.5 update 1. Just so you know...the directory was 2_files in my case...not 3_files.

Thanks for the information!

Jim

Re: errors after upgrade 3.5.0 to 3.5.0 Upgrade 1

Engelsman — Thu, 08 May 2008 12:41:03 GMT

Hi,

Hope someone can answer my additional questions:

For now I disabled the pegasus service. As far as I can see everything is still working fine.

Is there really a need for running the pegasus service? Are there any VMware, HP, IBM, Dell components making use of Pegasus?
Security-wise wouldnt it be best to run as few as possible services?

Greets,

Re: errors after upgrade 3.5.0 to 3.5.0 Upgrade 1

dmadden — Fri, 02 May 2008 15:21:58 GMT

It's safe to perform the workaround, however a patch will be released to fix the issue.

Re: errors after upgrade 3.5.0 to 3.5.0 Upgrade 1

carlo.toniolo — Fri, 02 May 2008 14:51:58 GMT

Thanks A LOT

Carlo

Re: errors after upgrade 3.5.0 to 3.5.0 Upgrade 1

mike.laspina — Thu, 24 Apr 2008 20:05:00 GMT

Hi,

If there was an issue with the solution I have provided VMware would have indicated it in their post.

They are just acknowledging they know about it and will include the fix in the near future so we the users are not saying hey where is VMware on this one.

I have worked with systems management to a fair degree and can tell you that this solution is what needs to be done to correct the update failure.

Re: errors after upgrade 3.5.0 to 3.5.0 Upgrade 1

bggb29 — Thu, 24 Apr 2008 16:26:16 GMT

This solution worked for me.
Thanks

Re: errors after upgrade 3.5.0 to 3.5.0 Upgrade 1

Monoman — Thu, 24 Apr 2008 11:35:27 GMT

The KB writeup does not mention the work around mentioned earlier in the thread? Does that mean we should wait and NOT perform the workaround? I would it would be safest to undo the workaround before applying the forthcoming patch.

thanks everyone.

Re: errors after upgrade 3.5.0 to 3.5.0 Upgrade 1

mjlin — Wed, 23 Apr 2008 20:27:40 GMT

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 Team

Re: errors after upgrade 3.5.0 to 3.5.0 Upgrade 1

mike.laspina — Tue, 22 Apr 2008 17:13:35 GMT

Confirmed no issue if the queue instance is not 3, it could be 1 2 or 3 etc. provided you are getting the same error.

Re: errors after upgrade 3.5.0 to 3.5.0 Upgrade 1

GraphiteDak — Tue, 22 Apr 2008 15:23:02 GMT

yes, you are correct.

Re: errors after upgrade 3.5.0 to 3.5.0 Upgrade 1

mjcb — Tue, 22 Apr 2008 15:20:49 GMT

OK,

I didn't have the 3_files directory, but the data was all in the 1_files directory. I ran through the steps but subsituted the

/var/pegasus/vmware/install_queue/3_files/mofs/root/PG_Interop/roleauth-schema.mof

with

/var/pegasus/vmware/install_queue/1_files/mofs/root/PG_Interop/roleauth-schema.mof

It worked...was that the right thing to do?

Re: errors after upgrade 3.5.0 to 3.5.0 Upgrade 1

mjcb — Tue, 22 Apr 2008 14:53:24 GMT

I followed the steps on my one environment, now on a different environment I don't have the 3_files directory. This was a fresh install...what do I do now?

Re: errors after upgrade 3.5.0 to 3.5.0 Upgrade 1

GraphiteDak — Tue, 22 Apr 2008 12:27:06 GMT

All they need to do is repackage the pegasus rpm. I went ahead and incorporated the fix into my kickstarts for now. Yes, thanks Mike!

Re: errors after upgrade 3.5.0 to 3.5.0 Upgrade 1

DFATAnt — Tue, 22 Apr 2008 03:32:45 GMT

I've been experiencing the same problem as mentioned by everyone else. We even logged an SR with VMware support and the best they could do was point us at this discussion thread. It's great that Mike.Laspina has posted a fix (thanks Mike), but I would have thought that VMware would have provided a revised package. I have a large number of ESX servers and I really don't want to have perform a work around on every ESX server to get around a flawed update provided by VMware. And yes I could write a script to make the work around alot easier, but once again why should I have do this when VMware should be providing a revised package.

Cheers

Ant

Re: errors after upgrade 3.5.0 to 3.5.0 Upgrade 1

mike.laspina — Wed, 16 Apr 2008 20:57:15 GMT

Hi,

What is pegasus? You would be best served by reading wiki http://en.wikipedia.org/wiki/Web-Based_Enterprise_Management

The pegasus service was still functional before the updates so this fix is not critical at this point.

The changes I made simply correct errors in the install components and will be ultimately what VMware will do to fix the problem.

The real benefit here is the boot process will be about 100 seconds faster.

Re: errors after upgrade 3.5.0 to 3.5.0 Upgrade 1

GraphiteDak — Fri, 18 Apr 2008 17:40:42 GMT

Let's just hope they re-package quickly.

Re: errors after upgrade 3.5.0 to 3.5.0 Upgrade 1

Monoman — Wed, 16 Apr 2008 19:58:20 GMT

I guess my questions are what is Pegasus? Is this problem superifcial or should it be addressed immediately? If it is a real problem that needs to be addressed then shouldn't VMWare issue a fix?

Re: errors after upgrade 3.5.0 to 3.5.0 Upgrade 1

mike.laspina — Tue, 15 Apr 2008 21:04:44 GMT

Hi,

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

Re: errors after upgrade 3.5.0 to 3.5.0 Upgrade 1

mjcb — Tue, 15 Apr 2008 18:51:17 GMT

Hello,

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

Thanks,

Re: errors after upgrade 3.5.0 to 3.5.0 Upgrade 1

daniel337 — Tue, 15 Apr 2008 13:12:13 GMT

@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

Re: errors after upgrade 3.5.0 to 3.5.0 Upgrade 1

Dram — Tue, 15 Apr 2008 06:32:49 GMT

Seems that everything go OK, Tanks!!!

Re: errors after upgrade 3.5.0 to 3.5.0 Upgrade 1

mike.laspina — Mon, 14 Apr 2008 21:38:54 GMT

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!

Re: errors after upgrade 3.5.0 to 3.5.0 Upgrade 1

mike.laspina — Mon, 14 Apr 2008 14:51:05 GMT

Hi,

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

Re: errors after upgrade 3.5.0 to 3.5.0 Upgrade 1

bkhowson — Mon, 14 Apr 2008 13:58:43 GMT

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?

Re: errors after upgrade 3.5.0 to 3.5.0 Upgrade 1

supersonic! — Mon, 14 Apr 2008 08:35:54 GMT

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

Re: errors after upgrade 3.5.0 to 3.5.0 Upgrade 1

mike.laspina — Sun, 13 Apr 2008 22:15:22 GMT

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.

Re: errors after upgrade 3.5.0 to 3.5.0 Upgrade 1

Dram — Sun, 13 Apr 2008 21:38:07 GMT

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?????

Re: errors after upgrade 3.5.0 to 3.5.0 Upgrade 1

Fredzone — Fri, 11 Apr 2008 13:38:46 GMT

The servers are HP ML570. IBM director is not installed on the servers.

Re: errors after upgrade 3.5.0 to 3.5.0 Upgrade 1

Fredzone — Fri, 11 Apr 2008 13:37:08 GMT

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

Re: errors after upgrade 3.5.0 to 3.5.0 Upgrade 1

bkhowson — Fri, 11 Apr 2008 13:32:06 GMT

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.

Re: errors after upgrade 3.5.0 to 3.5.0 Upgrade 1

kucharski — Fri, 11 Apr 2008 12:36:17 GMT

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

errors after upgrade 3.5.0 to 3.5.0 Upgrade 1

Fredzone — Fri, 11 Apr 2008 10:31:08 GMT

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