Connector won't start - 1 of 2 Logger Pools unavailable
Anyone else run into a similiar issue and found a resolution?
All of my connectors have 3 destinations (ESM, 1 Primary Logger Pool, 1 Secondary Logger Pool).
My secondary Logger pool is unavailble at the moment due to software failures.
I have multiple WINC (220.127.116.1136) connectors that refuse to start. The service is stuck in "Starting" and will not fully launch.
The logs indicate a the down pool is not available which I am aware of but I see no indication of why the connector would refuse to work with only 1 pool down.
Re: Connector won't start - 1 of 2 Logger Pools unavailable
By any chance did you tried with Arcsight Logger Samrt Message insted of Pool.
Check connectivity between the Logger and Connector.
As a best practise maximum you can use 6 to 10 windows devcies (need to increase heap size 1st) in a single connector.
Try removing few devices and use filtering for filter out unwanted events. Also try to upgrade your connector version.
Basically if connector java environmet faces any issues services hung error may occure.
You can also check for ram and memory utilization.
Best way to look into the agent.log file for any knind of error.
I have faced same issue couple of months earlier I have concentrated on above stated things and end up resolving the issue.
Hope it will work for you as well.