12 Úno
2024
12 Úno
'24
14:44
Hi Daniel,
I found out. The d-bus stuff originated from the OS trying to handle
the segfault, so it was not related to the real problem.
The segault itself was fixed by applying a few patches to SoftHSM that
I found in the Ubuntu package, but not present in the latest upstream
source.
Regards,
Erik Østlyngen
On 12.02.2024 14:22, Daniel Salzman wrote:
Hi Erik,
Did you find what the problem was? Keymgr doesn't use a session
d-bus.
Daniel
On 6/13/23 08:26, Erik P. Ostlyngen wrote:
> Hi,
>
> I'm evaluating the Knot DNS server as a DNSSEC signer engine.
> I'm currently running version 3.2.6 together with SoftHSM version
> 2.6.1 on an Ubuntu 20.04 linux server.
>
> Now I have a problem with keymgr crashing with a segmentation
> fault and dumping core. This happens with some of the commands of
> keymgr, but not all (the command keymgr -l runs fine). The
> commands 'keymgr trondheim.no list' produces the correct output,
> but then crashes. /var/log/apport.log indicates that a dbus
> session is missing in the environment:
>
> ERROR: apport (pid 811054) Tue Jun 13 07:56:00 2023: called for
> pid 811052, signal 11, core limit 0, dump mode 2 ERROR: apport
> (pid 811054) Tue Jun 13 07:56:00 2023: not creating core for pid
> with dump mode of 2 ERROR: apport (pid 811054) Tue Jun 13
> 07:56:00 2023: executable: /usr/sbin/keymgr (command line "keymgr
> trondheim.no list") ERROR: apport (pid 811054) Tue Jun 13
> 07:56:00 2023: is_closing_session(): no DBUS_SESSION_BUS_ADDRESS
> in environment ERROR: apport (pid 811054) Tue Jun 13 07:56:00
> 2023: apport: report /var/crash/_usr_sbin_keymgr.0.crash already
> exists and unseen, skipping to avoid disk usage DoS
>
> Running the command as 'dbus-run-session keymgr trondheim.no
> list' gives:
>
> ERROR: apport (pid 811174) Tue Jun 13 08:01:04 2023: called for
> pid 811173, signal 11, core limit 0, dump mode 2 ERROR: apport
> (pid 811174) Tue Jun 13 08:01:04 2023: not creating core for pid
> with dump mode of 2 ERROR: apport (pid 811174) Tue Jun 13
> 08:01:04 2023: executable: /usr/sbin/keymgr (command line "keymgr
> trondheim.no list") ERROR: apport (pid 811174) Tue Jun 13
> 08:01:04 2023: is_closing_session(): Could not determine DBUS
> socket. ERROR: apport (pid 811174) Tue Jun 13 08:01:04 2023:
> apport: report /var/crash/_usr_sbin_keymgr.0.crash already exists
> and unseen, skipping to avoid disk usage DoS
>
> I've tried to run the command as root and as the knot user, and I
> have to admit that I'm not very familiar with how to manage dbus
> sessions. I want to run the keymgr command from cron or from some
> other system shell, for periodically monitoring the keys.
> However, I'm unsure why keymgr wants to communicate on the dbus.
> Is it possible to disable this?
>
> Regards, Erik Østlyngen --