Suspend to memory lasts 0 seconds

[ahvth]

First of all, thanks for the awesome tool.

Whenever I run sspender, I can never get the machine to suspend for more than 0 seconds, where I'd like it to suspend indefinitely.

Here is the log output for a typical run:

==========|| Reading config file = /etc/sspender.cfg
Getting all the disks attached to the machine: loop0, loop1, loop2, loop3, loop4, sda, sdb, sdc, 

==========|| Loaded configuration from file = /etc/sspender.cfg
ips_to_watch = 
wake_at = 
sleep_mode = mem
check_if_idle_every (minutes) = 1
stop_monitoring_for (minutes) = 5
reset_monitoring_after (minutes) = 1
suspend_after (minutes) = 1

==========|| Using the following validated configuration:

Don't suspend the machine if any of these IPs is online: 
Suspend the machine if all these devices are idle: CPU,
Spin down these drives if they are idle: 
Wake up the machine at the following times: 
Sleep mode is: Suspend to RAM

==========|| Monitoring the machine
=====|| Checking if clients are online | Tue Oct 15 07:03:25 UTC 2019
=====|| Checking if system is idle | Tue Oct 15 07:03:25 UTC 2019
System is not idle (1.00 minutes).
CPU - busy - Load - 1.49%

loop0 - idle  - Load - 0.00%, Read - 0.00KB/s, Written - 0.00KB/s.

loop1 - idle  - Load - 0.00%, Read - 0.00KB/s, Written - 0.00KB/s.

loop2 - idle  - Load - 0.00%, Read - 0.00KB/s, Written - 0.00KB/s.

loop3 - idle  - Load - 0.00%, Read - 0.00KB/s, Written - 0.00KB/s.

loop4 - idle  - Load - 0.00%, Read - 0.00KB/s, Written - 0.00KB/s.

sda - idle  - Load - 0.00%, Read - 0.00KB/s, Written - 0.00KB/s.

sdb - idle  - Load - 0.00%, Read - 0.00KB/s, Written - 0.00KB/s.

sdc - idle  - Load - 0.00%, Read - 0.00KB/s, Written - 2.78KB/s.

System was busy for more than 1 mins, reseting idle timer.
system was idle for more than 1 mins, will suspend the machine.
=====|| Suspending the machine | Tue Oct 15 07:03:25 UTC 2019
Got: current time in minutes (423.00), suspend until(423.00).
Suspending the machine for 86100.00 seconds.
=====|| System returned from suspend | Tue Oct 15 07:03:32 UTC 2019
Suspend output: rtcwake: assuming RTC uses UTC ... , rtcwake: wakeup from "mem" using /dev/rtc0 at Wed Oct 16 06:58:26 2019 , 

If I've misconfigured something, please let me know.

The 0 seconds figure I got from this line Got: current time in minutes (423.00), suspend until(423.00).

[mountassir]

Hi, thanks for opening this ticket.

The task is supposed to suspend the machine for 24 hours if "wake_at" was empty Source-code and it seems like it is doing so as you can see in the logs Suspending the machine for 86100.00 seconds..

rtcwake is also confirming that the resume time was set the following day:
Suspend output: rtcwake: assuming RTC uses UTC ... , rtcwake: wakeup from "mem" using /dev/rtc0 at Wed Oct 16 06:58:26 2019

It sounds like the machine is unable to suspend to RAM, can you please try suspending it manually by running sudo /usr/sbin/rtcwake -m mem -s 60? That will tell us whether this is an issue with sspender or with your machine S3 set up.

[ahvth]

Thanks for getting back to me.

I tried running rtcwake using the command you specified, and the machine was successfully suspended to memory for exactly 60 seconds.

[mountassir]

Interesting, I tried running your exact set up (from what I see from the logs anyway) and my PC does suspend for 24 hours.

• Can you try and set a time in "wake_at" and test with that?
• If possible please attach your sspender.cfg so I can test it in a PC that I know works.

As for your request for being able to suspend indefinitely, rtcwake requires a number of seconds to suspend and I choose 24 hours to begin with. Though now that I think about it, if the user leaves "wake_at" empty, he/she most likely does not want the machine to wake up anytime soon, so I will change that to a period much longer than 24 hours.

[ahvth]

I will give this a shot as soon as I've finished the server's compute tasks for the day.

Regarding the second point, is there any obstacle to using systemd to suspend to memory instead of rtcwake? That should be a good option for true indefinite suspend. I tried doing this in my fork (not committed yet on github) and it works, but i haven't figured out how to resume monitoring after wake.