On Sun, Feb 7, 2016 at 3:14 PM, Johannes Kastl <mail@ojkastl.de> wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi everyone,
a quick search in the mailinglist archives does not reveal anything related, so:
On my Tumbleweed machine sshd does not start during boot, once the machine is up I can restart it without errors.
# systemctl status sshd
Jan 16 10:25:19 XYZ systemd[1]: sshd.service: Unit entered failed state. Jan 16 10:25:19 XYZ systemd[1]: sshd.service: Failed with result 'start-limit'. Jan 16 10:25:19 XYZ systemd-coredump[1488]: Process 1485 (sshd) of user 0 dumped core.
#journalctl -u sshd -b
-- Logs begin at .... -- Jan 16 10:25:19 XYZ systemd[1]: sshd.service: Unit entered failed state. Jan 16 10:25:19 XYZ systemd[1]: sshd.service: Failed with result 'start-limit'. Jan 16 10:25:19 XYZ systemd-coredump[1488]: Process 1485 (sshd) of user 0 dumped core. -- Subject: Process 1485 (sshd) dumped core -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- Documentation: man:core(5) -- -- Process 1485 (sshd) crashed and dumped core. -- -- This usually indicates a programming error in the crashing program and -- should be reported to its vendor as a bug.
I'm not sure when it started, as you can see the log is from 16th of January. I just tested it again today, it seems to work on some boots, but still I see this (3 out of 5 times today).
Any hints? Ringing any bells?
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 ? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org