On Sun, Feb 7, 2016 at 4:05 PM, Johannes Kastl
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi Cristian,
Am 07.02.16 schrieb Cristian Rodríguez:
I am not disregarding a possible bug,race condition whatever in openSSH.. but.. does your system RAM passes memtest ? what is the output of coredumpctl info ?
There is a lot of output from coredumpctl info,
So, you have an history of different processes crashing or is just sshd ?
the one belonging to the crash/log in my OP:
PID: 1446 (sshd) UID: 0 (root) GID: 0 (root) Signal: 11 (SEGV) Timestamp: Sa 2016-01-16 10:25:16 CET (3 weeks 1 days ago) Command Line: /usr/sbin/sshd -D Executable: /usr/sbin/sshd Control Group: /system.slice/sshd.service Unit: sshd.service Slice: system.slice Boot ID: 5313a059f4e64324af2f6067025b024e Machine ID: c33e941e82804ea784ea7a912d6d371b Hostname: XYZ Message: Process 1446 (sshd) of user 0 dumped core.
Is there a backtrace available.. coredumpctl gdb ..
I will run a memtest this night, thanks for the hint. But as the machine seems to work fine apart from not starting sshd on boot I do not think this is the reason...
It might be a bug..I will grant you that..openSSH in tumbleweed is very out of date too.. but when software that does crypto and is known to be reliable starts to randomly crash according to the phase of the moon..the first thing to look at is your RAM. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org