Expert
Product ManagerKelemvor​ did you ever get this resolved?
Mike_Moniz​ 's post is accurate. We do cycle the collector credential every 24 hours, but it should be quick.
Have you installed or updated any new LogicModules?
Have you checked the Health Check output on your collectors?
Have you taken a look at the Collector DataSources to see if anything is overloaded? If support was alleging that, I assume they would have pointed to some indicator. It is true that an overloaded collector can cause long restart intervals, but it should be confirmable by looking at the above.
ExpertWe have not gotten this figured out. It all started on May 1. We were wondering if LM rolled out any changes on that day since we started getting flooded by possibly every collector we have. We have an open ticket with Support but don't know what to do to figure out the problem. The one collector had a higher BatchScript count, but it even happens on collectors that don't use any scripts at all. We're at a loss to explain it so far.
Product ManagerMy deployment calendar doesn't show any deployments on May 1. So unless the change coincided with a portal upgrade, that's likely not it.
Any chance you updated modules and pulled in one that's running long or something?
Did you check the output of the collector health check?
Any chance you added Antivirus or something to the OS, outside of the collector?
