Foglight 5.6.7 控制台jboss報404

Foglight 5.6.7 控制台jboss報404 【終極問題原來就一資料庫權限問題！下文是由問題源找到的類似的dell support的相關文章,但卻是關于sql server error的,感興趣自己研究吧!,此文設計到的mysql載體庫權限問題】

有截圖,不知為什麼之前寫文檔截圖都是可以直接黏貼到文章上的,不久前此功能沒了,原因我我一直沒找到就不上圖了,直接主題吧.

    ************ ***********  ruiy by ************ ***************

    ==  Title                                                                                         ==

    **********************************************************                                            

Logging into Foglight receive error "HTTP Status 404 - description The requested resource (/conso

*************************************************************  

    ==  Description                                                                              ==

*************************************************************

When logging into the Foglight Console you receive this error below:

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 'your 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)

com.microsoft.sqlserver.jdbc.SQLServerStatement.getNextResult(Unknown Source)

com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.doExecutePreparedStatement(Unknown

com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement$PrepStmtExecCmd.doExecute(Unknown

      at com.microsoft.sqlserver.jdbc.TDSCommand.execute(Unknown

      at com.microsoft.sqlserver.jdbc.SQLServerConnection.executeCommand(Unknown

com.microsoft.sqlserver.jdbc.SQLServerStatement.executeCommand(Unknown Source)

com.microsoft.sqlserver.jdbc.SQLServerStatement.executeStatement(Unknown Sou

Cause

By default the Foglight external SQL Server database has a

recovery model of FULL - therefore the transaction log will be written to and

continue to grow unless a tranaction 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.

Resolution

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 your SQL

Server Maintenance Plan.

Restart the Foglight Service and you will be able to login.

我的解決user權重限!