Comment #2 : Bug #1908065 : Bugs : sssd package : Ubuntu

Comment 2 for bug 1908065

Revision history for this message
Valters Jansons (sigv) wrote :

This could also be something on systemd/journald side. Looking at the source code, it seems SYSLOG_IDENTIFIER is the relevant part that gets set, but then somehow ends up 'leaking' into SYSLOG_PID. https://github.com/SSSD/sssd/blob/sssd-2_2_3/src/util/sss_log.c#L110

There is a further upstream commit which amends the SSSD logging mechanism as https://github.com/SSSD/sssd/commit/18233532b72e62452eac6886652fa633ba055d8c and applying this patch on the 2.2.3-3 source appears to make the SYSLOG_PID go away for me. The change itself modifies the format strings. But the resulting SYSLOG_IDENTIFIER still does not seem fully correct, as with the patch applied I see SYSLOG_IDENTIFIER=sssd_be however I would expect to see SYSLOG_IDENTIFIER=sssd[be[EXAMPLE.COM]]. This does further make me lean in the direction of the bug being on systemd, potentially the processing of sd_journal_send, but I do not have experience in debugging the inner workings there.