Description of problem: I noticed this crash looking at my IPA server's log. It crashes fairly regularly (like every minute or so) Version-Release number of selected component: bind-dnssec-utils-32:9.16.24-1.fc34 Additional info: reporter: libreport-2.15.2 backtrace_rating: 4 cgroup: 0::/system.slice/ipa-dnskeysyncd.service cmdline: /usr/sbin/dnssec-keyfromlabel -K /var/named/dyndb-ldap/ipa/master/lan.removed-domain.org/tmpvx68kiml -a RSASHA256 -l pkcs11:object=1ff60678a352a91d465c8001e0a881ea;pin-source=/var/lib/ipa/dnssec/softhsm_pin -P 20211011215547 -A none -I none -D none -E pkcs11 lan.removed-domain.org crash_function: std::_Rb_tree<unsigned long const, std::pair<unsigned long const, Slot* const>, std::_Select1st<std::pair<unsigned long const, Slot* const> >, std::less<unsigned long const>, std::allocator<std::pair<unsigned long const, Slot* const> > >::_M_mbegin executable: /usr/sbin/dnssec-keyfromlabel journald_cursor: s=1e7faffaa6b34041b111aba17c49b0e1;i=21c8;b=062c7dd24b1c4e398363fc20824f23ad;m=3ef45ae2;t=5d84d89b42f86;x=75b89f65f8e7d577 kernel: 5.16.9-100.fc34.x86_64 rootdir: / runlevel: N 3 type: CCpp uid: 996 Truncated backtrace: Thread no. 1 (10 frames) #0 std::_Rb_tree<unsigned long const, std::pair<unsigned long const, Slot* const>, std::_Select1st<std::pair<unsigned long const, Slot* const> >, std::less<unsigned long const>, std::allocator<std::pair<unsigned long const, Slot* const> > >::_M_mbegin at /usr/include/c++/11/bits/stl_tree.h:749 #1 std::_Rb_tree<unsigned long const, std::pair<unsigned long const, Slot* const>, std::_Select1st<std::pair<unsigned long const, Slot* const> >, std::less<unsigned long const>, std::allocator<std::pair<unsigned long const, Slot* const> > >::_M_begin at /usr/include/c++/11/bits/stl_tree.h:754 #2 std::_Rb_tree<unsigned long const, std::pair<unsigned long const, Slot* const>, std::_Select1st<std::pair<unsigned long const, Slot* const> >, std::less<unsigned long const>, std::allocator<std::pair<unsigned long const, Slot* const> > >::lower_bound at /usr/include/c++/11/bits/stl_tree.h:1285 #3 std::map<unsigned long const, Slot* const, std::less<unsigned long const>, std::allocator<std::pair<unsigned long const, Slot* const> > >::lower_bound at /usr/include/c++/11/bits/stl_map.h:1259 #4 std::map<unsigned long const, Slot* const, std::less<unsigned long const>, std::allocator<std::pair<unsigned long const, Slot* const> > >::at at /usr/include/c++/11/bits/stl_map.h:539 #5 SlotManager::getSlot at SlotManager.cpp:174 #6 SoftHSM::C_CloseAllSessions at SoftHSM.cpp:1386 #7 C_CloseAllSessions at main.cpp:347 #8 pkcs11_release_slot at /usr/src/debug/openssl-pkcs11-0.4.11-2.fc34.x86_64/src/p11_slot.c:472 #9 pkcs11_release_all_slots at /usr/src/debug/openssl-pkcs11-0.4.11-2.fc34.x86_64/src/p11_slot.c:459
Created attachment 1861937 [details] File: backtrace
Created attachment 1861938 [details] File: core_backtrace
Created attachment 1861939 [details] File: cpuinfo
Created attachment 1861940 [details] File: dso_list
Created attachment 1861941 [details] File: environ
Created attachment 1861942 [details] File: exploitable
Created attachment 1861944 [details] File: limits
Created attachment 1861945 [details] File: maps
Created attachment 1861946 [details] File: mountinfo
Created attachment 1861947 [details] File: open_fds
Created attachment 1861948 [details] File: proc_pid_status
Could you please try update https://bodhi.fedoraproject.org/updates/FEDORA-2022-042d9c6146, whether it crashes still the same or something else changed? I haven't seen such error yet myself. Is the environment configured the same way as named-pkcs11.service? Is it run under named user or something different?
Updated and it still dumps core. This is the ipa-dnskeysyncd.service. It runs under the ods user
There seems to be only softhsm code and openssl involved. Almost nothing from bind. Moving to softhsm component, it seems more likely fix needs to be done there. If that is not the case, please return it back with an explanation. I expect this is closing handler, which might be related to atexit handlers or something similar. But that backtrace does not seem related to bind utility.
This message is a reminder that Fedora Linux 34 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 34 on 2022-06-07. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '34'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 34 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 34 entered end-of-life (EOL) status on 2022-06-07. Fedora Linux 34 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. Thank you for reporting this bug and we are sorry it could not be fixed.