5 Replies Latest reply on May 4, 2011 5:01 AM by NuggetGTR

    Capacity IQ vcenter sessions

    NuggetGTR Expert
    VMware EmployeesvExpert

      Hi,

       

      Its not so much of a problem its just an annoyance, since upgrading to Capacity IQ 1.5.1 it seams to constantly reconnect to vCenter but leave its old connections idle. currently there is 153 idle sessions from the service account capacity iq uses and 28 active sessions. Capacity IQ is the only machine using the particular account.

       

      anyone come accross this?

       

      Ive restarted both the vCenter server and the capacity IQ appliance but still happens.

       

      Cheers

        • 1. Re: Capacity IQ vcenter sessions
          Hot Shot

          Please generate the diagnostics bundle and attach it. I will take a look at it.

          • 2. Re: Capacity IQ vcenter sessions
            NuggetGTR Expert
            VMware EmployeesvExpert

            Unfortunatly im on a secure site so cant go uploading logs with names etc.

            But after having a look, I am getting the same errors on the affrected capiq box as this KB http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1033508

             

             

             

            [Thread-33] INFO  com.vmware.cm.connection.manager.impl.AbstractRootConnectionManagerImpl  2011-04-18 08:11:48,552+1000 - Root connection repair in progress ...
            [Thread-25] INFO  com.vmware.cm.inv.manager.impl.InventoryUpdateManagerImpl  2011-04-18 08:11:50,696+1000 - Time to pre-compute properties = 3.496 seconds
            [Thread-25] INFO  com.vmware.cm.inv.manager.impl.InventoryConstructionAgentImpl  2011-04-18 08:11:51,147+1000 - Time to persist pre-computed properties = 0.426 seconds
            [Thread-25] INFO  com.vmware.cm.inv.manager.impl.InventoryConstructionAgentImpl  2011-04-18 08:11:51,182+1000 - Time to apply updates = 0.035 seconds
            [Thread-33] INFO  com.vmware.cm.connection.manager.impl.SmsRootConnectionManagerImpl  2011-04-18 08:11:52,334+1000 - Created a root SMS service connection with SMS <https://vcenter/sdk>
            [Thread-33] INFO  com.vmware.cm.connection.manager.impl.AbstractRootConnectionManagerImpl  2011-04-18 08:11:52,358+1000 - Root connection restored!
            [Thread-33] INFO  com.vmware.cm.connection.manager.impl.AbstractRootConnectionManagerImpl  2011-04-18 08:11:53,363+1000 - Initiating health check for root connection. Reported exception:
            com.vmware.cm.connection.model.exception.ServiceConnectionException: 
            at com.vmware.cm.perf.manager.impl.SmsPerformanceCollector.collect(SmsPerformanceCollector.java:412)
            at com.vmware.cm.perf.manager.impl.AbstractPerformanceCollector.run(AbstractPerformanceCollector.java:72)
            at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
            at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
            at java.lang.Thread.run(Thread.java:619)
            Caused by: ServiceNotInitialized
            at sun.reflect.GeneratedConstructorAccessor153.newInstance(Unknown Source)
            at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
            at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
            at java.lang.Class.newInstance0(Class.java:355)
            at java.lang.Class.newInstance(Class.java:308)
            at org.apache.axis.encoding.ser.BeanDeserializer.<init>(BeanDeserializer.java:104)
            at org.apache.axis.encoding.ser.BeanDeserializer.<init>(BeanDeserializer.java:90)
            at com.vmware.vim.sms.ServiceNotInitialized.getDeserializer(ServiceNotInitialized.java:83)
            at sun.reflect.GeneratedMethodAccessor465.invoke(Unknown Source)
            at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
            at java.lang.reflect.Method.invoke(Method.java:597)
            at org.apache.axis.encoding.ser.BaseDeserializerFactory.getSpecialized(BaseDeserializerFactory.java:154)
            at org.apache.axis.encoding.ser.BaseDeserializerFactory.getDeserializerAs(BaseDeserializerFactory.java:84)
            at org.apache.axis.encoding.DeserializationContext.getDeserializer(DeserializationContext.java:464)
            at org.apache.axis.encoding.DeserializationContext.getDeserializerForType(DeserializationContext.java:547)
            at org.apache.axis.message.SOAPFaultDetailsBuilder.onStartChild(SOAPFaultDetailsBuilder.java:157)
            at org.apache.axis.encoding.DeserializationContext.startElement(DeserializationContext.java:1035)
            at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source)
            at org.apache.xerces.parsers.AbstractXMLDocumentParser.emptyElement(Unknown Source)
            at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source)
            at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
            at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
            at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
            at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
            at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
            at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
            at javax.xml.parsers.SAXParser.parse(SAXParser.java:395)
            at org.apache.axis.encoding.DeserializationContext.parse(DeserializationContext.java:227)
            at org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:696)
            at org.apache.axis.Message.getSOAPEnvelope(Message.java:435)
            at org.apache.axis.handlers.soap.MustUnderstandChecker.invoke(MustUnderstandChecker.java:62)
            at org.apache.axis.client.AxisClient.invoke(AxisClient.java:206)
            at org.apache.axis.client.Call.invokeEngine(Call.java:2784)
            at org.apache.axis.client.Call.invoke(Call.java:2767)
            at org.apache.axis.client.Call.invoke(Call.java:2443)
            at org.apache.axis.client.Call.invoke(Call.java:2366)
            at org.apache.axis.client.Call.invoke(Call.java:1812)
            at com.vmware.vim.sms.SmBindingStub.queryList(SmBindingStub.java:1652)
            at com.vmware.cm.perf.manager.impl.SmsPerformanceCollector.collect(SmsPerformanceCollector.java:348)
            ... 4 more
             
            
            
            

             

            I dont get the 501 when browsing the the SDK URL and other webservices are working fine.

             

            So looks like it is just looping and every time making another connection to vcenter, only did this since the upgrade i believe.

             

            Would unregistering it and re registering to the vcenter be worth a try? by doing so will all the data collected be lost?

            • 3. Re: Capacity IQ vcenter sessions
              NuggetGTR Expert
              vExpertVMware Employees

              Ok,

               

              Looked to have solved the huge amount of connections to my vcenter server. but im still getting the issue mentioned previously http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1033508

               

              Looking at the ciq log if I stop and start the capiq service its fine for maybe 5 - 10 minutes then its starts this root connection repair. the sdk URL is up and working as we have some custom apps which rely on it.

               

              This is running Capiq 1.5.1 and vCenter 4.0

               

              I have 4 other vcenter servers with 4 other capiq appliances all running fine, This particular one is the only one having issues.

               

              Any ideas would be much appreciated, just glad I don't have 150 capiq sessions anymore

              • 4. Re: Capacity IQ vcenter sessions
                sanlau Enthusiast
                VMware Employees

                Please check if the Storage Management Service in vCenter has been initialized (check if you can see Storage Tab). If not, please see if it is the known issue mentioned in the KB article below:

                 

                http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1013462

                 

                Thanks,

                San

                1 person found this helpful
                • 5. Re: Capacity IQ vcenter sessions
                  NuggetGTR Expert
                  vExpertVMware Employees

                  There is definatly an issue with my storage management service, never really realised, thanks for the pickup. ive gone through most of the KBs on the storage management service issues but havent found a solution yet, Just about to upgrade to 4.1 so I might leave it untill then and hope it fixes the problem, but if I get time ill continue trouble shooting as I want to know why its not working correctly.

                   

                  Cheers