The FglAM upgrade failed in the middle due to an out of disk space situation. The following error was displayed when trying to start the FglAM
2011-10-04 11:12:27.250 ERROR [Startup Thread] com.quest.glue.core.Glue - Unable to start
com.quest.glue.core.credentials.KeyStoreManagerException: Failed to initialize CredentialManager
at com.quest.glue.core.credentials.CredentialManager.<init>(CredentialManager.java:119)
at com.quest.glue.core.Glue.<init>(Glue.java:366)
at com.quest.glue.core.Glue$GlueMainThread.run(Glue.java:635)
at java.lang.Thread.run(Unknown Source)
Caused by: com.quest.glue.core.credentials.KeyStoreManagerException: java.io.EOFException
at com.quest.glue.core.credentials.KeyStoreManager.initKeyStore(KeyStoreManager.java:450)
at com.quest.glue.core.credentials.KeyStoreManager.<init>(KeyStoreManager.java:99)
at com.quest.glue.core.credentials.CredentialManager.<init>(CredentialManager.java:117)
... 3 more
Caused by: java.io.EOFException
The FglAM upgrade failure left the credentials.keystore file empty
./state/default/credentials:
-rw------- 1 pipmp01 dipm 0 Oct 3 11:36 credentials.keystore
Since the file had a 0 byte size (empty) it triggered a path in the code that “if the file exists, read it”. This caused the failure with the error
The same code path states “if the file doesn’t exist, create it” so the solution is to remove this file, and allow FglAM to recreate it.
1) Navigate to the Client where the FglAM is installed
2) Delete the 0 byte size file
FglAM/state/default/credentials/credentials.keystore
3) Start the FglAM
© ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center