The blocking and sessions panels in the SQL Azure agent do not display data.
Error messages similar to the following appear in the Azure agent log files
ERROR [AzureSQL_DB-lowPriorityPool-4593-[DBSS_Azure_Database_Replication][YYYY/MM/DD 17:07:04]] com.quest.qsi.fason.core.collection.processor.InstanceProcessor - Failed to run DBSSAzureDatabaseReplicationProcessor processor of DBSS_Azure_Database_Replication collection.
java.lang.RuntimeException: Failed to execute collection [DBSS_Azure_Database_Replication], reason=[Foglight][SQLServer JDBC Driver]Connection reset by peer: socket write error- Profile:AzureProfile{server='AZURE HOSTNAME', database= 'AzureSQL', username='sysadmin', authType= 'SQL_SERVER', port= '0', socketTimeout= '0', packetSize= '0', ApplicationIntent= 'NONE', enforceSSLVersion= 'NONE', lockTimeout= '10000', codePageOverride = '' }
for the following collections
ISSUE 1
Errors like the following appear in the FMS (Foglight Management Server) log
ISSUE 2
Errors like this appear in the FglAM (Foglight Agent Manager) log
CAUSE 1
Port 3260 was blocked from the FglAM to the FMS preventing the RMI connection from succeeding. The port should be opened bidirectionally.
CAUSE 2
Java issue related to IP address resolution by the FglAM service. This external article describing the bug can be found on Oracle's Java website: https://bugs.java.com/bugdatabase/view_bug.do?bug_id=6754672
ISSUE 1
WORKAROUND
Change the RMI port used to connect to Azure as per KB 312636.
RESOLUTION
Open the default port 3260 for the RMI connection to Azure.
ISSUE 2
This issue has been found on a server where the FMS (Foglight Management Server) and FglAM (Foglight Agent Manager) are installed on the same system.
Please contact Support for this issue as this has not yet been investigated previously.
Options may include
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center