On 10/19/2011 07:24 PM, Ulli Horlacher wrote: > Besides my problem with "cannot stop/kill lxc-start" (see other mail), I > have now an even more severe problem: I cannot start ANY container anymore! > > I am sure I have overlooked something, but I cannot see what. I am really > desperate now, because this happens to my production environment! > > Server host is: > > root@vms1:/lxc# lsb_release -a; uname -a; lxc-version > No LSB modules are available. > Distributor ID: Ubuntu > Description: Ubuntu 10.04.3 LTS > Release: 10.04 > Codename: lucid > Linux vms1 2.6.35-30-server #60~lucid1-Ubuntu SMP Tue Sep 20 22:28:40 UTC > 2011 x86_64 GNU/Linux > lxc version: 0.7.4.1 > > (linux-image-server-lts-backport-maverick) > > All my lxc files reside in /lxc : > > root@vms1:/lxc# l vmtest1* > dRWX - 2011-05-17 19:47 vmtest1 > -RWT 1,127 2011-10-19 18:54 vmtest1.cfg > -RW- 476 2011-10-19 18:54 vmtest1.fstab > > I boot the container with: > > root@vms1:/lxc# lxc-start -f /data/lxc/vmtest1.cfg -n vmtest1 -d -o > /data/lxc/vmtest1.log
What is in log if you don't use -d but -l DEBUG? > But nothing happens, there is only a lxc-start process dangling around: > > root@vms1:/lxc# psg vmtest1 > USER PID PPID %CPU VSZ COMMAND > root 31571 1 0.0 20872 lxc-start -f /data/lxc/vmtest1.cfg -n > vmtest1 -d -o /data/lxc/vmtest1.log ps axf ? > The logfile is empty: > > root@vms1:/lxc# l vmtest1.log > -RW- 0 2011-10-19 19:09 vmtest1.log What about strace -ff -s 10000 ? tamas ------------------------------------------------------------------------------ The demand for IT networking professionals continues to grow, and the demand for specialized networking skills is growing even more rapidly. Take a complimentary Learning@Ciosco Self-Assessment and learn about Cisco certifications, training, and career opportunities. http://p.sf.net/sfu/cisco-dev2dev _______________________________________________ Lxc-users mailing list Lxc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxc-users
