Troubleshooting
Problem
Tivoli Storage FlashCopy Manager DB2 local snapshot fails with FMM9328E and GSKit return code 407.
Symptom
Following error can be seen in summary.date.log:
FMM9328E An error occurred in the secure communication layer when running the following function: gsk_secure_soc_init(). GSKit return code: 407. GSKit error: GSK_ERROR_BAD_KEYFILE_LABEL.
while receiving connection from host 'hostname'
Cause
The GSKit certification created during the FlashCopy Manager setup process is either missing or broken.
Diagnosing The Problem
FlashCopy Manager acsgend trace shows the following error:
19:39:59.705 4000 (1) esd-securesocket.cpp:66 setupSecureSocket()
19:39:59.830 ffffffff (1) esd-socket.cpp:326 premature eof
19:39:59.830 4000 (1) esd-securesocket.cpp:693 ESD_InterruptedException
caught in ioReadCallbackWrapper(), error code: 5
19:39:59.830 4000 (1) esd-securesocket.cpp:110 Secure socket 10 could
not be connected to peer: :
19:39:59.830 ffffffff (1) esd-exception.cpp:53 entering ESD_Exception
19:39:59.830 ffffffff (1) esd-exception.cpp:55 stackTrace.data()=(
esd-exception.cpp(113): )
( esd-socket.cpp(282): )
( esd-securesocket.cpp(534): )
( esd-securesocket.cpp(672): )
esd-securesocket.cpp(66):
esd-secureclientsocketfactory.cpp(72):
esd-clientsocketfactory.cpp(64):
esd-splitint.cpp(449):
esd-splitint.cpp(505):
19:39:59.830 ffffffff (1) esd-exception.cpp:57 ESD_CSTR(text_)=FMM9328E
An error occurred in the secure communication layer when running the
following function: gsk_secure_soc_init(). GSKit return code: 406. GSKit
error: GSK_ERROR_IO.
19:39:59.830 ffffffff (1) esd-exception.cpp:59 leaving ESD_Exception
The acsd trace shows the following error:
- 19:39:59.786 4000 (1) esd-securesocket.cpp:61
ESD_SecureSocket::ESD_SecureSocket
19:39:59.824 4000 (1) esd-securesocket.cpp:61 ... EXIT }
19:39:59.824 4000 (1) esd-securesocket.cpp:66 { ENTRY ...
19:39:59.824 4000 (1) esd-securesocket.cpp:66 setupSecureSocket()
19:39:59.824 4000 (1) esd-securesocket.cpp:110 Secure socket 13 could
not be connected to peer: :
19:39:59.825 ffffffff (1) esd-exception.cpp:53 entering ESD_Exception
19:39:59.825 ffffffff (1) esd-exception.cpp:55
stackTrace.data()=esd-securesocket.cpp(66):
esd-secureserversocketfactory.cpp(81):
esd-serversocketfactory.cpp(406):
esd-prole.cpp(208):
prole.cpp(254):
19:39:59.825 ffffffff (1) esd-exception.cpp:57 ESD_CSTR(text_)=FMM9328E
An error occurred in the secure communication layer when running the
following function: gsk_secure_soc_init(). GSKit return code: 407. GSKit
error: GSK_ERROR_BAD_KEYFILE_LABEL.
Resolving the problem
Resolving The Problem
Import the self-signed certificate by using the following GSKit command:
gsk8capicmd_64 -cert -add -db fcmcert.kdb -stashed -label "FCM server certificate" -file <path to fcmselfcert.arm> -format ascii
If this command returns 'CTGSK3012W The input file "<path to fcmselfcert.arm>" could not be found', remove the certificate with the label FCM server certificate. You can use the following command:
gsk8capicmd_64 -cert -delete -db fcmcert.kdb -stashed -label "FCM server certificate"
Then re-run the setup script and verify if fcmselfcert.arm is generated. If generated, run the DB2 snapshot again.
Product Synonym
FCM TSM
Was this topic helpful?
Document Information
Modified date:
17 June 2018
UID
swg21957897