Bug 1229724
| Summary: | pam_lastlog(sshd:session): unable to open /var/log/lastlog: No such file or directory | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Jan Pazdziora (Red Hat) <jpazdziora> |
| Component: | rhel-server-atomic | Assignee: | Colin Walters <walters> |
| Status: | CLOSED WONTFIX | QA Contact: | atomic-bugs <atomic-bugs> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 7.1 | CC: | jpazdziora, miabbott, walters |
| Target Milestone: | rc | Keywords: | Extras |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2020-12-15 07:34:45 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
Jan Pazdziora (Red Hat)
2015-06-09 14:01:50 UTC
On a freshly booted RHELAH 7.4.5 system, I can see both errors about the missing 'lastlog' file and a message saying that it was created. # journalctl | grep lastlog Feb 12 15:34:44 micah-rhelah-vm0212a sshd[13484]: pam_lastlog(sshd:session): unable to open /var/log/lastlog: No such file or directory Feb 12 15:34:44 micah-rhelah-vm0212a sshd[13484]: lastlog_openseek: Couldn't stat /var/log/lastlog: No such file or directory Feb 12 15:34:44 micah-rhelah-vm0212a sshd[13484]: lastlog_openseek: Couldn't stat /var/log/lastlog: No such file or directory Feb 12 15:34:46 micah-rhelah-vm0212a su[13508]: pam_lastlog(su-l:session): file /var/log/lastlog created It appears that the 'lastlog' file hasn't been created before the first SSH login, but when I escalate privileges via 'sudo su -' this causes the file to be created. Interestingly, if I do the same thing with a freshly provisioned RHEL 7.4 Server system, there are no errors in the journal about the 'lastlog' file. From the compose logs for the RHELAH content, I do see the following: ... Mutating /usr/lib/os-release Executing postprocessing script 'treecompose-post-7.4.sh' + cp -f /usr/lib/locale/locale-archive /usr/lib/locale/locale-archive.tmpl + build-locale-archive Finished postprocessing script 'treecompose-post-7.4.sh' Initializing rootfs Moving /usr to target Copying toplevel compat symlinks Migrating /usr/etc/passwd to /usr/lib/ Migrating /usr/etc/group to /usr/lib/ Ignoring non-directory/non-symlink '/var/log/tallylog' Ignoring non-directory/non-symlink '/var/log/grubby_prune_debug' Ignoring non-directory/non-symlink '/var/log/lastlog' ... And those three files under /var/log are not present on a freshly provisioned RHELAH host. Colin, is this something that should be changed as part of our compose process? Seems like having '/var/log/lastlog' present on a fresh host would be important for keeping parity with RHEL Server. After evaluating this issue, there are no plans to address it further or fix it in an upcoming release. Therefore, it is being closed. If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened. The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days |