@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
@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
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
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
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
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
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
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 |
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 | \_
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
(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
** 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:
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
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
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
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
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
** 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.
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
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 |
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 | \_
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
(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)
** 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
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
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
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.
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
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
** 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
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
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
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)
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
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
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
36 matches
Mail list logo
