Solved!
Go to Solutioninstall scaleio 1.32 vsphere plugin
hi
i try to install the scaleio vsphere plugin on my windows 2008 r3 vcenter 6
while the powershell script runs without error the scaleio plugin is not installed in the web-client. the only error i was able to find is in the following log:
C:\EMC-ScaleIO\gatewayServer\logs\scaleio.log
2015-06-07 21:37:38,365 [localhost-startStop-1] INFO o.s.web.servlet.DispatcherServlet - FrameworkServlet 'scaleio': initialization completed in 865 ms
2015-06-07 21:37:44,054 [http-nio-65101-exec-4] INFO c.e.s.s.w.controller.UtilController - Downloading the Plugin file 'EMC-ScaleIO-vSphere-web-plugin-1.32.402.1.zip' from 'C:\EMC-ScaleIO\gatewayServer\webapps\ROOT\resources'
2015-06-07 21:37:45,751 [http-nio-65101-exec-4] WARN c.e.s.s.w.controller.UtilController - Failed providing Plugin file for download
2015-06-07 21:37:45,830 [http-nio-65101-exec-4] ERROR c.e.s.s.w.controller.UtilController - Got an exception in handleException
com.emc.s3g.scaleio.services.ScaleIOFileDownloadException: org.apache.catalina.connector.ClientAbortException: java.io.IOException: An existing connection was forcibly closed by the remote host
at com.emc.s3g.scaleio.web.controller.UtilController.handleFileDownload(UtilController.java:59) ~[UtilController.class:na]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[na:1.8.0_45]
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) ~[na:1.8.0_45]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) ~[na:1.8.0_45]
at java.lang.reflect.Method.invoke(Unknown Source) ~[na:1.8.0_45]
at org.springframework.web.method.support.InvocableHandlerMethod.invoke(InvocableHandlerMethod.java:215) ~[spring-web-3.2.9.RELEASE.jar:3.2.9.RELEASE]
at org.springframework.web.method.support.InvocableHandlerMethod.invokeForRequest(InvocableHandlerMethod.java:132) ~[spring-web-3.2.9.RELEASE.jar:3.2.9.RELEASE]
at org.springframework.web.servlet.mvc.method.annotation.ServletInvocableHandlerMethod.invokeAndHandle(ServletInvocableHandlerMethod.java:104) ~[spring-webmvc-3.2.9.RELEASE.jar:3.2.9.RELEASE]
When i check the path: C:\EMC-ScaleIO\gatewayServer\webapps\ROOT\resources
The requested file is there.
How can i check if the gateway is running?
Might there be a port conflict with some other application?
regards
Andi
When running the plugin script are you using the standard or advanced option? Normally in a VMware only environment the gateway is deployed on vcenter during the SIO deployment.
A couple things to check:
Check the virgo log on your vcenter sever. This is where you find errors related to the plugin install.
Make sure the vsphere account you are using has administrative privileges.
Test connection via VMware powercli Connect-VIServer -Server
BJH
ok now i start to understand, the "gatewayServer" the script installs is only temporary until "enter" is pressed. that's why i never saw a listener on 65101.
what i did now is i selected advance instead of standard used the administrator@vsphere.local user enterd all the information and did NOT press enter untill i logged back into vsphere-web-client. And voila the plug-in shows up-
Many thanks for the help!
So can the plug-in install directory including the during execution of the .ps1 created "gatewayServer" folder be safely deletet?
i did run the script for the first time with an vcenter admin account and not with SSO admin priviledges.
later on i tried to deregister and register with administrator@vsphere.local, also without success.
i use standard for the deployment method. as described in the 1.32 esx install notes
powercli Connect-VIServer works
in vsphere-client-virgo.log i see:
[2015-06-03T22:41:41.328+02:00] [INFO ] vc-extensionmanager-pool-469 70000295 100010 200004 com.vmware.vise.vim.extension.VcExtensionManager Downloading plugin package from https://87.237.169.105:65101/resources/plugin (no proxy defined) [2015-06-03T22:41:41.403+02:00] [INFO ] cm-catalog-manager-pool-467 70000295 100010 200004 com.vmware.vise.vim.cm.CmCatalogManager Detected service providers (ms):126 [2015-06-03T22:41:41.403+02:00] [INFO ] cm-catalog-manager-pool-467 70000295 100010 200004 com.vmware.vise.vim.cm.CmCatalogManager No new locales or service infos to download. [2015-06-03T22:41:42.337+02:00] [ERROR] vc-extensionmanager-pool-469 70000295 100010 200004 com.vmware.vise.vim.extension.VcExtensionManager Package com.emc.s3g.scaleio.vSpherePlugin was not installed! Error downloading https://87.237.169.105:65101/resources/plugin. Make sure that the URL is reachable then logout/login to force another download. java.net.ConnectException: Connection refused: connect
so who should listen at port 65101?
i see that in vcenter there is a service "com.emc.s3g.scaleio.vSpherePlugin.label (vcenter.fqdn)"
what else could i check?
I'm seeing the same problem on my vSphere 6.0 setup. I'm running the powershell script on windows 2012 R2. I can see the gateway server via https://192.168.1.197:65101.
The plugin is registered in the extension manager (mob)
extensionList["com.emc.s3g.scaleio.vSpherePlugin"] Extension but its not showing up when i login to the vSphere Web Client. I do have the powershell script running:
Successfully connected to vCenter vc-01.brsvlab.local
Registering ScaleIO extension...
Log out, and then log back in to vSphere web client. The plugin is downloaded up
on login to the vSphere web client. After you have logged back in, press ENTER.
Yes.
i tried different browsers such as IE & Firefox, cleared the cache on chrome.
Eventually i rebooted my vSphere 6 Server Appliance and after i logged back into vSphere Web Client the ScaleIO plugin was there.
Was it because i'm using the vSphere Server appliance i needed the reboot?
Carl-Adam_Lilje
32 Posts
468
0
Posted June 9th, 2015 08:00
Did you perhaps have the "old" vSphere client running as well?
I have hit that in other plug-in installs where just logging out of the vSphere Web Client wasn't enough, the plug-in didn't show up until you killed both
alexkh
60 Posts
1710
0
Posted June 8th, 2015 05:00
I guess, 87.237.169.105 is the host, you're running the script from?
When you run the script, it starts a web server, which is listening on port 65101.
Make sure, you do not press enter (which will stop the servers) till you logout and login to the vSphere client.