Start a Conversation

This post is more than 5 years old

Solved!

Go to Solution

2761

February 19th, 2016 11:00

ScaleIO v1.32 + ESX/vCenter v5.5 - Registering Plugin Fail

Hello!!

We are trying to deploy a ScaleIO environment but the plugin registration is not working. Inside PowerCLI the scripts says it worked but loging back on the web client the SIO ScaleIO icon never shows up.

Inside virgo logs I see these mesages:

[2016-02-18 17:12:15.291] [INFO ] vc-service-pool-13       70000059 100003 200001 com.vmware.vise.vim.extension.VcExtensionManager              Downloading plugin package from https://10.62.36.3:65101/resources/plugin (no proxy defined)
[2016-02-18 17:12:15.298] [ERROR] vc-service-pool-13       70000059 100003 200001 com.vmware.vise.vim.extension.VcExtensionManager              Package com.emc.s3g.scaleio.vSpherePlugin was not installed!

Error downloading https://10.62.36.3:65101/resources/plugin. Make sure that the URL is reachable then logout/login to force another download. java.net.ConnectException: Connection refused

    at java.net.PlainSocketImpl.socketConnect(Native Method)

    at java.net.AbstractPlainSocketImpl.doConnect(Unknown Source)

    at java.net.AbstractPlainSocketImpl.connectToAddress(Unknown Source)

    at java.net.AbstractPlainSocketImpl.connect(Unknown Source)

    at java.net.SocksSocketImpl.connect(Unknown Source)

    at java.net.Socket.connect(Unknown Source)

    at sun.security.ssl.SSLSocketImpl.connect(Unknown Source)

    at sun.net.NetworkClient.doConnect(Unknown Source)

    at sun.net.www.http.HttpClient.openServer(Unknown Source)

    at sun.net.www.http.HttpClient.openServer(Unknown Source)

    at sun.net.www.protocol.https.HttpsClient. (Unknown Source)

    at sun.net.www.protocol.https.HttpsClient.New(Unknown Source)

    at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.getNewHttpClient(Unknown Source)

    at sun.net.www.protocol.http.HttpURLConnection.plainConnect(Unknown Source)

    at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(Unknown Source)

    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(Unknown Source)

    at java.net.HttpURLConnection.getResponseCode(Unknown Source)

    at sun.net.www.protocol.https.HttpsURLConnectionImpl.getResponseCode(Unknown Source)

    at com.vmware.vise.util.http.ConnectionManager.connect(ConnectionManager.java:184)

    at com.vmware.vise.util.http.SimpleHttpClient.connect(SimpleHttpClient.java:182)

    at com.vmware.vise.util.http.SimpleHttpClient.executeMethodResponseAsStream(SimpleHttpClient.java:105)

    at com.vmware.vise.vim.extension.VcExtensionManager.writePackageToFile(VcExtensionManager.java:487)

    at com.vmware.vise.vim.extension.VcExtensionManager.downloadPackage(VcExtensionManager.java:434)

    at com.vmware.vise.vim.extension.VcExtensionManager.access$100(VcExtensionManager.java:63)

    at com.vmware.vise.vim.extension.VcExtensionManager$1.call(VcExtensionManager.java:325)

    at com.vmware.vise.vim.extension.VcExtensionManager$1.call(VcExtensionManager.java:322)

    at java.util.concurrent.FutureTask.run(Unknown Source)

    at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)

    at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)

    at java.lang.Thread.run(Unknown Source)

I already tryed to execute this script from 2 different laptops and from a Windows 2012r2 VM inside the ESX environment. The behaviour is always the same. The script says it's ok but the icon never shows up.

I can ping the vCenter. vCenter can ping my laptop. On my laptop (while the script is running) if I browse to https://10.62.36.3:65101/resources/plugin my brower downloads EMC-ScaleIO-vSphere-web-plugin-1.32.1440.3.zip immediately.

There are no firewalls in between vcenter and my laptop. They are on the same VLAN/Network. I tryed restarting vCenter multiple times but it didn't do anything.

The odd thing is that after the script finishes the registration, If I connect to vCenter using vsphere client, on the plugins menu I see the scaleio plugin but with a message saying "No client side download is needed for this plug-in". But on the web client the icon never shows up. And as far as I know we can't go on with the deploy without this icon on web client.

Any ideas why this is not working?

Thanks!

Rafael Bianco

51 Posts

February 22nd, 2016 07:00

Rafael,

The error of

"Error downloading https://10.62.36.3:65101/resources/plugin. Make sure that the URL is reachable then logout/login to force another download. java.net.ConnectException: Connection refused"

indicates an inability to connect from the vCenter VM to 10.62.36.3, on port 65101.

To verify this, log into the vCenter appliance either via SSH or the vSphere console and run the following command:

"curl -k https://10.62.36.3:65101/resources/plugin > tmp.plugin". It should download a .zip of the plugin.

If the vCenter server is running Windows, then browse to the URL https://10.62.36.3:65101/resources/plugin in Internet Explorer. It should download a .zip of the plugin.

This will attempt to pull the plugin file from the Windows host running the install script, as that's exactly what the installation tries to do.  If this test fails, you'll know that the vCenter box can't reach port 65101 and you will need to check firewalls, etc, until it succeeds.

Once this test succeeds, the plugin install should also work.

February 20th, 2016 23:00

Hi,

I see you're using 1.32.1 which is an old version.

In the FnF download page we should have version 1.32.3 / 1.32.4 (latest from 1.32) already uploaded - I recommend using it instead.

Qs:

1. Which PowerCLI version are you using (5.5/5.8/6.0 - 32/64 bit)? Are you running it as administrator?

2. On Which OS is your VC installed?

3. Did the ScaleIO plugin folder downloaded to the VC location (see paths below)?

4. Are there "old" scaleio plugins in the same plugin folder?

I also recommend doing this clean-up procedure before attempting the registration again.

How to clean-up your Env and perform clean install (while using previously defined networks):

  1. IMPORTANT: Unmap and delete any ScaleIO volumes that you have in your system
  2. If needed: Unregister your ScaleIO system (from within the plugin)
  3. If needed: Delete all your ScaleIO SVMs
  4. Close the existing PowerCLI sessions and open a new one (as administrator)
  5. Unregister plugin (using PS1 script)
  6. Stop vSphere web client service (VC Linux: service vsphere-client stop)
  7. Delete the content of the folder (VC 5.5 plugin location): C:\ProgramData\VMware\vSphere Web Client\vc-packages\vsphere-client-serenity
  8. Delete the content of the folder, or folder itself (VC 5.5): "C:\Windows\System32\config\systemprofile\AppData\Roaming\VMware\scaleio"
  9. Clean the Virgo logs folder: C:\ProgramData\VMware\vSphere Web Client\serviceability\logs
  10. Start the vSphere web client service (VC Linux: service vsphere-client start)
  11. Clear your web browser's cache/cookies (or use a different web browser)
  12. Register the plugin via PowerCLI (using the PS1 script) -> remember NOT to press Enter until you perform the log-in into your vSphere web client (that completes the registration)
  13. Once you see the SIO icon in the vSphere web client, you can press Enter in the PowerCLI session (that will stop the embedded tomcat)
  14. If needed: Remove the SDC module params + vib itself from the ESXs by connecting via SSH to each ESX and run these 2 commands:

~ # esxcli system module parameters set -m scini -p ""

~ # esxcli software vib remove -n scaleio-sdc-esx5.5 / 6.0

15.  If needed: Reboot all ESXs that SDC was removed from

**Paths per VC version and OS **

VC 5.5

Windows:

Virgo logs: C:\ProgramData\VMware\vSphere Web Client\serviceability\logs

Plugin logs and other files: C:\Windows\System32\config\systemprofile\AppData\Roaming\VMware\scaleio

Plugin location C:\ProgramData\VMware\vSphere Web Client\vc-packages\vsphere-client-serenity

Linux:

Virgo logs: /var/log/vmware/vsphere-client/

Plugin logs and other files: /opt/.vmware/scaleio

Plugin location /var/lib/vmware/vsphere-client/vc-packages/vsphere-client-serenity/

VC 6.0

Windows:

Virgo logs: C:\ProgramData\VMWare\vCenterServer\logs\vsphere-client\logs

Plugin logs and other files: C:\Users\vspherewebclientsvc\AppData\Roaming\VMware\scaleio

Plugin location C:\ProgramData\VMware\vCenterServer\cfg\vsphere-client\vc-packages\vsphere-client-serenity

Linux:

Virgo logs: /var/log/vmware/vsphere-client/logs

Plugin logs and other files: /etc/vmware/vsphere-client/vc-packages/scaleio

Plugin location: /etc/vmware/vsphere-client/vc-packages/vsphere-client-serenity

6 Posts

February 21st, 2016 17:00

Hello tomer! Thanks for the reply. Here are the answers...

Yes we are not using the latest version. Our environment has 1.32.1 running and we are deploy a lab. So we wanted to make everything as close to production as possible.

1. Which PowerCLI version are you using (5.5/5.8/6.0 - 32/64 bit)? Are you running it as administrator?

We used v6 64bit. And yes, ran it as administrator.

2. On Which OS is your VC installed?

This vCenter is the appliance one, so I think SuSe. It's the one deployed through this OVA: VMware-vCenter-Server-Appliance-5.5.0.20500-2646489_OVF10.ova

3. Did the ScaleIO plugin folder downloaded to the VC location (see paths below)?

Gonna check this first thing monday morning.

4. Are there "old" scaleio plugins in the same plugin folder?

I believe not since this is a green field installation. Everything is brand new. ESXs, vCenter and ScaleIO. I was following the official installation guide so we hang on the plugin registration. Nothing else was done.

I'll try some of those troubleshooting steps.

Thank you so much for your help.

Rafael Bianco

6 Posts

February 24th, 2016 06:00

Hello Ruh!!

Sorry for the delay on the reply. But yes. There was a connectivity issue. And since during the first install I got this error there were probably some garbage inside vCenter blocking the other installations retrys.

In my case (and I kid you not) my windows laptop marked the network I was connected to as public (instead of private) and was blocking the communication (even disabling the Windows Firewall didn't fix it).

What I suggest everybody is connecting through SSH on vCenter and trying to ping the machine you're running the script. That will do the real connectivity test.

CONNECTIVITY (NO FIREWALL/FILTERING AT ALL) BETWEEN VCENTER AND THE MACHINE RUNNING THE SCRIPT SHOULD BE THE WAY TO GO.

After all the connectivity issues were solved I removed all ESXs from vCenter and re-deployed vCenter and executed the script again. It ran smoothly! ScaleIO is now up and running!

Thank you everybody!!

No Events found!

Top