[systemd-devel] systemd and sshd.socket/sshd at .service
Vasiliy G Tolstov
v.tolstov at selfip.ru
Fri Feb 18 03:27:55 PST 2011
On Tue, 2011-02-08 at 13:08 +0100, Lennart Poettering wrote:
> On Tue, 08.02.11 14:49, Vasiliy G Tolstov (v.tolstov at selfip.ru) wrote:
>
> > > Oh, intreresting. It's in "failed" state. Can you check syslog/kmsg if
> > > systemd generated any kind of log output when this happened? i.e. around
> > > Mon, 07 Feb 2011 22:36:51 +0300. This should give us a hint on what
> > > might be wrong.
> > >
> > > Lennart
> > >
> >
> > /var/log/messages does not contain any info
> > sshd log says: error: Could not load host
> > key: /etc/ssh/ssh_host_ecdsa_key , but this not critical (sshd runs
> > after systemctl stat sshd.socket)
>
> Hmm, can you try to reproduce this when booting with
> systemd.log_level=debug and systemd.log_target=kmsg on the kernel
> cmdline? Then, kmsg should definitely include a message on what is going
> on. (and when we found it we probably should bump up the error level of
> that msg)
>
> Lennart
>
Hm.. I'm upgrade systemd to current (18) and reboot. After that systemct
start sshd at .service says that unit name not valid. Is this correct
behaviour?
--
Vasiliy G Tolstov <v.tolstov at selfip.ru>
Selfip.Ru
More information about the systemd-devel
mailing list