Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionNalin Dahyabhai
2014-01-30 18:26:15 UTC
Description of problem:
Unresolvable symbols make the package's plugins not loadable.
Version-Release number of selected component (if applicable):
opencryptoki-3.0-9.el7.x86_64
How reproducible:
Always
Steps to Reproduce:
1. Start the pkcsslotd service.
2. Run "pkcs11-tool --module=/usr/lib64/pkcs11/PKCS11_API.so -L".
3. Examine the system logs using "journalctl -xn" or directly.
Actual results:
Available slots:
No slots.
... and in /var/log/messages:
Jan 30 13:20:27 pillbox pkcs11-tool: tpm_specific.c mkdir(/var/lock/opencryptoki/tpm/nalin): No such file or directory
Jan 30 13:20:27 pillbox pkcs11-tool: apiutil.c DL_Load: dlopen() failed for [libpkcs11_ica.so]; dlerror = [libpkcs11_ica.so: cannot open shared object file: No such file or directory]
Jan 30 13:20:27 pillbox pkcs11-tool: apiutil.c DL_Load: dlopen() failed for [libpkcs11_cca.so]; dlerror = [libpkcs11_cca.so: cannot open shared object file: No such file or directory]
Jan 30 13:20:27 pillbox pkcs11-tool: ../common/utility.c open(/var/lock/opencryptoki/swtok/LCK..swtok): No such file or directory
Jan 30 13:20:27 pillbox pkcs11-tool: apiutil.c DL_Load: dlopen() failed for [F[#005]; dlerror = [F[#005: cannot open shared object file: No such file or directory]
Expected results:
Available slots:
Slot 0 (0x0): Linux
token label :
token manufacturer :
token model :
token flags : PIN pad present, token initialized, user PIN count low, other flags=0x8a4832d0
hardware version : 1.0
firmware version : 0.0
serial num :
Slot 1 (0x3): Linux
token label :
token manufacturer :
token model :
token flags : PIN pad present, token initialized, user PIN count low, other flags=0x8a4832d0
hardware version : 1.0
firmware version : 0.0
serial num :
opencryptoki package was split and the plugins are now in subpackages:
opencryptoki-ccatok.s390x : CCA cryptographic devices (secure-key) support for
opencryptoki-icatok.s390x : ICA cryptographic devices (clear-key) support for
opencryptoki-icsftok.s390x : ICSF token support for opencryptoki
opencryptoki-swtok.s390x : The software token implementation for opencryptoki
opencryptoki-tpmtok.s390x : Trusted Platform Module (TPM) device support for
Installing all the sub-packages should solve this issue.
Ok, the logs in the journal are a bit annoying. But dlopen() does not give us any guide why the action failed, except the string returned from dlerror().
The only thing we can do about it from my current understanding is to make it more silent in the logs. Instead of LOG_ERR (which it is not), LOG_WARNING or LOG_NOTICE should be appropriate. I will send mail upstream to check if it is appropriate solution.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://rhn.redhat.com/errata/RHBA-2016-2212.html