Red Hat Bugzilla – Bug 1272430
User session open/close counts don't match
Last modified: 2016-07-19 15:06:06 EDT
Description of problem:
The user session open/close message counts in the logwatch 'systemd-user' report section don't match: if a user has run more than one session during the day the number of 'open's often exceeds the number of 'close's, even when the sessions for that user were all interactive and didn't cross the midnight boundary. The same applies to cron jobs: today a job that started at 02:45 and ended less than a minute later showed an open count of 1 and no close count.
while a getmail job that is run at 2,17,32 and 47 minutes past the hour (and so is never running over the midnight boundary) and never runs for more than 5 minutes shows 140 opens and 129 closes.
Is this merely a reporting anomaly or does it indicate a deeper problem?
Version-Release number of selected component (if applicable): -
This behavior first showed up under Fedora 22 and has been shown in every logwatch report since the upgrade. My system is dnf updated on a weekly basis.
Steps to Reproduce:
1. Look at the logwatch report
Something like this:
session opened for user getmail by (uid=0): 140 Time(s)
session closed for user getmail: 129 Time(s)
session closed for user gliding: 2 Time(s)
session closed for user av: 1 Time(s)
session closed for user root: 1 Time(s)
session opened for user av by (uid=0): 1 Time(s)
session opened for user gliding by (uid=0): 1 Time(s)
session opened for user ma by (uid=0): 1 Time(s)
session opened for user root by (uid=0): 1 Time(s)
The open and close counts should be the same except for sessions that were running over midnight and don't run every day.
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
Thank you for reporting this bug and we are sorry it could not be fixed.
This problem has persisted from Fedora 22 through into Fedora 23 and is still currently alive and well. While its not obviously harmful it does show a certain lack of attention to detail by the developer responsible for that code. This would be bad enough if it only appeared when debugging was on, but as logwatch reports every day since I raised the bug have shown mismatched 'session opened' and 'session closed' counts, this doesn't give a good impression....