[Bug 1294284] Re: LXC Ubuntu containers do not start in Ubuntu 14.04
I may have solved the problem after re-installing the server. Before upgrading to 14.04 I made sure to check if Ubuntu Saucy container starts and it did. Then I upgraded to 14.04 and created new Ubuntu Trusty container. Both Saucy and Trusty containers started properly, although both output some errors which I believe is normal. Then I started re-applying all the changes I had made previously before re-install. A problem appeared after I edited fstab to add nodev/noexec/nosuid mount options. I already knew that I couldn't use noexec for /var, but now both Ubuntu containers refused to even try to start if I had nodev and nosuid mount options for /var. Debian Wheezy container does start even with nodev and nosuid mount options. Before re-install I had created symlinks to point from /var/lib/lxc to /srv/lxc and /srv did not have these mount options. This might explain the difference in what happened when I started the containers before and after re-install. So apparently I can't use nodev and nosuid mount options for /var even if I use another partition without these mount options by using symlinks. Meanwhile, Debian containers worked all this time. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1294284 Title: LXC Ubuntu containers do not start in Ubuntu 14.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1294284/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1294284] Re: LXC Ubuntu containers do not start in Ubuntu 14.04
Output you requested attached. ** Attachment added: "output.txt" https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1294284/+attachment/4032814/+files/output.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1294284 Title: LXC Ubuntu containers do not start in Ubuntu 14.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1294284/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1294284] Re: LXC Ubuntu containers do not start in Ubuntu 14.04
I never showed the results for the "u1" container as they were identical to "ubuntu". -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1294284 Title: LXC Ubuntu containers do not start in Ubuntu 14.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1294284/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1294284] Re: LXC Ubuntu containers do not start in Ubuntu 14.04
As a matter of fact, even if I stop the apparmor service it doesn't change the problem with Ubuntu containers. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1294284 Title: LXC Ubuntu containers do not start in Ubuntu 14.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1294284/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1294284] lxc.default.txt
apport information ** Attachment added: "lxc.default.txt" https://bugs.launchpad.net/bugs/1294284/+attachment/4032648/+files/lxc.default.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1294284 Title: LXC Ubuntu containers do not start in Ubuntu 14.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1294284/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1294284] KernLog.txt
apport information ** Attachment added: "KernLog.txt" https://bugs.launchpad.net/bugs/1294284/+attachment/4032645/+files/KernLog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1294284 Title: LXC Ubuntu containers do not start in Ubuntu 14.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1294284/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1294284] Re: LXC Ubuntu containers do not start in Ubuntu 14.04
Added the line but no change. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1294284 Title: LXC Ubuntu containers do not start in Ubuntu 14.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1294284/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1294284] lxcsyslog.txt
apport information ** Attachment added: "lxcsyslog.txt" https://bugs.launchpad.net/bugs/1294284/+attachment/4032649/+files/lxcsyslog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1294284 Title: LXC Ubuntu containers do not start in Ubuntu 14.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1294284/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1294284] Re: LXC Ubuntu containers do not start in Ubuntu 14.04
Meminfo attached. ** Attachment added: "meminfo" https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1294284/+attachment/4032652/+files/meminfo -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1294284 Title: LXC Ubuntu containers do not start in Ubuntu 14.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1294284/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1294284] Re: LXC Ubuntu containers do not start in Ubuntu 14.04
Syslog attached. ** Attachment added: "syslog" https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1294284/+attachment/4032651/+files/syslog -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1294284 Title: LXC Ubuntu containers do not start in Ubuntu 14.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1294284/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1294284] lxc-net.default.txt
apport information ** Attachment added: "lxc-net.default.txt" https://bugs.launchpad.net/bugs/1294284/+attachment/4032647/+files/lxc-net.default.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1294284 Title: LXC Ubuntu containers do not start in Ubuntu 14.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1294284/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1294284] Re: LXC Ubuntu containers do not start in Ubuntu 14.04
lxc-start: Device or resource busy - failed to set memory.use_hierarchy to 1; continuing lxc-start: Device or resource busy - failed to set memory.use_hierarchy to 1; continuing <6>init: Handling startup event <6>init: mountall goal changed from stop to start <6>init: mountall state changed from waiting to starting <6>init: hostname goal changed from stop to start <6>init: hostname state changed from waiting to starting <6>init: plymouth-ready (startup) goal changed from stop to start <6>init: plymouth-ready (startup) state changed from waiting to starting <6>init: Handling starting event <6>init: plymouth goal changed from stop to start <6>init: plymouth state changed from waiting to starting <6>init: hwclock goal changed from stop to start <6>init: hwclock state changed from waiting to starting <6>init: ureadahead goal changed from stop to start <6>init: ureadahead state changed from waiting to starting <6>init: Handling starting event <6>init: hostname state changed from starting to security <6>init: hostname state changed from security to pre-start <6>init: hostname state changed from pre-start to spawned <2>init: error.c:219: Assertion failed in _nih_error_raise_system: errno > 0 <2>init: Caught abort, core dumped <6>init: hostname main process (4) <6>init: hostname state changed from spawned to post-start <6>init: hostname state changed from post-start to running <6>init: Handling starting event <6>init: plymouth-ready (startup) state changed from starting to security <6>init: plymouth-ready (startup) state changed from security to pre-start <6>init: plymouth-ready (startup) state changed from pre-start to spawned <2>init: error.c:219: Assertion failed in _nih_error_raise_system: errno > 0 <2>init: Caught abort, core dumped <6>init: plymouth-ready (startup) main process (6) <6>init: plymouth-ready (startup) state changed from spawned to post-start <6>init: plymouth-ready (startup) state changed from post-start to running <6>init: Handling starting event <6>init: plymouth state changed from starting to security <6>init: plymouth state changed from security to pre-start <6>init: plymouth state changed from pre-start to spawned <2>init: error.c:219: Assertion failed in _nih_error_raise_system: errno > 0 <2>init: Caught abort, core dumped <6>init: plymouth main process (8) <6>init: Handling starting event <6>init: hwclock state changed from starting to security <6>init: hwclock state changed from security to pre-start <6>init: hwclock state changed from pre-start to spawned <2>init: error.c:219: Assertion failed in _nih_error_raise_system: errno > 0 <2>init: Caught abort, core dumped <6>init: hwclock main process (10) <6>init: hwclock state changed from spawned to post-start <6>init: hwclock state changed from post-start to running <6>init: Handling starting event <6>init: ureadahead state changed from starting to security <6>init: ureadahead state changed from security to pre-start <6>init: ureadahead state changed from pre-start to spawned <2>init: error.c:219: Assertion failed in _nih_error_raise_system: errno > 0 <2>init: Caught abort, core dumped <6>init: ureadahead main process (12) <6>init: Handling started event <6>init: startpar-bridge (hostname--started) goal changed from stop to start <6>init: startpar-bridge (hostname--started) state changed from waiting to starting <6>init: Handling started event <6>init: startpar-bridge (plymouth-ready-startup-started) goal changed from stop to start <6>init: startpar-bridge (plymouth-ready-startup-started) state changed from waiting to starting <6>init: Handling started event <6>init: startpar-bridge (hwclock--started) goal changed from stop to start <6>init: startpar-bridge (hwclock--started) state changed from waiting to starting <6>init: Handling starting event <6>init: startpar-bridge (hostname--started) state changed from starting to security <6>init: startpar-bridge (hostname--started) state changed from security to pre-start <6>init: startpar-bridge (hostname--started) state changed from pre-start to spawned <2>init: error.c:219: Assertion failed in _nih_error_raise_system: errno > 0 <2>init: Caught abort, core dumped <6>init: startpar-bridge (hostname--started) main process (14) <6>init: startpar-bridge (hostname--started) state changed from spawned to post-start <6>init: startpar-bridge (hostname--started) state changed from post-start to running <6>init: Handling starting event <6>init: startpar-bridge (plymouth-ready-startup-started) state changed from starting to security <6>init: startpar-bridge (plymouth-ready-startup-started) state changed from security to pre-start <6>init: startpar-bridge (plymouth-ready-startup-started) state changed from pre-start to spawned <2>init: error.c:219: Assertion failed in _nih_error_raise_system: errno > 0 <2>init: Caught abort, core dumped <6>init: startpar-bridge (plymouth-ready-startup-started) main process (16) <6>init: startpar-bridge (plymouth-ready-startup-started) state changed from spaw
[Bug 1294284] RelatedPackageVersions.txt
apport information ** Attachment added: "RelatedPackageVersions.txt" https://bugs.launchpad.net/bugs/1294284/+attachment/4032646/+files/RelatedPackageVersions.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1294284 Title: LXC Ubuntu containers do not start in Ubuntu 14.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1294284/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1294284] Re: LXC Ubuntu containers do not start in Ubuntu 14.04
apport information ** Tags added: apparmor apport-collected trusty ** Description changed: I have a testing server which I installed Ubuntu 13.10 and then upgraded to Ubuntu 14.04 beta using do-release-upgrade -d. I do not have the option to create clean install with 14.04 directly as hosting provider does not offer it yet (for obvious reasons). Anyhow, after installing lxc and creating a new Ubuntu container using lxc-create -t ubuntu -n ubuntu I tried to start it using lxc-start -n ubuntu. I receive lots of errors and it never reaches login prompt. I have to stop the server from another shell session using lxc-stop -n ubuntu. Combined output of start and stop below. <2>init: error.c:219: Assertion failed in _nih_error_raise_system: errno > 0 <2>init: Caught abort, core dumped <2>init: error.c:219: Assertion failed in _nih_error_raise_system: errno > 0 <2>init: Caught abort, core dumped <2>init: error.c:219: Assertion failed in _nih_error_raise_system: errno > 0 <2>init: Caught abort, core dumped <2>init: error.c:219: Assertion failed in _nih_error_raise_system: errno > 0 <2>init: Caught abort, core dumped <2>init: error.c:219: Assertion failed in _nih_error_raise_system: errno > 0 <2>init: Caught abort, core dumped <2>init: error.c:219: Assertion failed in _nih_error_raise_system: errno > 0 <2>init: Caught abort, core dumped <2>init: error.c:219: Assertion failed in _nih_error_raise_system: errno > 0 <2>init: Caught abort, core dumped <2>init: error.c:219: Assertion failed in _nih_error_raise_system: errno > 0 <2>init: Caught abort, core dumped <3>init: Error while reading from descriptor: Bad file descriptor <3>init: Error while reading from descriptor: Bad file descriptor <4>init: hostname main process (4) terminated with status 6 <4>init: plymouth-ready (startup) main process (6) terminated with status 6 <4>init: plymouth main process (8) terminated with status 6 <4>init: hwclock main process (10) terminated with status 6 <4>init: ureadahead main process (12) terminated with status 6 <4>init: startpar-bridge (hostname--started) main process (14) terminated with status 6 <4>init: startpar-bridge (plymouth-ready-startup-started) main process (16) terminated with status 6 <4>init: startpar-bridge (hwclock--started) main process (18) terminated with status 6 <2>init: error.c:219: Assertion failed in _nih_error_raise_system: errno > 0 <2>init: Caught abort, core dumped <2>init: error.c:219: Assertion failed in _nih_error_raise_system: errno > 0 <2>init: Caught abort, core dumped <2>init: error.c:219: Assertion failed in _nih_error_raise_system: errno > 0 <2>init: Caught abort, core dumped <2>init: error.c:219: Assertion failed in _nih_error_raise_system: errno > 0 <2>init: Caught abort, core dumped <2>init: error.c:219: Assertion failed in _nih_error_raise_system: errno > 0 <2>init: Caught abort, core dumped <2>init: error.c:219: Assertion failed in _nih_error_raise_system: errno > 0 <2>init: Caught abort, core dumped <3>init: Error while reading from descriptor: Bad file descriptor <4>init: mountall main process (20) terminated with status 6 <4>init: startpar-bridge (hostname--stopped) main process (22) terminated with status 6 <4>init: startpar-bridge (plymouth-ready-startup-stopped) main process (24) terminated with status 6 <4>init: startpar-bridge (plymouth--stopped) main process (26) terminated with status 6 <4>init: startpar-bridge (hwclock--stopped) main process (28) terminated with status 6 <4>init: startpar-bridge (ureadahead--stopped) main process (30) terminated with status 6 <2>init: error.c:219: Assertion failed in _nih_error_raise_system: errno > 0 <2>init: Caught abort, core dumped <4>init: mountall post-stop process (32) terminated with status 6 <2>init: error.c:219: Assertion failed in _nih_error_raise_system: errno > 0 <2>init: Caught abort, core dumped <2>init: error.c:219: Assertion failed in _nih_error_raise_system: errno > 0 <2>init: Caught abort, core dumped <2>init: error.c:219: Assertion failed in _nih_error_raise_system: errno > 0 <2>init: Caught abort, core dumped <2>init: error.c:219: Assertion failed in _nih_error_raise_system: errno > 0 <2>init: Caught abort, core dumped <3>init: Error while reading from descriptor: Bad file descriptor <4>init: startpar-bridge (mountall--stopped) main process (34) terminated with status 6 <4>init: console-setup main process (36) terminated with status 6 <4>init: plymouth-stop pre-start process (38) terminated with status 6 <4>init: startpar-bridge (console-setup--started) main process (40) terminated with status 6 <2>init: error.c:219: Assertion failed in _nih_error_raise_system: errno > 0 <2>init: Caught abort, core dumped <2>init: error.c:219: Assertion failed in _nih_error_raise_system: errno > 0 <2>init: Caught abort, core dumped <2>init: error.c:219: Assertion failed
[Bug 1294284] Re: LXC Ubuntu containers do not start in Ubuntu 14.04
lxc-execute appears to work, but it does output two errors.
lxc-execute: Device or resource busy - failed to set memory.use_hierarchy to 1;
continuing
lxc-execute: Device or resource busy - failed to set memory.use_hierarchy to 1;
continuing
And here's the output from strace:
lxc-start: Device or resource busy - failed to set memory.use_hierarchy to 1;
continuing
lxc-start: Device or resource busy - failed to set memory.use_hierarchy to 1;
continuing
execve("/sbin/init", ["/sbin/init"], [/* 1 var */]) = 0
brk(0) = 0x7f2679976000
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory)
mmap(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x7f2679372000
access("/etc/ld.so.preload", R_OK) = -1 ENOENT (No such file or directory)
open("/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=10673, ...}) = 0
mmap(NULL, 10673, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7f267936f000
close(3)= 0
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory)
open("/lib/x86_64-linux-gnu/libnih.so.1", O_RDONLY|O_CLOEXEC) = 3
read(3, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0`G\0\0\0\0\0\0"..., 832)
= 832
fstat(3, {st_mode=S_IFREG|0644, st_size=96280, ...}) = 0
mmap(NULL, 2191776, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) =
0x7f2678f3a000
mprotect(0x7f2678f51000, 2093056, PROT_NONE) = 0
mmap(0x7f267915, 8192, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x16000) = 0x7f267915
close(3)= 0
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory)
open("/lib/x86_64-linux-gnu/libnih-dbus.so.1", O_RDONLY|O_CLOEXEC) = 3
read(3, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\340,\0\0\0\0\0\0"...,
832) = 832
fstat(3, {st_mode=S_IFREG|0644, st_size=38920, ...}) = 0
mmap(NULL, 2134040, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) =
0x7f2678d3
mprotect(0x7f2678d38000, 2097152, PROT_NONE) = 0
mmap(0x7f2678f38000, 8192, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x8000) = 0x7f2678f38000
close(3)= 0
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory)
open("/lib/x86_64-linux-gnu/libdbus-1.so.3", O_RDONLY|O_CLOEXEC) = 3
read(3, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0@h\0\0\0\0\0\0"..., 832)
= 832
fstat(3, {st_mode=S_IFREG|0644, st_size=281552, ...}) = 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x7f267936e000
mmap(NULL, 2377344, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) =
0x7f2678aeb000
mprotect(0x7f2678b2f000, 2093056, PROT_NONE) = 0
mmap(0x7f2678d2e000, 8192, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x43000) = 0x7f2678d2e000
close(3)= 0
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory)
open("/lib/x86_64-linux-gnu/libselinux.so.1", O_RDONLY|O_CLOEXEC) = 3
read(3, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\0[\0\0\0\0\0\0"...,
832) = 832
fstat(3, {st_mode=S_IFREG|0644, st_size=134296, ...}) = 0
mmap(NULL, 2238192, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) =
0x7f26788c8000
mprotect(0x7f26788e8000, 2093056, PROT_NONE) = 0
mmap(0x7f2678ae7000, 8192, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x1f000) = 0x7f2678ae7000
mmap(0x7f2678ae9000, 5872, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7f2678ae9000
close(3)= 0
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory)
open("/lib/x86_64-linux-gnu/libjson-c.so.2", O_RDONLY|O_CLOEXEC) = 3
read(3, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\320&\0\0\0\0\0\0"...,
832) = 832
fstat(3, {st_mode=S_IFREG|0644, st_size=39328, ...}) = 0
mmap(NULL, 2134472, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) =
0x7f26786be000
mprotect(0x7f26786c7000, 2093056, PROT_NONE) = 0
mmap(0x7f26788c6000, 8192, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x8000) = 0x7f26788c6000
close(3)= 0
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory)
open("/lib/x86_64-linux-gnu/librt.so.1", O_RDONLY|O_CLOEXEC) = 3
read(3, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0P#\0\0\0\0\0\0"..., 832)
= 832
fstat(3, {st_mode=S_IFREG|0644, st_size=31792, ...}) = 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x7f267936d000
mmap(NULL, 2129016, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) =
0x7f26784b6000
mprotect(0x7f26784bd000, 2093056, PROT_NONE) = 0
mmap(0x7f26786bc000, 8192, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x6000) = 0x7f26786bc000
close(3)= 0
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory)
open("/lib/x86_64-l
[Bug 1294284] Re: LXC Ubuntu containers do not start in Ubuntu 14.04
Yeah, I can use chroot without issues. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1294284 Title: LXC Ubuntu containers do not start in Ubuntu 14.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1294284/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1294284] Re: LXC Ubuntu containers do not start in Ubuntu 14.04
I created new container with the command you suggested, same results as original Ubuntu container I created. Here's trace output. lxc-start 1395236983.307 INFO lxc_start_ui - using rcfile /var/lib/lxc/ubuntu/config lxc-start 1395236983.309 WARN lxc_log - lxc_log_init called with log already initialized lxc-start 1395236983.309 INFO lxc_lsm - LSM security driver AppArmor lxc-start 1395236983.311 DEBUGlxc_conf - allocated pty '/dev/pts/1' (5/6) lxc-start 1395236983.311 DEBUGlxc_conf - allocated pty '/dev/pts/2' (7/8) lxc-start 1395236983.312 DEBUGlxc_conf - allocated pty '/dev/pts/3' (9/10) lxc-start 1395236983.312 DEBUGlxc_conf - allocated pty '/dev/pts/5' (11/12) lxc-start 1395236983.312 INFO lxc_conf - tty's configured lxc-start 1395236983.312 DEBUGlxc_start - sigchild handler set lxc-start 1395236983.312 DEBUGlxc_console - opening /dev/tty for console peer lxc-start 1395236983.312 DEBUGlxc_console - using '/dev/tty' as console lxc-start 1395236983.312 DEBUGlxc_console - 4057 got SIGWINCH fd 17 lxc-start 1395236983.312 DEBUGlxc_console - set winsz dstfd:14 cols:237 rows:63 lxc-start 1395236983.312 INFO lxc_start - 'ubuntu' is initialized lxc-start 1395236983.325 DEBUGlxc_start - Not dropping cap_sys_boot or watching utmp lxc-start 1395236983.331 DEBUGlxc_conf - instanciated veth 'veth8TFYFI/veth7V6YKY', index is '24' lxc-start 1395236983.331 INFO lxc_cgroup - cgroup driver cgroupfs initing for ubuntu lxc-start 1395236983.332 ERRORlxc_cgfs - Device or resource busy - failed to set memory.use_hierarchy to 1; continuing lxc-start 1395236983.332 ERRORlxc_cgfs - Device or resource busy - failed to set memory.use_hierarchy to 1; continuing lxc-start 1395236983.341 DEBUGlxc_cgfs - cgroup 'devices.deny' set to 'a' lxc-start 1395236983.342 DEBUGlxc_cgfs - cgroup 'devices.allow' set to 'c *:* m' lxc-start 1395236983.342 DEBUGlxc_cgfs - cgroup 'devices.allow' set to 'b *:* m' lxc-start 1395236983.342 DEBUGlxc_cgfs - cgroup 'devices.allow' set to 'c 1:3 rwm' lxc-start 1395236983.342 DEBUGlxc_cgfs - cgroup 'devices.allow' set to 'c 1:5 rwm' lxc-start 1395236983.342 DEBUGlxc_cgfs - cgroup 'devices.allow' set to 'c 5:0 rwm' lxc-start 1395236983.342 DEBUGlxc_cgfs - cgroup 'devices.allow' set to 'c 5:1 rwm' lxc-start 1395236983.342 DEBUGlxc_cgfs - cgroup 'devices.allow' set to 'c 1:8 rwm' lxc-start 1395236983.342 DEBUGlxc_cgfs - cgroup 'devices.allow' set to 'c 1:9 rwm' lxc-start 1395236983.342 DEBUGlxc_cgfs - cgroup 'devices.allow' set to 'c 5:2 rwm' lxc-start 1395236983.342 DEBUGlxc_cgfs - cgroup 'devices.allow' set to 'c 136:* rwm' lxc-start 1395236983.342 DEBUGlxc_cgfs - cgroup 'devices.allow' set to 'c 254:0 rm' lxc-start 1395236983.342 DEBUGlxc_cgfs - cgroup 'devices.allow' set to 'c 10:229 rwm' lxc-start 1395236983.342 DEBUGlxc_cgfs - cgroup 'devices.allow' set to 'c 10:200 rwm' lxc-start 1395236983.342 DEBUGlxc_cgfs - cgroup 'devices.allow' set to 'c 1:7 rwm' lxc-start 1395236983.342 DEBUGlxc_cgfs - cgroup 'devices.allow' set to 'c 10:228 rwm' lxc-start 1395236983.342 DEBUGlxc_cgfs - cgroup 'devices.allow' set to 'c 10:232 rwm' lxc-start 1395236983.342 INFO lxc_cgfs - cgroup has been setup lxc-start 1395236983.370 DEBUGlxc_conf - move '(null)' to '4065' lxc-start 1395236983.371 INFO lxc_conf - 'ubuntu' hostname has been setup lxc-start 1395236983.402 DEBUGlxc_conf - mac address '00:16:3e:47:4f:b4' on 'eth0' has been setup lxc-start 1395236983.403 DEBUGlxc_conf - 'eth0' has been setup lxc-start 1395236983.403 INFO lxc_conf - network has been setup lxc-start 1395236983.417 DEBUGlxc_conf - mounted '/var/lib/lxc/ubuntu/rootfs' on '/usr/lib/x86_64-linux-gnu/lxc' lxc-start 1395236983.417 DEBUGlxc_conf - Set exec command to /sbin/init lxc-start 1395236983.418 INFO lxc_conf - Autodev not required. lxc-start 1395236983.418 INFO lxc_conf - mount points have been setup lxc-start 1395236983.419 DEBUGlxc_conf - mounted 'proc' on '/usr/lib/x86_64-linux-gnu/lxc/proc', type 'proc' lxc-start 1395236983.419 DEBUGlxc_conf - mounted 'sysfs' on '/usr/lib/x86_64-linux-gnu/lxc/sys', type 'sysfs' lxc-start 1395236983.419 DEBUGlxc_conf - remounting /sys/fs/fuse/connections on /usr/lib/x86_64-linux-gnu/lxc/sys/fs/fuse/connections to respect bind or remount options lxc-start 1395236983.419 DEBUGlxc_conf - mounted '/sys/fs/fuse/connections' on '/usr/lib/x86_64-linux-gnu/lxc/sys/fs/fuse/connections', type 'none' lxc-start 1395236983.419 DEBUGlxc_conf - remounting /sys/kernel/debug on /usr/lib/x86_6
[Bug 1294284] [NEW] LXC Ubuntu containers do not start in Ubuntu 14.04
Public bug reported: I have a testing server which I installed Ubuntu 13.10 and then upgraded to Ubuntu 14.04 beta using do-release-upgrade -d. I do not have the option to create clean install with 14.04 directly as hosting provider does not offer it yet (for obvious reasons). Anyhow, after installing lxc and creating a new Ubuntu container using lxc-create -t ubuntu -n ubuntu I tried to start it using lxc-start -n ubuntu. I receive lots of errors and it never reaches login prompt. I have to stop the server from another shell session using lxc-stop -n ubuntu. Combined output of start and stop below. <2>init: error.c:219: Assertion failed in _nih_error_raise_system: errno > 0 <2>init: Caught abort, core dumped <2>init: error.c:219: Assertion failed in _nih_error_raise_system: errno > 0 <2>init: Caught abort, core dumped <2>init: error.c:219: Assertion failed in _nih_error_raise_system: errno > 0 <2>init: Caught abort, core dumped <2>init: error.c:219: Assertion failed in _nih_error_raise_system: errno > 0 <2>init: Caught abort, core dumped <2>init: error.c:219: Assertion failed in _nih_error_raise_system: errno > 0 <2>init: Caught abort, core dumped <2>init: error.c:219: Assertion failed in _nih_error_raise_system: errno > 0 <2>init: Caught abort, core dumped <2>init: error.c:219: Assertion failed in _nih_error_raise_system: errno > 0 <2>init: Caught abort, core dumped <2>init: error.c:219: Assertion failed in _nih_error_raise_system: errno > 0 <2>init: Caught abort, core dumped <3>init: Error while reading from descriptor: Bad file descriptor <3>init: Error while reading from descriptor: Bad file descriptor <4>init: hostname main process (4) terminated with status 6 <4>init: plymouth-ready (startup) main process (6) terminated with status 6 <4>init: plymouth main process (8) terminated with status 6 <4>init: hwclock main process (10) terminated with status 6 <4>init: ureadahead main process (12) terminated with status 6 <4>init: startpar-bridge (hostname--started) main process (14) terminated with status 6 <4>init: startpar-bridge (plymouth-ready-startup-started) main process (16) terminated with status 6 <4>init: startpar-bridge (hwclock--started) main process (18) terminated with status 6 <2>init: error.c:219: Assertion failed in _nih_error_raise_system: errno > 0 <2>init: Caught abort, core dumped <2>init: error.c:219: Assertion failed in _nih_error_raise_system: errno > 0 <2>init: Caught abort, core dumped <2>init: error.c:219: Assertion failed in _nih_error_raise_system: errno > 0 <2>init: Caught abort, core dumped <2>init: error.c:219: Assertion failed in _nih_error_raise_system: errno > 0 <2>init: Caught abort, core dumped <2>init: error.c:219: Assertion failed in _nih_error_raise_system: errno > 0 <2>init: Caught abort, core dumped <2>init: error.c:219: Assertion failed in _nih_error_raise_system: errno > 0 <2>init: Caught abort, core dumped <3>init: Error while reading from descriptor: Bad file descriptor <4>init: mountall main process (20) terminated with status 6 <4>init: startpar-bridge (hostname--stopped) main process (22) terminated with status 6 <4>init: startpar-bridge (plymouth-ready-startup-stopped) main process (24) terminated with status 6 <4>init: startpar-bridge (plymouth--stopped) main process (26) terminated with status 6 <4>init: startpar-bridge (hwclock--stopped) main process (28) terminated with status 6 <4>init: startpar-bridge (ureadahead--stopped) main process (30) terminated with status 6 <2>init: error.c:219: Assertion failed in _nih_error_raise_system: errno > 0 <2>init: Caught abort, core dumped <4>init: mountall post-stop process (32) terminated with status 6 <2>init: error.c:219: Assertion failed in _nih_error_raise_system: errno > 0 <2>init: Caught abort, core dumped <2>init: error.c:219: Assertion failed in _nih_error_raise_system: errno > 0 <2>init: Caught abort, core dumped <2>init: error.c:219: Assertion failed in _nih_error_raise_system: errno > 0 <2>init: Caught abort, core dumped <2>init: error.c:219: Assertion failed in _nih_error_raise_system: errno > 0 <2>init: Caught abort, core dumped <3>init: Error while reading from descriptor: Bad file descriptor <4>init: startpar-bridge (mountall--stopped) main process (34) terminated with status 6 <4>init: console-setup main process (36) terminated with status 6 <4>init: plymouth-stop pre-start process (38) terminated with status 6 <4>init: startpar-bridge (console-setup--started) main process (40) terminated with status 6 <2>init: error.c:219: Assertion failed in _nih_error_raise_system: errno > 0 <2>init: Caught abort, core dumped <2>init: error.c:219: Assertion failed in _nih_error_raise_system: errno > 0 <2>init: Caught abort, core dumped <2>init: error.c:219: Assertion failed in _nih_error_raise_system: errno > 0 <2>init: Caught abort, core dumped <2>init: error.c:219: Assertion failed in _nih_error_raise_system: errno > 0 <2>init: Caught abort, core dumped <3>init: Error while reading from descriptor
[Bug 69494] Re: Kopete 0.12.3 can't log in to ICQ anymore
Edgy fix works here too. -- Kopete 0.12.3 can't log in to ICQ anymore https://launchpad.net/bugs/69494 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 68020] Re: Azureus 2.5.0.0 crashes
Here's java error log from the crash if it helps any. ** Attachment added: "Java error log from Azureus 2.5.0.0 crash" http://librarian.launchpad.net/4933850/hs_err_pid6357.log -- Azureus 2.5.0.0 crashes https://launchpad.net/bugs/68020 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 68020] Azureus 2.5.0.0 crashes
Public bug reported: Binary package hint: azureus New Azureus 2.5.0.0 hit the Edgy repositories earlier, however it crashes as soon as it has loaded and the main screen comes up. I already tried to remove azureus with purge and with and without the new azureus- gcj package. ** Affects: azureus (Ubuntu) Importance: Undecided Status: Unconfirmed -- Azureus 2.5.0.0 crashes https://launchpad.net/bugs/68020 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 66210] Re: Integrated audio occasionally gets index 0
*** This bug is a duplicate of bug 48377 *** In addition, I believe it is largely thanks to the default lines below "# Prevent abnormal drivers from grabbing index 0" in /etc/modprobe.d /alsa-base that this bug does not get much more attention. -- Integrated audio occasionally gets index 0 https://launchpad.net/bugs/66210 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 66210] Re: Integrated audio occasionally gets index 0
*** This bug is a duplicate of bug 48377 *** The difference between Dapper and Edgy seems to be that Dapper ignores devices disabled in BIOS but Edgy doesn't. When you disable onboard audio device from BIOS, it should be ignored entirely, yet Edgy tries to use it like it is enabled. I'm not a developer but this smells like a kernel bug to me. -- Integrated audio occasionally gets index 0 https://launchpad.net/bugs/66210 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 66210] Re: Integrated audio occasionally gets index 0
After adding following lines to /etc/modprobe.d/alsa-base the problem has not occured since. options snd-via82xx index=-2 options snd-via82cxxx_audio index=-2 -- Integrated audio occasionally gets index 0 https://launchpad.net/bugs/66210 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 57875] Re: Azureus does not start
I have this same problem on Kubuntu 6.10. I solved the problem by replacing /usr/share/java/Azureus.jar with Azureus2.5.0.0.jar (rename to Azureus.jar) which can be downloaded from http://prdownloads.sourceforge.net/azureus/Azureus2.5.0.0.jar?download When Azureus 2.5.0.0 is started the first time, it gives a warning notice about old Eclipse but it does not come up afterwards and as far as I can tell, works just fine. -- Azureus does not start https://launchpad.net/bugs/57875 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 66210] Re: Integrated audio occasionally gets index 0
** Summary changed: - Integrated SoundMAX AD1980 occasionally gets index 0 + Integrated audio occasionally gets index 0 ** Description changed: I have Asus K8V Deluxe motherboard with integrated SoundMAX AD1980 soundcard, I have disabled it from BIOS and instead use Audigy 2 ZS. I downloaded Kubuntu 6.10 Beta a while back and I have a problem with it. Kubuntu 6.10 seems to recognize the integrated AD1980 chip as VIA 8237, but the real problem is that often the VIA 8237 is primary sound card and I cannot get any sound out of my Audigy. I haven't found any other solution to this problem but reboot until Audigy is again the default sound card. It seems like it is totally random which audio device is the primary sound card on boot. Whether the integrated audio is disabled or enabled in BIOS does not affect this problem. My Kubuntu 6.10 installation is a clean install, not an upgrade from 6.06. Just now I had to reboot three times to get my Audigy working, it's a bit annoying all right. :) I can say that this bug did not exist in Ubuntu 6.06, but unfortunately I haven't tried Ubuntu 6.10 or Kubuntu 6.06. I guess I can try both of them if it is really necessary, but I'd like to avoid that work if I just can. ;) Thanks. + + + Edit: Changed summary a bit. -- Integrated audio occasionally gets index 0 https://launchpad.net/bugs/66210 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 66210] Re: Integrated SoundMAX AD1980 occasionally gets index 0
** Description changed: I have Asus K8V Deluxe motherboard with integrated SoundMAX AD1980 soundcard, I have disabled it from BIOS and instead use Audigy 2 ZS. I downloaded Kubuntu 6.10 Beta a while back and I have a problem with it. Kubuntu 6.10 seems to recognize the integrated AD1980 chip as VIA 8237, but the real problem is that often the VIA 8237 is primary sound card and I cannot get any sound out of my Audigy. I haven't found any other solution to this problem but reboot until Audigy is again the default sound card. It seems like it is totally random which audio device is the primary sound card on boot. Whether the integrated audio is disabled or enabled in BIOS does not affect this problem. - I can say that this bug did not exist in Ubuntu 6.06, but unfortunately - I haven't tried Ubuntu 6.10 or Kubuntu 6.06. I guess I can try both of - them if it is really necessary, but I'd like to avoid that work if I - just can. ;) Thanks. + My Kubuntu 6.10 installation is a clean install, not an upgrade from + 6.06. Just now I had to reboot three times to get my Audigy working, + it's a bit annoying all right. :) I can say that this bug did not exist + in Ubuntu 6.06, but unfortunately I haven't tried Ubuntu 6.10 or Kubuntu + 6.06. I guess I can try both of them if it is really necessary, but I'd + like to avoid that work if I just can. ;) Thanks. -- Integrated SoundMAX AD1980 occasionally gets index 0 https://launchpad.net/bugs/66210 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 66210] Integrated SoundMAX AD1980 occasionally gets index 0
Public bug reported: I have Asus K8V Deluxe motherboard with integrated SoundMAX AD1980 soundcard, I have disabled it from BIOS and instead use Audigy 2 ZS. I downloaded Kubuntu 6.10 Beta a while back and I have a problem with it. Kubuntu 6.10 seems to recognize the integrated AD1980 chip as VIA 8237, but the real problem is that often the VIA 8237 is primary sound card and I cannot get any sound out of my Audigy. I haven't found any other solution to this problem but reboot until Audigy is again the default sound card. It seems like it is totally random which audio device is the primary sound card on boot. Whether the integrated audio is disabled or enabled in BIOS does not affect this problem. I can say that this bug did not exist in Ubuntu 6.06, but unfortunately I haven't tried Ubuntu 6.10 or Kubuntu 6.06. I guess I can try both of them if it is really necessary, but I'd like to avoid that work if I just can. ;) Thanks. ** Affects: Ubuntu Importance: Undecided Status: Unconfirmed -- Integrated SoundMAX AD1980 occasionally gets index 0 https://launchpad.net/bugs/66210 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
