https://bugzilla.suse.com/show_bug.cgi?id=1229028 https://bugzilla.suse.com/show_bug.cgi?id=1229028#c7 --- Comment #7 from Antonio Feijoo <antonio.feijoo@suse.com> --- Thanks for the logs. So it's sshd:
Aug 30 09:53:39 asus sshd[2025]: Accepted publickey for root from 192.168.0.14 port 48240 ssh2: RSA SHA256:fQ/WvO6CBX8uzQaDceKKxAYRJRA17sO1sGYtxqle+RM Aug 30 09:53:39 asus sshd[2027]: Received disconnect from 192.168.0.14 port 48240:11: disconnected by user Aug 30 09:53:39 asus sshd[2027]: Disconnected from user root 192.168.0.14 port 48240 Aug 30 09:53:39 asus systemd[1]: Received SIGCHLD from PID 2027 (sshd). Aug 30 09:53:39 asus kernel: Core dump to |/bin/false pipe failed Aug 30 09:53:39 asus systemd[1]: Child 2027 (sshd) died (code=exited, status=255/EXCEPTION) Aug 30 09:53:39 asus systemd[1]: sshd.service: Child 2027 belongs to sshd.service.
Now there are 2 options: - First I would check if you can ssh to your machine _after_ the system is completely booted (i.e., not on the initrd). If this fails, there is an issue in sshd. - If that does not fail, then there should be some missing dependency/library in the initrd. If you have direct access to this machine, could you add `rd.break` to the kernel command line (this stops the boot process before switching root and displays the emergency shell), try to connect from another system to create the failure, and then get the output of `systemctl status sshd.service` from the emergency shell to check if it provides more useful info? -- You are receiving this mail because: You are on the CC list for the bug.