Installation of a new database agent fails with the following error logged in the Foglight Management Server (FMS) logs:
Cause 1:
Foglight Agent Manager (FglAM) sizing issues impacting performance.
Cause 2:
High topology churn causing instability.
Cause 3:
Undetermined/unknown internal issues.
Cause 4:
Callback timeout settings too low.
Cause 5:
Insufficient disk space on the FMS repository database.
Example error from FMS log:
com.microsoft.sqlserver.jdbc.SQLServerException: Could not allocate space for object 'dbo.obs_metric_aggregate_0064'.'PK__obs_metr__2FD4DC06004D55BA' in database 'DATABASE' because the 'PRIMARY' filegroup is full. Create disk space by deleting unneeded files, dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup.
Resolution 1:
Verify that your environment meets Foglight for Databases sizing guidelines for CPU, memory, disk space, and that VM resource reservations and antivirus exclusions are configured properly.
Resolution 2:
Investigate and reduce topology churn that may be affecting FMS performance. Refer to KB 4353149 for instructions on identifying churn from the Diagnostic Snapshot.
Resolution 3:
Restart the Foglight Management Server and Foglight Agent Manager services, then retry the database agent installation.
Resolution 4:
Increase callback timeout values for the relevant SPIRepository or installer agents:
For DBSS-SPIRepository or DBO-SPIRepository agents:
Go to Administration > Agents > Agent Status > select the agent > Edit > Modify private properties > increase Standard callback timeout to 1800000 ms > Save changes.
For SQL Server installer agents:
Go to Administration > Agents > Agent Status > select DBSS-Installer-{FglAMName} > Edit > Modify private properties > increase SQL Server Connection Timeout to 120000 ms > Save changes.
For DB2 installer agents:
Go to Administration > Agents > Agent Status > select DB2-Installer-{FglAMName} > Edit > Modify private properties > increase Standard callback timeout to 1800000 ms > Save changes.
For Oracle installer agents:
Go to Administration > Agents > Agent Status > select Oracle-Installer-{FglAMName} > Edit > Modify private properties > increase Standard callback timeout to 1800000 ms > Save changes.
Resolution 5:
If the FMS repository database is out of space, add additional storage to the database to allow new agents to be added successfully.
If problems continue after applying these resolutions, collect relevant logs and support bundles and contact Quest Support for further assistance.
