On Tue, 2023-11-14 at 14:26 +0000, Barry wrote: > > > > On 14 Nov 2023, at 13:52, Patrick O'Callaghan > > <pocallaghan@xxxxxxxxx> wrote: > > > > My system (both F38 and now F39) reboots itself every morning at > > 8am, > > yet nothing in the cron configuration is telling it to do that and > > I > > don't see anything obvious in the journal to cause it. > > > > How can I figure out what is triggering this? I know the > > description is > > vague, but there it is. > > > > Check for systemd timers as well. systemctl list-timers. None of them are scheduled for near that time. > > Does the journal show system shutdown was requested? No. Here is a snippet of today's journal: Nov 14 07:51:03 Bree systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully. Nov 14 07:51:17 Bree systemd[1]: plocate-updatedb.service: Deactivated successfully. Nov 14 07:51:17 Bree systemd[1]: Finished plocate-updatedb.service - Update the plocate database. Nov 14 07:51:17 Bree systemd[1]: plocate-updatedb.service: Consumed 9.667s CPU time. Nov 14 07:52:29 Bree sshd[73704]: fatal: Timeout before authentication for 43.153.185.216 port 51704 -- Boot c04ce0f9f0b94587b88a1f8c0a2c4659 -- Nov 14 08:00:27 Bree kernel: microcode: updated early: 0x19 -> 0x21, date = 2019-02-13 Nov 14 08:00:27 Bree kernel: Linux version 6.5.11-300.fc39.x86_64 (mockbuild@d23353abed4340e492bce6e111e27898) (gcc (GCC) 13.2.1 20231011 (Red Hat 13.2.1-4), GNU ld version 2.40-1> Nov 14 08:00:27 Bree kernel: Command line: BOOT_IMAGE=(hd2,gpt2)/vmlinuz-6.5.11-300.fc39.x86_64 root=UUID=8e1f7af4-c0bf-434e-b1c4-a9af2c810d56 ro rootflags=subvol=root modprobe.bl> Nov 14 08:00:27 Bree kernel: BIOS-provided physical RAM map: The last entry before reboot is irrelevant (I run a small web server and fail2ban is constantly fending off attempted logins, mainly from China. Every day I'm getting the same thing at the same time. Full disclosure: I have a nightly hibernation/resume procedure which wakes the machine at 07:50, using a smart power plug. The journal shows that this is working as expected, and AFAIK is unrelated to the reboot. I've triple-checked the smart plug settings and toggled it manually to make sure. poc _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
