11 Replies Latest reply on Jul 27, 2010 12:43 PM by ctanner

    Data Collection Issue

      Hi,

      I've got profiler up and running and returning information from the VC.

      However on some hosts even though it is returning data  on vm's, in the Status box (top right) I have a question mark and "Data Collection Issue" message.

      Where should i be goingto look for a log of these errors? I can't seem to find anywhere.

       

      Many Thanks

        • Re: Data Collection Issue
          HolyGuacamole

          whats the last collect time for the ESX host with the Data Collection issue? The last collect time is show on the Console page for the ESX Host

            • Re: Data Collection Issue

              Hi,

              I'm seeing different results from different hosts.  In 1 cluster I'm seeing 1 host showing 1.5hr and another in the showing 6.5hrs.  The VC server says 14.8hr.

               

              Thanks

                • Re: Data Collection Issue
                  HolyGuacamole

                  The one showing 6.5 hours perhaps shows a Data Collection issue? The other hosts most likely are showing a normal status I suppose.

                    • Re: Data Collection Issue

                      All hosts are showing data collection issues. All have the ? icon.

                      There does not seem to be away of locating the issue that the host is having.

                        • Re: Data Collection Issue
                          HolyGuacamole

                          Can you click on the traffic light icon for 1 of your ESX hosts, then click on the virtualization module and paste the last few lines from the log?

                            • Re: Data Collection Issue

                              Hi,

                               

                              As requested

                               

                              22 Jul 2010 08:52:00 - VMware_strg_17 : VMClient :  Browser timeout.
                              22 Jul 2010 08:52:01 - VMDataGatherer_Strg(17) : DataStore Name = FC_FO_Prod_CLUSTER01_213(datastore-9186)
                              22 Jul 2010 08:52:01 - VMDataGatherer_Strg(17) :getHostInitiatorAndProtocolForDeviceName: PortWWN = 10:00:00:00:c9:8a:e5:58
                              22 Jul 2010 08:52:01 - VMDataGatherer_Strg(17) : Host Initiator = 10:00:00:00:c9:8a:e5:58 Lun id = 213 Target id = 0  Protocol = FC LUN Vendor = HP       Disk Name = naa.600508b4000ce6120000700003920000 Partition Id = 1
                              22 Jul 2010 08:55:01 - VMware_strg_17 : VMClient :  Browser timeout.
                              22 Jul 2010 08:55:02 - VMDataGatherer_Strg(17) : DataStore Name = FC_FO_Prod_CLUSTER01_214(datastore-9188)
                              22 Jul 2010 08:55:02 - VMDataGatherer_Strg(17) :getHostInitiatorAndProtocolForDeviceName: PortWWN = 10:00:00:00:c9:8a:e5:58
                              22 Jul 2010 08:55:02 - VMDataGatherer_Strg(17) : Host Initiator = 10:00:00:00:c9:8a:e5:58 Lun id = 214 Target id = 0  Protocol = FC LUN Vendor = HP       Disk Name = naa.600508b4000ce6120000700003960000 Partition Id = 1
                              22 Jul 2010 08:55:29 - VMDataGatherer_Strg(17) : DataStore Name = FC_FO_Prod_CLUSTER01_215(datastore-9190)
                              22 Jul 2010 08:55:29 - VMDataGatherer_Strg(17) :getHostInitiatorAndProtocolForDeviceName: PortWWN = 10:00:00:00:c9:8a:e5:58
                              22 Jul 2010 08:55:29 - VMDataGatherer_Strg(17) : Host Initiator = 10:00:00:00:c9:8a:e5:58 Lun id = 215 Target id = 0  Protocol = FC LUN Vendor = HP       Disk Name = naa.600508b4000ce61200007000039a0000 Partition Id = 1
                              22 Jul 2010 08:58:30 - VMware_strg_17 : VMClient :  Browser timeout.
                              22 Jul 2010 08:58:30 - VMDataGatherer_Strg(17) : DataStore Name = FC_FO_Prod_CLUSTER01_216(datastore-9192)
                              22 Jul 2010 08:58:30 - VMDataGatherer_Strg(17) :getHostInitiatorAndProtocolForDeviceName: PortWWN = 10:00:00:00:c9:8a:e5:58
                              22 Jul 2010 08:58:30 - VMDataGatherer_Strg(17) : Host Initiator = 10:00:00:00:c9:8a:e5:58 Lun id = 216 Target id = 0  Protocol = FC LUN Vendor = HP       Disk Name = naa.600508b4000ce61200007000039e0000 Partition Id = 1
                                   
                                • Re: Data Collection Issue
                                  HolyGuacamole

                                  It looks alright from an agent perspective. Can you please open a support ticket here and post the case id ?

                                  http://www.solarwinds.com/support/ticket

                                    • Re: Data Collection Issue

                                      Hi

                                      Case opened:

                                             Case #176086 - "Data collection issue"

                                      Thanks for your help.

                                        • Re: Data Collection Issue
                                          KarimK

                                          Hi,

                                           

                                          I've been having this exact same issue on my system as well.  Even after upgrade to 4.12, spreading ESX hosts across multiple hosts, only trying to monitor a few servers at a time instead of our entire cluster.  Always ends up with "data collection issue" and same timeout messages in the virtualisation log file.

                                          I've had a support ticket open (170020) for over a month but it's still unresolved.  Support are saying the problem is on the VMWare side.

                                          Any one else seen this and been able to resolve it?    I've tried changing the <browseTimeOutInMinutes>XX</browseTimeOutInMinutes> in mod.sys.virtual.Virtual.xml config file on the poller host to a larger value from the default of 3 mins but that just means it timesout after 10 or 15 mins or whatever I set it to.

                                          Any other help or suggestions from anybody?

                                           

                                          Thanks.

                                          Karim

                                            • Re: Data Collection Issue

                                              Hi,

                                              We've been able to move it abit further forward.  It seems that the server (HP g3) I'm hosting it on is having problem writing the data back to disk, seeing very high disk queue on the logical disk (perfmon)

                                              Going to move profiler to a newer server and see whether the problem re-occurs

                                              As a side note I have removed all but 2 clusters from being monitored and am still seeing the issue.

                            • Re: Data Collection Issue
                              ctanner

                              When you are seeing this in the logs: 

                               

                              VMware_strg_xx : VMClient :  Browser timeout.

                              That means that we are attempting to browse the datastore via the VC API and are not getting a response back from the VC. Typically this points to an environmental situation where VC is not able to return the data that we are requesting.