[opensuse-factory] Tumbleweed: SSHD not starting during boot, manual restart works after boot has finished
-----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). System is: openSUSE 20160130 (x86_64) VERSION = 20160130 CODENAME = Tumbleweed Any hints? Ringing any bells? Johannes -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 Comment: Using GnuPG with SeaMonkey - http://www.enigmail.net/ iEYEARECAAYFAla3iZwACgkQzi3gQ/xETbIAuACfZTa9jBNrRPR9lUaN4hLlWv49 5sYAn080pkIviY+5cNfSiIiW1ISiUbRY =jWKQ -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
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
-----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, 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.
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... Johannes -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 Comment: Using GnuPG with SeaMonkey - http://www.enigmail.net/ iEYEARECAAYFAla3lVcACgkQzi3gQ/xETbJ+3gCfSaEuTB7XY3PerIJJPV9Up2Ns kb0AnAriOi0DTG1F6R0T4B7bWyTb/Dve =8IFd -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Sun, Feb 7, 2016 at 4:05 PM, Johannes Kastl <mail@ojkastl.de> wrote:
-----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
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Am 07.02.16 schrieb Cristian Rodríguez:
On Sun, Feb 7, 2016 at 4:05 PM, Johannes Kastl <mail@ojkastl.de> wrote:
There is a lot of output from coredumpctl info,
So, you have an history of different processes crashing or is just sshd ?
At first glance it seems to be mainly sshd, I saw one from snapper. I'll have a closer look tomorrow, memtest is still running (see below) .
Is there a backtrace available.. coredumpctl gdb ..
I'll have a look, once memtest is finished.
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.
After nearly 24h auf memtest there are not errors shown, so I guess it's not the ram. But just to be sure I'll let it run another night. Johannes -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 Comment: Using GnuPG with SeaMonkey - http://www.enigmail.net/ iEYEARECAAYFAla44O4ACgkQzi3gQ/xETbLCugCfUE5J4T1Jx+/oDBhDej6Ut+uJ /CAAn0H5ywsw1m42p/N2X6jiR3vZer4K =O81q -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On lundi, 8 février 2016 19.39:47 h CET Johannes Kastl wrote:
Am 07.02.16 schrieb Cristian Rodríguez:
On Sun, Feb 7, 2016 at 4:05 PM, Johannes Kastl <mail@ojkastl.de> wrote:
There is a lot of output from coredumpctl info,
So, you have an history of different processes crashing or is just sshd ?
At first glance it seems to be mainly sshd, I saw one from snapper. I'll have a closer look tomorrow, memtest is still running (see below) .
Is there a backtrace available.. coredumpctl gdb ..
I'll have a look, once memtest is finished.
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.
After nearly 24h auf memtest there are not errors shown, so I guess it's not the ram. But just to be sure I'll let it run another night.
Johannes
Check also your ssd ... when they start bugging no one could stop them. -- Bruno Friedmann Ioda-Net Sàrl www.ioda-net.ch openSUSE Member, fsfe fellowship GPG KEY : D5C9B751C4653227 irc: tigerfoot -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Hi Bruno, sorry for the late reply. Am 12.02.16 schrieb Bruno Friedmann:
Check also your ssd ... when they start bugging no one could stop them.
This on is on rotating rust aka HDD. Which is fine, according to SMART. I'll try to have a look at the strackstrace that Cristian mentioned, once I find time... Johannes
participants (4)
-
Bruno Friedmann -
Cristian Rodríguez -
Johannes Kastl -
Johannes Kastl