From: "Ludovic Courtès" <ludo@gnu.org>
To: Brant Gardner <mail@lnklnx.com>
Cc: 34580@debbugs.gnu.org
Subject: bug#34580: Service ssh-daemon could not be started
Date: Thu, 26 Sep 2019 22:48:58 +0200 [thread overview]
Message-ID: <87o8z6kclh.fsf@gnu.org> (raw)
In-Reply-To: <6d672221-0e2f-40cd-b129-1f893fe13472@www.fastmail.com> (Brant Gardner's message of "Tue, 24 Sep 2019 07:20:10 -0500")
[-- Attachment #1: Type: text/plain, Size: 448 bytes --]
Hi Brand,
"Brant Gardner" <mail@lnklnx.com> skribis:
> I'll cheerfully do the experiment, but I don't know how - can you direct me for how to add strace where you need it to a booting system?
You could try something like the patch below. When ‘ssh-daemon’ fails
to start, you’ll have to make sure to grab /tmp/ssh.log.
I’ve just experienced it on a headless machine so I sympathize all the
more now…
HTH!
Ludo’.
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: Type: text/x-patch, Size: 790 bytes --]
--- a/gnu/services/ssh.scm
+++ b/gnu/services/ssh.scm
@@ -23,6 +23,7 @@
(define-module (gnu services ssh)
#:use-module (gnu packages ssh)
#:use-module (gnu packages admin)
+ #:use-module (gnu packages linux)
#:use-module (gnu services)
#:use-module (gnu services shepherd)
#:use-module (gnu system pam)
@@ -491,7 +492,8 @@ of user-name/file-like tuples."
(openssh-configuration-pid-file config))
(define openssh-command
- #~(list (string-append #$(openssh-configuration-openssh config) "/sbin/sshd")
+ #~(list #$(file-append strace "/bin/strace") "-f" "-s" "300" "-Tt" "-o" "/tmp/ssh.log"
+ (string-append #$(openssh-configuration-openssh config) "/sbin/sshd")
"-D" "-f" #$(openssh-config-file config)))
(list (shepherd-service
next prev parent reply other threads:[~2019-09-26 20:50 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-19 21:21 bug#34580: Service ssh-daemon could not be started Andreas Enge
2019-02-20 22:21 ` Leo Famulari
2019-02-20 22:48 ` Andreas Enge
2019-02-20 22:51 ` Leo Famulari
2019-02-20 23:08 ` Andreas Enge
2019-02-20 23:56 ` Leo Famulari
2019-03-14 22:11 ` Leo Famulari
2019-03-15 16:35 ` Leo Famulari
2019-02-22 6:52 ` Chris Marusich
2019-09-20 20:00 ` Brant Gardner
2019-09-24 8:08 ` Ludovic Courtès
2019-09-24 12:20 ` Brant Gardner
2019-09-26 20:48 ` Ludovic Courtès [this message]
2019-09-27 14:57 ` Brant Gardner
2019-09-28 9:45 ` Ludovic Courtès
2019-09-28 12:38 ` Brant Gardner
2019-09-28 13:54 ` pelzflorian (Florian Pelz)
2019-09-28 17:44 ` Ludovic Courtès
2019-09-28 18:23 ` Danny Milosavljevic
2019-09-28 18:31 ` Danny Milosavljevic
2019-09-28 19:47 ` Ludovic Courtès
2019-09-28 19:47 ` Ludovic Courtès
2019-09-29 13:02 ` Brant Gardner
2019-09-28 14:11 ` Ludovic Courtès
2019-10-09 14:49 ` Brant Gardner
2019-10-11 10:14 ` Ludovic Courtès
2019-10-12 12:09 ` Brant Gardner
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=87o8z6kclh.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=34580@debbugs.gnu.org \
--cc=mail@lnklnx.com \
/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).