djfflow
Goto Top

CoreOS Rebooted automatisch

Hallo,

ich wollte mich privat mal mit Docker etc. ausprobieren.
Dafür habe ich einen alten HP ProDesk 400G5 DM mit CoreOS installiert.
Das hat auch alles soweit funktioniert.
Leider startet der Host alle paar Minuten neu ohne erkennbaren Grund.
Die Einträge von journalctl sind wie folgt:

Nov 03 16:06:01 coreos kernel: r8169 0000:02:00.0 enp2s0: Link is Up - 1Gbps/Full - flow control off
Nov 03 16:06:01 coreos NetworkManager[1026]: <info>  [1730646361.6686] device (enp2s0): carrier: link connected
Nov 03 16:06:01 coreos NetworkManager[1026]: <info>  [1730646361.6693] device (enp2s0): state change: unavailable -> disconnected (reason 'carrier-changed', sys-iface-state: 'managed')  
Nov 03 16:06:01 coreos NetworkManager[1026]: <info>  [1730646361.6704] policy: auto-activating connection 'Wired connection 1' (3fd2f2c2-148d-3dad-ac0b-a16061d603c7)  
Nov 03 16:06:01 coreos NetworkManager[1026]: <info>  [1730646361.6710] device (enp2s0): Activation: starting connection 'Wired connection 1' (3fd2f2c2-148d-3dad-ac0b-a16061d603c7)  
Nov 03 16:06:01 coreos NetworkManager[1026]: <info>  [1730646361.6711] device (enp2s0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')  
Nov 03 16:06:01 coreos NetworkManager[1026]: <info>  [1730646361.6714] manager: NetworkManager state is now CONNECTING
Nov 03 16:06:01 coreos NetworkManager[1026]: <info>  [1730646361.6717] device (enp2s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')  
Nov 03 16:06:01 coreos NetworkManager[1026]: <info>  [1730646361.6741] device (enp2s0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')  
Nov 03 16:06:01 coreos NetworkManager[1026]: <info>  [1730646361.6748] dhcp4 (enp2s0): activation: beginning transaction (timeout in 45 seconds)
Nov 03 16:06:01 coreos NetworkManager[1026]: <info>  [1730646361.6775] dhcp4 (enp2s0): state changed new lease, address=192.168.2.161, acd pending
Nov 03 16:06:01 coreos NetworkManager[1026]: <info>  [1730646361.8559] dhcp4 (enp2s0): state changed new lease, address=192.168.2.161
Nov 03 16:06:01 coreos NetworkManager[1026]: <info>  [1730646361.8566] policy: set 'Wired connection 1' (enp2s0) as default for IPv4 routing and DNS  
Nov 03 16:06:01 coreos systemd-resolved[982]: enp2s0: Bus client set search domain list to: Wolff.internal
Nov 03 16:06:01 coreos systemd-resolved[982]: enp2s0: Bus client set default route setting: yes
Nov 03 16:06:01 coreos systemd-resolved[982]: enp2s0: Bus client set DNS server list to: 192.168.2.173, 192.168.2.191
Nov 03 16:06:01 coreos NetworkManager[1026]: <info>  [1730646361.8642] device (enp2s0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')  
Nov 03 16:06:01 coreos NetworkManager[1026]: <info>  [1730646361.8948] device (enp2s0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')  
Nov 03 16:06:01 coreos NetworkManager[1026]: <info>  [1730646361.8950] device (enp2s0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')  
Nov 03 16:06:01 coreos NetworkManager[1026]: <info>  [1730646361.8952] manager: NetworkManager state is now CONNECTED_SITE
Nov 03 16:06:01 coreos NetworkManager[1026]: <info>  [1730646361.8953] device (enp2s0): Activation: successful, device activated.
Nov 03 16:06:01 coreos NetworkManager[1026]: <info>  [1730646361.8957] manager: NetworkManager state is now CONNECTED_GLOBAL
Nov 03 16:06:01 coreos NetworkManager[1026]: <info>  [1730646361.8959] manager: startup complete
Nov 03 16:06:01 coreos systemd[1]: iscsi.service: Unit cannot be reloaded because it is inactive.
Nov 03 16:06:02 coreos NetworkManager[1026]: <info>  [1730646362.8517] policy: set 'Wired connection 1' (enp2s0) as default for IPv6 routing and DNS  
Nov 03 16:06:06 coreos chronyd[1072]: Selected source 94.16.122.152 (2.fedora.pool.ntp.org)
Nov 03 16:06:06 coreos chronyd[1072]: System clock TAI offset set to 37 seconds
Nov 03 16:06:08 coreos chronyd[1072]: Selected source 31.209.85.242 (2.fedora.pool.ntp.org)
Nov 03 16:06:11 coreos systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
Nov 03 16:06:11 coreos audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'  
Nov 03 16:06:28 coreos systemd[1]: systemd-hostnamed.service: Deactivated successfully.
Nov 03 16:06:28 coreos audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-hostnamed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'  
Nov 03 16:06:28 coreos audit: BPF prog-id=73 op=UNLOAD
Nov 03 16:06:28 coreos audit: BPF prog-id=72 op=UNLOAD
Nov 03 16:06:28 coreos audit: BPF prog-id=71 op=UNLOAD
Nov 03 16:07:03 coreos systemd[1]: rpm-ostreed.service: Deactivated successfully.
Nov 03 16:07:03 coreos audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=rpm-ostreed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'  
Nov 03 16:08:18 coreos chronyd[1072]: Source 85.215.166.214 replaced with 2a01:4f8:c17:b041::1 (2.fedora.pool.ntp.org)
-- Boot 396390055ecb43619fb04a847d2e5306 --
Nov 03 16:10:11 localhost kernel: Linux version 6.10.10-200.fc40.x86_64 (mockbuild@2374eca717094fd08bdac86b6da02923) (gcc (GCC) 14.2.1 20240801 (Red Hat 14.2.1-1), GNU ld version 2.41-37.fc40) #1 SMP PREEMPT_DYNAMIC Thu Sep 12 18:26:09 UTC 2024
Nov 03 16:10:11 localhost kernel: Command line: BOOT_IMAGE=(hd0,gpt3)/boot/ostree/fedora-coreos-8241641a3abd0f0493dc733abbcc99739b0ff91286dfccbd787c4fac50e0acd9/vmlinuz-6.10.10-200.fc40.x86_64 rw mitigations=auto,nosmt ostree=/ostree/boot.0/fedora-coreos/8241641a3abd0f0493dc733abbcc99739b0ff91286dfccbd787c4fac50e0acd9/0 ignition.platform.id=metal root=UUID=5ec73e2a-5925-4c15-9c06-78e9b80074bc rw rootflags=prjquota boot=UUID=7ca9b88e-1b58-4caf-99ad-0455fd2a2590

Was ist der Fehler?

MfG

Content-ID: 669220

Url: https://administrator.de/contentid/669220

Ausgedruckt am: 05.11.2024 um 10:11 Uhr

catrell
catrell 03.11.2024 aktualisiert um 18:15:29 Uhr
Goto Top
Moin.
Da im Log nichts über einen regulären Reboot steht wird's vermutlich auf ne Kernel Panic hinaus gelaufen sein.
dmesg Log, und pstore Logs des Kernels checken
https://docs.kernel.org/admin-guide/pstore-blk.html

Gruß catrell
djfflow
djfflow 04.11.2024 um 10:05:07 Uhr
Goto Top
Hi,

da ich leider ein absoluter Anfänger bei Linux bin, ist meine Frage: Wie kann ich das konfigurieren?

PS. Das Verhalten tritt nur auf, wenn kein Monitor angeschlossen ist. Sobald ein TFT dran ist, läuft die Maschine ganz normal.

Gruß
catrell
catrell 04.11.2024 um 10:38:28 Uhr
Goto Top