Hi Valters, This really seems to be a systemd issue: sssd never sets SYSLOG_PID when calling sd_journal_send(), yet journalctl shows e.g. SYSLOG_PID=sudo instead of an empty string. Looks like systemd is mixing the variables or leaking one into the others. The sssd upstream patch you pointed to may act as a partial workaround, but the logging is still odd as you noted.
The sssd upstream devs agree the problem is likely on the systemd side in the bug report you opened [1]. I tried to install systemd and its dependencies from Groovy and Hirsute on a Focal system as a rough way to see if a newer version of systemd fixes the issue, but it kept behaving exactly the same. I think debugging this requires writing a reproducer in the form of a minimal C program calling sd_journal_send() like sssd does, having it log/set SYSLOG_PID even when it should not. I'm adding a systemd task to this bug report. Paride [1] https://github.com/SSSD/sssd/issues/5431, Dec 15 comment. ** Bug watch added: github.com/SSSD/sssd/issues #5431 https://github.com/SSSD/sssd/issues/5431 -- 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
