[Solved] Odd message "The system will suspend now!" in SSH even though suspend is disabled

[olignyf]

I just installed Debian 12.
I did the following as per the doc https://wiki.debian.org/Suspend

Code: Select all

systemctl mask sleep.target suspend.target hibernate.target hybrid-sleep.target

Then rebooted.
The system successfully stays awake.

However my SSH sessions receive this unexpected message

Code: Select all

Broadcast message from Debian-gdm@angel on tty1 (Sat 2023-09-09 11:00:59 EDT):

The system will suspend now!

The SSH session stays alive though.

[lindi]

That just means that gnome was about to call the API that suspends the system. It does not know that it is disabled

[lindi]

Masking that service might not be the best way to disable suspend.

[olignyf]

I found the solution. This method works better and doesn't have the spurious message on connected SSH clients.

Create /etc/systemd/sleep.conf.d/nosuspend.conf as

Code: Select all

[Sleep]
AllowSuspend=no
AllowHibernation=no
AllowSuspendThenHibernate=no
AllowHybridSleep=no

They should probably edit the documentation and swap both solution so this one is the first one and not marked as an "alternative"

[Aki]

Hello,

I found the solution. This method works better and doesn't have the spurious message on connected SSH clients.

Create /etc/systemd/sleep.conf.d/nosuspend.conf as

Code: Select all

[Sleep]
AllowSuspend=no
AllowHibernation=no
AllowSuspendThenHibernate=no
AllowHybridSleep=no

They should probably edit the documentation and swap both solution so this one is the first one and not marked as an "alternative"

Thank you for sharing the solution. Please update the discussion by adding the tag "[Solved]" to the beginning of the subject of the first post. Happy Debian ! :-)

[olignyf]

Thank you for sharing the solution. Please update the discussion by adding the tag "[Solved]" to the beginning of the subject of the first post. Happy Debian !

Thanks Aki! Shouldn't the documentation be updated for it to be considered solved? How can I submit a correction to the doc?

[Aki]

Hello,

Thank you for sharing the solution. Please update the discussion by adding the tag "[Solved]" to the beginning of the subject of the first post. Happy Debian ! :-)

Thanks Aki! Shouldn't the documentation be updated for it to be considered solved? How can I submit a correction to the doc?

I suggested to mark the discussion as "solved" since you "solved" your issue: the suspension message does not appear in ssh sessions.

The manual page for systemd-sleep.conf [1] already explains how to configure its parameters and systemd-sleep [2] explains the service. The documentation seems fine to me.

As already user @lindi pointed out in previous posts, you disabled the suspension service, but you didn't identified what triggers it. Perhaps this would merit further investigation on your part if you are interested. I'm not a gnome user, but a quick search landed here (as an example):

• GNOME suspends after 15 minutes of user inactivity, even on AC power

• applets-inhibit

---
[1] https://manpages.debian.org/bookworm/systemd/systemd-sleep.conf.5.en.html
[2] https://manpages.debian.org/bookworm/systemd/systemd-sleep.8.en.html

[olignyf]

The documentation seems fine to me.

The documentation list the problematic method first and the newer working method secondly as an alternative... it should be reversed.

[eccenux]

What is interesting is that when you upgrade from e.g. Debian 10 to 12 the system will suspend when you are reading changelogs or make decisions. The system is suspended without any warning! Without any message visible in SSH console. This is bad. VERY BAD. It made me drive to work today... I blamed UPS initially (mostly because I don't have a screen on this computer)... So that was "fun". Never would've thought this could be intentional (to suspend during upgrade I mean).

When this happens during upgrade you seem to be able to join apt process (like `sudo apt full-upgrade`) by using:

Code: Select all

sudo killall apt
sudo dpkg --configure -a

This makes apt continue from the place where there was a question about configuration changes.

[olignyf]

(...)
As already user @lindi pointed out in previous posts, you disabled the suspension service, but you didn't identified what triggers it. Perhaps this would merit further investigation on your part if you are interested. I'm not a gnome user, but a quick search landed here (as an example):

• GNOME suspends after 15 minutes of user inactivity, even on AC power

• applets-inhibit

---
[1] https://manpages.debian.org/bookworm/systemd/systemd-sleep.conf.5.en.html
[2] https://manpages.debian.org/bookworm/systemd/systemd-sleep.8.en.html

I'm not sure why you guys mention Gnome. I'm not using Gnome. The issue occurs when leaving the computer idle at login screen then doing remote login SSH session to the system. What additional investigation is needed? Adjusting the documentation seems to be the next step at this point. I updated the topic to [Solved].