Problem after update VMware 4 with Vcenter update

[psmeele]

Hello All,

After we did an update by Vcenter of one of our VM-server to the latest 4.0 updates the server cannot connect to vcenter anymore.

I've found an error message "error: Signature mismatch betweem vmkctl (nov 30 2010 16:26:35) adn vmkernel (_unknown_ )"

We also couldn't ping this server.

Does anyone had the same problem and can someone tell us how to solve this.

Unfortunately we have no linux expirience.

Thanks in advantage

Best regards

Peter

[bshubinsky]

Can you not ping the ESX Host or is it the vCenter server that you can't ping?

[nkrishnan]

Hi,

> I've found an error message "error: Signature mismatch betweem vmkctl (nov 30 2010 16:26:35) adn vmkernel (_unknown_ )"

Above error i found if ESX has been patched or upgrade /update the vmkernel and run some vmkernel/esx commands before rebooting  ESX host. Here the running vmkernel is old version before the reboot and vmkctl will look for new vmkernel which is not yet loaded in the memory

please reboot the esx host once and re-try your operations

Thanks

Nithin

[psmeele]

Hello Bo,

I can't ping the ESX host

Thanks for your reply

Peter

[psmeele]

Hello Nithin,

I've rebooted the host al many times ;-(

Thanks for your reply

Peter

[nkrishnan]

From what level you upgrade to which level are you upgraded the ESX4.0X VM. what method are you used for upgrade

Can you collect esxupdate.log , messages and vmkernel.log

Did you try to apply latest patches and try the scenario

Thanks

Nithin

[psmeele]

Hello Nithin,

We were upgrading from the latest VM-software (4.0.0.294855) to the latest 6 patches.

We did the update by VCenter update manager, like we always do.

Thanks for your reply and time

Peter

[rico4400]

Hi Peter

My 2 cents

I encounter the same problem after applying ESX 4.1 U1 with viupdate

What I did

reboot in troubleshooting mode

I tried  esxcfg-boot -b

but still received error message when build

It was /boot full

not easy to hit on the keyboard (as a lot of error message scrolled)

free space in /boot

esxcfg-boot -b again

reboot ESX

In my case it was ok

[nkrishnan]

It is recommand to /boot 100MB while upgrading and i hope it would appicable for patching also based on the patch bundle size.

Thanks

Nithin

[rico4400]

Nithin you're right

/boot by default is 100 MB

But in this case,a few weeks ago my client did ESX 3.5 to 4.1 migration

This was ok

but  he didn't cleanup (post install cleanup-esx3)

So when he wanted to apply U1 , not enough space

Advice: if somebody upgrade ESX from 3.5, do not forget to clean ESX server

otherwise /boot would be full after applying patch or update

Cheers

[psmeele]

Hello Rico4400,

We solved it by doing a reinstall of the VMware software.

We have 2 partition, 1 with VMware the other one with the virtual servers.

Updating all other server had gave no problem.

Best regards