[systemd-bugs] [Bug 89024] New: logind session gets stuck semi-often
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Sat Feb 7 12:49:16 PST 2015
https://bugs.freedesktop.org/show_bug.cgi?id=89024
Bug ID: 89024
Summary: logind session gets stuck semi-often
Product: systemd
Version: unspecified
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: general
Assignee: systemd-bugs at lists.freedesktop.org
Reporter: marius.vollmer at redhat.com
QA Contact: systemd-bugs at lists.freedesktop.org
systemd-216-17.fc21.x86_64
In our testsuite, we can fairly regularly observe sessions stuck in the
'closing' state without any processes in them:
3 - admin (1000)
Since: Sat 2015-02-07 19:35:01 EET; 4min 41s ago
Leader: 782
TTY: cockpit-782
Remote: 10.111.111.200
Service: cockpit; type tty; class user
State: closing
Unit: session-3.scope
<empty>
As far as I can tell, this state persists indefinitely. "loginctl
terminate-session 3" will remove the session immediately.
The session is created by our own code. The journal shows these messages:
Feb 07 16:57:08 localhost.localdomain systemd-logind[320]: New session 3 of
user admin.
Feb 07 16:57:08 localhost.localdomain systemd[786]:
pam_unix(systemd-user:session): session opened for user admin by (uid=0)
...
Feb 07 16:57:10 localhost.localdomain cockpit-session[781]:
pam_unix(cockpit:session): session closed for user admin
Note that systemd seems to open the session, but cockpit-session seems to close
it. (If I have copied the right lines.)
Any hints for debugging this would be appreciated.
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/systemd-bugs/attachments/20150207/553c2891/attachment.html>
More information about the systemd-bugs
mailing list