Am 17.03.2011 01:13, schrieb Lennart Poettering: > On Sat, 19.02.11 00:15, Vasiliy G Tolstov (v.tols...@selfip.ru) wrote: > >>>>> 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 >>>>> >> Ok. I'm add corresponding params to kernel cmdline. After sometime i >> get on screen messages like in attached image > Your sshd seems to return exit with a non-zero exit code just indicating > a failure of some kind. use "ExecStart=-/foo/bar" instead of > "ExecStart=/foo/bar" to spawn a process and ignore if it fails. > > Lennart > The most likely failure here is an authentication failure. sshd exits with exit code 254(afair) in that case if in inet mode. This caused the very same problem (sshd.socket shutting down) for me on a machine that was accessable from the internet where I get a few hundred failed login attempts per day.
Mirco
signature.asc
Description: OpenPGP digital signature
_______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
