dfollis
1 Copper

VSM 4.6 vCenter 6 VCSA SOAPFaultException

Attempting to install Dell VSM-4.6.0-20160707.122300-139 virtual appliance to vCenter v6u2 (3634794). The OVA installs without error and the VSM appears in the vCenter Web Client, but attempting to access presents a "SOAPFaultException".  I am also able to register it as a VASA storage provider without error. The error appears in the ASMVE.log, Console.log, and Server.log files when exported from the VSM VM.

Log example:

2016-09-15 12:10:39,156 ERROR [org.jboss.ejb3.invocation] (http-0.0.0.0-0.0.0.0-443-1) JBAS014134: EJB Invocation failed on component VSMApplianceImpl for method public abstract com.equallogic.hitve.shared.rest.v4_0.data.VSMSummary com.equallogic.hitve.shared.rest.v4_0.api.VSMApplianceApi.getSummary(): com.equallogic.hitve.shared.exceptions.VSMException: javax.xml.ws.soap.SOAPFaultException: A general system error occurred:
at com.equallogic.hitve.server.rmi.HostHandler.getHbaIpAddresses(HostHandler.java:2674) [eqlvmsnap-api-2.0.jar:"4.6.0.1242"]
at com.equallogic.hitve.server.rmi.HostHandler.populateHBAsInfo(HostHandler.java:653) [eqlvmsnap-api-2.0.jar:"4.6.0.1242"]
at com.equallogic.hitve.server.rmi.HostHandler.access$400(HostHandler.java:142) [eqlvmsnap-api-2.0.jar:"4.6.0.1242"]
at com.equallogic.hitve.server.rmi.HostHandler$HostListener.generateManagedObjectFromProps(HostHandler.java:264) [eqlvmsnap-api-2.0.jar:"4.6.0.1242"]
at com.equallogic.hitve.server.rmi.HostHandler$HostListener.retrieveObject(HostHandler.java:356) [eqlvmsnap-api-2.0.jar:"4.6.0.1242"]
at com.equallogic.hitve.server.rmi.HostHandler.retrieveHost(HostHandler.java:757) [eqlvmsnap-api-2.0.jar:"4.6.0.1242"]
at com.equallogic.hitve.server.rmi.DatastoreHandler.getHostsForDatastore(DatastoreHandler.java:5948) [eqlvmsnap-api-2.0.jar:"4.6.0.1242"]
at com.equallogic.hitve.server.rmi.HostHandler.findIqn(HostHandler.java:506) [eqlvmsnap-api-2.0.jar:"4.6.0.1242"]
at com.equallogic.hitve.server.rmi.DatastoreHandler$DatastoreListener.generateManagedObjectFromProps(DatastoreHandler.java:482)

Tags (3)
0 Kudos
10 Replies
DELL-Donald Wi
5 Rhenium

RE: VSM 4.6 vCenter 6 VCSA SOAPFaultException

Hello, 

 These sorts of issues are difficult to triage in a forum setting.  

 One suggestion:   In vCenter you have to configure the Managed IP address of the vCenter Server.  It's under the vCenter Sever settings->Runtime Settings and the vCenter Server Name should be resolvable. 

 If you haven't already opened a Support case I would suggest you do. 

 Regards, 

Don 

Social Media and Community Professional
#IWork4Dell
Get Support on Twitter - @dellcarespro

0 Kudos
dfollis
1 Copper

RE: VSM 4.6 vCenter 6 VCSA SOAPFaultException

Thanks for the hint.  I confirmed that the Runtime IP Settings were set before install.  I just unregistered vsm as the VASA provider, deleted the VSM appliance, and rebooted VCSA.  That worked without fail.  I then tried to reinstall, the appliance, re-register the VASA storage provider and no errors.  But the minute I access the VSM from the Web GUI I get the SOAPFaultException error.  I'm stumped.

VMWare spent two hours on the phone with me today.  Services appear t be working ok and they cannot see any obvious error logs.

I have a case open: 

Case ID:

936231805

Request date:

9/15/2016

This looks to me like some sort of UI coding bug.

0 Kudos
Highlighted
DELL-Donald Wi
5 Rhenium

RE: VSM 4.6 vCenter 6 VCSA SOAPFaultException

Thanks for the update. 

Did you happen to modify the default EQL array banner?   If so, please delete it all and try again..  

The only time I've seen a SOAP error was actually coming FROM vCenter and passed back to VSM.  Not saying that's it here, as the messages aren't exact match, 

 Are you using a non English language configuration? 

 Regards,

don 

 

Social Media and Community Professional
#IWork4Dell
Get Support on Twitter - @dellcarespro

0 Kudos
dfollis
1 Copper

RE: VSM 4.6 vCenter 6 VCSA SOAPFaultException

So odd.  I just noticed that if I register my PS6100E, that does work.  I still get the SOAP error occasionally, but I can use VSM to view the array and datastores.  I have not tried to use it to create a datastore yet.

0 Kudos
dfollis
1 Copper

RE: VSM 4.6 vCenter 6 VCSA SOAPFaultException

No I'm using the standard firmware.  All US English.  Also this error appears before the EQL is registered so this is something between VSM and vCenter.

0 Kudos
DELL-Donald Wi
5 Rhenium

RE: VSM 4.6 vCenter 6 VCSA SOAPFaultException

Hello, 

 Any update since you added in the group?   Can you create Datastores, snapshots, etc? 

 re: SOAP error.  I understand that it occurred before you added the group.  Only the VCS and VSM communicate.  VCS doesn't ever connect to the group, only VSM does that.  So VCS returning an error to VSM would still be valid without having a group added yet. 

 Regards,

Don 

Social Media and Community Professional
#IWork4Dell
Get Support on Twitter - @dellcarespro

0 Kudos
stein_ivar87
1 Copper

RE: VSM 4.6 vCenter 6 VCSA SOAPFaultException

I have the exact same problem. I'm running VCSA 6 and VSM 4.6.0. Whenever I try to retrieve any informasjon from VSM I get "An unexpected error occurred: SOAPFaultException". I get the following in console.log:

2016-10-20 14:18:21,057 ERROR [org.jboss.ejb3.invocation] (http-0.0.0.0-0.0.0.0-443-2) JBAS014134: E...

See the pastebin for full stack.

This happed before and after I added the group, I can see informasion about my group, but I cannot create datastores, which fails with the same SOAPFaultException error.

0 Kudos
DELL-Donald Wi
5 Rhenium

RE: VSM 4.6 vCenter 6 VCSA SOAPFaultException

Hello, 

 I would suggest you open a support case for this issue. 

 Regards,

Don 

Social Media and Community Professional
#IWork4Dell
Get Support on Twitter - @dellcarespro

0 Kudos
stein_ivar87
1 Copper

RE: VSM 4.6 vCenter 6 VCSA SOAPFaultException

Hello, 

 I would suggest you open a support case for this issue. 

 Regards,

Don 

I have resolved my issue. 

Looking at the stacktrace I saw:
at com.equallogic.hitve.server.rmi.HostHandler.getHbaIpAddresses(HostHandler.java:2674) [eqlvmsnap-api-2.0.jar:"4.6.0.1242"]

It turns out that my hosts iSCSI software adapter had a phantom vmkernel adapter and was failing. I disabled the adapter and removed everything under /etc/vmware/vmkiscsid on that host and restarted it. Now VMS is working perfectly.