touch-packages team mailing list archive

[Martin Pitt <martin.pitt@xxxxxxxxxx>]

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:

- systemd session files fills up space
+ logind session files fill up /run space

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1426362

Title:
  logind session files fill up /run space

Status in systemd package in Ubuntu:
  New

Bug description:
  Under Ubuntu 14.10 (server), systemd fills up /run/systemd/sessions directory with files.
  The files are 240-260 bytes, but there are many
   As per default install, /run is on tmpfs with 50 MB size. After a couple of days, /run/ runs out of free space, which can cause not so funny errors, like failed kernel update (kernel postinst tries to create files here, then fails)

  As I see, thesefiles are releated to ssh sesssions, and yes there are
  plenty SSH connection to this host. Shouldn't systemd remove these old
  session files?

  # lsb_release -rd
  Description:    Ubuntu 14.10
  Release:        14.10

  # apt-cache policy systemd
  systemd:
    Installed: 208-8ubuntu8.2
    Candidate: 208-8ubuntu8.2
    Version table:
   *** 208-8ubuntu8.2 0
          500 http://hu.archive.ubuntu.com/ubuntu/ utopic-updates/main amd64 Packages
          100 /var/lib/dpkg/status
       208-8ubuntu8 0
          500 http://hu.archive.ubuntu.com/ubuntu/ utopic/main amd64 Packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1426362/+subscriptions