Bug#858143: Gets killed by logind kills user processes
Paul van Tilburg
paulvt at debian.org
Tue May 23 14:57:46 UTC 2017
I would like to report a problem with the fix in 0.9.1-9 and
I hope you would consider reopening this bug report.
The first issue is that it seems that when a user logs in now, the
xrdp-sesman main process is moved to scope of the first session!
(This did not used to happen before.)
$ systemctl status xrdp-sesman.service
● xrdp-sesman.service - xrdp session manager
Loaded: loaded (/lib/systemd/system/xrdp-sesman.service; enabled; vendor preset: enabled)
Active: active (running) since Mon 2017-05-15 10:49:28 CEST; 1 weeks 1 days ago
Main PID: 3050 (xrdp-sesman)
Tasks: 0 (limit: 4915)
‣ 3050 /usr/sbin/xrdp-sesman
SESSION UID USER SEAT TTY
426 1001 paul
c4 1002 other.user
$ systemctl status session-c4.scope
● session-c4.scope - Session c4 of user corry.kosters
Loaded: loaded (/run/systemd/transient/session-c4.scope; transient; vendor preset: enabled)
Active: active (running) since Mon 2017-05-15 10:49:43 CEST; 1 weeks 1 days ago
├─ 3050 /usr/sbin/xrdp-sesman
We have a deployment where we have configured systemd-logind to
kill user process when there are no more sessions for said user (via
both Xrdp and ssh). So, now, not only his/her session is killed but also the
main xrdp-sessman process (!), after which Xrdp becomes unavailable.
A workaround is to login with a user that just disconnects, but that
is not exactly ideal.
A secondary effect of the fix that I see is that loginctl also
only reports a session for the first user that logged in.
For example, see the loginctl output above. The session of my
user (c5) is not visible at all.
Both issues indicate that there is still an issue with properly
registering the sessions. I have confirmed that going back to 0.9.1-7
fixes both issues.
Using the Power of Debian GNU/Linux | E-mail: paulvt at debian.org
Jabber/XMPP: paul at luon.net | GnuPG key ID: 0x50064181
More information about the pkg-remote-team