Return
-
Title
Error "Failed to initialize SQL PI engine" in the Agent logs -
Description
SQL PI dashboard doesn't show current metrics.
The agent logs show an error like:ERROR [FglAM:IncomingMessage[4]-336] com.quest.qsi.fason.sqlserver.common.spi.BaseSpiController - Failed to initialize SQL PI engine java.lang.IllegalStateException: ManagerFactory [org.apache.logging.log4j.core.appender.rolling.RollingFileManager$RollingFileManagerFactory@7898ea91] unable to create manager for [/fglam_home/state/default/agents/fb8be857-fbcf-4747-973d-295a8570e581/DB_SQL_Server/6.1.2.10/logs/MSSQL_statistics.log] with data [org.apache.logging.log4j.core.appender.rolling.RollingFileManager$FactoryData@320656d6[pattern=/fglam_home/state/default/agents/fb8be857-fbcf-4747-973d-295a8570e581/DB_SQL_Server/6.1.2.10/logs/MSSQL_statistics.log-%d{MM-dd-yy}.log.gz, append=true, bufferedIO=true, bufferSize=8192, policy=SizeBasedTriggeringPolicy(size=20971520), strategy=DefaultRolloverStrategy(min=1, max=10, useMax=true), advertiseURI=null, layout=%d{yyyy-MM-dd HH:mm:ss.SSS} %p [%t] - %m%n, filePermissions=null, fileOwner=null]] at org.apache.logging.log4j.core.appender.AbstractManager.getManager(AbstractManager.java:116) at org.apache.logging.log4j.core.appender.OutputStreamManager.getManager(OutputStreamManager.java:100) at org.apache.logging.log4j.core.appender.rolling.RollingFileManager.getFileManager(RollingFileManager.java:217) at org.apache.logging.log4j.core.appender.RollingFileAppender$Builder.build(RollingFileAppender.java:146) at com.dell.dsgi.spi.common.utils.services.log4j.Log4JLogService.configLogContext(Log4JLogService.java:86) at com.dell.dsgi.spi.common.utils.services.log4j.Log4JLogService.<init>(Log4JLogService.java:64)ERROR [HOSTNAME-MSSQLSRV-lowPriorityPool-2-[DBSS_PI_Engine_Maintenance][2023/05/02 17:31:40]] com.quest.qsi.fason.sqlserver.common.spi.BaseSpiController - Failed to initialize SQL PI engine java.lang.IllegalStateException: ManagerFactory [org.apache.logging.log4j.core.appender.rolling.RollingFileManager$RollingFileManagerFactory@7898ea91] unable to create manager for [/fglam_home/state/default/agents/fb8be857-fbcf-4747-973d-295a8570e581/DB_SQL_Server/6.1.2.10/HOSTNAME-MSSQLSRV_sql_pi_statistics.log] with data [org.apache.logging.log4j.core.appender.rolling.RollingFileManager$FactoryData@51bf8b9b[pattern=/fglam_home/state/default/agents/fb8be857-fbcf-4747-973d-295a8570e581/DB_SQL_Server/6.1.2.10/HOSTNAME-MSSQLSRV_sql_pi_statistics.log-%d{MM-dd-yy}.log.gz, append=true, bufferedIO=true, bufferSize=8192, policy=SizeBasedTriggeringPolicy(size=20971520), strategy=DefaultRolloverStrategy(min=1, max=10, useMax=true), advertiseURI=null, layout=%d{yyyy-MM-dd HH:mm:ss.SSS} %p [%t] - %m%n, filePermissions=null, fileOwner=null]] at org.apache.logging.log4j.core.appender.AbstractManager.getManager(AbstractManager.java:116) at org.apache.logging.log4j.core.appender.OutputStreamManager.getManager(OutputStreamManager.java:100) at org.apache.logging.log4j.core.appender.rolling.RollingFileManager.getFileManager(RollingFileManager.java:217) at org.apache.logging.log4j.core.appender.RollingFileAppender$Builder.build(RollingFileAppender.java:146) at com.dell.dsgi.spi.common.utils.services.log4j.Log4JLogService.configLogContext(Log4JLogService.java:86) at com.dell.dsgi.spi.common.utils.services.log4j.Log4JLogService.<init>(Log4JLogService.java:64)
-
Cause
One possible cause is that the file targeted while initializing RollingFileManager is invalid for some reason (e.g. permissions, full disk, etc).
Similar issue is caused by special characters in the Agent name.
-
Resolution
Confirm that the user account running the FglAM has read+write access to the whole FglAM installation directory tree and that the disk can be written to.
KB article How to change ownership of files for Foglight user (4327248) can be used as reference.