Could be this bug https://github.com/systemd/systemd/issues/8672
-- 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/2020177 Title: Leaking sessions in pam_systemd Status in systemd package in Ubuntu: Incomplete Bug description: May 19 12:38:38 s20.wr0.ru sshd[3793128]: pam_systemd(sshd:session): Failed to create session: Maximum number of sessions (8192) reached, refusing further sessions. # loginctl list-sessions|wc -l 8195 # loginctl session-status 302548700 302548700 - topaz (450) Since: Tue 2022-10-18 09:29:02; 7 months 0 days ago Leader: 2637625 Remote: 92.42.15.122 Service: sshd; type tty; class user State: closing Unit: session-302548700.scope # ps axf|wc -l 72 The only way I could figure to fix this is to reboot. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemd 245.4-4ubuntu3.21 Uname: Linux 4.15.0 x86_64 ApportVersion: 2.20.11-0ubuntu27.26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDmesg: Date: Fri May 19 12:58:47 2023 Lsusb: Error: [Errno 2] No such file or directory: 'lsusb' Lsusb-t: Error: [Errno 2] No such file or directory: 'lsusb' Lsusb-v: Error: [Errno 2] No such file or directory: 'lsusb' ProcEnviron: SHELL=/bin/bash LANG=en_US.utf8 TERM=xterm-256color PATH=(custom, no user) ProcInterrupts: Error: [Errno 2] No such file or directory: '/proc/interrupts' ProcKernelCmdLine: quiet SourcePackage: systemd UpgradeStatus: Upgraded to focal on 2022-01-26 (478 days ago) acpidump: mtime.conffile..etc.systemd.journald.conf: 2022-08-19T16:13:27.570934 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2020177/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
