This bug was fixed in the package lxc - 0.9.0~alpha3-0ubuntu3
---
lxc (0.9.0~alpha3-0ubuntu3) raring; urgency=low
* 0001-fix-race-with-fast-init: Before starting lxc_mainloop, check whether
lxc-init has already exited. If it has, return immediately to reap it.
(LP: #1134923
The problem is that src/lxc/start.c:lxc_poll, which checks signalfd for
sigchld from container init, can start after the container init has
exited. It then hangs trying to talk over the monitor. The container
init mainwhile waits to be reaped (by the fn which called lxc_poll,
which does waitpid a
While I have identified a possible problem in the lxc start code (still
to test), I note that there are several other unrelated defunct
processes in some those VMs. For instance
lp 19479 19478 1 17:41 ?00:00:00 [python3]
lp 19496 19478 6 17:41 ?00:00:00 [python3]
Oh but I'm being silly - lxc-init is defunct, that is where the bug is
:)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1144873
Title:
"lxc-execute: Failed to find an lxc-init" Error during lxc smo
Indeed the hang is at the end of lxc-execute. It seems to be
accompannied with
run 26
PID TTY TIME CMD
1 ?00:00:00 lxc-init
2 ?00:00:00 ps
lxc-execute: No such file or directory - stat(/proc/25055/root/dev/lxc/console)
that error message, however on bare metal
On your host (which is a raring qemu VM, bridged to hardware nic, on a
precise host) if I do
while [ 1 ]; do
mv -f outout outout2
lxc-execute -n r1 -l info -o outout -- ps
done
after some time, lxc-execute hangs. But the debug output file shows
both the good and bad runs made it to at leas
The host is an amd64 installation of 12.04.1. Ill give the information
about accessing it separately. Thanks
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1144873
Title:
"lxc-execute: Failed to fi
Is it possible for me to get access to a machine where it is failing?
Are these on raring hosts?
status incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1144873
Title:
"lxc-execute: Failed
@hallyn,
This has happened in i386 test as well; a test is running for more than 2 hours
where 30 mins was the time it took when it passed in the previous runs. All the
outputs for the above commands are similar.
--
You received this bug notification because you are a member of Ubuntu
Bugs, whi
The following are the results of from a an amd64 vm from a test which was
running for more than 12 hours and still running
1) utah@utah-5695-raring-server-amd64:~$ ps -ef
(attached as a text file)
2) utah@utah-5695-raring-server-amd64:~$ sudo lxc-ls --fancy
Cannot open network namespace: No
Quoting Parameswaran Sivatharman (para.s...@canonical.com):
> Yes at present the tests in amd64 are hanging. I ran it a couple of
> times and every time the tests with amd64 installations hang
Ok I really can't reproduce this now. Can you leave it running for, say
twice as long as it takes to com
Yes at present the tests in amd64 are hanging. I ran it a couple of
times and every time the tests with amd64 installations hang
indefinitely (until I forcefully abort the tests). The test-lucid was
still running after more than 3 hours.
The tests in with i386 installations seem to pass after the
@psivaa,
I can't reproduce this any more. Are you saying that happened to you in
the last 15 hours (since my last commit to the utah server testsuite),
or that that is what happened to you at comment #8?
If you havent re-run since comment #8, can you please do so? The tests
all pass for me here
Yes, it never shuts down.
and /var/log/lxc/test-lucid.log in the host contains only the following,
lxc-execute 1362505584.513 ERRORlxc_conf - No such file or directory -
stat(/proc/2296/root/dev//console)
utah@utah-5629-raring-server-amd64:~$ sudo lxc-info --name test-lucid
[sudo] password f
Quoting Parameswaran Sivatharman (para.s...@canonical.com):
> The tests have still been running for more than 3 hours with the revno of 87.
> I am able to ssh to the host and I get 'test-lucid' returned when I run both
> these commands,
> sudo lxc-ls --active
> sudo lx
The tests have still been running for more than 3 hours with the revno of 87. I
am able to ssh to the host and I get 'test-lucid' returned when I run both
these commands,
sudo lxc-ls --active
sudo lxc-ls --running
--
You received this bug notification because you are
Yes, thanks. That happened to me last night too, but the way it hung
made me wonder if utah or kvm was crashing.
But I see what is happening - I think the lxc.postinst which sets up
dnsmasq may be messing up the host's networking. I think I do still
need to set /usr/sbin/policy-rc.d.
I've just
The tests appear to hang with the revno of 86. Unable to extract any
logs since the logs wont be written to any files until the tests finish
executing.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/114
Oops - the command to actually install lxc-init got dropped (purely my
fault). I believe it's now fixed, but test is still running.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1144873
Title:
"lxc
** Changed in: lxc (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1144873
Title:
"lxc-execute: Failed to find an lxc-init" Error during lxc smoke
t
Thanks for reporting this bug.
assignee serge-hallyn
importance high
status confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1144873
Title:
"lxc-execute: Failed to find an lxc-init" Error
** Changed in: lxc (Ubuntu)
Importance: Undecided => High
** Changed in: lxc (Ubuntu)
Status: New => Confirmed
** Changed in: lxc (Ubuntu)
Assignee: (unassigned) => Serge Hallyn (serge-hallyn)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
One of the impacted jobs is
https://jenkins.qa.ubuntu.com/view/Raring/view/Smoke%20Testing/job/raring-server-amd64-smoke-lxc/110/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1144873
Title:
"lxc-
** Attachment added: "utah-5580-raring-server-amd64.syslog.log"
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1144873/+attachment/3556864/+files/utah-5580-raring-server-amd64.syslog.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
24 matches
Mail list logo
