System crash - Leap 15.0 - Dell R640

Hi

Urgent help appreciated. Wanted to start going over to Suse.

We have been running Leap 15.0 for a month but have had 3 system freezes so far.

Any suggestions, Leap 15.0 not stable yet?
Is there another stable open Suse I can try?

I have done an OS update a week ago.

journalctl

Nov 12 09:35:30 linux-0ttl systemd[1]: Started Getty on tty1.
Nov 12 09:35:39 linux-0ttl login[29931]: pam_unix(login:auth): authentication failure; logname=LOGIN uid=0 euid=0 tty=tty1 ruse>
Nov 12 09:35:40 linux-0ttl login[29931]: FAILED LOGIN 1 FROM tty1 FOR root, Authentication failure
Nov 12 09:36:08 linux-0ttl sshd[29937]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost>
Nov 12 09:36:10 linux-0ttl sshd[29934]: error: PAM: Authentication failure for root from 192.168.1.54
Nov 12 09:36:33 linux-0ttl systemd[1]: getty@tty1.service: Service has no hold-off time, scheduling restart.
Nov 12 09:36:33 linux-0ttl systemd[1]: Stopped Getty on tty1.
Nov 12 09:36:33 linux-0ttl systemd[1]: Started Getty on tty1.
Nov 12 09:36:37 linux-0ttl sshd[29934]: Accepted keyboard-interactive/pam for root from 192.168.1.54 port 56091 ssh2
Nov 12 09:36:37 linux-0ttl systemd[1]: Created slice User Slice of root.
Nov 12 09:36:37 linux-0ttl systemd[1]: Starting User Manager for UID 0…
Nov 12 09:36:37 linux-0ttl systemd-logind[1070]: New session 4 of user root.
Nov 12 09:36:37 linux-0ttl systemd[1]: Started Session 4 of user root.
Nov 12 09:36:37 linux-0ttl systemd[29940]: pam_unix(systemd-user:session): session opened for user root by (uid=0)
Nov 12 09:36:37 linux-0ttl systemd[29940]: Starting D-Bus User Message Bus Socket.
Nov 12 09:36:37 linux-0ttl systemd[29940]: Reached target Paths.
Nov 12 09:36:37 linux-0ttl systemd[29940]: Reached target Timers.
Nov 12 09:36:37 linux-0ttl systemd[29940]: Listening on D-Bus User Message Bus Socket.
Nov 12 09:36:37 linux-0ttl systemd[29940]: Reached target Sockets.
Nov 12 09:36:37 linux-0ttl systemd[29940]: Reached target Basic System.
Nov 12 09:36:37 linux-0ttl sshd[29934]: pam_unix(sshd:session): session opened for user root by (uid=0)
Nov 12 09:36:37 linux-0ttl systemd[29940]: Reached target Default.
Nov 12 09:36:37 linux-0ttl systemd[29940]: Startup finished in 98ms.
Nov 12 09:36:37 linux-0ttl systemd[1]: Started User Manager for UID 0.
Nov 12 09:40:56 linux-0ttl kernel: usb 1-14.1.1: USB disconnect, device number 7
Nov 12 09:41:16 linux-0ttl kernel: usb 1-14.1.1: new high-speed USB device number 8 using xhci_hcd
Nov 12 09:41:17 linux-0ttl kernel: usb 1-14.1.1: New USB device found, idVendor=0624, idProduct=0249
Nov 12 09:41:17 linux-0ttl kernel: usb 1-14.1.1: New USB device strings: Mfr=4, Product=5, SerialNumber=6
Nov 12 09:41:17 linux-0ttl kernel: usb 1-14.1.1: Product: Keyboard/Mouse Function
Nov 12 09:41:17 linux-0ttl kernel: usb 1-14.1.1: Manufacturer: Avocent
Nov 12 09:41:17 linux-0ttl kernel: usb 1-14.1.1: SerialNumber: 20151118
Nov 12 09:41:17 linux-0ttl kernel: input: Avocent Keyboard/Mouse Function as /devices/pci0000:00/0000:00:14.0/usb1/1-14/1-14.1/>
Nov 12 09:41:17 linux-0ttl kernel: hid-generic 0003:0624:0249.0005: input,hidraw0: USB HID v1.00 Keyboard [Avocent Keyboard/Mou>
Nov 12 09:41:17 linux-0ttl kernel: input: Avocent Keyboard/Mouse Function as /devices/pci0000:00/0000:00:14.0/usb1/1-14/1-14.1/>
Nov 12 09:41:17 linux-0ttl kernel: hid-generic 0003:0624:0249.0006: input,hidraw1: USB HID v1.00 Mouse [Avocent Keyboard/Mouse >
Nov 12 09:41:17 linux-0ttl mtp-probe[30016]: checking bus 1, device 8: "/sys/devices/pci0000:00/0000:00:14.0/usb1/1-14/1-14.1/1>
Nov 12 09:41:17 linux-0ttl mtp-probe[30016]: bus: 1, device: 8 was not an MTP device
Nov 12 09:41:17 linux-0ttl systemd-logind[1070]: Watching system buttons on /dev/input/event0 (Avocent Keyboard/Mouse Function)
Nov 12 09:41:47 linux-0ttl sshd[29934]: pam_unix(sshd:session): session closed for user root
Nov 12 09:41:47 linux-0ttl systemd-logind[1070]: Removed session 4.
Nov 12 09:41:47 linux-0ttl systemd[1]: Stopping User Manager for UID 0…
Nov 12 09:41:47 linux-0ttl systemd[29940]: Stopped target Default.
Nov 12 09:41:47 linux-0ttl systemd[29940]: Stopped target Basic System.
Nov 12 09:41:47 linux-0ttl systemd[29940]: Stopped target Timers.
Nov 12 09:41:47 linux-0ttl systemd[29940]: Stopped target Paths.
Nov 12 09:41:47 linux-0ttl systemd[29940]: Stopped target Sockets.
Nov 12 09:41:47 linux-0ttl systemd[29940]: Closed D-Bus User Message Bus Socket.
Nov 12 09:41:47 linux-0ttl systemd[29940]: Reached target Shutdown.
Nov 12 09:41:47 linux-0ttl systemd[29940]: Starting Exit the Session…
Nov 12 09:41:47 linux-0ttl systemd[29940]: Received SIGRTMIN+24 from PID 30026 (kill).
Nov 12 09:41:47 linux-0ttl systemd[29941]: pam_unix(systemd-user:session): session closed for user root
Nov 12 09:41:47 linux-0ttl systemd[1]: Stopped User Manager for UID 0.
Nov 12 09:41:47 linux-0ttl systemd[1]: Removed slice User Slice of root.
Nov 12 09:41:59 linux-0ttl kernel: usb 1-14.1.1: USB disconnect, device number 8
Nov 12 10:00:00 linux-0ttl systemd[1]: Started Timeline of Snapper Snapshots.
Nov 12 10:00:00 linux-0ttl dbus-daemon[1018]: [system] Activating service name=‘org.opensuse.Snapper’ requested by ‘:1.2328’ (u>
Nov 12 10:00:00 linux-0ttl dbus-daemon[1018]: [system] Successfully activated service ‘org.opensuse.Snapper’
Nov 12 11:00:00 linux-0ttl systemd[1]: Started Timeline of Snapper Snapshots.
Nov 12 11:00:00 linux-0ttl dbus-daemon[1018]: [system] Activating service name=‘org.opensuse.Snapper’ requested by ‘:1.2330’ (u>
Nov 12 11:00:00 linux-0ttl dbus-daemon[1018]: [system] Successfully activated service ‘org.opensuse.Snapper’
Nov 12 12:00:00 linux-0ttl systemd[1]: Started Timeline of Snapper Snapshots.
Nov 12 12:00:00 linux-0ttl dbus-daemon[1018]: [system] Activating service name=‘org.opensuse.Snapper’ requested by ‘:1.2332’ (u>
Nov 12 12:00:00 linux-0ttl dbus-daemon[1018]: [system] Successfully activated service ‘org.opensuse.Snapper’
Nov 12 13:00:00 linux-0ttl systemd[1]: Started Timeline of Snapper Snapshots.
Nov 12 13:00:00 linux-0ttl dbus-daemon[1018]: [system] Activating service name=‘org.opensuse.Snapper’ requested by ‘:1.2334’ (u>
Nov 12 13:00:00 linux-0ttl dbus-daemon[1018]: [system] Successfully activated service ‘org.opensuse.Snapper’
Nov 12 14:00:00 linux-0ttl systemd[1]: Started Timeline of Snapper Snapshots.
Nov 12 14:00:00 linux-0ttl dbus-daemon[1018]: [system] Activating service name=‘org.opensuse.Snapper’ requested by ‘:1.2336’ (u>
Nov 12 14:00:00 linux-0ttl dbus-daemon[1018]: [system] Successfully activated service ‘org.opensuse.Snapper’
Nov 12 15:00:00 linux-0ttl systemd[1]: Started Timeline of Snapper Snapshots.
Nov 12 15:00:00 linux-0ttl dbus-daemon[1018]: [system] Activating service name=‘org.opensuse.Snapper’ requested by ‘:1.2338’ (u>
Nov 12 15:00:00 linux-0ttl dbus-daemon[1018]: [system] Successfully activated service ‘org.opensuse.Snapper’
Nov 12 15:01:17 linux-0ttl chronyd[1095]: Selected source 217.114.59.66

– Reboot –

Nov 12 15:19:48 linux-0ttl kernel: Linux version 4.12.14-lp150.12.22-default (geeko@buildhost) (gcc version 7.3.1 20180323 gcc>
Nov 12 15:19:48 linux-0ttl kernel: Command line: root=UUID=a1c6fa7b-0a94-429a-a9af-3004c9bdd6ba resume=/dev/disk/by-uuid/9b4c9>
Nov 12 15:19:48 linux-0ttl kernel: x86/fpu: Supporting XSAVE feature 0x001: ‘x87 floating point registers’
Nov 12 15:19:48 linux-0ttl kernel: x86/fpu: Supporting XSAVE feature 0x002: ‘SSE registers’
Nov 12 15:19:48 linux-0ttl kernel: x86/fpu: Supporting XSAVE feature 0x004: ‘AVX registers’
Nov 12 15:19:48 linux-0ttl kernel: x86/fpu: Supporting XSAVE feature 0x020: ‘AVX-512 opmask’
Nov 12 15:19:48 linux-0ttl kernel: x86/fpu: Supporting XSAVE feature 0x040: ‘AVX-512 Hi256’
Nov 12 15:19:48 linux-0ttl kernel: x86/fpu: Supporting XSAVE feature 0x080: ‘AVX-512 ZMM_Hi256’

Thanks!!

What is the nature of the freezes, forcing to reboot? Unresponsive for a determinate period? Other?

How much freespace is available on the system’s filesystem?

Has memtest been used to confirm all RAM seems OK?

When were the freezes, all recent, or spread out randomly over the whole month since installation?

Have you tried to determine if the freezes are associated in time when an hourly timeline snapshot was taking place?

Thank you for your response…

Complete freeze, iDrac console dead, no ssh. Have to boot with iDrac.

New system, lots of space.

I am going to try that now.

3 Times in two weeks, not same times. Sun,Mon,Mon.

I do not think it is related as the freezes was not one the hour.

Felix