VMware Cloud Community
Theovd
Enthusiast
Enthusiast
Jump to solution

vmkping give 'syscall version mismatch' after upgrading to ESX 3.0.2 update 1

Hi all,

I upgraded our ESX servers from 3.0.2 to 3.0.2 update 1. After this I get an error when using vmkping:

  1. vmkping 172.16.2.102
syscall version mismatch (compiled: 0x7616c4e3, kernel: 0x50f63116)

Has anyone an idea what is going wrong and how to solve it?

Regards,

Theo.

Reply
0 Kudos
1 Solution

Accepted Solutions
fatih
Enthusiast
Enthusiast
Jump to solution

Yes...if we all just read the release notes then we would not have to ask these questions...;-)

Regards

View solution in original post

Reply
0 Kudos
6 Replies
BUGCHK
Commander
Commander
Jump to solution

I have just finished a fresh installation of 3.0.2u1 and see this too.

Reply
0 Kudos
davesherman
Enthusiast
Enthusiast
Jump to solution

I am also seeing this on several boxes, fresh install and upgrades.

Reply
0 Kudos
fatih
Enthusiast
Enthusiast
Jump to solution

I have also upgraded and have done fresh installations with the same error but Vmotion seems to work perfect and even faster !

I was able to get an correct answer from servers not yet upgraded when I used vmkping from an upgraded server...

Maybe the problem is only with the command utility "vmkping" itself ?

Regards

Reply
0 Kudos
fatih
Enthusiast
Enthusiast
Jump to solution

Yes...if we all just read the release notes then we would not have to ask these questions...;-)

Regards

Reply
0 Kudos
davidbarclay
Virtuoso
Virtuoso
Jump to solution

...still....it's pretty average..I saw the same thing today.

without care they will end up with the.."wait for SP1 release" mantra that MS customers have

Remember 2.5.4 Update 4?

Ouch?!

Dave

Reply
0 Kudos
mghelech
Contributor
Contributor
Jump to solution

Has nothing to do with the patch. Make sure you are using "sudo" or "su" credentials. I recieved the same error in 4.0.1 and after login as "su" it worked fine.

Reply
0 Kudos