25 Posts

August 22nd, 2016 15:00

I got through the upgrade to 2.0 and at the end enabled Secure Communication as instructed in the Deployment Guide.  This problem went away as soon as all the certs were trusted.  It appears launching the ScaleIO gateway from the vsphere plugin doesn't work correctly until the certs are approved and the system put into secure mode.

25 Posts

August 15th, 2016 13:00

Found this on the gateway in catalina.out as well.

SLF4J: Failed toString() invocation on an object of type [com.emc.s3g.scaleio.domain.installation.configuration.Configuration]

java.lang.NullPointerException

        at com.emc.s3g.scaleio.domain.installation.configuration.Configuration.toString(Configuration.java:321)

        at org.slf4j.helpers.MessageFormatter.safeObjectAppend(MessageFormatter.java:304)

        at org.slf4j.helpers.MessageFormatter.deeplyAppendParameter(MessageFormatter.java:276)

        at org.slf4j.helpers.MessageFormatter.arrayFormat(MessageFormatter.java:230)

        at ch.qos.logback.classic.spi.LoggingEvent. (LoggingEvent.java:115)

        at ch.qos.logback.classic.Logger.buildLoggingEventAndAppend(Logger.java:439)

        at ch.qos.logback.classic.Logger.filterAndLog_2(Logger.java:432)

        at ch.qos.logback.classic.Logger.debug(Logger.java:510)

        at com.emc.s3g.scaleio.im.services.installation.configurators.CommandServiceMdmConnection.getConfiguration(CommandServiceMdmConnection.java:2603)

        at com.emc.s3g.scaleio.domain.installation.commands.ConfigurationQueryCommand.executeMdmCommand(ConfigurationQueryCommand.java:59)

        at com.emc.s3g.scaleio.domain.installation.commands.ConfigurationQueryCommand.executeMdmCommand(ConfigurationQueryCommand.java:34)

        at com.emc.s3g.scaleio.domain.installation.commands.MdmCommand.executeCommand(MdmCommand.java:91)

        at com.emc.s3g.scaleio.domain.installation.commands.BaseCommand.call(BaseCommand.java:323)

        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)

25 Posts

August 15th, 2016 14:00

After looking at this problem for a while and the errors posted above, and considering what I am trying to accomplish, I think this is related to the fact I never deployed Scaleio through the Vsphere plugin.  I installed manually and added it to vsphere later.  When I click launch ScaleIO gateway it spins on trying to update SDC information from ScaleIO Gateway and then bombs with the 1009 error in the web gui with the exceptions caught above in the catalina.out logs on the gateway and virgo logs of the web client.  I want to use the gateway to perform the upgrade to 2.0.0.1 but I will need to get past this.

25 Posts

August 15th, 2016 15:00

It appears the Open ScaleIO Gateway link in the vsphere web client is affected by this file.  I had an old copy of the folder when I originally tried to deploy with the wizard and when I tossed it in my new folder, I started getting authentication errors. 

C:\Windows\System32\config\systemprofile\AppData\Roaming\VMware\scaleio\serverConfig.cfg


My guess is that when I add an existing ScaleIO system this file or some other configuration location should be updated with my current configuration and it is not.  This is preventing the Open ScaleIO Gateway link from working due to the missing data. 

No Events found!

Top