PKCS11 Log File
Log File Name: cs_pkcs11_R3.log
Location: Defined by the LogPath parameter in the PKCS#11 configuration file. Example: \tmp for Linux.
Details: This log captures detailed information about PKCS#11 operations, including initialization, cryptographic actions, and error messages. The verbosity is controlled by the Logging Loglevel setting.
To simplify your testing process, it's recommended that you enable the PKCS#11 log file by adjusting the logging settings.
Specifically: Set the LogPath to a writable directory (not a specific file). Set the Logging Loglevel to 1 for basic logging. Increase it to 4 for more detailed output during testing. This will generate a log file named cs_pkcs11_R3.log within the specified LogPath directory. Reviewing this log can help with troubleshooting if you encounter issues.
Once testing is complete, it's advisable to reduce Logging Loglevel to limit output to only critical or important messages
Sybase ASE Log File
Log File Name: <servername>.log (eg: SAP01.log)
Location: $SYBASE/$SYBASE_ASE/install (eg:/opt/sap/ASE-16_1/install/)
Details: This log captures low‑level interaction details between SAP ASE and the Utimaco PKCS#11 library, providing visibility into the initialization, execution, and failure of cryptographic operations offloaded to the HSM.