SQL Server agents fire alerts like the following:
Fatal: MSSQLServer@TESTINSTANCE: DBSS - Usability Connect Availability FMS server TESTFMS reports: MSSQLServer@TESTINSTANCE: The connection to the instance failed. Network error IOException: Address already in use: connect- Profile:MSSQLProfile{hos
According to some research, it seems like Foglight may be opening faster than the OS can service them. Is this a known issue?
And is changing the OS registry the only way to handle these?
After evaluating this our Development team has found that it looks like both the errors and the solutions provided are system related.
The Operating System vendor (Microsoft) should be consulted to determine if this is the best course of action.
Once the connection/address errors are resolved in the system, the db agents should work as expected.
If you run a "netstat -a" from the command prompt it may show a large number of tcp/ip connections established by the agent. Most TCP/IP connections are displayed as short-lived ports that have already closed but stay reserved in a TIME_WAIT state before they can be reused. This can affect an agent's ability to create new connections.
By default, Microsoft limits the OS to 3975 open TCP/IP connections at any given time. The TIME_WAIT state is configured by default to be 240 seconds, this causes Windows to only support an average of 33 TCP/IP connections per second.
Monitoring agents might have to wait 240 seconds before being able to reuse those connections. Processing 3975 connections every 4 minutes may not be enough.
With some applications, there seem to be three possible workarounds:
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Feedback Terms of Use Privacy Cookie Preference Center