Quoting Peter Steele ([email protected]): > I'm seeing these messages on some of my containers during their > initial start-up: > > systemd: Failed at step CGROUP spawning /usr/sbin/sshd-keygen: No > such file or directory > systemd: sshd-keygen.service: main process exited, code=exited, > status=219/CGROUP > systemd: Failed to start OpenSSH Server Key Generation. > systemd: Unit sshd-keygen.service entered failed state. > > The net effect of this of course is that I cannot ssh into the > containers that encounter this problem. The odd thing is that > /usr/sbin/sshd-keygen *does* exist, and restarting the containers > corrects the problem (the keygen works on the reboot). It's not > clear to me why the containers think this file is missing and why > some containers running pretty much the identical image do not hit > this problem. Has anyone seen this?
My guess is that the no such file or directory is talking about a cgroup dir. what does /proc/1/cgroup in the container show? Make sure to run the latest lxcfs on the host, as that's needed because systemd moves itself to name=systemd:/init.scope cgroup. When systemd is having trouble, you can usually find out more info by running lxc-start -n containername -F -o /dev/stdout -- /sbin/init log_target=console log_level=debug _______________________________________________ lxc-users mailing list [email protected] http://lists.linuxcontainers.org/listinfo/lxc-users
