-
Title
Timedout (90000 ms) while trying to acquire a permit for connection (0 available permits of NNN) -
Description
The FMS generated an alarm with this message.
Timedout (90000 ms) while trying to acquire a permit for connection (0 available permits of 1024). Please check Agent and Agent Manager logs for more details. You can increase the value of 'maxActiveConnectionsCap' for this Agent Manager.
The total number of permits can vary.
-
Cause
The FglAM has a -Dcom.quest.connection.regulator.maxActiveConnectionsCap parameter that allows some control over how many OS connections can be held at the same time as permits. This value is set to 200 by default, but some environments require a higher number of permits due to the number of agents or types of agents. If these connections are taking longer to be released or there are too many agents, these permits get exhausted. -
Resolution
Resolution 1.
Increase the number of maxActiveConnectionsCap. Edit baseline.jvmargs.config and add or edit this line:
vmparameter.X = "-Dcom.quest.connection.regulator.maxActiveConnectionsCap=NNN";
Note: Replace X for a unique number and NNN for a value higher than the value in the Alarm.
Restart the FglAM service or daemon to apply changes.
Resolution 2.
Reduce the amount of connections by disabling unimportant collections on the existing agents.
A good candidate for saving up on concurrent connections is to disable Collect Log Events collection from all WindowsAgent if the Event Log rule is disabled (this is the only use for this collection).
Another good option would be to disable CPU, Disk, Memory and Network metrics from any Infrastructure Cartridge agent that is monitoring a Virtual Machine that is already being monitored by a VMware or Hyper-V agent.