RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1888409 - sssd component logging is now too generic in syslog/journal [rhel-7.9.z]
Summary: sssd component logging is now too generic in syslog/journal [rhel-7.9.z]
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: sssd
Version: 7.9
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Alexey Tikhonov
QA Contact: Madhuri
URL:
Whiteboard: sync-to-jira qetodo
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-10-14 19:09 UTC by Orion Poplawski
Modified: 2020-12-15 11:22 UTC (History)
10 users (show)

Fixed In Version: sssd-1.16.5-10.el7_9.6
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-12-15 11:22:17 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github SSSD sssd issues 5384 0 None closed sssd syslog/journal logging is now too generic 2021-02-03 15:56:37 UTC

Description Orion Poplawski 2020-10-14 19:09:01 UTC 
Description of problem:

Before log messages were like:

Oct 14 07:11:30 hostname sssd[1244]: Starting up
Oct 14 07:11:31 hostname sssd[sudo][1411]: Starting up
Oct 14 07:11:31 hostname sssd[ssh][1413]: Starting up
Oct 14 07:11:31 hostname sssd[autofs][1414]: Starting up
Oct 14 07:11:31 hostname sssd[nss][1410]: Starting up
Oct 14 07:11:31 hostname sssd[pam][1412]: Starting up
Oct 14 07:11:31 hostname sssd[pac][1415]: Starting up

Now they are like:

Oct 14 07:41:22 hostname sssd[21141]: Starting up
Oct 14 07:41:22 hostname ssh[21161]: Starting up
Oct 14 07:41:22 hostname nss[21158]: Starting up
Oct 14 07:41:22 hostname pam[21160]: Starting up

This is too generic - in particular the "pam" line which gets picked up by logwatch as PAM messages.

Version-Release number of selected component (if applicable):
sssd-1.16.5-10.el7_9.5.x86_64
Comment 2 Alexey Tikhonov 2020-10-15 11:12:53 UTC 
This was done upstream (https://github.com/SSSD/sssd/commit/225fe9950f2807d5fb226f6b3be1ff4cefd731f0) with own sssd logs (/var/log/sssd/*) in mind where this prefix was useless.

It's not that I totally ignored journal/syslog when proposed this patch: journal has this information in trusted fields "COMM=, _EXE=, _CMDLINE=". So it can be extracted with something like "journalctl -o verbose --output-fields=_COMM,MESSAGE"

But I agree that doesn't look pretty with default output. I'll check what can be done.

Meanwhile perhaps you could tweak logwatch configuration to use _COMM.
Comment 3 Alexey Tikhonov 2020-10-21 18:55:05 UTC 
Upstream PR: https://github.com/SSSD/sssd/pull/5373
Comment 5 Pavel Březina 2020-11-05 10:49:01 UTC 
Pushed PR: https://github.com/SSSD/sssd/pull/5373

* `master`
    * 18233532b72e62452eac6886652fa633ba055d8c - DEBUG: fixes program identifier as seen in syslog
    * 833034f5332d2492d413a9c97fded1480b58bf14 - DEBUG: journal_send() was made static
* `sssd-1-16`
    * 647a130b501374c22b63937decdcf97da5c92505 - DEBUG: fixes program identifier as seen in syslog
    * 208372c7f6ad7d1d1d4b5cad57aaa08affaa0fac - DEBUG: journal_send() was made static
Comment 9 Madhuri 2020-12-02 17:26:43 UTC 
Reproduce with:
[root@ci-vm-10-0-154-72 ~]# rpm -qa sssd
sssd-1.16.5-10.el7_9.5.x86_64

Dec 02 12:21:38 ci-vm-10-0-154-72.hosted.upshift.rdu2.redhat.com sssd[7289]: Starting up
Dec 02 12:21:38 ci-vm-10-0-154-72.hosted.upshift.rdu2.redhat.com be[example1][7290]: Starting up
Dec 02 12:21:38 ci-vm-10-0-154-72.hosted.upshift.rdu2.redhat.com nss[7291]: Starting up
Dec 02 12:21:38 ci-vm-10-0-154-72.hosted.upshift.rdu2.redhat.com pam[7292]: Starting up
Dec 02 12:21:38 ci-vm-10-0-154-72.hosted.upshift.rdu2.redhat.com systemd[1]: Started System Security Services Daemon.


Verified with:
# rpm -qa sssd
sssd-1.16.5-10.el7_9.6.x86_64

Dec 02 11:52:39 ci-vm-10-0-153-8.hosted.upshift.rdu2.redhat.com sssd[sssd][7135]: Starting up
Dec 02 11:52:39 ci-vm-10-0-153-8.hosted.upshift.rdu2.redhat.com sssd[be[example1]][7136]: Starting up
Dec 02 11:52:39 ci-vm-10-0-153-8.hosted.upshift.rdu2.redhat.com sssd[pam][7138]: Starting up
Dec 02 11:52:39 ci-vm-10-0-153-8.hosted.upshift.rdu2.redhat.com sssd[nss][7137]: Starting up
Comment 13 errata-xmlrpc 2020-12-15 11:22:17 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (sssd bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2020:5459
Note You need to log in before you can comment on or make changes to this bug.