`VM` is crashing every 30 minutes and need reset !!!

[saberistic]

Have we checked os crashes logs? Please share them

[Amirsharifico]

used last -x reboot to find out the reboot time, then using journalctl --since "2023-08-17 15:37:00" --until "2023-08-17 15:42:00" got the log few minutes before and after the reboot (reboot time bolded below), from here I do not see or can not see what caused the reboot , Please advise

Aug 17 15:26:20 designity2nd-vm systemd[1]: Starting GCE Workload Certificate refresh... Aug 17 15:26:20 designity2nd-vm gce_workload_cert_refresh[20078]: 2023/08/17 15:26:20: Error getting config status, workload certificates may not be configured: HTTP 404 Aug 17 15:26:20 designity2nd-vm gce_workload_cert_refresh[20078]: 2023/08/17 15:26:20: Done Aug 17 15:26:20 designity2nd-vm systemd[1]: gce-workload-cert-refresh.service: Succeeded. Aug 17 15:26:20 designity2nd-vm systemd[1]: Finished GCE Workload Certificate refresh. Aug 17 15:26:35 designity2nd-vm dhclient[468]: XMT: Solicit on ens4, interval 110220ms. Aug 17 15:28:25 designity2nd-vm dhclient[468]: XMT: Solicit on ens4, interval 119280ms. Aug 17 15:30:24 designity2nd-vm dhclient[468]: XMT: Solicit on ens4, interval 116820ms. Aug 17 15:32:21 designity2nd-vm dhclient[468]: XMT: Solicit on ens4, interval 110580ms. Aug 17 15:34:12 designity2nd-vm dhclient[468]: XMT: Solicit on ens4, interval 127190ms. Aug 17 15:36:35 designity2nd-vm dhclient[468]: XMT: Solicit on ens4, interval 114770ms. Aug 17 15:38:51 designity2nd-vm dhclient[468]: XMT: Solicit on ens4, interval 127560ms. Aug 17 15:39:29 designity2nd-vm systemd[1]: Starting GCE Workload Certificate refresh... Aug 17 15:39:30 designity2nd-vm gce_workload_cert_refresh[22873]: 2023/08/17 15:39:30: Error getting config status, workload certificates may not be configured: HTTP 404 Aug 17 15:39:30 designity2nd-vm gce_workload_cert_refresh[22873]: 2023/08/17 15:39:30: Done Aug 17 15:39:30 designity2nd-vm systemd[1]: gce-workload-cert-refresh.service: Succeeded. Aug 17 15:39:30 designity2nd-vm systemd[1]: Finished GCE Workload Certificate refresh. Aug 17 15:39:31 designity2nd-vm sshd[22868]: Received disconnect from 35.235.244.34 port 33795:11: [preauth] Aug 17 15:39:31 designity2nd-vm sshd[22868]: Disconnected from authenticating user mehdidehdar89 35.235.244.34 port 33795 [preauth] Aug 17 15:39:34 designity2nd-vm google_guest_agent[520]: Updating keys for user mehdidehdar89. Aug 17 15:39:45 designity2nd-vm sshd[23046]: Accepted publickey for mehdidehdar89 from 35.235.244.34 port 40977 ssh2: ECDSA SHA256:1Se1LRDHbYjIMoZ//TV7uBRXfnaECR2emRyLhjXlXcM Aug 17 15:39:45 designity2nd-vm sshd[23046]: pam_unix(sshd:session): session opened for user mehdidehdar89(uid=1001) by (uid=0) Aug 17 15:39:45 designity2nd-vm systemd-logind[893]: New session 8 of user mehdidehdar89. Aug 17 15:39:45 designity2nd-vm systemd[1]: Started Session 8 of user mehdidehdar89. -- Boot 92764a270ca1482d82ab65414722d0e6 -- Aug 17 15:40:06 debian kernel: Linux version 5.10.0-24-cloud-amd64 (debian-kernel@lists.debian.org) (gcc-10 (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2) #1 SMP Debian 5.10.179-5 (2023-08-08) Aug 17 15:40:06 debian kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.10.0-24-cloud-amd64 root=UUID=72d18f0c-ddaf-4b73-b512-56102153f78f ro console=tty0 console=ttyS0,115200 earlyprintk=ttyS0,115200 consoleblank=0 Aug 17 15:40:06 debian kernel: BIOS-provided physical RAM map: Aug 17 15:40:06 debian kernel: BIOS-e820: [mem 0x0000000000000000-0x0000000000000fff] reserved Aug 17 15:40:06 debian kernel: BIOS-e820: [mem 0x0000000000001000-0x0000000000054fff] usable Aug 17 15:40:06 debian kernel: BIOS-e820: [mem 0x0000000000055000-0x000000000005ffff] reserved Aug 17 15:40:06 debian kernel: BIOS-e820: [mem 0x0000000000060000-0x0000000000097fff] usable Aug 17 15:40:06 debian kernel: BIOS-e820: [mem 0x0000000000098000-0x000000000009ffff] reserved Aug 17 15:40:06 debian kernel: BIOS-e820: [mem 0x0000000000100000-0x00000000bf8ecfff] usable Aug 17 15:40:06 debian kernel: BIOS-e820: [mem 0x00000000bf8ed000-0x00000000bf9ecfff] reserved Aug 17 15:40:06 debian kernel: BIOS-e820: [mem 0x00000000bf9ed000-0x00000000bfaecfff] type 20 Aug 17 15:40:06 debian kernel: BIOS-e820: [mem 0x00000000bfaed000-0x00000000bfb6cfff] reserved Aug 17 15:40:06 debian kernel: BIOS-e820: [mem 0x00000000bfb6d000-0x00000000bfb7efff] ACPI data Aug 17 15:40:06 debian kernel: BIOS-e820: [mem 0x00000000bfb7f000-0x00000000bfbfefff] ACPI NVS Aug 17 15:40:06 debian kernel: BIOS-e820: [mem 0x00000000bfbff000-0x00000000bffdffff] usable Aug 17 15:40:06 debian kernel: BIOS-e820: [mem 0x00000000bffe0000-0x00000000bfffffff] reserved Aug 17 15:40:06 debian kernel: BIOS-e820: [mem 0x0000000100000000-0x000000043fffffff] usable Aug 17 15:40:06 debian kernel: printk: bootconsole [earlyser0] enabled Aug 17 15:40:06 debian kernel: NX (Execute Disable) protection: active Aug 17 15:40:06 debian kernel: efi: EFI v2.70 by EDK II Aug 17 15:40:06 debian kernel: efi: TPMFinalLog=0xbfbf7000 ACPI=0xbfb7e000 ACPI 2.0=0xbfb7e014 SMBIOS=0xbf9ca000 MEMATTR=0xbe394018 Aug 17 15:40:06 debian kernel: secureboot: Secure boot disabled Aug 17 15:40:06 debian kernel: SMBIOS 2.4 present. Aug 17 15:40:06 debian kernel: DMI: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/03/2023 Aug 17 15:40:06 debian kernel: Hypervisor detected: KVM Aug 17 15:40:06 debian kernel: kvm-clock: Using msrs 4b564d01 and 4b564d00 Aug 17 15:40:06 debian kernel: kvm-clock: cpu 0, msr 3d6a01001, primary cpu clock Aug 17 15:40:06 debian kernel: kvm-clock: using sched offset of 8204473680 cycles Aug 17 15:40:06 debian kernel: clocksource: kvm-clock: mask: 0xffffffffffffffff max_cycles: 0x1cd42e4dffb, max_idle_ns: 881590591483 ns Aug 17 15:40:06 debian kernel: tsc: Detected 2200.154 MHz processor Aug 17 15:40:06 debian kernel: e820: update [mem 0x00000000-0x00000fff] usable ==> reserved Aug 17 15:40:06 debian kernel: e820: remove [mem 0x000a0000-0x000fffff] usable Aug 17 15:40:06 debian kernel: last_pfn = 0x440000 max_arch_pfn = 0x400000000 Aug 17 15:40:06 debian kernel: MTRR default type: write-back Aug 17 15:40:06 debian kernel: MTRR fixed ranges enabled:

[Amirsharifico]

https://cloudlogging.app.goo.gl/BjFQtjyToykEZeZs8

the GCP VM log also may help !!!

[saberistic]

any progress here? still happening? stale issue!

[Amirsharifico]

Last progress was the one that I asked for advise