Dell PowerVault ML6000 User Manual

Also see for PowerVault TL2000: Getting started guide Faq Quick start guide User guide Release notes

Contents

Chapter 6. Problem DeterminationYou can enable debugging for an individual component, multiple components, orall components of the Encryption Key Manager.Check These Important Files for Encryption Key Manager ServerProblemsWhen the Encryption Key Manager fails to start there are three files to check todetermine the cause of the problem.v native_stdout.log and native_stderr.log– Since the Encryption Key Manager Server runs in a background process, ithas no console to display its normal informational and error messages. Thosemessages are logged to these two files.– If the Encryption Key Manager Server properties file contains the propertydebug.output.file, then these two files are created in the same directory asthe debug log.– If the Encryption Key Manager Server properties file does not contain theproperty debug.output.file, then these two files are created in the workingdirectory.– These two files are deleted and recreated on every start of the Encryption KeyManager Server.v Audit log– Audit log contains records that were logged as the Encryption Key Manageris processing.– The location of this file is specified by two properties inKeyManagerConfig.properties, the Encryption Key Manager Serverconfiguration properties file:- Audit.handler.file.directory – specifies which directory the audit log shouldbe located- Audit.handler.file.name – specifies the filename of the audit log.– For more information on Audit, see Chapter 7, “Audit Records,” on page 7-1.Log Entries for Keystore Passwords Greater than 127 CharactersWhen the Encryption Key Manager is installed as a Windows Service and thekeystore passwords in the KeyManagerConfig.properties file are 128 characters inlength or greater, the Encryption Key Manager will fail to start because it has noway to prompt for a password of acceptable length. The native Encryption KeyManager logs will contain entries similar to the following:native_stdout.logServer initializedDefault keystore failed to loadnative_stderr.logat com.ibm.keymanager.KeyManagerException: Default keystore failed to loadat com.ibm.keymanager.keygroups.KeyGroupManager.loadDefaultKeyStore(KeyGroupManager.java:145)at com.ibm.keymanager.keygroups.KeyGroupManager.init(KeyGroupManager.java:605)at com.ibm.keymanager.EKMServer.c(EKMServer.java:243)6-1