MicroOS servers stop working randomly after auto-updates

I have two servers running MicroOS:

#1) Virtual machine at Hetzner
#2) Physical server next to my table

Both servers stop running randomly one or the other day. It looks like they are running for one or two days and then crash after an auto-update:

#1) Does not respond to ICMP ping or the virtual console (no output at all).
#2) Does not respond to ICMP ping, no ARP entry in the local network and the connected monitor stays black.

The physical server is the new one and until now I thought I misconfigured the virtual machine, but the physical server behaves exacly the same. So I checked the logs:

I can see that the server auto-updates at 00:19:

cat /var/log/zypper.log:

2026-03-19 00:20:22 <1> cl2-standalone2(78314) [Progress++] progressdata.cc(report):75 {#58|Executing triggerpostun script for: systemd-259.5-1.1.x86_64} START
2026-03-19 00:20:22 <1> cl2-standalone2(78314) [Progress++] progressdata.cc(report):95 {#58|Executing triggerpostun script for: systemd-259.5-1.1.x86_64} END
2026-03-19 00:20:22 <1> cl2-standalone2(78314) [zypp::exec++] abstractspawnengine.cc(checkStatus):189 Pid 78437 successfully completed
2026-03-19 00:20:22 <1> cl2-standalone2(78314) [Progress++] progressdata.cc(report):75 {#59|Executing triggerpostun script for: systemd-259.5-1.1.x86_64} START
2026-03-19 00:20:22 <1> cl2-standalone2(78314) [Progress++] progressdata.cc(report):95 {#59|Executing triggerpostun script for: systemd-259.5-1.1.x86_64} END
2026-03-19 00:20:22 <1> cl2-standalone2(78314) [zypp] TargetImpl.cc(RunUpdateScripts):643 Looking for new update scripts in (/tmp/transactional-update-IZ1KXn)/var/adm/update-scripts
2026-03-19 00:20:22 <1> cl2-standalone2(78314) [zypp-core] PathInfo.cc(dirForEachImpl):574 readdir /tmp/transactional-update-IZ1KXn/var/adm/update-scripts
2026-03-19 00:20:22 <1> cl2-standalone2(78314) [zypp] TargetImpl.cc(RunUpdateMessages):878 Looking for new update messages in (/tmp/transactional-update-IZ1KXn)/var/adm/update-messages
2026-03-19 00:20:22 <1> cl2-standalone2(78314) [zypp-core] PathInfo.cc(dirForEachImpl):574 readdir /tmp/transactional-update-IZ1KXn/var/adm/update-messages
2026-03-19 00:20:22 <1> cl2-standalone2(78314) [zypp-core] PathInfo.cc(clean_dir):474 clean_dir /tmp/transactional-update-IZ1KXn/var/cache/zypp/packages/repo-oss/.preload
2026-03-19 00:20:22 <1> cl2-standalone2(78314) [ZYPP_MEDIA_CURL] request.cc(~NetworkRequestPrivate):86 0x5641505497c0 curl_easy_cleanup
2026-03-19 00:20:22 <1> cl2-standalone2(78314) [ZYPP_MEDIA_CURL] request.cc(~NetworkRequestPrivate):86 0x56415054dbb0 curl_easy_cleanup
2026-03-19 00:20:22 <1> cl2-standalone2(78314) [ZYPP_MEDIA_CURL] request.cc(~NetworkRequestPrivate):86 0x564150552000 curl_easy_cleanup
2026-03-19 00:20:22 <1> cl2-standalone2(78314) [ZYPP_MEDIA_CURL] request.cc(~NetworkRequestPrivate):86 0x5641505562e0 curl_easy_cleanup
2026-03-19 00:20:22 <1> cl2-standalone2(78314) [ZYPP_MEDIA_CURL] request.cc(~NetworkRequestPrivate):86 0x56415055a820 curl_easy_cleanup
2026-03-19 00:20:22 <1> cl2-standalone2(78314) [zypp::fetcher++] MediaSetAccess.cc(release):545 Releasing all media IDs held by this MediaSetAccess
2026-03-19 00:20:22 <1> cl2-standalone2(78314) [zypp::plugin++] PluginExecutor.cc(send):89 +++++++++++++++ send PluginFrame[COMMITEND](0){1705}
2026-03-19 00:20:22 <1> cl2-standalone2(78314) [zypp::plugin++] PluginScript.cc(send):292 PluginScript[78356] /usr/lib/zypp/plugins/commit/btrfs-defrag-plugin.sh ->send PluginFrame[COMMITEND](0){1705}
2026-03-19 00:20:22 <1> cl2-standalone2(78314) [zypp::plugin++] PluginScript.cc(receive):441 PluginScript[78356] /usr/lib/zypp/plugins/commit/btrfs-defrag-plugin.sh <-PluginFrame[ERROR](0){0}
2026-03-19 00:20:22 <2> cl2-standalone2(78314) [zypp::plugin] PluginExecutor.cc(doSend):144 Bad plugin response from PluginScript[78356] /usr/lib/zypp/plugins/commit/btrfs-defrag-plugin.sh: PluginFrame[ERROR](0){0}
2026-03-19 00:20:22 <2> cl2-standalone2(78314) [zypp::plugin] PluginExecutor.cc(doSend):145 (Expected ACK or _ENOMETHOD)
2026-03-19 00:20:22 <1> cl2-standalone2(78314) [zypp::plugin++] PluginScript.cc(close):249 Close:PluginScript[78356] /usr/lib/zypp/plugins/commit/btrfs-defrag-plugin.sh
2026-03-19 00:20:22 <1> cl2-standalone2(78314) [zypp::plugin++] PluginScript.cc(send):292 PluginScript[78356] /usr/lib/zypp/plugins/commit/btrfs-defrag-plugin.sh ->send PluginFrame[_DISCONNECT](0){0}
2026-03-19 00:20:22 <2> cl2-standalone2(78314) [zypp::plugin] PluginScript.cc(receive):398 Unexpected EOF
2026-03-19 00:20:22 <5> cl2-standalone2(78314) [zypp-core] Exception.cc(log):245 PluginScript.cc(receive):399 THROW:    Receive: script died unexpectedly
2026-03-19 00:20:22 <5> cl2-standalone2(78314) [zypp-core] Exception.cc(log):245 History:
2026-03-19 00:20:22 <5> cl2-standalone2(78314) [zypp-core] Exception.cc(log):245  - [0-Success]
2026-03-19 00:20:22 <2> cl2-standalone2(78314) [zypp::exec] abstractspawnengine.cc(checkStatus):182 Pid 78356 exited with status 1
2026-03-19 00:20:22 <1> cl2-standalone2(78314) [zypp::plugin++] PluginScript.cc(close):271 PluginScript[-1] /usr/lib/zypp/plugins/commit/btrfs-defrag-plugin.sh -> [1] Command exited with status 1.
2026-03-19 00:20:22 <1> cl2-standalone2(78314) [zypp::plugin++] PluginScript.cc(send):292 PluginScript[78367] /usr/lib/zypp/plugins/commit/boot-plugin ->send PluginFrame[COMMITEND](0){1705}
2026-03-19 00:20:22 <2> cl2-standalone2(78314) [PLUGIN] PluginScript.cc(~PluginDumpStderr):86 ! INFO:(boot-plugin):COMMITEND BEGIN
2026-03-19 00:20:22 <2> cl2-standalone2(78314) [PLUGIN] PluginScript.cc(~PluginDumpStderr):86 ! DEBUG:(boot-plugin): loading zypp-boot-plugin.conf from /usr/etc/zypp and /etc/zypp
2026-03-19 00:20:22 <2> cl2-standalone2(78314) [PLUGIN] PluginScript.cc(~PluginDumpStderr):86 ! DEBUG:(boot-plugin):  --- Found package grub2
2026-03-19 00:20:22 <2> cl2-standalone2(78314) [PLUGIN] PluginScript.cc(~PluginDumpStderr):86 ! DEBUG:(boot-plugin):      Found for level: reboot
2026-03-19 00:20:22 <2> cl2-standalone2(78314) [PLUGIN] PluginScript.cc(~PluginDumpStderr):86 ! INFO:(boot-plugin):Set 'reboot' in /run/reboot-needed
2026-03-19 00:20:22 <2> cl2-standalone2(78314) [PLUGIN] PluginScript.cc(~PluginDumpStderr):86 ! INFO:(boot-plugin):COMMITEND END
2026-03-19 00:20:22 <1> cl2-standalone2(78314) [zypp::plugin++] PluginScript.cc(receive):441 PluginScript[78367] /usr/lib/zypp/plugins/commit/boot-plugin <-PluginFrame[ACK](0){0}
2026-03-19 00:20:22 <1> cl2-standalone2(78314) [zypp::plugin++] PluginExecutor.cc(send):98 --------------- send PluginFrame[COMMITEND](0){1705}
2026-03-19 00:20:22 <1> cl2-standalone2(78314) [zypp-core] PathInfo.cc(dirForEachImpl):574 readdir /tmp/transactional-update-IZ1KXn/etc/products.d
2026-03-19 00:20:22 <1> cl2-standalone2(78314) [zypp] TargetImpl.cc(buildCache):1128 Read cookie: /tmp/transactional-update-IZ1KXn/var/cache/zypp/solv/@System/cookie{- 0644 0/0 size 76}
2026-03-19 00:20:22 <1> cl2-standalone2(78314) [zypp] TargetImpl.cc(buildCache):1135 Read cookie: /tmp/transactional-update-IZ1KXn/var/cache/zypp/solv/@System/cookie says: outdated
2026-03-19 00:20:22 <1> cl2-standalone2(78314) [zypp-core] TmpPath.cc(Impl):54 /tmp/transactional-update-IZ1KXn/var/cache/zypp/solv/@System/solvmZwBtC
2026-03-19 00:20:22 <1> cl2-standalone2(78314) [zypp::exec++] forkspawnengine.cc(start):274 Executing 'rpmdb2solv' '-r' '/tmp/transactional-update-IZ1KXn' '-D' '/usr/lib/sysimage/rpm' '-X' '-p' '/tmp/transactional-update-IZ1KXn/etc/products.d' '/tmp/transactional-update-IZ1KXn/var/cache/zypp/solv/@System/solv' '-o' '/tmp/transactional-update-IZ1KXn/var/cache/zypp/solv/@System/solvmZwBtC'
2026-03-19 00:20:22 <1> cl2-standalone2(78314) [zypp::exec++] forkspawnengine.cc(start):427 pid 82699 launched
2026-03-19 00:20:22 <1> cl2-standalone2(78314) [zypp::exec++] abstractspawnengine.cc(checkStatus):189 Pid 82699 successfully completed
2026-03-19 00:20:22 <1> cl2-standalone2(78314) [zypp-core] PathInfo.cc(rename):767 rename /tmp/transactional-update-IZ1KXn/var/cache/zypp/solv/@System/solvmZwBtC -> /tmp/transactional-update-IZ1KXn/var/cache/zypp/solv/@System/solv
2026-03-19 00:20:22 <1> cl2-standalone2(78314) [zypp-core] PathInfo.cc(chmod):1117 chmod /tmp/transactional-update-IZ1KXn/var/cache/zypp/solv/@System/solv 00644
2026-03-19 00:20:22 <1> cl2-standalone2(78314) [zypp] TargetImpl.cc(commit):1706 TargetImpl::commit(<pool>, CommitPolicy( DownloadInAdvance rpmInstFlags{0x00000001} )) returns: CommitResult  (total 15, done 15, error 0, skipped 0, updateMessages 0)
2026-03-19 00:20:22 <1> cl2-standalone2(78314) [zypp::plugin++] PluginExecutor.cc(send):89 +++++++++++++++ send PluginFrame[PLUGINEND](0){0}
2026-03-19 00:20:22 <1> cl2-standalone2(78314) [zypp::plugin++] PluginScript.cc(send):292 PluginScript[78367] /usr/lib/zypp/plugins/commit/boot-plugin ->send PluginFrame[PLUGINEND](0){0}
2026-03-19 00:20:22 <2> cl2-standalone2(78314) [PLUGIN] PluginScript.cc(~PluginDumpStderr):86 ! INFO:(boot-plugin):PLUGINEND
2026-03-19 00:20:22 <1> cl2-standalone2(78314) [zypp::plugin++] PluginScript.cc(receive):441 PluginScript[78367] /usr/lib/zypp/plugins/commit/boot-plugin <-PluginFrame[ACK](0){0}
2026-03-19 00:20:22 <1> cl2-standalone2(78314) [zypp::plugin++] PluginExecutor.cc(send):98 --------------- send PluginFrame[PLUGINEND](0){0}
2026-03-19 00:20:22 <1> cl2-standalone2(78314) [zypp::plugin++] PluginScript.cc(close):249 Close:PluginScript[78367] /usr/lib/zypp/plugins/commit/boot-plugin
2026-03-19 00:20:22 <1> cl2-standalone2(78314) [zypp::plugin++] PluginScript.cc(send):292 PluginScript[78367] /usr/lib/zypp/plugins/commit/boot-plugin ->send PluginFrame[_DISCONNECT](0){0}
2026-03-19 00:20:22 <1> cl2-standalone2(78314) [zypp::plugin++] PluginScript.cc(receive):441 PluginScript[78367] /usr/lib/zypp/plugins/commit/boot-plugin <-PluginFrame[ACK](0){0}
2026-03-19 00:20:22 <1> cl2-standalone2(78314) [zypp::plugin++] PluginScript.cc(close):271 PluginScript[78367] /usr/lib/zypp/plugins/commit/boot-plugin -> [0]
2026-03-19 00:20:22 <1> cl2-standalone2(78314) [zypp-core] ShutdownLock.cc(~ShutdownLock):33 Terminate inhibitor lock: pid 78349
2026-03-19 00:20:22 <2> cl2-standalone2(78314) [zypp::exec] abstractspawnengine.cc(checkStatus):203 Pid 78349 was killed by signal 15 (Terminated)
2026-03-19 00:20:22 <1> cl2-standalone2(78314) [zypp++] ZYppImpl.cc(commit):250 unloading @System repo from pool
2026-03-19 00:20:22 <1> cl2-standalone2(78314) [zypp] Repository.cc(eraseFromPool):301 sat::repo(@System){prio -99.0, size 628} removed from pool
2026-03-19 00:20:22 <1> cl2-standalone2(78314) [zypp::satpool] PoolImpl.cc(setDirty):260 _deleteRepo @System
2026-03-19 00:20:22 <1> cl2-standalone2(78314) [zypp] ZYppImpl.cc(commit):255 Commit (CommitPolicy( DownloadDefault rpmInstFlags{0x00000001} )) returned: CommitResult  (total 15, done 15, error 0, skipped 0, updateMessages 0)
2026-03-19 00:20:22 <1> cl2-standalone2(78314) [zypper] solve-commit.cc(solve_and_commit):976
2026-03-19 00:20:22 <1> cl2-standalone2(78314) [zypper] solve-commit.cc(solve_and_commit):976 DONE
2026-03-19 00:20:22 <2> cl2-standalone2(78314) [DEFINE_LOGGROUP] application.cc(setExitCode):79 setExitCode 0
2026-03-19 00:20:22 <1> cl2-standalone2(78314) [zypper] Zypper.cc(doCommand):700 Done
2026-03-19 00:20:22 <1> cl2-standalone2(78314) [zypper] Zypper.cc(cleanup):752 START
2026-03-19 00:20:22 <1> cl2-standalone2(78314) [zypper] main.cc(~Bye):115 ===== Exiting main(0) =====

→ Finished successfully

journalctl -b -1 -n 10000 | grep -v "Getty" | grep -v "getty" | grep -v "sshd":

Mar 19 00:20:23 cl2-standalone2 transactional-update[83976]: New default snapshot is #41 (/.snapshots/41/snapshot).
Mar 19 00:20:23 cl2-standalone2 transactional-update[83979]: transactional-update finished
Mar 19 00:20:23 cl2-standalone2 transactional-update[83984]: tukit 6.0.6 started
################### reboot called ->
Mar 19 00:20:23 cl2-standalone2 transactional-update[83984]: Options: --log=console reboot auto
Mar 19 00:20:23 cl2-standalone2 transactional-update[83987]: tukit 6.0.6 started
Mar 19 00:20:23 cl2-standalone2 transactional-update[83987]: Options: --log=console reboot auto
Mar 19 00:20:23 cl2-standalone2 rebootmgrd[1376]: Varlink method "Status" called...
Mar 19 00:20:23 cl2-standalone2 transactional-update[83984]: Minimally required reboot level: reboot
Mar 19 00:20:23 cl2-standalone2 transactional-update[83984]: Triggering reboot using rebootmgrctl reboot.
Mar 19 00:20:23 cl2-standalone2 transactional-update[83987]: Minimally required reboot level: reboot
Mar 19 00:20:23 cl2-standalone2 transactional-update[83987]: Triggering reboot using rebootmgrctl reboot.
Mar 19 00:20:23 cl2-standalone2 rebootmgrd[1376]: Varlink method "Reboot" called...
Mar 19 00:20:23 cl2-standalone2 rebootmgrd[1376]: Reboot in 14959 seconds at Thu 2026-03-19 04:29:43 UTC
################### <- reboot called
Mar 19 00:20:23 cl2-standalone2 transactional-update[83984]: Transaction completed.
Mar 19 00:20:23 cl2-standalone2 transactional-update[83987]: Transaction completed.
Mar 19 00:20:23 cl2-standalone2 systemd[1]: transactional-update.service: Deactivated successfully.
Mar 19 00:20:23 cl2-standalone2 systemd[1]: Finished Update the system.
Mar 19 00:20:23 cl2-standalone2 systemd[1]: transactional-update.service: Consumed 22.384s CPU time over 28.494s wall clock time.
Mar 19 00:21:23 cl2-standalone2 systemd[1]: snapperd.service: Deactivated successfully.
Mar 19 00:21:23 cl2-standalone2 systemd[1]: snapperd.service: Consumed 2.626s CPU time over 1min 22.310s wall clock time.
Mar 19 00:40:34 cl2-standalone2 systemd[1]: Started Daily Cleanup of Snapper Snapshots.
Mar 19 00:40:34 cl2-standalone2 systemd[1]: Starting DBus interface for snapper...
Mar 19 00:40:34 cl2-standalone2 systemd[1]: Started DBus interface for snapper.
Mar 19 00:40:34 cl2-standalone2 systemd-helper[84904]: Running cleanup for 'root'.
Mar 19 00:40:34 cl2-standalone2 systemd-helper[84904]: Running number cleanup for 'root'.
Mar 19 00:40:34 cl2-standalone2 systemd-helper[84904]: Deleting snapshot from root:
Mar 19 00:40:34 cl2-standalone2 systemd-helper[84904]: 18
Mar 19 00:40:34 cl2-standalone2 systemd-helper[84904]: Deleting snapshot from root:
Mar 19 00:40:34 cl2-standalone2 systemd-helper[84904]: 31
Mar 19 00:40:36 cl2-standalone2 kernel: BTRFS info (device nvme0n1p3): qgroup scan completed (inconsistency flag cleared)
Mar 19 00:40:40 cl2-standalone2 systemd-helper[84904]: Running timeline cleanup for 'root'.
Mar 19 00:40:40 cl2-standalone2 systemd-helper[84904]: Running empty-pre-post cleanup for 'root'.
Mar 19 00:40:40 cl2-standalone2 systemd-helper[84904]: Running 'btrfs qgroup clear-stale /.snapshots'.
Mar 19 00:40:40 cl2-standalone2 systemd[1]: snapper-cleanup.service: Deactivated successfully.
Mar 19 00:41:40 cl2-standalone2 systemd[1]: snapperd.service: Deactivated successfully.
Mar 19 00:57:09 cl2-standalone2 systemd[1]: Starting Rotate log files...
Mar 19 00:57:09 cl2-standalone2 systemd[1]: logrotate.service: Deactivated successfully.
Mar 19 00:57:09 cl2-standalone2 systemd[1]: Finished Rotate log files.
Mar 19 01:00:03 cl2-standalone2 systemd[1]: Started Timeline of Snapper Snapshots.
Mar 19 01:00:03 cl2-standalone2 systemd[1]: Starting DBus interface for snapper...
Mar 19 01:00:03 cl2-standalone2 systemd[1]: Started DBus interface for snapper.
Mar 19 01:00:03 cl2-standalone2 systemd[1]: snapper-timeline.service: Deactivated successfully.
Mar 19 01:01:03 cl2-standalone2 systemd[1]: snapperd.service: Deactivated successfully.
Mar 19 01:34:03 cl2-standalone2 auditd[1338]: Audit daemon rotating log files
Mar 19 01:40:34 cl2-standalone2 systemd[1]: Started Daily Cleanup of Snapper Snapshots.
Mar 19 01:40:34 cl2-standalone2 systemd[1]: Starting DBus interface for snapper...
Mar 19 01:40:34 cl2-standalone2 systemd[1]: Started DBus interface for snapper.
Mar 19 01:40:34 cl2-standalone2 systemd-helper[88063]: Running cleanup for 'root'.
Mar 19 01:40:34 cl2-standalone2 systemd-helper[88063]: Running number cleanup for 'root'.
Mar 19 01:40:36 cl2-standalone2 kernel: BTRFS info (device nvme0n1p3): qgroup scan completed (inconsistency flag cleared)
Mar 19 01:40:36 cl2-standalone2 systemd-helper[88063]: Running timeline cleanup for 'root'.
Mar 19 01:40:36 cl2-standalone2 systemd-helper[88063]: Running empty-pre-post cleanup for 'root'.
Mar 19 01:40:36 cl2-standalone2 systemd-helper[88063]: Running 'btrfs qgroup clear-stale /.snapshots'.
Mar 19 01:40:36 cl2-standalone2 systemd[1]: snapper-cleanup.service: Deactivated successfully.
Mar 19 01:41:36 cl2-standalone2 systemd[1]: snapperd.service: Deactivated successfully.
Mar 19 02:00:01 cl2-standalone2 systemd[1]: Started Timeline of Snapper Snapshots.
Mar 19 02:00:01 cl2-standalone2 systemd[1]: Starting DBus interface for snapper...
Mar 19 02:00:01 cl2-standalone2 systemd[1]: Started DBus interface for snapper.
Mar 19 02:00:01 cl2-standalone2 systemd[1]: snapper-timeline.service: Deactivated successfully.
Mar 19 02:01:01 cl2-standalone2 systemd[1]: snapperd.service: Deactivated successfully.
Mar 19 02:40:34 cl2-standalone2 systemd[1]: Started Daily Cleanup of Snapper Snapshots.
Mar 19 02:40:34 cl2-standalone2 systemd[1]: Starting DBus interface for snapper...
Mar 19 02:40:34 cl2-standalone2 systemd[1]: Started DBus interface for snapper.
Mar 19 02:40:34 cl2-standalone2 systemd-helper[90679]: Running cleanup for 'root'.
Mar 19 02:40:34 cl2-standalone2 systemd-helper[90679]: Running number cleanup for 'root'.
Mar 19 02:40:36 cl2-standalone2 kernel: BTRFS info (device nvme0n1p3): qgroup scan completed (inconsistency flag cleared)
Mar 19 02:40:36 cl2-standalone2 systemd-helper[90679]: Running timeline cleanup for 'root'.
Mar 19 02:40:36 cl2-standalone2 systemd-helper[90679]: Running empty-pre-post cleanup for 'root'.
Mar 19 02:40:36 cl2-standalone2 systemd-helper[90679]: Running 'btrfs qgroup clear-stale /.snapshots'.
Mar 19 02:40:36 cl2-standalone2 systemd[1]: snapper-cleanup.service: Deactivated successfully.
Mar 19 02:41:36 cl2-standalone2 systemd[1]: snapperd.service: Deactivated successfully.
Mar 19 03:00:09 cl2-standalone2 systemd[1]: Started Timeline of Snapper Snapshots.
Mar 19 03:00:09 cl2-standalone2 systemd[1]: Starting DBus interface for snapper...
Mar 19 03:00:09 cl2-standalone2 systemd[1]: Started DBus interface for snapper.
Mar 19 03:00:09 cl2-standalone2 systemd[1]: snapper-timeline.service: Deactivated successfully.
Mar 19 03:01:09 cl2-standalone2 systemd[1]: snapperd.service: Deactivated successfully.

After the update at 00:20 a reboot gets triggered, but 3 h later at 03:20 still no reboot and the machine stops working. No further log entries, no crash dump, no ping, no entry in ARP on my local network, no monitor output.

The service file /usr/lib/systemd/system/transactional-update.service states:

[Service]
ExecStart=/usr/sbin/transactional-update cleanup ${UPDATE_METHOD} reboot

I also checked cat /usr/etc/transactional-update.conf:

[...]
#REBOOT_METHOD=auto
[...]

→ No REBOOT_METHOD variable has been set, therefore the command in systemd is as followes:

/usr/sbin/transactional-update cleanup reboot

Any idea what I can check additionally? Has anyone ever experienced such a problem? The log is also not showing a reason why there was no reboot.

And I forgot to add a working reboot one day earlier:

transactional-update ran successfully:

Mar 18 01:15:44 cl2-standalone2 transactional-update[65281]: Options: --log=console reboot auto
Mar 18 01:15:44 cl2-standalone2 transactional-update[65284]: tukit 6.0.6 started
Mar 18 01:15:44 cl2-standalone2 transactional-update[65284]: Options: --log=console reboot auto
Mar 18 01:15:44 cl2-standalone2 rebootmgrd[1373]: Varlink method "Status" called...
Mar 18 01:15:44 cl2-standalone2 transactional-update[65281]: Minimally required reboot level: soft-reboot
Mar 18 01:15:44 cl2-standalone2 transactional-update[65281]: Triggering reboot using rebootmgrctl reboot.
Mar 18 01:15:44 cl2-standalone2 transactional-update[65284]: Minimally required reboot level: soft-reboot
Mar 18 01:15:44 cl2-standalone2 transactional-update[65284]: Triggering reboot using rebootmgrctl reboot.
Mar 18 01:15:44 cl2-standalone2 rebootmgrd[1373]: Varlink method "Reboot" called...
Mar 18 01:15:44 cl2-standalone2 rebootmgrd[1373]: Reboot in 11638 seconds at Wed 2026-03-18 04:29:43 UTC
Mar 18 01:15:44 cl2-standalone2 transactional-update[65281]: Transaction completed.
Mar 18 01:15:44 cl2-standalone2 transactional-update[65284]: Transaction completed.
Mar 18 01:15:44 cl2-standalone2 systemd[1]: transactional-update.service: Deactivated successfully.
Mar 18 01:15:44 cl2-standalone2 systemd[1]: Finished Update the system.
Mar 18 01:15:44 cl2-standalone2 systemd[1]: transactional-update.service: Consumed 7.735s CPU time over 12.281s wall clock time.
Mar 18 01:16:44 cl2-standalone2 systemd[1]: snapperd.service: Deactivated successfully.

→ finished at 01:16

Reboot triggered at 04:29:43:

Mar 18 04:29:43 cl2-standalone2 rebootmgrd[1373]: rebootmgr: reboot triggered now!
Mar 18 04:29:43 cl2-standalone2 systemd-logind[1381]: The system will reboot now!
Mar 18 04:29:43 cl2-standalone2 systemd-logind[1381]: System is rebooting.
[...]
Mar 18 04:29:45 cl2-standalone2 systemd[1]: systemd-reboot.service: Deactivated successfully.
Mar 18 04:29:45 cl2-standalone2 systemd[1]: Finished System Reboot.
Mar 18 04:29:45 cl2-standalone2 systemd[1]: Reached target System Reboot.
Mar 18 04:29:45 cl2-standalone2 systemd[1]: Shutting down.
Mar 18 04:29:45 cl2-standalone2 systemd[1]: Using hardware watchdog /dev/watchdog0: 'SP5100 TCO timer', version 0.
Mar 18 04:29:45 cl2-standalone2 systemd[1]: Watchdog running with a hardware timeout of 10min.
Mar 18 04:29:45 cl2-standalone2 kernel: watchdog: watchdog0: watchdog did not stop!
Mar 18 04:29:45 cl2-standalone2 systemd-shutdown[1]: Using hardware watchdog /dev/watchdog0: 'SP5100 TCO timer', version 0.
Mar 18 04:29:45 cl2-standalone2 systemd-shutdown[1]: Watchdog running with a hardware timeout of 10min.
Mar 18 04:29:45 cl2-standalone2 systemd-shutdown[1]: Syncing filesystems and block devices.
Mar 18 04:29:45 cl2-standalone2 systemd-shutdown[1]: Sending SIGTERM to remaining processes...
Mar 18 04:29:45 cl2-standalone2 systemd-journald[1143]: Received SIGTERM from PID 1 (systemd-shutdow).
Mar 18 04:29:45 cl2-standalone2 systemd-journald[1143]: Journal stopped

→ 04:29:45

The reboot has been triggered 3:11 h later and succeeded 2 s later

I checked the last boot logs of both maschines as followes:

journalctl -b -1 -g "Minimally required reboot level"

That leads to this output:

Mar 20 01:45:53 cl2-standalone2 transactional-update[47180]: Minimally required reboot level: kexec

As far as I can tell there are these reboot levels:

  • reboot
  • soft-reboot
  • kexec

Then I checked the last lines of each boot to see some specific lines:

journalctl -b -1 -n 100

Mar 20 04:29:45 cl2-standalone2 systemd-shutdown[1]: Using hardware watchdog /dev/watchdog0: 'SP5100 TCO timer', version 0.
Mar 20 04:29:45 cl2-standalone2 systemd-shutdown[1]: Watchdog running with a hardware timeout of 10min.
Mar 20 04:29:45 cl2-standalone2 systemd-shutdown[1]: Syncing filesystems and block devices.
Mar 20 04:29:45 cl2-standalone2 systemd-shutdown[1]: Sending SIGTERM to remaining processes...
Mar 20 04:29:45 cl2-standalone2 systemd-journald[1512]: Journal stopped

→ If these lines appear then it was a correct reboot.

Until now I can’t figure out which of these three reboot levels can trigger the failed reboot. With two servers and only the last 5 boot logs available there’s not enough evidence.

Interesting side node: My VM has not crashed within the last week, but two or three weeks before that about every second day.

It looks like that both servers are running since the last update, so it seems to be fixed now!

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.