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. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908065 Title: Invalid SYSLOG_PID for (systemd) journal messages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1908065/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
