all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Martin Castillo <castilma@uni-bremen.de>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: help-guix@gnu.org
Subject: Re: ssh-daemon service fails to auto start
Date: Tue, 6 Feb 2018 19:49:16 +0100	[thread overview]
Message-ID: <70093a20-9a2c-12d3-c59d-53796328fb9f@uni-bremen.de> (raw)
In-Reply-To: <87wp00k3ce.fsf@gnu.org>



On 29.01.2018 18:00, Ludovic Courtès wrote:
> Hi Martin,
> 
> Martin Castillo <castilma@uni-bremen.de> skribis:
> 
>> i have a problem with the ssh-service. I want it to autostart on system
>> boot.
>>
>> my configuration is (similar to) desk,nossh.scm.
> 
> I tried this config in ‘guix system vm’ and sshd is automatically
> started on boot, as can be seen with ‘herd status ssh-daemon’ etc.
> 
> Does this config work for you in ‘guix system vm’?

No.


> Could you check /var/log/shepherd.log?  It will tell you which services,
> besides sshd, failed to start.
> 
> ‘ssh-daemon’ depends only on ‘syslogd’, so as long as ‘syslogd’ is
> started, ‘ssh-daemon’ should start.
> 

I checked /var/log/shepherd.log. Only user-homes and ssh-daemon could
not be started.

Has this maybe to do with missing randomness to create keys? (Even
though there are already server keys.)

Maybe shepherd should store the output of launched programs? Is that
really not possible? I can't be the first one to need that.

Martin

-- 
GPG: 7FDE 7190 2F73 2C50 236E  403D CC13 48F1 E644 08EC

  reply	other threads:[~2018-02-06 18:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-27 22:08 ssh-daemon service fails to auto start Martin Castillo
2018-01-29 17:00 ` Ludovic Courtès
2018-02-06 18:49   ` Martin Castillo [this message]
2018-02-11  9:31     ` Chris Marusich
2018-02-06 20:01 ` Leo Famulari
2018-02-12 20:02   ` Martin Castillo
2018-02-15  0:08     ` Leo Famulari

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=70093a20-9a2c-12d3-c59d-53796328fb9f@uni-bremen.de \
    --to=castilma@uni-bremen.de \
    --cc=help-guix@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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.