Shazzam probe being stuck

[Paul125]

Hello, we have weekly discovery schedules set up in place and have been working for years. All of sudden these schedules being canceled it self due to time out. after digging further, we found that 'shazzam' probe being sent out but 'processed' state is showing processed but timestamp showing empty and 'updated on' showing discovery end time like below. Has anyone experienced before? Thanks

[Branden]

IF only this were the case.  It should yes.  But once things get stuck, the automated mechanisms tend to give up the ghost in terms of clearing things out.  I've done this as late as Jakarta (although haven't had to do it to K yet!) 

[tim_broberg]

Hmm... once what kind of things get stuck?

There have definitely been problems like PRB750509 where temporary network issues resulted in permanent mid server fibrillation.

We've been actively hunting those down and killing them.

What symptoms are you seeing?

    - Tim.

[DaveHertel]

If nothing has changed recently on your instance, it may be worth a chat with your network engineers to inquire about any recent changes on network. Sounds kinda suspicious that perhaps some other unintended change - outside of the SN platform maybe impacting Shazzam scanning... ? Food for thought..Dave

[Paul125]

Thanks for the reply Dave. I haven't restarted MIDs yet I have to do that first then will move ahead with further exercises. 

[Paul125]

Dave, this issue has been resolved after restarting MIDs from the host. How can we prevent this happening from next time. Thanks.