Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Description of problem:
I have configured the new systemd feature StopIdleSessionSec. And seems to be working because I can see sessions being stopped. Sadly without any evidence why the user session is stopped.
Looking at https://github.com/redhat-plumbers/systemd-rhel8/commit/24439b08e3a3437b423553c385cde1d4cddf18f6#diff-0b375f3118a9ae0b86c5bd218491126a329817a5bfeb41fff8f164b36b00604cR676 the info that a session is idle is logged only on debug level instead of info level that to inform the administrator what is going on.
Can we please adjust the log severity of the idle message to an info level so it is included in journal/syslog so that it is for administrators traceable why sessions are stopped?
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1. Modify /etc/systemd/logind.conf, add 'StopIdleSessionSec=10'
2. sudo systemctl restart systemd-logind
3. Run 'while true; do echo $n; sleep 1; n=$(( n + 1 )); done'
4. Login again
5. Run 'sudo grep -i idle /var/log/messages /var/log/secure'
Actual Result:
- Session correct killed at 10 seconds
- After login again the grep does not give any result (for 'idle' keyword)
Expected results:
Below line logs about idle session, but its only in debug mode, can we get this for info (default) log severity?
log_debug("Session \"%s\" of user \"%s\" is idle, stopping.", s->id, s->user->name);
Additional info:
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 (systemd 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-2023:2985