Bug 1894540

Summary:	sssd component logging is now too generic in syslog/journal
Product:	Red Hat Enterprise Linux 8	Reporter:	Alexey Tikhonov <atikhono>
Component:	sssd	Assignee:	Alexey Tikhonov <atikhono>
Status:	CLOSED ERRATA	QA Contact:	Madhuri <mupadhye>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	8.3	CC:	dlavu, grajaiya, jhrozek, lslebodn, mzidek, pbrezina, sgoveas, tscherf
Target Milestone:	rc	Keywords:	Triaged
Target Release:	---	Flags:	pm-rhel: mirror+
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	sync-to-jira qetodo
Fixed In Version:	sssd-2.4.0-3.el8	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-05-18 15:03:59 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Alexey Tikhonov 2020-11-04 13:22:15 UTC

This bug was initially created as a copy of Bug #1888409

I am copying this bug because: to track fix for RHEL8



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-11-05 11:19:56 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 7 Madhuri 2020-12-17 10:05:10 UTC

Verified with
# rpm -qa sssd
sssd-2.4.0-3.el8.x86_64

-- Unit sssd.service has begun starting up.
Dec 17 09:58:37 hostname3 sssd[sssd][19901]: Starting up
Dec 17 09:58:37 hostname3 sssd[be[implicit_files]][19902]: Starting up
Dec 17 09:58:37 hostname3 sssd[be[example1]][19903]: Starting up
Dec 17 09:58:37 hostname3 sssd[pam][19905]: Starting up
Dec 17 09:58:37 hostname3 sssd[nss][19904]: Starting up
Dec 17 09:58:37 hostname3 systemd[1]: Started System Security Services Daemon.
-- Subject: Unit sssd.service has finished start-up

Comment 9 errata-xmlrpc 2021-05-18 15:03:59 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-2021:1666