openEuler22.03无故频繁重启

版本信息:

[root@huawei ~]# uname -a
Linux huawei 5.10.0-177.0.0.rt62.61.oe2203sp3.aarch64 #1 SMP PREEMPT_RT Sat Dec 30 13:16:24 CST 2023 aarch64 aarch64 aarch64 GNU/Linux

无故重启时的日志文件:

Dec  5 15:50:24 huawei systemd[1]: Finished system activity accounting tool.
Dec  5 15:52:11 huawei sshd[10229]: Connection reset by authenticating user zzc 192.168.137.171 port 55439 [preauth]
Dec  5 15:52:30 huawei NetworkManager[2181]: <info>  [1733385150.7786] device (enp125s0f1): carrier: link connected
Dec  5 15:52:57 huawei chronyd[2129]: Selected source 139.199.214.202 (pool.ntp.org)
Dec  5 15:52:59 huawei sshd[10266]: Accepted password for root from 192.168.137.170 port 62992 ssh2
Dec  5 15:52:59 huawei dbus-daemon[2065]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.21' (uid=0 pid=10276 comm="/usr/bin/hostnamectl --transient " label="unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023")
Dec  5 15:52:59 huawei systemd[1]: Starting Hostname Service...
Dec  5 15:53:00 huawei dbus-daemon[2065]: [system] Successfully activated service 'org.freedesktop.hostname1'
Dec  5 15:53:00 huawei systemd[1]: Started Hostname Service.
Dec  5 15:53:00 huawei sshd[10271]: Accepted password for root from 192.168.137.170 port 62994 ssh2
Dec  5 15:53:00 huawei sftp-server[10344]: session opened for local user root from [192.168.137.170]
Dec  5 15:53:30 huawei systemd[1]: systemd-hostnamed.service: Deactivated successfully.
Dec  5 15:54:33 huawei NetworkManager[2181]: <info>  [1733385273.6587] device (enp125s0f2): carrier: link connected
Dec  5 15:54:44 huawei NetworkManager[2181]: <info>  [1733385284.9226] device (enp125s0f2): carrier: link connected
Dec  5 15:55:36 huawei sshd[10445]: Accepted password for zyz from 192.168.137.170 port 63082 ssh2
Dec  5 15:56:47 huawei NetworkManager[2181]: <info>  [1733385407.8026] device (enp125s0f2): carrier: link connected
Dec  5 15:56:59 huawei NetworkManager[2181]: <info>  [1733385419.0665] device (enp125s0f1): carrier: link connected
Dec  5 15:57:02 huawei NetworkManager[2181]: <info>  [1733385422.1384] device (enp125s0f1): carrier: link connected
Dec  5 15:58:00 huawei NetworkManager[2181]: <info>  [1733385480.5065] device (enp125s0f1): carrier: link connected
Dec  5 15:58:28 huawei systemd[1]: Starting dnf makecache...
Dec  5 15:58:28 huawei python3[10990]: ldapdb_canonuser_plug_init() failed in sasl_canonuser_add_plugin(): invalid parameter supplied
Dec  5 15:58:28 huawei dnf[10990]: Metadata cache refreshed recently.
Dec  5 15:58:28 huawei systemd[1]: dnf-makecache.service: Deactivated successfully.
Dec  5 15:58:28 huawei systemd[1]: Finished dnf makecache.
Dec  5 15:59:14 huawei NetworkManager[2181]: <info>  [1733385554.2345] device (enp125s0f1): carrier: link connected
Dec  5 16:00:23 huawei NetworkManager[2181]: <info>  [1733385623.8666] device (enp125s0f1): carrier: link connected
Dec  5 16:00:23 huawei systemd[1]: Starting system activity accounting tool...
Dec  5 16:00:23 huawei systemd[1]: sysstat-collect.service: Deactivated successfully.
Dec  5 16:00:23 huawei systemd[1]: Finished system activity accounting tool.
Dec  5 16:01:50 huawei systemd[1]: Starting Cleanup of Temporary Directories...
Dec  5 16:01:50 huawei systemd-tmpfiles[11065]: /usr/lib/tmpfiles.d/net-snmp.conf:1: Line references path below legacy directory /var/run/, updating /var/run/net-snmp → /run/net-snmp; please update the tmpfiles.d/ drop-in file accordingly.
Dec  5 16:01:50 huawei systemd-tmpfiles[11065]: /usr/lib/tmpfiles.d/tog-pegasus.conf:1: Line references path below legacy directory /var/run/, updating /var/run/tog-pegasus → /run/tog-pegasus; please update the tmpfiles.d/ drop-in file accordingly.
Dec  5 16:01:50 huawei systemd[1]: systemd-tmpfiles-clean.service: Deactivated successfully.
Dec  5 16:01:50 huawei systemd[1]: Finished Cleanup of Temporary Directories.
Dec  5 16:01:51 huawei sshd[11069]: Accepted password for wc from 192.168.192.20 port 55947 ssh2
Dec  5 16:01:51 huawei dbus-daemon[2065]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.24' (uid=1008 pid=11077 comm="/usr/bin/hostnamectl --transient " label="unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023")
Dec  5 16:01:51 huawei systemd[1]: Starting Hostname Service...
Dec  5 16:01:51 huawei dbus-daemon[2065]: [system] Successfully activated service 'org.freedesktop.hostname1'
Dec  5 16:01:51 huawei systemd[1]: Started Hostname Service.
Dec  5 16:02:04 huawei rsyslogd[3016]: imjournal: journal files changed, reloading...  [v8.2210.0 try https://www.rsyslog.com/e/0 ]
Dec  5 16:02:04 huawei su[11144]: (to root) root on pts/7
Dec  5 16:02:10 huawei sshd[11209]: Accepted password for wc from 192.168.192.20 port 55949 ssh2
Dec  5 16:02:11 huawei su[11282]: (to root) root on pts/8
Dec  5 16:02:14 huawei sshd[11347]: Accepted password for wc from 192.168.192.20 port 55950 ssh2
Dec  5 16:02:15 huawei su[11420]: (to root) root on pts/9
Dec  5 16:02:18 huawei sshd[11485]: Accepted password for wc from 192.168.192.20 port 55951 ssh2
Dec  5 16:02:19 huawei su[11558]: (to root) root on pts/10
Dec  5 16:02:36 huawei sshd[11627]: Accepted password for wc from 192.168.192.20 port 55956 ssh2
Dec  5 16:02:37 huawei su[11700]: (to root) root on pts/7
Dec  5 16:03:06 huawei systemd[1]: systemd-hostnamed.service: Deactivated successfully.
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                Jan  1 08:00:01 huawei systemd-journald[687]: Journal started
Jan  1 08:00:01 huawei systemd-journald[687]: Runtime Journal (/run/log/journal/3097ee7381f4419fbd9d436b8fc870a2) is 8.0M, max 563.1M, 555.1M free.
Jan  1 08:00:01 huawei rngd[683]: Initializing available sources
Jan  1 08:00:01 huawei rngd[683]: [hwrng ]: Initialization Failed
Jan  1 08:00:01 huawei rngd[683]: [rndr  ]: No HW SUPPORT
Jan  1 08:00:01 huawei rngd[683]: [rndr  ]: Initialization Failed
Jan  1 08:00:01 huawei systemd[1]: Starting Create Volatile Files and Directories...
Jan  1 08:00:01 huawei systemd[1]: Finished Create Volatile Files and Directories.
Jan  1 08:00:01 huawei rngd[683]: [jitter]: Initializing AES buffer
Jan  1 08:00:01 huawei systemd[1]: Finished Setup Virtual Console.
Jan  1 08:00:01 huawei systemd[1]: Condition check resulted in dracut ask for additional cmdline parameters being skipped.
Jan  1 08:00:01 huawei systemd[1]: Starting dracut cmdline hook...
Jan  1 08:00:01 huawei dracut-cmdline[713]: dracut-22.03 (LTS-SP3) dracut-055-9.oe2203sp3
Jan  1 08:00:01 huawei dracut-cmdline[713]: Using kernel command line parameters:    BOOT_IMAGE=/vmlinuz-5.10.0-177.0.0.rt62.61.oe2203sp3.aarch64 root=/dev/mapper/openeuler_huawei-root ro rd.lvm.lv=openeuler_huawei/root rd.lvm.lv=openeuler_huawei/swap video=VGA-1:640x480-32@60me cgroup_disable=files apparmor=0 crashkernel=1024M,high smmu.bypassdev=0x1000:0x17 smmu.bypassdev=0x1000:0x15 rhgb quiet console=tty0 memmap=0x90000000$0x2100800000 rd.shell=0
Jan  1 08:00:01 huawei systemd[1]: Finished Apply Kernel Variables.
Jan  1 08:00:01 huawei systemd[1]: Finished dracut cmdline hook.
Jan  1 08:00:01 huawei systemd[1]: Starting dracut pre-udev hook...
Jan  1 08:00:01 huawei systemd[1]: Finished dracut pre-udev hook.
Jan  1 08:00:01 huawei systemd[1]: Starting Rule-based Manager for Device Events and Files...
Jan  1 08:00:01 huawei systemd[1]: Started Rule-based Manager for Device Events and Files.
Jan  1 08:00:01 huawei systemd[1]: Condition check resulted in dracut pre-trigger hook being skipped.
Jan  1 08:00:01 huawei systemd[1]: Starting Coldplug All udev Devices...
Jan  1 08:00:01 huawei systemd-udevd[977]: Change current work dir to /etc/ndctl/keys failed: No such file or directory
Jan  1 08:00:02 huawei systemd[1]: Finished Coldplug All udev Devices.
Jan  1 08:00:02 huawei systemd[1]: Reached target System Initialization.
Jan  1 08:00:02 huawei systemd[1]: Starting dracut initqueue hook...
Jan  1 08:00:02 huawei systemd[1]: Starting Show Plymouth Boot Screen...
Jan  1 08:00:02 huawei systemd[1]: Received SIGRTMIN+20 from PID 1034 (plymouthd).
Jan  1 08:00:02 huawei systemd[1]: Started Show Plymouth Boot Screen.
Jan  1 08:00:02 huawei systemd[1]: Condition check resulted in Dispatch Password Requests to Console Directory Watch being skipped.
Jan  1 08:00:02 huawei systemd[1]: Started Forward Password Requests to Plymouth Directory Watch.
Jan  1 08:00:02 huawei systemd[1]: Reached target Path Units.
Jan  1 08:00:02 huawei systemd[1]: Reached target Basic System.
Jan  1 08:00:02 huawei systemd[1]: System is tainted: cgroupsv1
Jan  1 08:00:02 huawei systemd-udevd[887]: Using default interface naming scheme 'v249'.

基本上每天都会重启,求解决办法

从你贴的log里面看,也没有看到什么异常的log信息,你能把/var/log/messages文件上传下吗?里面应该包含完整的log信息。同时你执行下#last reboot 这条命令,把结果也给贴下哈!另外你描述说每天都重启,你查看下是否有重启的定时任务#crontab -l

last reboot输出:

[root@huawei xml]# last reboot
reboot   system boot  5.10.0-177.0.0.r Thu Jan  1 08:00   still running
reboot   system boot  5.10.0-177.0.0.r Thu Jan  1 08:00   still running
reboot   system boot  5.10.0-177.0.0.r Thu Jan  1 08:00   still running
reboot   system boot  5.10.0-177.0.0.r Thu Jan  1 08:00 - 21:39 (20062+13:39)
reboot   system boot  5.10.0-177.0.0.r Thu Jan  1 08:00 - 21:39 (20062+13:39)
reboot   system boot  5.10.0-177.0.0.r Thu Jan  1 08:00 - 21:39 (20062+13:39)
reboot   system boot  5.10.0-177.0.0.r Thu Jan  1 08:00 - 21:39 (20062+13:39)
reboot   system boot  5.10.0-177.0.0.r Thu Jan  1 08:00 - 15:41 (20062+07:40)
reboot   system boot  5.10.0-177.0.0.r Thu Jan  1 08:00 - 15:41 (20062+07:40)
reboot   system boot  5.10.0-177.0.0.r Thu Jan  1 08:00 - 15:41 (20062+07:40)
reboot   system boot  5.10.0-177.0.0.r Thu Jan  1 08:00 - 15:41 (20062+07:40)
reboot   system boot  5.10.0-177.0.0.r Thu Jan  1 08:00 - 09:56 (20062+01:56)
reboot   system boot  5.10.0-177.0.0.r Thu Jan  1 08:00 - 09:56 (20062+01:56)
reboot   system boot  5.10.0-177.0.0.r Thu Jan  1 08:00 - 09:56 (20062+01:56)
reboot   system boot  5.10.0-177.0.0.r Thu Jan  1 08:00 - 15:49 (20056+07:49)
reboot   system boot  5.10.0-177.0.0.r Thu Jan  1 08:00 - 15:49 (20056+07:49)
reboot   system boot  5.10.0-177.0.0.r Thu Jan  1 08:00 - 15:49 (20056+07:49)
reboot   system boot  5.10.0-177.0.0.r Thu Jan  1 08:00 - 15:49 (20056+07:49)
reboot   system boot  5.10.0-177.0.0.r Thu Jan  1 08:00 - 15:49 (20056+07:49)
reboot   system boot  5.10.0-177.0.0.r Thu Jan  1 08:00 - 15:49 (20056+07:49)
reboot   system boot  5.10.0-177.0.0.r Thu Jan  1 08:00 - 15:49 (20056+07:49)
reboot   system boot  5.10.0-177.0.0.r Thu Jan  1 08:00 - 15:49 (20056+07:49)
reboot   system boot  5.10.0-177.0.0.r Thu Jan  1 08:00 - 15:49 (20056+07:49)
reboot   system boot  5.10.0-177.0.0.r Thu Jan  1 08:00 - 15:49 (20056+07:49)
reboot   system boot  5.10.0-177.0.0.r Thu Jan  1 08:00 - 15:49 (20056+07:49)
reboot   system boot  5.10.0-177.0.0.r Thu Jan  1 08:00 - 15:49 (20056+07:49)
reboot   system boot  5.10.0-177.0.0.r Thu Jan  1 08:00 - 15:49 (20056+07:49)
reboot   system boot  5.10.0-177.0.0.r Thu Jan  1 08:00 - 15:49 (20056+07:49)
reboot   system boot  5.10.0-177.0.0.r Thu Jan  1 08:00 - 15:49 (20056+07:49)
reboot   system boot  5.10.0-177.0.0.r Thu Jan  1 08:00 - 15:49 (20056+07:49)
reboot   system boot  5.10.0-177.0.0.r Thu Jan  1 08:00 - 15:49 (20056+07:49)
reboot   system boot  5.10.0-177.0.0.r Thu Jan  1 08:00 - 15:49 (20056+07:49)
reboot   system boot  5.10.0-177.0.0.r Thu Jan  1 08:00 - 15:49 (20056+07:49)
reboot   system boot  5.10.0-177.0.0.r Thu Jan  1 08:00 - 15:49 (20056+07:49)
reboot   system boot  5.10.0-177.0.0.r Thu Jan  1 08:00 - 15:49 (20056+07:49)
reboot   system boot  5.10.0-177.0.0.r Thu Jan  1 08:00 - 15:49 (20056+07:49)
reboot   system boot  5.10.0-177.0.0.r Thu Jan  1 08:00 - 16:09 (20033+08:09)
reboot   system boot  5.10.0-177.0.0.r Thu Jan  1 08:00 - 16:09 (20033+08:09)
reboot   system boot  5.10.0-177.0.0.r Thu Jan  1 08:00 - 16:09 (20033+08:09)
reboot   system boot  5.10.0-177.0.0.r Thu Jan  1 08:00 - 16:09 (20033+08:09)
reboot   system boot  5.10.0-177.0.0.r Thu Jan  1 08:00 - 16:09 (20033+08:09)
reboot   system boot  5.10.0-177.0.0.r Thu Jan  1 08:00 - 10:03 (20028+02:03)
reboot   system boot  5.10.0-177.0.0.r Thu Jan  1 08:00 - 18:20 (20027+10:20)
reboot   system boot  5.10.0-177.0.0.r Thu Jan  1 08:00 - 18:20 (20027+10:20)
reboot   system boot  5.10.0-177.0.0.r Thu Jan  1 08:00 - 18:20 (20027+10:20)
reboot   system boot  5.10.0-177.0.0.r Thu Jan  1 08:00 - 19:29 (20026+11:29)
reboot   system boot  5.10.0-177.0.0.r Thu Jan  1 08:00 - 19:29 (20026+11:29)
reboot   system boot  5.10.0-231.0.0.1 Wed Oct 30 14:50 - 19:29  (04:39)
reboot   system boot  5.10.0-177.0.0.r Thu Jan  1 08:00 - 19:29 (20026+11:29)
reboot   system boot  5.10.0-231.0.0.1 Wed Oct 30 09:47 - 14:39  (04:52)
reboot   system boot  5.10.0-177.0.0.r Thu Jan  1 08:00 - 09:45 (20026+01:45)
reboot   system boot  5.10.0-177.0.0.r Thu Jan  1 08:00 - 09:45 (20026+01:45)
reboot   system boot  5.10.0-177.0.0.r Thu Jan  1 08:00 - 09:45 (20026+01:45)
reboot   system boot  5.10.0-177.0.0.r Thu Jan  1 08:00 - 09:45 (20026+01:45)
reboot   system boot  5.10.0-231.0.0.1 Thu Oct 17 17:17 - 08:47 (9+15:29)
reboot   system boot  5.10.0-177.0.0.r Thu Jan  1 08:00 - 08:47 (20023+00:47)
reboot   system boot  5.10.0-177.0.0.r Thu Jan  1 08:00 - 08:47 (20023+00:47)
reboot   system boot  5.10.0-231.0.0.1 Tue Oct 15 10:41 - 08:47 (11+22:05)
reboot   system boot  5.10.0-177.0.0.r Thu Jan  1 08:00 - 08:00  (00:00)
reboot   system boot  5.10.0-177.0.0.r Thu Jan  1 08:00 - 08:00  (00:00)
reboot   system boot  5.10.0-177.0.0.r Thu Jan  1 08:00 - 10:32 (20011+02:32)
reboot   system boot  5.10.0-182.0.0.9 Fri Oct 11 13:24 - 15:54 (3+02:29)
reboot   system boot  5.10.0-182.0.0.9 Fri Sep 27 14:07 - 13:23 (13+23:15)
reboot   system boot  5.10.0-182.0.0.9 Fri Sep 27 10:36 - 13:23 (14+02:46)
reboot   system boot  5.10.0-182.0.0.9 Wed Sep 25 11:32 - 10:34 (1+23:02)
reboot   system boot  5.10.0-182.0.0.9 Tue Sep 24 18:19 - 10:34 (2+16:15)
reboot   system boot  5.10.0-182.0.0.9 Tue Sep 24 17:17 - 10:34 (2+17:17)
reboot   system boot  5.10.0-182.0.0.9 Tue Sep 24 15:55 - 17:15  (01:20)
reboot   system boot  5.10.0-182.0.0.9 Tue Sep 24 14:57 - 15:54  (00:57)
reboot   system boot  5.10.0-182.0.0.9 Mon Sep 23 19:42 - 14:54  (19:11)
reboot   system boot  5.10.0-182.0.0.9 Thu Sep 12 22:11 - 19:40 (10+21:29)
reboot   system boot  5.10.0-182.0.0.9 Thu Sep 12 15:41 - 22:09  (06:28)
reboot   system boot  5.10.0-182.0.0.9 Thu Sep 12 14:54 - 22:09  (07:14)
reboot   system boot  5.10.0-182.0.0.9 Tue Sep 10 09:56 - 14:53 (2+04:57)
reboot   system boot  5.10.0-182.0.0.9 Fri Sep  6 12:49 - 23:44 (3+10:54)
reboot   system boot  5.10.0-182.0.0.9 Sun Sep  1 16:30 - 12:48 (4+20:17)
reboot   system boot  5.10.0-182.0.0.9 Sun Sep  1 12:49 - 16:28  (03:39)
reboot   system boot  5.10.0-182.0.0.9 Fri Aug 30 16:49 - 12:47 (1+19:58)
reboot   system boot  5.10.0-182.0.0.9 Fri Aug 30 16:37 - 16:47  (00:10)
reboot   system boot  5.10.0-182.0.0.9 Fri Aug 30 10:22 - 16:36  (06:13)

wtmp begins Fri Aug 30 10:22:12 2024

查看重启的定时任务:

[root@huawei xml]# crontab -l
no crontab for root

我没有找到在哪里上传文件,只能把日志文件上传到网盘中了,今天又无故重启了一次,
链接:夸克网盘分享

今天重启的时间大概是在16:45,每次重启前系统时间都会突然改变,您可在日志文件中可查找“Dec 11 16:42:24 huawei systemd[1]: Finished dnf makecache.”这句快速找到今天重启时的日志。

于今天17:18分又重启一次:

[root@huawei log]# last reboot
reboot   system boot  5.10.0-177.0.0.r Thu Jan  1 08:00   still running
reboot   system boot  5.10.0-177.0.0.r Thu Jan  1 08:00   still running
reboot   system boot  5.10.0-177.0.0.r Thu Jan  1 08:00   still running
reboot   system boot  5.10.0-177.0.0.r Thu Jan  1 08:00   still running
reboot   system boot  5.10.0-177.0.0.r Thu Jan  1 08:00 - 21:39 (20062+13:39)
reboot   system boot  5.10.0-177.0.0.r Thu Jan  1 08:00 - 21:39 (20062+13:39)
reboot   system boot  5.10.0-177.0.0.r Thu Jan  1 08:00 - 21:39 (20062+13:39)
reboot   system boot  5.10.0-177.0.0.r Thu Jan  1 08:00 - 21:39 (20062+13:39)
reboot   system boot  5.10.0-177.0.0.r Thu Jan  1 08:00 - 15:41 (20062+07:40)
reboot   system boot  5.10.0-177.0.0.r Thu Jan  1 08:00 - 15:41 (20062+07:40)
reboot   system boot  5.10.0-177.0.0.r Thu Jan  1 08:00 - 15:41 (20062+07:40)
reboot   system boot  5.10.0-177.0.0.r Thu Jan  1 08:00 - 15:41 (20062+07:40)
reboot   system boot  5.10.0-177.0.0.r Thu Jan  1 08:00 - 09:56 (20062+01:56)
reboot   system boot  5.10.0-177.0.0.r Thu Jan  1 08:00 - 09:56 (20062+01:56)
reboot   system boot  5.10.0-177.0.0.r Thu Jan  1 08:00 - 09:56 (20062+01:56)
reboot   system boot  5.10.0-177.0.0.r Thu Jan  1 08:00 - 15:49 (20056+07:49)
reboot   system boot  5.10.0-177.0.0.r Thu Jan  1 08:00 - 15:49 (20056+07:49)
reboot   system boot  5.10.0-177.0.0.r Thu Jan  1 08:00 - 15:49 (20056+07:49)
reboot   system boot  5.10.0-177.0.0.r Thu Jan  1 08:00 - 15:49 (20056+07:49)
reboot   system boot  5.10.0-177.0.0.r Thu Jan  1 08:00 - 15:49 (20056+07:49)
reboot   system boot  5.10.0-177.0.0.r Thu Jan  1 08:00 - 15:49 (20056+07:49)
reboot   system boot  5.10.0-177.0.0.r Thu Jan  1 08:00 - 15:49 (20056+07:49)
reboot   system boot  5.10.0-177.0.0.r Thu Jan  1 08:00 - 15:49 (20056+07:49)
reboot   system boot  5.10.0-177.0.0.r Thu Jan  1 08:00 - 15:49 (20056+07:49)
reboot   system boot  5.10.0-177.0.0.r Thu Jan  1 08:00 - 15:49 (20056+07:49)
reboot   system boot  5.10.0-177.0.0.r Thu Jan  1 08:00 - 15:49 (20056+07:49)
reboot   system boot  5.10.0-177.0.0.r Thu Jan  1 08:00 - 15:49 (20056+07:49)
reboot   system boot  5.10.0-177.0.0.r Thu Jan  1 08:00 - 15:49 (20056+07:49)
reboot   system boot  5.10.0-177.0.0.r Thu Jan  1 08:00 - 15:49 (20056+07:49)
reboot   system boot  5.10.0-177.0.0.r Thu Jan  1 08:00 - 15:49 (20056+07:49)
reboot   system boot  5.10.0-177.0.0.r Thu Jan  1 08:00 - 15:49 (20056+07:49)
reboot   system boot  5.10.0-177.0.0.r Thu Jan  1 08:00 - 15:49 (20056+07:49)
reboot   system boot  5.10.0-177.0.0.r Thu Jan  1 08:00 - 15:49 (20056+07:49)
reboot   system boot  5.10.0-177.0.0.r Thu Jan  1 08:00 - 15:49 (20056+07:49)
reboot   system boot  5.10.0-177.0.0.r Thu Jan  1 08:00 - 15:49 (20056+07:49)
reboot   system boot  5.10.0-177.0.0.r Thu Jan  1 08:00 - 15:49 (20056+07:49)
reboot   system boot  5.10.0-177.0.0.r Thu Jan  1 08:00 - 15:49 (20056+07:49)
reboot   system boot  5.10.0-177.0.0.r Thu Jan  1 08:00 - 16:09 (20033+08:09)
reboot   system boot  5.10.0-177.0.0.r Thu Jan  1 08:00 - 16:09 (20033+08:09)
reboot   system boot  5.10.0-177.0.0.r Thu Jan  1 08:00 - 16:09 (20033+08:09)
reboot   system boot  5.10.0-177.0.0.r Thu Jan  1 08:00 - 16:09 (20033+08:09)
reboot   system boot  5.10.0-177.0.0.r Thu Jan  1 08:00 - 16:09 (20033+08:09)
reboot   system boot  5.10.0-177.0.0.r Thu Jan  1 08:00 - 10:03 (20028+02:03)
reboot   system boot  5.10.0-177.0.0.r Thu Jan  1 08:00 - 18:20 (20027+10:20)
reboot   system boot  5.10.0-177.0.0.r Thu Jan  1 08:00 - 18:20 (20027+10:20)
reboot   system boot  5.10.0-177.0.0.r Thu Jan  1 08:00 - 18:20 (20027+10:20)
reboot   system boot  5.10.0-177.0.0.r Thu Jan  1 08:00 - 19:29 (20026+11:29)
reboot   system boot  5.10.0-177.0.0.r Thu Jan  1 08:00 - 19:29 (20026+11:29)
reboot   system boot  5.10.0-231.0.0.1 Wed Oct 30 14:50 - 19:29  (04:39)
reboot   system boot  5.10.0-177.0.0.r Thu Jan  1 08:00 - 19:29 (20026+11:29)
reboot   system boot  5.10.0-231.0.0.1 Wed Oct 30 09:47 - 14:39  (04:52)
reboot   system boot  5.10.0-177.0.0.r Thu Jan  1 08:00 - 09:45 (20026+01:45)
reboot   system boot  5.10.0-177.0.0.r Thu Jan  1 08:00 - 09:45 (20026+01:45)
reboot   system boot  5.10.0-177.0.0.r Thu Jan  1 08:00 - 09:45 (20026+01:45)
reboot   system boot  5.10.0-177.0.0.r Thu Jan  1 08:00 - 09:45 (20026+01:45)
reboot   system boot  5.10.0-231.0.0.1 Thu Oct 17 17:17 - 08:47 (9+15:29)
reboot   system boot  5.10.0-177.0.0.r Thu Jan  1 08:00 - 08:47 (20023+00:47)
reboot   system boot  5.10.0-177.0.0.r Thu Jan  1 08:00 - 08:47 (20023+00:47)
reboot   system boot  5.10.0-231.0.0.1 Tue Oct 15 10:41 - 08:47 (11+22:05)
reboot   system boot  5.10.0-177.0.0.r Thu Jan  1 08:00 - 08:00  (00:00)
reboot   system boot  5.10.0-177.0.0.r Thu Jan  1 08:00 - 08:00  (00:00)
reboot   system boot  5.10.0-177.0.0.r Thu Jan  1 08:00 - 10:32 (20011+02:32)
reboot   system boot  5.10.0-182.0.0.9 Fri Oct 11 13:24 - 15:54 (3+02:29)
reboot   system boot  5.10.0-182.0.0.9 Fri Sep 27 14:07 - 13:23 (13+23:15)
reboot   system boot  5.10.0-182.0.0.9 Fri Sep 27 10:36 - 13:23 (14+02:46)
reboot   system boot  5.10.0-182.0.0.9 Wed Sep 25 11:32 - 10:34 (1+23:02)
reboot   system boot  5.10.0-182.0.0.9 Tue Sep 24 18:19 - 10:34 (2+16:15)
reboot   system boot  5.10.0-182.0.0.9 Tue Sep 24 17:17 - 10:34 (2+17:17)
reboot   system boot  5.10.0-182.0.0.9 Tue Sep 24 15:55 - 17:15  (01:20)
reboot   system boot  5.10.0-182.0.0.9 Tue Sep 24 14:57 - 15:54  (00:57)
reboot   system boot  5.10.0-182.0.0.9 Mon Sep 23 19:42 - 14:54  (19:11)
reboot   system boot  5.10.0-182.0.0.9 Thu Sep 12 22:11 - 19:40 (10+21:29)
reboot   system boot  5.10.0-182.0.0.9 Thu Sep 12 15:41 - 22:09  (06:28)
reboot   system boot  5.10.0-182.0.0.9 Thu Sep 12 14:54 - 22:09  (07:14)
reboot   system boot  5.10.0-182.0.0.9 Tue Sep 10 09:56 - 14:53 (2+04:57)
reboot   system boot  5.10.0-182.0.0.9 Fri Sep  6 12:49 - 23:44 (3+10:54)
reboot   system boot  5.10.0-182.0.0.9 Sun Sep  1 16:30 - 12:48 (4+20:17)
reboot   system boot  5.10.0-182.0.0.9 Sun Sep  1 12:49 - 16:28  (03:39)
reboot   system boot  5.10.0-182.0.0.9 Fri Aug 30 16:49 - 12:47 (1+19:58)
reboot   system boot  5.10.0-182.0.0.9 Fri Aug 30 16:37 - 16:47  (00:10)
reboot   system boot  5.10.0-182.0.0.9 Fri Aug 30 10:22 - 16:36  (06:13)

wtmp begins Fri Aug 30 10:22:12 2024

对应的日志文件链接:夸克网盘分享
可在日志文件中搜索“Dec 11 17:16:58 huawei dockerd[3054]: time=“2024-12-11T17:16:58.932995006+08:00””来快速定位至重启时间附近的日志

你提供的last reboot的时间很怪异,你的系统应该是跑在虚拟机里面吧?
另外由于公司的网络无法访问夸克网盘,所以我只能下班后,回去看下你上传到夸克网盘中的log.

系统运行在物理机上,每次异常重启前,系统的时钟都会错乱,我也不知道什么原因

我看了下你提供的log,但是里面缺少出现问题时的内核log,也无法看到重启的原因,我看你的log中有启动kdump,应该是重启的时候会生成内核的coredump文件
Jan 1 08:00:33 huawei kdumpctl[3076]: kexec: loaded kdump kernel
Jan 1 08:00:33 huawei kdumpctl[3076]: Starting kdump: [OK]
Jan 1 08:00:33 huawei systemd[1]: Finished Crash recovery kernel arming.

你看下,你的/var/crash目录下是否有生成kernel的core文件?有的话,使用crash工具分析下,是由于什么原因导致重启的。
关于kdump和crash工具的使用,如果没接触过的话,你可以到网上搜下相关资料学习下,资料挺多的,也比较容易上手.