unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: "Brant Gardner" <mail@lnklnx.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 34580@debbugs.gnu.org
Subject: bug#34580: Service ssh-daemon could not be started
Date: Sat, 12 Oct 2019 07:09:51 -0500	[thread overview]
Message-ID: <b7fa80f0-02b9-4d7e-bfdc-9ecd289a9683@www.fastmail.com> (raw)
In-Reply-To: <87o8ynpp0r.fsf@gnu.org>

Well, now that I actually test it - yes.  But I said it had not because the 'herd status ssh-daemon' message indicated that it isn't running:

root@janus ~# herd status ssh-daemon
Status of ssh-daemon:
  It is stopped.
  It is enabled.
  Provides (ssh-daemon).
  Requires (syslogd loopback).
  Conflicts with ().
  Will be respawned.

Is this maybe a side effect of strace being involved?

--
Brant Gardner

On Fri, Oct 11, 2019, at 05:14, Ludovic Courtès wrote:
> Hi Brant,
> 
> Thanks for sending the log!
> 
> "Brant Gardner" <mail@lnklnx.com> skribis:
> 
> > 284   09:31:59 socket(AF_UNIX, SOCK_DGRAM|SOCK_CLOEXEC, 0) = 4 <0.000013>
> > 284   09:31:59 connect(4, {sa_family=AF_UNIX, sun_path="/dev/log"}, 110) = 0 <0.000014>
> > 284   09:31:59 sendto(4, "<38>Oct  9 09:31:59 sshd[284]: Server listening on 0.0.0.0 port 22.", 67, MSG_NOSIGNAL, NULL, 0) = 67 <3.103979>
> > 284   09:32:02 close(4)                 = 0 <0.000016>
> > 284   09:32:02 socket(AF_INET6, SOCK_STREAM, IPPROTO_TCP) = 4 <0.000024>
> > 284   09:32:02 fcntl(4, F_GETFL)        = 0x2 (flags O_RDWR) <0.000011>
> > 284   09:32:02 fcntl(4, F_SETFL, O_RDWR|O_NONBLOCK) = 0 <0.000011>
> > 284   09:32:02 fcntl(4, F_SETFD, FD_CLOEXEC) = 0 <0.000011>
> > 284   09:32:02 setsockopt(4, SOL_SOCKET, SO_REUSEADDR, [1], 4) = 0 <0.000011>
> > 284   09:32:02 setsockopt(4, SOL_IPV6, IPV6_V6ONLY, [1], 4) = 0 <0.000011>
> > 284   09:32:02 bind(4, {sa_family=AF_INET6, sin6_port=htons(22), sin6_flowinfo=htonl(0), inet_pton(AF_INET6, "::", &sin6_addr), sin6_scope_id=0}, 28) = 0 <0.000014>
> > 284   09:32:02 listen(4, 128)           = 0 <0.000012>
> > 284   09:32:02 getpid()                 = 284 <0.000011>
> > 284   09:32:02 socket(AF_UNIX, SOCK_DGRAM|SOCK_CLOEXEC, 0) = 5 <0.000013>
> > 284   09:32:02 connect(5, {sa_family=AF_UNIX, sun_path="/dev/log"}, 110) = 0 <0.000014>
> > 284   09:32:02 sendto(5, "<38>Oct  9 09:32:02 sshd[284]: Server listening on :: port 22.", 62, MSG_NOSIGNAL, NULL, 0) = 62 <4.195488>
> > 284   09:32:07 close(5)                 = 0 <0.000019>
> 
> I’m under the impression that sshd successfully start this time, didn’t it?
> 
> Thanks,
> Ludo’.
>

      reply	other threads:[~2019-10-12 12:11 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
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 [this message]

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=b7fa80f0-02b9-4d7e-bfdc-9ecd289a9683@www.fastmail.com \
    --to=mail@lnklnx.com \
    --cc=34580@debbugs.gnu.org \
    --cc=ludo@gnu.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).