2019-02-15 05:22:23 INFO [EventCollector] Trying to close event protocol for agent: XXXXXXXXXX:XXXXX 2019-02-15 05:22:23 INFO [EventCollector] Event protocol for agent: XXXXXXXXXX:XXXXX closed! 2019-02-15 05:22:23 INFO [EventCollector] Event Protocol Thread for agent: XXXXXXXXXX:XXXXX terminated! 2019-02-15 05:22:23 INFO [Instrumentor] Agent XXXXXXXXXX:XXXXX (ID: c58aa89e) requesting logoff (RECONNECT) 2019-02-15 05:22:23 INFO [AgentPeer] Shutting down EventCollector of XXXXXXXXXX:XXXXX 2019-02-15 05:22:23 INFO [EventCollector] Trying to close event protocol for agent: XXXXXXXXXX:XXXXX 2019-02-15 05:22:23 INFO [EventCollector] Unable to close event protocol for agent: XXXXXXXXXX:XXXXX. Event Collector is already shutdown! 2019-02-15 05:22:23 INFO [AgentCenter] Starting Agent Shutdown: XXXXXXXXXX:XXXXX, disconnection state: FOR_RECONNECT 2019-02-15 05:22:23 INFO [AgentPeerPool] removed agent 'XXXXXXXXXX:XXXXX' from pool - number of agents: 6 2019-02-15 05:22:23 INFO [AgentCenter] Shutdown agent finished. Adding unregister entry for agent XXXXXXXXXX:XXXXX to the AgentRegistrationQueue 2019-02-15 05:22:23 INFO [AgentCenter$AgentRegistrationQueueWorker] Removed unregister entry for agent XXXXXXXXXX:XXXXX from the AgentRegistrationQueue 2019-02-15 05:22:23 INFO [Instrumentor] Finished shutdown of agent in AgentCenter: XXXXXXXXXX:XXXXX 2019-02-15 05:22:23 INFO [Instrumentor] stopped WebserverInstrumentor@XXXXXXXXXX:XXXXX 2019-02-15 06:52:30 INFO [AgentListener] Incoming connection from
Answer by ashutosh s. ·
Hi Sebastian,
We have done collector grouping. So if one collector is not reachable it trying to reach second one. Cause of that agents are showing disconnected but data are coming through those.
Kindly help me on this collector behavior.
Regards,
Ashutosh Kumar Singh
Are you sure that ports are open for all collector instances? I think you should open support ticket and post there support archive, it will be faster for you.
Sebastian
JANUARY 15, 3:00 PM GMT / 10:00 AM ET