Bug 2093495

Summary: pam_motd spews errors
Product: Red Hat Enterprise Linux 8 Reporter: Tim Jackson <rpm>
Component: pamAssignee: Iker Pedrosa <ipedrosa>
Status: CLOSED DUPLICATE QA Contact: sssd-qe <sssd-qe>
Severity: low Docs Contact:
Priority: low    
Version: CentOS StreamCC: bstinson, cory.bannister, jwboyer, ksyblast, pbrezina, thalunil-redhat-bugzilla, twaugh
Target Milestone: rcKeywords: Triaged
Target Release: 8.0Flags: pm-rhel: mirror+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-09-12 07:21:39 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 Tim Jackson 2022-06-03 21:59:28 UTC
This bug was initially created as a copy of Bug #1847501

I am copying this bug because: the bug now exists in CentOS Stream 8


Description of problem:

pam_motd spews errors:

sshd[xxx]: pam_motd(sshd:session): pam_motd: error scanning directory /etc/motd.d
sshd[xxx]: pam_motd(sshd:session): pam_motd: error scanning directory /run/motd.d
sshd[xxx]: pam_motd(sshd:session): pam_motd: error scanning directory /usr/lib/motd.d

Was not present in pam-1.3.1-16.el8

Version-Release number of selected component (if applicable):
pam-1.3.1-18.el8.x86_64

Steps to Reproduce:
1. ssh into machine

Expected results:
No error messages in logs

Comment 1 thalunil 2022-06-15 12:49:28 UTC
seems fixed with the current version pam-1.3.1-20.el8.x86_64.rpm

Comment 2 Tim Waugh 2022-06-21 12:41:39 UTC
I still see:

sshd[xxx]: pam_motd(sshd:session): pam_motd: error scanning directory /run/motd.d

with pam-1.3.1-20.el8.x86_64.

I think maybe /usr/lib/tmpfiles.d/pam.conf needs to declare that one?

Comment 3 Iker Pedrosa 2022-06-21 12:50:23 UTC
The issue hasn't been fixed so I assume that thalunil isn't getting any error because the folder exists in their system.

Comment 4 thalunil 2022-06-21 13:21:14 UTC
That's true, problem still there

Comment 5 Iker Pedrosa 2022-09-12 07:21:39 UTC

*** This bug has been marked as a duplicate of bug 2091062 ***