The CreatorCon Call for Content is officially open! Get started here.

discovery is stuck

sahityamalipedd
Kilo Contributor

i am trying to do quick discovery but it is not finishing. it is stuck at shazzam launch not moving any further . the ecc queue shazzam- output is in ready state only. the state of discovery status   is active only it is not being canceled or completed . yesterday it was running properly but today it is stuck. i dont know what is the cause for it.

please help me fix issue.1.pngScreenshot from 2016-10-19 14_17_41.png

10 REPLIES 10

That'll do it!  



Don't forget to check that your MID servers have upgraded post-instance upgrade.



Give the MIDs about 10 mins to do this post-instance upgrade.



On the Instance:



1) System Diagnostics > Stats > Stats


2) On the 10th (or thereabouts) line of the output you will see "MID buildstamp" - which will look something like:



MID buildstamp: geneva-08-25-2015__patch8-07-27-2016_08-16-2016_1231



This shows the MID server version that the Instance is expecting to be installed on its MID servers.



3) MID Server > Servers


* You can personalise the List view and add "Version" - or click into each MID server record for the "Version" (*may be necessary to add this on the form if not displayed).



4) Check that the version matches from that in the MID buildstamp of the instance.



MID buildstamp reported version: geneva-08-25-2015__patch8-07-27-2016_08-16-2016_1231



MID server reported version (*may be truncated): geneva-08-25-2015__patch8-07-27-2016_08-



If the output of the MID server matches (even if the last but is truncated) - the MIDs are on the correct version.



If they do not match, then it will be necessary to troubleshoot why the MIDs did not upgrade.



If raising an incident for Technical Support to assist with this, please ensure that you provide the logs:



<path_to_midserver>\agent\logs\wrapper.log


<path_to_midserver>\agent\logs\agent0.log.0



Zip these up and attach to the incident, as they will be required for troubleshooting purposes.





my instance and mid server was upgraded successfully but still it shazzam is stuck


Hi,



Kindly check the MID Server status in the Instance and the version of the MID Server should match the build stamp in the Stats.



Kindly restart the MID Server service and try again. If your instance is upgraded recently kindly go through the upgrade history and check the upgrade details associated with CMDB & Discovery. You have to review your customization made for discovery.



Kindly revert in case of more info is needed.



Kindly mark this as answered or helpful if you feel your query is fullfilled.



Regards,


Sundaresan M


my instance is upgraded successfully and mid server is also upgraded both are in same version. if i try to discover with down mid server also same thing is happening. so i am unable to find from where the issue is occurring.   Antony.Alldisdoug.schulze


I previously provided links to the videos to assist you with troubleshooting:



Troubleshooting a Failed Discovery Part 1 of 5: Introduction - YouTube


Troubleshooting a Failed Discovery Part 2 of 5: Scanning Phase - YouTube


Troubleshooting a Failed Discovery Part 3 of 5: Classification Phase - YouTube


Troubleshooting a Failed Discovery Part 4 of 5: Identification Phase - YouTube


Troubleshooting a Failed Discovery Part 5 of 5: Exploration Phase - YouTube



And asked you to review the 1st and 2nd videos in the links above specifically.



Can you please inform me of what troubleshooting you have undertaken given the guidance from these videos, and what the results were?