On Tue, 08.02.11 14:49, Vasiliy G Tolstov (v.tols...@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 -- Lennart Poettering - Red Hat, Inc. _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
