From: Jelle Licht <jlicht@fsfe.org>
To: "Giovanni Biscuolo" <g@xelera.eu>, 宋文武 <iyzsong@member.fsf.org>
Cc: 37309@debbugs.gnu.org
Subject: bug#37309: ‘ssh-daemon’ service fails to start at boot
Date: Fri, 29 Nov 2019 10:51:46 +0100 [thread overview]
Message-ID: <87r21rui19.fsf@jlicht.xyz> (raw)
In-Reply-To: <87imn3f52y.fsf@roquette.mug.biscuolo.net>
Hi Giovanni,
Giovanni Biscuolo <g@xelera.eu> writes:
> Hi Jelle,
>
> Jelle Licht <jlicht@fsfe.org> writes:
>
> [...]
>
>> I think I am also running into a similar issue on my spinning rust based
>> T400. Is there a workaround available that does the above,
>
> I added `(extra-content "ListenAddress 0.0.0.0")` to my
> openssh-configuration, to only listen on IPv4 addresses:
>
> --8<---------------cut here---------------start------------->8---
> (service openssh-service-type
> (openssh-configuration
> (port-number 22)
> (extra-content "ListenAddress 0.0.0.0")
> (authorized-keys
> `(("g" ,(local-file "keys/ssh/g.pub"))
> ("hydra",(local-file "keys/ssh/hydra.pub"))))))
> --8<---------------cut here---------------end--------------->8---
>
> I tried to reboot several times one machine I can use for testing and it
> works for me: please can you try and report if this also works for you?
This, in combination with setting the pid-file-timeout to 30 seconds,
made everything work! I guess it is a combination of fun IPv6
interactions with extremely slow and busy spinning rust.
Thank you!
This does still like a workaround instead of a proper fix though; is
there something we can do to mitigate these issues in the first place?
- Jelle
next prev parent reply other threads:[~2019-11-29 9:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87k1da6fdb.fsf@roquette.mug.biscuolo.net>
[not found] ` <87y315t3hw.fsf@roquette.mug.biscuolo.net>
[not found] ` <87tvbhra2v.fsf@roquette.mug.biscuolo.net>
[not found] ` <87imrvhhpy.fsf@cbaines.net>
[not found] ` <874l3crjqr.fsf@roquette.mug.biscuolo.net>
[not found] ` <87k1c6p914.fsf@roquette.mug.biscuolo.net>
[not found] ` <20190817152031.GA3191@jurong>
[not found] ` <87pnkuyac0.fsf_-_@gnu.org>
[not found] ` <20190828181141.GA27765@jurong>
2019-09-05 13:18 ` bug#37309: ‘ssh-daemon’ service fails to start at boot Giovanni Biscuolo
2019-09-08 4:19 ` 宋文武
2019-11-26 18:34 ` Jelle Licht
2019-11-29 8:40 ` Giovanni Biscuolo
2019-11-29 9:51 ` Jelle Licht [this message]
2019-12-03 20:12 ` bug#37309: [PATCH] services: openssh: Restrict to IPv4 Leo Famulari
2019-12-03 21:53 ` Julien Lepiller
2019-12-04 13:41 ` Leo Famulari
2019-12-10 16:47 ` Ludovic Courtès
2020-11-27 23:00 ` bug#37309: ‘ssh-daemon’ service fails to start at boot Christopher Lemmer Webber
2020-11-28 1:08 ` Marius Bakke
2020-12-03 20:38 ` Leo Famulari
2020-12-03 21:56 ` Christopher Lemmer Webber
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r21rui19.fsf@jlicht.xyz \
--to=jlicht@fsfe.org \
--cc=37309@debbugs.gnu.org \
--cc=g@xelera.eu \
--cc=iyzsong@member.fsf.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).