All sessions appear in closing state, here's another one:
$ loginctl show-session 77
Id=77
User=1004
Name=raccess
Timestamp=Чт 2018-03-29 20:30:02 MSK
TimestampMonotonic=2363185101
VTNr=0
Remote=yes
RemoteHost=216.126.59.227
Service=sshd
Scope=session-77.scope
Leader=3389
Audit=77
Type=tty
I am having the same issue on Ubuntu 16.04 now. All sessions appear to
be for one user that is used for incoming ssh connections for rsync.
Here's an example:
$ loginctl show-session 59
Id=59
User=1004
Name=raccess
Timestamp=Чт 2018-03-29 20:20:03 MSK
TimestampMonotonic=1763641802
VTNr=0
This only seems to happen for us, on 14.04 LTS at least, if the package
'systemd' is installed rather than merely libsystemd-{daemon,login}0,
and systemd-{services,shim}. It could be that a workaround is simply to
remove the 'systemd' package, assuming it's not required for your
particular setup.
We have same issue :(
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd-shim in Ubuntu.
https://bugs.launchpad.net/bugs/1426362
Title:
logind session files fill up /run space
Status in systemd-shim package in
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: systemd-shim (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd-shim in Ubuntu.
I'm noticing this as an issue as well. My scenario is in using Fabric or
Ansible to do deployments. A large number of these dangling SSH files
are in the /run/systemd/sessions/ folder and eventually cause the out
of disk space issue.
--
You received this bug notification because you are a member
** Package changed: systemd (Ubuntu) = systemd-shim (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd-shim in Ubuntu.
https://bugs.launchpad.net/bugs/1426362
Title:
logind session files fill up /run space
The server (vm) used as a management gateway to other service. Sessions
opened by SSH. Remote machine opens a SSH connection with a key, by SSH
force command, a python script opens, do the stuffs, and exits.
Sessions are in 'closing' state, but no processes (not even zombies) are
exist under
It should remove them, yes. I wonder if all these sessions are still
open, i. e. are there any leftover processes in them? Can you please
give me the output of loginctl, and then loginctl id for a few
session IDs? (local ones look like c2, remote ones should just be a
number).
** Summary changed:
I. e. it should remove them as soon as the sessions are actually closed.
Otherwise, if you log out, they merely go into state closing, and wait
until all remaining processes are going away. If you start screen
sessions or other background jobs, they'll stay around for those.
--
You received this
10 matches
Mail list logo
