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
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
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
Yeah, I can use chroot without issues.
--
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/1294284
Title:
LXC Ubuntu containers do not start in Ubuntu 14.04
To manage notifications about
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:
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
Server Team, which is subscribed to lxc in Ubuntu.
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
Server Team, which is subscribed to lxc in Ubuntu.
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
Server Team, which is subscribed to lxc in Ubuntu.
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
6init: Handling startup event
6init: mountall goal changed from stop to start
6init: mountall state changed from
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
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
Server Team, which is subscribed to lxc in Ubuntu.
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
Server Team, which is subscribed to lxc in Ubuntu.
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
Server Team, which is subscribed to lxc in Ubuntu.
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
Server Team, which is subscribed to lxc in Ubuntu.
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
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1294284
Title:
LXC Ubuntu
Added the line but no change.
--
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/1294284
Title:
LXC Ubuntu containers do not start in Ubuntu 14.04
To manage notifications about this bug
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
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1294284
Title:
LXC Ubuntu containers do not start in
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
Server Team, which is subscribed to lxc in Ubuntu.
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
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:
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:
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
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.
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
6init: Handling startup event
6init: mountall goal changed from stop to start
6init: mountall state changed from
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.
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
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
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:
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:
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
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
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
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
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.
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
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
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
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
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
*** 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
*** 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
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
** 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
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
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
** 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
46 matches
Mail list logo
