Fedora 43 keeps randomly restarting

Ask Fedora
,
1

Hi everyone,

My Install of Fedora 43 KDE edition keeps randomly restarting itself. This has been happening for a while and usually just after its been running for a good while. Usually the only thing i have open is Obsidian as a appimage, Firefox and maybe the Dolphin File Manager.

I ran $ journalctl -b -1 -p 3, with this being the output at time of the crash:

Jan 14 13:00:42 fedora anacron[21708]: Can't find sendmail at /usr/sbin/sendmail, not mailing output
Jan 14 13:00:42 fedora dbus-broker-launch[882]: Activation request for 'org.freedesktop.Avahi' failed.
Jan 14 13:00:42 fedora dbus-broker-launch[882]: Activation request for 'org.bluez' failed.
Jan 14 13:00:42 fedora dbus-broker-launch[882]: Activation request for 'org.freedesktop.nm_dispatcher' failed.
Jan 14 13:00:42 fedora dbus-broker-launch[882]: Activation request for 'org.bluez' failed.
Jan 14 13:00:42 fedora dbus-broker-launch[882]: Activation request for 'org.bluez' failed.
Jan 14 13:00:43 fedora dbus-broker-launch[1903]: Activation request for 'org.bluez.obex' failed.
Jan 14 13:00:43 fedora kwin_wayland[2154]: Applying output configuration failed!
Jan 14 13:00:43 fedora systemd-coredump[26812]: Failed to send coredump datagram: Connection reset by peer
Jan 14 13:00:44 fedora dbus-broker-launch[882]: Activation request for 'org.freedesktop.nm_dispatcher' failed.
Jan 14 13:00:44 fedora dbus-broker-launch[882]: Activation request for 'org.freedesktop.nm_dispatcher' failed.
Jan 14 13:00:44 fedora dbus-broker-launch[882]: Activation request for 'org.freedesktop.nm_dispatcher' failed.
Jan 14 13:00:44 fedora kernel: watchdog: watchdog0: watchdog did not stop!

However i have to admit that im not particularly well versed in Linux/Fedora to figure out what could have caused the crash.

I would appreciate some help from People more knowledgeable then me, thanks in advance!

2

Post the (full) journalctl output from around 30 seconds prior to this. You can use the --since and --until flags for this. See man journalctl for specifics on how to use these.

1 Like
3

Like this?

4 
Jan 14 13:00:42 fedora systemd-logind[967]: The system will reboot now!
Jan 14 13:00:42 fedora systemd-logind[967]: System is rebooting.
Jan 14 13:00:42 fedora sddm-helper[1777]: Signal received: SIGTERM

Looks like something is intentionally triggering a reboot. Perhaps one of your cron jobs does this?

1 Like
5

I wouldnt have set it up like that intentionally, however this at least helps me to continue troubleshooting. Thanks!

1 Like
6

Right - I’m guessing a bit, but it’s probably worth having a look at what happens in your cron job.

The crashes later in your log are probably triggered by the reboot, rather than vice versa. (i.e. the crashes happen because processes don’t shut down gracefully when the system is shutting down ready for reboot.)

1 Like
7

That does make sense. Again my cron job was basically empty, i did disable it tho. If it happens again ill continue searching but here’s hoping!

8

2 Week Update: I hadnt had any crashes so far, so maybe the cron job i i disabled was the culprit after all. I cant be 100% sure obviously for now they are gone.