I have 30 23 * * * /usr/sbin/rtcwake -s 23400 -m mem
in my root crontab.
This runs at 23:30 and suspends the server and wakes it at 06:00.
As a part of debugging a problem (the server doesn't seem to reconnect to my network on awakening) I checked out the logs using journalctl. There I see something confusing: It says "stopping disk", "Preparing to enter system sleep state S3" and "CPU 1 is now offline" in the morning (when I expected it to wake up) and not in the evening. (logs below)
My question: Is this just faulty logging (i.e. everything is in fact in order and it just happens to be the case that the logs are for some reason shifted to the morning) or is this an indication of the server not entering sleep correctly?
jan 08 06:00:02 vivo kernel: sd 1:0:0:0: [sdb] Starting disk
jan 08 06:00:02 vivo kernel: sd 0:0:0:0: [sda] Starting disk
jan 08 06:00:02 vivo kernel: rtlwifi: rtlwifi: wireless switch is on
jan 08 06:00:02 vivo kernel: ACPI: PM: Waking up from system sleep state S3
jan 08 06:00:02 vivo kernel: CPU3 is up
jan 08 06:00:02 vivo kernel: smpboot: Booting Node 0 Processor 3 APIC 0x3
jan 08 06:00:02 vivo kernel: CPU2 is up
jan 08 06:00:02 vivo kernel: smpboot: Booting Node 0 Processor 2 APIC 0x1
jan 08 06:00:02 vivo kernel: CPU1 is up
jan 08 06:00:02 vivo kernel: smpboot: Booting Node 0 Processor 1 APIC 0x2
jan 08 06:00:02 vivo kernel: x86: Booting SMP configuration:
jan 08 06:00:02 vivo kernel: Enabling non-boot CPUs ...
jan 08 06:00:02 vivo kernel: ACPI: PM: Restoring platform NVS memory
jan 08 06:00:02 vivo kernel: ACPI: PM: Low-level resume complete
jan 08 06:00:02 vivo kernel: smpboot: CPU 3 is now offline
jan 08 06:00:02 vivo kernel: smpboot: CPU 2 is now offline
jan 08 06:00:02 vivo kernel: smpboot: CPU 1 is now offline
jan 08 06:00:02 vivo kernel: Disabling non-boot CPUs ...
jan 08 06:00:02 vivo kernel: ACPI: PM: Saving platform NVS memory
jan 08 06:00:02 vivo kernel: ACPI: PM: Preparing to enter system sleep state S3
jan 08 06:00:02 vivo kernel: sd 1:0:0:0: [sdb] Stopping disk
jan 08 06:00:02 vivo kernel: sd 0:0:0:0: [sda] Stopping disk
jan 08 06:00:02 vivo kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache
jan 08 06:00:02 vivo kernel: sd 1:0:0:0: [sdb] Synchronizing SCSI cache
jan 08 06:00:02 vivo kernel: printk: Suspending console(s) (use no_console_suspend to debug)
jan 08 06:00:02 vivo kernel: Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
jan 08 06:00:02 vivo kernel: OOM killer disabled.
jan 08 06:00:02 vivo kernel: Freezing user space processes ... (elapsed 0.001 seconds) done.
jan 07 23:30:01 vivo kernel: Filesystems sync: 0.002 seconds
jan 07 23:30:01 vivo kernel: PM: suspend entry (deep)
jan 07 23:30:01 vivo CRON[5382]: pam_unix(cron:session): session closed for user root
jan 07 23:30:01 vivo CRON[5385]: (root) CMD ([ -x /etc/init.d/anacron ] && if [ ! -d /run/systemd/system ]; then /usr/sbin/invoke-rc.d anacron start >/dev/>
jan 07 23:30:01 vivo CRON[5384]: (root) CMD (/usr/sbin/rtcwake -s 23400 -m mem)
jan 07 23:30:01 vivo CRON[5383]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
jan 07 23:30:01 vivo CRON[5382]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)