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.
Applies also to opencryptoki-3.17.0-3.el9
+++ This bug was initially created as a clone of Bug #2040677 +++
Description of problem:
# yum -y install opencryptoki
# su - bz1063763user
$ pkcsconf -t
Error initializing the PKCS11 library: 0x6 (CKR_FUNCTION_FAILED)
Note: all non-root users that require access to PKCS#11 tokens using opencryptoki must be assigned to the pkcs11 group to be able to communicate with the pkcsslotd daemon.
...
at this moment the process is stuck.
Problem is not present when user is in pkcs11 group.
Version-Release number of selected component (if applicable):
opencryptoki-3.17.0-2.el8
Bug is not present in opencryptoki-3.15.1-7.el8_4
How reproducible:
always
(gdb) run -t
Starting program: /usr/sbin/pkcsconf -t
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
Error initializing the PKCS11 library: 0x6 (CKR_FUNCTION_FAILED)
Note: all non-root users that require access to PKCS#11 tokens using opencryptoki must be assigned to the pkcs11 group to be able to communicate with the pkcsslotd daemon.
^C
Program received signal SIGINT, Interrupt.
__lll_lock_wait () at ../sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:103
103 2: movl %edx, %eax
(gdb) bt full
#0 __lll_lock_wait () at ../sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:103
No locals.
#1 0x00007ffff7bb9a79 in __GI___pthread_mutex_lock (mutex=mutex@entry=0x7ffff4f76600 <GlobMutex>) at ../nptl/pthread_mutex_lock.c:80
ignore1 = <optimized out>
ignore2 = <optimized out>
ignore3 = <optimized out>
type = <optimized out>
__PRETTY_FUNCTION__ = "__pthread_mutex_lock"
id = <optimized out>
#2 0x00007ffff4d6d2e7 in C_Finalize (pReserved=<optimized out>) at usr/lib/api/api_interface.c:1647
sltp = <optimized out>
slotID = <optimized out>
shData = <optimized out>
sinfp = <optimized out>
#3 0x000055555555b95d in cleanup () at usr/sbin/pkcsconf/pkcsconf.c:1184
rc = <optimized out>
#4 0x000055555555ba8e in init () at usr/sbin/pkcsconf/pkcsconf.c:1171
rc = 6
symPtr = <optimized out>
#5 0x0000555555557189 in main (argc=2, argv=0x7fffffffe438) at usr/sbin/pkcsconf/pkcsconf.c:199
rv = 0
flags = 16
sopin = 0x0
pin = 0x0
newpin = 0x0
newpin2 = 0x0
c = -1
newpinlen = <optimized out>
newpin2len = <optimized out>
errflag = 0
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 (new packages: opencryptoki), 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://access.redhat.com/errata/RHBA-2022:3999