On 04/19/2011 08:25 AM, Ulli Horlacher wrote:
> I have a new container which I cannot attach to (lxc-console):
>
>
> root@zoo:/lxc# /usr/bin/lxc-start -f egal.cfg -n egal&
> [1] 3800
>
> root@zoo:/lxc# pstree -p 3800
> lxc-start(3800)---init(3801)-+-cron(3857)
> |-rsyslogd(3827)-+-{rsyslogd}(3839)
> | `-{rsyslogd}(3840)
> |-su(3849)---bash(3854)
> |-su(3851)---bash(3860)
> `-su(3899)---bash(3903)
>
> root@zoo:/lxc# lxc-console -n egal
> lxc-console: 'egal' is stopped
>
>
> Why is it in mode 'stopped'?
That means lxc-console was not able to find the unix socket and failed
with an ECONNREFUSED.
It is interpreted the lxc-start supervisor (the container's init parent)
is not there, so no such container is running.
> How can I debug this?
Yes, let's understand why we can't connect.
(1) strace lxc-console
(2) netstat -lx | grep lxc
For the latter you should see @/var/lib/lxc/egal/command
If I refer to the process tree you gave, I don't see any getty, so I
suppose you didn't set the tty option in the configuration file, right ?
------------------------------------------------------------------------------
Benefiting from Server Virtualization: Beyond Initial Workload
Consolidation -- Increasing the use of server virtualization is a top
priority.Virtualization can reduce costs, simplify management, and improve
application availability and disaster protection. Learn more about boosting
the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev
_______________________________________________
Lxc-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/lxc-users
