[Bug 819621] Re: lucid container start failure after calling lxc-stop (fails across reboots)
@Aaz, I can't actually reproduce this on a fresh natty install. Can you file a new bug showing precise reproduction instructions? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/819621 Title: lucid container start failure after calling lxc-stop (fails across reboots) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/819621/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 819621] Re: lucid container start failure after calling lxc-stop (fails across reboots)
@Aaz, I can't actually reproduce this on a fresh natty install. Can you file a new bug showing precise reproduction instructions? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/819621 Title: lucid container start failure after calling lxc-stop (fails across reboots) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/819621/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 819621] Re: lucid container start failure after calling lxc-stop (fails across reboots)
The same recipe works for natty amd64 container running on natty amd64 host. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/819621 Title: lucid container start failure after calling lxc-stop (fails across reboots) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/819621/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 819621] Re: lucid container start failure after calling lxc-stop (fails across reboots)
The same recipe works for natty amd64 container running on natty amd64 host. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/819621 Title: lucid container start failure after calling lxc-stop (fails across reboots) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/819621/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 819621] Re: lucid container start failure after calling lxc-stop (fails across reboots)
This bug was fixed in the package lxc - 0.7.4.2-3ubuntu6 --- lxc (0.7.4.2-3ubuntu6) oneiric; urgency=low * Add lxc-start-ephemeral by Robert Collins (LP: #807351) * Add a --quit-on-stop arg to lxc-monitor for use by lxc-start-ephemeral. * Modify lxcguest.conf to clear out /var/run (LP: #819621) * Fix a bug in lxc-ps when cgroup-bin is not mounted. * Modify lxc-ps to accept '-n name' and support '--' to separate options for ps. (LP: #820720) -- Serge Hallyn serge.hal...@ubuntu.com Wed, 03 Aug 2011 19:48:11 -0500 ** Changed in: lxc (Ubuntu) Status: Confirmed = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/819621 Title: lucid container start failure after calling lxc-stop (fails across reboots) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/819621/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 819621] Re: lucid container start failure after calling lxc-stop (fails across reboots)
This bug was fixed in the package lxc - 0.7.4.2-3ubuntu6 --- lxc (0.7.4.2-3ubuntu6) oneiric; urgency=low * Add lxc-start-ephemeral by Robert Collins (LP: #807351) * Add a --quit-on-stop arg to lxc-monitor for use by lxc-start-ephemeral. * Modify lxcguest.conf to clear out /var/run (LP: #819621) * Fix a bug in lxc-ps when cgroup-bin is not mounted. * Modify lxc-ps to accept '-n name' and support '--' to separate options for ps. (LP: #820720) -- Serge Hallyn serge.hal...@ubuntu.com Wed, 03 Aug 2011 19:48:11 -0500 ** Changed in: lxc (Ubuntu) Status: Confirmed = Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/819621 Title: lucid container start failure after calling lxc-stop (fails across reboots) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/819621/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 819621] Re: lucid container start failure after calling lxc-stop (fails across reboots)
So now I made a clean container; copied it to (sudo cp -a ) to a temp dir, ran the original, and now have a diff of the changes. I've not yet tested to see if reverting them fixes it.?field.comment=So now I made a clean container; copied it to (sudo cp -a ) to a temp dir, ran the original, and now have a diff of the changes. I've not yet tested to see if reverting them fixes it. the mtab being nonempty in the nonrunning container is a little suspect as are the .udev files *on disk* (mainly symlinks it appears) ** Attachment added: diff of broken, working containers https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/819621/+attachment/2248777/+files/brokendiff -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/819621 Title: lucid container start failure after calling lxc-stop (fails across reboots) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/819621/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 819621] Re: lucid container start failure after calling lxc-stop (fails across reboots)
ps fax for the broken container starting up; 4134 pts/0S+ 0:00 | \_ sudo lxc-start -n lucid-test-lp 4135 pts/0S+ 0:00 | \_ lxc-start -n lucid-test-lp 4150 ?Ss 0:00 | \_ /sbin/init 4192 ?S 0:00 | \_ upstart-udev-bridge --daemon 4197 ?Ss0:00 | \_ udevd --daemon 4273 ?S 0:00 | | \_ udevd --daemon 4274 ?S 0:00 | | \_ udevd --daemon 4200 ?Ss 0:00 | \_ /usr/sbin/sshd -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/819621 Title: lucid container start failure after calling lxc-stop (fails across reboots) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/819621/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 819621] Re: lucid container start failure after calling lxc-stop (fails across reboots)
Pre breakage: 4534 pts/0S+ 0:00 | \_ sudo lxc-start -n lucid-test-lp 4535 pts/0S+ 0:00 | \_ lxc-start -n lucid-test-lp 4546 ?Ss 0:00 | \_ /sbin/init 4593 ?S 0:00 | \_ upstart-udev-bridge --daemon 4597 ?Ss0:00 | \_ udevd --daemon 4728 ?S 0:00 | | \_ udevd --daemon 4729 ?S 0:00 | | \_ udevd --daemon 4936 pts/4Ss+0:00 | \_ /sbin/getty -8 38400 tty4 4937 pts/2Ss+0:00 | \_ /sbin/getty -8 38400 tty2 4939 pts/3Ss+0:00 | \_ /sbin/getty -8 38400 tty3 4945 ?S 0:00 | \_ /bin/sh /etc/init.d/ondemand background 4957 ?S 0:00 | | \_ sleep 60 4952 pts/1Ss+0:00 | \_ /sbin/getty -8 38400 tty1 4953 pts/5Ss+0:00 | \_ /sbin/getty -8 38400 /dev/console 4982 ?Ss 0:00 | \_ dhclient3 -e IF_METRIC=100 -pf /var/run/dhclient.eth0.pid -lf /var/lib/dhcp3/dhclient.eth0.leases eth0 4997 ?Ss 0:00 | \_ /usr/sbin/sshd -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/819621 Title: lucid container start failure after calling lxc-stop (fails across reboots) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/819621/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 819621] Re: lucid container start failure after calling lxc-stop (fails across reboots)
4936 pts/4 Ss+ 0:00 | \_ /sbin/getty -8 38400 tty4 4937 pts/2 Ss+ 0:00 | \_ /sbin/getty -8 38400 tty2 4939 pts/3 Ss+ 0:00 | \_ /sbin/getty -8 38400 tty3 4945 ? S 0:00 | \_ /bin/sh /etc/init.d/ondemand background 4957 ? S 0:00 | | \_ sleep 60 4952 pts/1 Ss+ 0:00 | \_ /sbin/getty -8 38400 tty1 4953 pts/5 Ss+ 0:00 | \_ /sbin/getty -8 38400 /dev/console 4982 ? Ss 0:00 | \_ dhclient3 -e IF_METRIC=100 -pf /var/run/dhclient.eth0.pid -lf /var/lib/dhcp3/dhclient.eth0.leases eth0 look to be the unique processes -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/819621 Title: lucid container start failure after calling lxc-stop (fails across reboots) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/819621/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 819621] Re: lucid container start failure after calling lxc-stop (fails across reboots)
(Meta: does ondemand make any sense for containers anyhow?) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/819621 Title: lucid container start failure after calling lxc-stop (fails across reboots) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/819621/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 819621] Re: lucid container start failure after calling lxc-stop (fails across reboots)
** Changed in: lxc (Ubuntu) Status: New = Confirmed ** Changed in: lxc (Ubuntu) Importance: Undecided = High -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/819621 Title: lucid container start failure after calling lxc-stop (fails across reboots) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/819621/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 819621] Re: lucid container start failure after calling lxc-stop (fails across reboots)
Thanks, Robert. It looks like ssh is not being properly killed. When we force it to die with lxc-stop, it does not remove its /var/run/ files. Then it fails to start bc those already exist. Until this is fixed, you can work around this by doing rm -rf /var/lib/lxc/container-name/rootfs/var/run mkdir !!:2 After this I'm able to restart the lucid container. You can automate this by changing your container's /etc/init/lxcmount to the one I'm about to attach. With that, I still need to kill the container by hand, but then lxc-start works. I'm tempted to wait to see if we can implement proper container reboot/poweroff support at the lxc sprint next week, because the lxc- monitor watching /var/run/utmp is an ugly hack anyway, and continually finding ways to fix its breaks does not seem productive. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/819621 Title: lucid container start failure after calling lxc-stop (fails across reboots) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/819621/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 819621] Re: lucid container start failure after calling lxc-stop (fails across reboots)
Replacing a lucid container's /etc/init/lxcmount.conf with this attachment should allow the container to start after a forced stop. ** Attachment added: lxcmount.conf https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/819621/+attachment/2249500/+files/lxcmount.conf -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/819621 Title: lucid container start failure after calling lxc-stop (fails across reboots) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/819621/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 819621] Re: lucid container start failure after calling lxc-stop (fails across reboots)
Note also that when we get proper poweroff/reboot support, we can have /lib/init/fstab mount a tmpfs onto /var/run, which will prevent these issues with /var/run/* files persisting. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/819621 Title: lucid container start failure after calling lxc-stop (fails across reboots) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/819621/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 819621] Re: lucid container start failure after calling lxc-stop (fails across reboots)
indeed, brilliant - thanks. I guess this needs a new lxcguest package? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/819621 Title: lucid container start failure after calling lxc-stop (fails across reboots) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/819621/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 819621] Re: lucid container start failure after calling lxc-stop (fails across reboots)
This workaround is a little coarse - it breaks utmp depending things (like postgresql :P) so rm -rf /var/run touch /var/run/utmp chmod root:utmp /var/run/utmp That seems to be more robust. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/819621 Title: lucid container start failure after calling lxc-stop (fails across reboots) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/819621/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 819621] Re: lucid container start failure after calling lxc-stop (fails across reboots)
** Attachment added: utmp safe version https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/819621/+attachment/2250880/+files/lxcmount.conf -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/819621 Title: lucid container start failure after calling lxc-stop (fails across reboots) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/819621/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 819621] Re: lucid container start failure after calling lxc-stop (fails across reboots)
So now I made a clean container; copied it to (sudo cp -a ) to a temp dir, ran the original, and now have a diff of the changes. I've not yet tested to see if reverting them fixes it.?field.comment=So now I made a clean container; copied it to (sudo cp -a ) to a temp dir, ran the original, and now have a diff of the changes. I've not yet tested to see if reverting them fixes it. the mtab being nonempty in the nonrunning container is a little suspect as are the .udev files *on disk* (mainly symlinks it appears) ** Attachment added: diff of broken, working containers https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/819621/+attachment/2248777/+files/brokendiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/819621 Title: lucid container start failure after calling lxc-stop (fails across reboots) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/819621/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 819621] Re: lucid container start failure after calling lxc-stop (fails across reboots)
ps fax for the broken container starting up; 4134 pts/0S+ 0:00 | \_ sudo lxc-start -n lucid-test-lp 4135 pts/0S+ 0:00 | \_ lxc-start -n lucid-test-lp 4150 ?Ss 0:00 | \_ /sbin/init 4192 ?S 0:00 | \_ upstart-udev-bridge --daemon 4197 ?Ss0:00 | \_ udevd --daemon 4273 ?S 0:00 | | \_ udevd --daemon 4274 ?S 0:00 | | \_ udevd --daemon 4200 ?Ss 0:00 | \_ /usr/sbin/sshd -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/819621 Title: lucid container start failure after calling lxc-stop (fails across reboots) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/819621/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 819621] Re: lucid container start failure after calling lxc-stop (fails across reboots)
Pre breakage: 4534 pts/0S+ 0:00 | \_ sudo lxc-start -n lucid-test-lp 4535 pts/0S+ 0:00 | \_ lxc-start -n lucid-test-lp 4546 ?Ss 0:00 | \_ /sbin/init 4593 ?S 0:00 | \_ upstart-udev-bridge --daemon 4597 ?Ss0:00 | \_ udevd --daemon 4728 ?S 0:00 | | \_ udevd --daemon 4729 ?S 0:00 | | \_ udevd --daemon 4936 pts/4Ss+0:00 | \_ /sbin/getty -8 38400 tty4 4937 pts/2Ss+0:00 | \_ /sbin/getty -8 38400 tty2 4939 pts/3Ss+0:00 | \_ /sbin/getty -8 38400 tty3 4945 ?S 0:00 | \_ /bin/sh /etc/init.d/ondemand background 4957 ?S 0:00 | | \_ sleep 60 4952 pts/1Ss+0:00 | \_ /sbin/getty -8 38400 tty1 4953 pts/5Ss+0:00 | \_ /sbin/getty -8 38400 /dev/console 4982 ?Ss 0:00 | \_ dhclient3 -e IF_METRIC=100 -pf /var/run/dhclient.eth0.pid -lf /var/lib/dhcp3/dhclient.eth0.leases eth0 4997 ?Ss 0:00 | \_ /usr/sbin/sshd -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/819621 Title: lucid container start failure after calling lxc-stop (fails across reboots) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/819621/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 819621] Re: lucid container start failure after calling lxc-stop (fails across reboots)
4936 pts/4 Ss+ 0:00 | \_ /sbin/getty -8 38400 tty4 4937 pts/2 Ss+ 0:00 | \_ /sbin/getty -8 38400 tty2 4939 pts/3 Ss+ 0:00 | \_ /sbin/getty -8 38400 tty3 4945 ? S 0:00 | \_ /bin/sh /etc/init.d/ondemand background 4957 ? S 0:00 | | \_ sleep 60 4952 pts/1 Ss+ 0:00 | \_ /sbin/getty -8 38400 tty1 4953 pts/5 Ss+ 0:00 | \_ /sbin/getty -8 38400 /dev/console 4982 ? Ss 0:00 | \_ dhclient3 -e IF_METRIC=100 -pf /var/run/dhclient.eth0.pid -lf /var/lib/dhcp3/dhclient.eth0.leases eth0 look to be the unique processes -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/819621 Title: lucid container start failure after calling lxc-stop (fails across reboots) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/819621/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 819621] Re: lucid container start failure after calling lxc-stop (fails across reboots)
(Meta: does ondemand make any sense for containers anyhow?) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/819621 Title: lucid container start failure after calling lxc-stop (fails across reboots) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/819621/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 819621] Re: lucid container start failure after calling lxc-stop (fails across reboots)
** Changed in: lxc (Ubuntu) Status: New = Confirmed ** Changed in: lxc (Ubuntu) Importance: Undecided = High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/819621 Title: lucid container start failure after calling lxc-stop (fails across reboots) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/819621/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 819621] Re: lucid container start failure after calling lxc-stop (fails across reboots)
Thanks, Robert. It looks like ssh is not being properly killed. When we force it to die with lxc-stop, it does not remove its /var/run/ files. Then it fails to start bc those already exist. Until this is fixed, you can work around this by doing rm -rf /var/lib/lxc/container-name/rootfs/var/run mkdir !!:2 After this I'm able to restart the lucid container. You can automate this by changing your container's /etc/init/lxcmount to the one I'm about to attach. With that, I still need to kill the container by hand, but then lxc-start works. I'm tempted to wait to see if we can implement proper container reboot/poweroff support at the lxc sprint next week, because the lxc- monitor watching /var/run/utmp is an ugly hack anyway, and continually finding ways to fix its breaks does not seem productive. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/819621 Title: lucid container start failure after calling lxc-stop (fails across reboots) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/819621/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 819621] Re: lucid container start failure after calling lxc-stop (fails across reboots)
Replacing a lucid container's /etc/init/lxcmount.conf with this attachment should allow the container to start after a forced stop. ** Attachment added: lxcmount.conf https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/819621/+attachment/2249500/+files/lxcmount.conf -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/819621 Title: lucid container start failure after calling lxc-stop (fails across reboots) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/819621/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 819621] Re: lucid container start failure after calling lxc-stop (fails across reboots)
Note also that when we get proper poweroff/reboot support, we can have /lib/init/fstab mount a tmpfs onto /var/run, which will prevent these issues with /var/run/* files persisting. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/819621 Title: lucid container start failure after calling lxc-stop (fails across reboots) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/819621/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 819621] Re: lucid container start failure after calling lxc-stop (fails across reboots)
indeed, brilliant - thanks. I guess this needs a new lxcguest package? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/819621 Title: lucid container start failure after calling lxc-stop (fails across reboots) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/819621/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 819621] Re: lucid container start failure after calling lxc-stop (fails across reboots)
This workaround is a little coarse - it breaks utmp depending things (like postgresql :P) so rm -rf /var/run touch /var/run/utmp chmod root:utmp /var/run/utmp That seems to be more robust. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/819621 Title: lucid container start failure after calling lxc-stop (fails across reboots) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/819621/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 819621] Re: lucid container start failure after calling lxc-stop (fails across reboots)
** Attachment added: utmp safe version https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/819621/+attachment/2250880/+files/lxcmount.conf -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/819621 Title: lucid container start failure after calling lxc-stop (fails across reboots) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/819621/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 819621] Re: lucid container start failure after calling lxc-stop (fails across reboots)
Further investigation shows that just: logging into the new container installing some packages (see https://dev.launchpad.net/Running/LXC) and calling lxc-stop from another terminal will cause this. Am progressing with shorter and shorter tests ** Summary changed: - container start failure after calling poweroff -n + lucid container start failure after calling lxc-stop (fails across reboots) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/819621 Title: lucid container start failure after calling lxc-stop (fails across reboots) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/819621/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 819621] Re: lucid container start failure after calling lxc-stop (fails across reboots)
start, login, log out, lxc-stop from another terminal - the broken situation. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/819621 Title: lucid container start failure after calling lxc-stop (fails across reboots) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/819621/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 819621] Re: lucid container start failure after calling lxc-stop (fails across reboots)
And confirmed its still nuked after a reboot. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/819621 Title: lucid container start failure after calling lxc-stop (fails across reboots) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/819621/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 819621] Re: lucid container start failure after calling lxc-stop (fails across reboots)
Further investigation shows that just: logging into the new container installing some packages (see https://dev.launchpad.net/Running/LXC) and calling lxc-stop from another terminal will cause this. Am progressing with shorter and shorter tests ** Summary changed: - container start failure after calling poweroff -n + lucid container start failure after calling lxc-stop (fails across reboots) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/819621 Title: lucid container start failure after calling lxc-stop (fails across reboots) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/819621/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 819621] Re: lucid container start failure after calling lxc-stop (fails across reboots)
start, login, log out, lxc-stop from another terminal - the broken situation. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/819621 Title: lucid container start failure after calling lxc-stop (fails across reboots) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/819621/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 819621] Re: lucid container start failure after calling lxc-stop (fails across reboots)
And confirmed its still nuked after a reboot. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/819621 Title: lucid container start failure after calling lxc-stop (fails across reboots) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/819621/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
