ylafont22
Enthusiast
Enthusiast

A general system error occurred: Timed out waiting for vpxa to start

This is my first installation of a VM-Ware environment and I am hoping someone can point me in the right direction.  

Installed  esxi Host 6.5

installed  esxi  6.5 vcenter server Appliance   (although installation was not smooth (stuck at 80% and other - however manage to get it installed.))

installed Vphere web Client 6.5

I am know stuck at adding a host to VSHERE web client.

Created DataCenter

Added host

enter root user and password

repacel the SHA1 Key

List VM-Machines in Host

assign license

disable lock-down mode

select folder

finish

and all i get is  "A general system error occurred: Timed out waiting for vpxa to start"

I have preformed the following

service mgmt-vmware restart

service vmware-vpxa restart

AND

followed this thread

Adding host to cluster: "Timed waiting for vpxa to start"   where the time is changed.

these are the last few lines of the wmkernal.log file

2018-08-05T01:31:21.740Z cpu29:2097256)ScsiDeviceIO: 3015: Cmd(0x459a4b3ecec0) 0x85, CmdSN 0x182 from world 2100057 to dev "mpx.vmhba32:C0:T0:L0" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0.

2018-08-05T11:31:26.620Z cpu50:2097277)ScsiDeviceIO: 3015: Cmd(0x459a4c4d6500) 0x85, CmdSN 0x2fe from world 2100057 to dev "mpx.vmhba32:C0:T0:L0" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0.

2018-08-05T15:54:02.729Z cpu37:2098121)vmw_ahci[0000001f]: HBAIntrHandler:new interrupts coming, PxIS = 0x8, no repeat

2018-08-05T17:55:01.523Z cpu52:2098121)Tcpip_Flow: 127: Failed to pin vmk0 rxDisp 0 to world 2113082 (worker): Not initialized

2018-08-05T21:08:42.857Z cpu11:2099523 opID=2acdffb1)World: 11942: VC opID b56322a3 maps to vmkernel opID 2acdffb1

2018-08-05T21:08:42.857Z cpu11:2099523 opID=2acdffb1)NVDManagement: 1478: No nvdimms found on the system

2018-08-05T21:10:39.811Z cpu23:2131048)Config: 703: "SIOControlFlag2" = 0, Old Value: 0, (Status: 0x0)

2018-08-05T21:10:39.825Z cpu23:2131048)WARNING: VisorFS: 1093: Attempt to setattr non sticky dir/file from tar mount

2018-08-05T21:10:45.026Z cpu8:2131048)Config: 703: "VMOverheadGrowthLimit" = 4294967295, Old Value: 4294967295, (Status: 0x0)

2018-08-05T21:31:34.116Z cpu36:2097263)ScsiDeviceIO: 3015: Cmd(0x459a4c543100) 0x85, CmdSN 0x47a from world 2100057 to dev "mpx.vmhba32:C0:T0:L0" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0.

2018-08-06T07:31:38.817Z cpu29:2097256)ScsiDeviceIO: 3015: Cmd(0x459a4b536980) 0x85, CmdSN 0x5f6 from world 2100057 to dev "mpx.vmhba32:C0:T0:L0" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0.

these are the last few lines of the vpza.log

2018-08-06T12:29:39.133Z warning vpxa[2164447] [Originator@6876 sub=SoapAdapter] Unsupported version URI "urn:vpxa3/6.5"

2018-08-06T12:29:39.133Z error vpxa[2164447] [Originator@6876 sub=SoapAdapter] Unsupported version URI "urn:vpxa3/6.5"

-->

--> while parsing SOAP body

--> at line 9, column 0

-->

--> while parsing SOAP envelope

--> at line 2, column 0

-->

--> while parsing HTTP request before method was determined

--> at line 1, column 0

2018-08-06T12:29:40.475Z warning vpxa[2164433] [Originator@6876 sub=SoapAdapter] Unsupported version URI "urn:vpxa3/6.5"

2018-08-06T12:29:40.475Z error vpxa[2164433] [Originator@6876 sub=SoapAdapter] Unsupported version URI "urn:vpxa3/6.5"

-->

--> while parsing SOAP body

--> at line 9, column 0

-->

--> while parsing SOAP envelope

--> at line 2, column 0

-->

--> while parsing HTTP request before method was determined

if any one can point me in the right direction, i  would greatly appreciate it.  thank you in advance.

Tags (1)
7 Replies
iopsGent
Enthusiast
Enthusiast

What 6.5 build version of vCentre and ESXi are you using?

Please consider marking this answer as "correct" or "helpful" if you think your questions have been answered.
0 Kudos
Lalegre
Virtuoso
Virtuoso

That error is common when the version of your ESXi is higher than your vCenter.

Correlate the build from your vCenter and your ESXi using the next KB: VMware Knowledge Base

If you see that your ESXi is in a higher version than your vCenter then there is your issue

ylafont22
Enthusiast
Enthusiast

OMG - i would have never even gone there

Esxi Host = 6.7.0 (Build 8169922)

Vmware vsphere client  6.5.0 (build 7312210)

where the build numbers i was using, i downgraded the host  and worked like a charm. 

Thank you for the assistance! greatly appreciated.

iopsGent
Enthusiast
Enthusiast

Glad you got it working!

Please consider marking this answer as "correct" or "helpful" if you think your questions have been answered.
0 Kudos
CIjalba
Contributor
Contributor

An it's still very valid as of 2020! you just sorted my problem out, Thanx!

0 Kudos
CIjalba
Contributor
Contributor

This question should be marked as Answered.

0 Kudos
vigo332
Contributor
Contributor

I think this is inconvenience for users, why they have to break, and not been fixed. 

Both my ESXi host and vCetner are upgraded to their latest version as of now, respectively. 

ESXi 7.0.3a build number 18825058, 

vCenter 7.0.3 build number 18778458,

now they don't work together!

 

0 Kudos