Re: Unknown key name 'StopIdleSessionSec' in section 'Login'

[Lennart Poettering <lennart@xxxxxxxxxxxxxx>]

On Mi, 23.10.24 12:23, David (info@xxxxxxxxxxxxxxxx) wrote:

> Hello, from a novice at system administration and systemd.
>
> A week ago, I installed Google Chrome on a Debian 11 VPS to get access to a headless browser. Soon afterward, ConfigServer (CSF) began sending alerts that 2 processes were exceeding the limit. These 2 processes are:
>
> /lib/systemd/systemd —user
> (sd-pam)
>
> The VPS only has two (reseller) users that these processes are running under.
>
> Searching around, I found an article (*1) that seemed to address the situation. In another article (*2), I found the configuration file, incidentally, with every key commented out.
>
> In this config file: /etc/systemd/logind.conf, I added 'StopIdleSessionSec=600’, then restarted logind with:
>
> # systemctl restart systemd-logind
>
> And checked for status with:
>
> # journalctl -u systemd-logind
>
> wherein, the following lines are at the end:
>
> Oct 23 11:35:39 vps.lan-software.com systemd[1]: Stopping User Login Management...
> Oct 23 11:35:39 vps.lan-software.com systemd[1]: systemd-logind.service: Succeeded.
> Oct 23 11:35:40 vps.lan-software.com systemd[1]: Stopped User Login Management.
> Oct 23 11:35:41 vps.lan-software.com systemd[1]: Starting User Login Management...
> Oct 23 11:35:41 vps.lan-software.com systemd-logind[94302]: /etc/systemd/logind.conf:43: Unknown key name 'StopIdleSessionSec' in section 'Login', ignoring
> Oct 23 11:35:41 vps.lan-software.com systemd-logind[94302]: System
> has /dev/tty0 but not /sys/class/tty/tty0/active which is broken,
> ignoring: No such file or directory

This must be a very broken or very old system given this log line.

If it's a really old system, not that StopIdleSessionSec= has been
added in systemd v252 only, I'd guess your version is older. But you
didn't specify which version you are using.

> Oct 23 11:35:41 vps.lan-software.com systemd[1]: Started User Login Management.
> Oct 23 11:35:41 vps.lan-software.com systemd-logind[94302]: New seat seat0.
> Oct 23 11:35:41 vps.lan-software.com systemd-logind[94302]: New session 2266973 of user root.
>
> I think the Chrome installation did something that is causing systemd to start a session, but not close it.
>
> How can I get these 2 processes to shutdown?

They are part of the per-user service manager we are maintaining. They
go away once the user fully logged out, after a brief time-out (which
can be controlled via UserStopDelaySec= (only since v240).

Lennart

--
Lennart Poettering, Berlin