When logging into the Foglight Console the following is displayed:
HTTP Status 404 - /console/page/main
type Status report
message /console/page/main
description The requested resource (/console/page/main) is not available.
After restarting the Foglight Service the ServerStartup html page displays the following message:
"Status: The server startup is completed but some main services failed to start."
In the Management Server logs on the Foglight Server there will be entries as follows:
YYYY-MM-DD HH:MM:SS.SSS WARN [main] com.quest.nitro.service.persistence.obs.storage.StorageManagerService - Unable to determine the master storage manager. Possible database connectivity problem.
org.hibernate.TransactionException: JTA commit failed:
at org.hibernate.transaction.JTATransaction.commit(JTATransaction.java:153)
Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: The transaction log for database 'external database name' is full. To find out why space in the log cannot be reused, see the log_reuse_wait_desc column in sys.databases
at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDatabaseError(Unknown Source)
at com.microsoft.sqlserver.jdbc.SQLServerStatement.getNextResult(Unknown Source)
at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.doExecutePreparedStatement(Unknown Source)
at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement$PrepStmtExecCmd.doExecute(Unknown Source)
at com.microsoft.sqlserver.jdbc.TDSCommand.execute(Unknown Source)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.executeCommand(Unknown Source)
The external SQL Server database has a recovery model of FULL - therefore the transaction log will be written to and continue to grow unless a transaction backup is made with the TRUNCATE option. After some time the database may start to reach the limit of the log size initially defined (50MB), and this causes database connectivity issues.
The easiest way to resolve this issue is to check the size of the log file vs the actual size used/available. Remember the physical size of the database log file (.LDF) does not necessarily represent how much it has been used.
Use SQL Server Management Studios "shrink" option against the Foglight database. Alternatively run a transaction log backup to release the used space. This should form part of the SQL Server Maintenance Plan.
After performing the required database maintenance, restart the Foglight Management Server.
See also:
Foglight will not start, logs shows error "org.hibernate.TransactionException: JTA commit failed"
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Feedback Terms of Use Privacy Cookie Preference Center