unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: ng0 <contact.ng0@cryptolab.net>
Cc: 25688@debbugs.gnu.org
Subject: bug#25688: services: ssh-daemon quits too early
Date: Sat, 11 Feb 2017 15:40:38 +0100	[thread overview]
Message-ID: <878tpc3i55.fsf@gnu.org> (raw)
In-Reply-To: <20170211141740.thdgjg5wmyok77kw@wasp> (ng0's message of "Sat, 11 Feb 2017 14:17:40 +0000")

ng0 <contact.ng0@cryptolab.net> skribis:

> I have my openssh-service configured like this (not exactly, but it
> serves an example well enough to not expose too much):
>
> (service openssh-service-type
>  (openssh-configuration
>   (port-number 2200)
>   (password-authentication? #t)
>   (permit-root-login 'without-password)))
>
> Now, when I reconfigure the system, ssh-daemon is started and I can ssh in.
> When I reboot and try to ssh into the machine again, I see ssh-daemon is
> stopped and I can't log in from a remote machine.
>
> The issue seems to be that network-service is taking too long to come up
> and therefore ssh-service is stopped at system boot similar to something
> like this:
>
> * starting ssh-daemon-service
> * ssh-daemon depends on networking-service
> * stopping ssh-daemon-service

Could you send the relevant part of /var/log/shepherd.log, which shows
messages corresponding to the startup of the ‘networking’ and
‘ssh-daemon’ services?

TIA,
Ludo’.

  reply	other threads:[~2017-02-11 14:41 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-11 14:17 bug#25688: services: ssh-daemon quits too early ng0
2017-02-11 14:40 ` Ludovic Courtès [this message]
2017-02-11 15:00   ` ng0
2017-02-11 21:18     ` Ludovic Courtès
2017-02-12 14:14       ` ng0
2017-02-12 16:17         ` Ludovic Courtès
2017-02-12 16:23           ` ng0
2017-03-02 21:58     ` Leo Famulari
2017-03-02 22:20       ` ng0
2017-03-03 11:36         ` ng0
2017-03-04 16:47           ` ng0

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=878tpc3i55.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=25688@debbugs.gnu.org \
    --cc=contact.ng0@cryptolab.net \
    /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).