[Bug 1261338] Re: lxc-stop and even lxc-stop -k can hang
It never happened again (and may have been a misuse involving immortal sudo subprocesses but I'm blurry on the details), marking invalid but fixed released may be correct as well. ** Changed in: lxc (Ubuntu) Status: Expired => Invalid -- 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/1261338 Title: lxc-stop and even lxc-stop -k can hang To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1261338/+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 1436723] Re: Regression: Nested LXC is broken on Vivid
@Chris: Thanks ! I had to implement a different scheme not using nested containers but still requiring lxc-1.1.2. I'll give nested containers another shot asap. -- 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/1436723 Title: Regression: Nested LXC is broken on Vivid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1436723/+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 1436723] Re: Regression: Nested LXC is broken on Vivid
I run into the same issue on a vivid host while trying to start a trusty nested container from inside a trusty container. -- 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/1436723 Title: Regression: Nested LXC is broken on Vivid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1436723/+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 1436723] Re: Regression: Nested LXC is broken on Vivid
@Chris: Where do you add the ubuntu-lxc/daily ppa ? On the host or on the outer container ? -- 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/1436723 Title: Regression: Nested LXC is broken on Vivid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1436723/+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 1445143] Re: fail to process user-data with cloud-config-archive
Building on top of the added test (test_cloud_config_archive), using the following breaks (the yaml can't be parsed): message = '''#cloud-config-archive - content: #cloud-config\napt_update: true\napt_upgrade: true\nchpasswd:\n expire:\ \ false\nmanage_etc_hosts: true\npackages:\n- bzr\n- ubuntu-desktop\n- avahi-daemon\n\ password: ubuntu\npower_state:\nmode: poweroff\n ''' -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1445143 Title: fail to process user-data with cloud-config-archive To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1445143/+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 1443557] Re: snappy update error message 'already locked' is confusing
** Package changed: snappy (Ubuntu) = snappy-ubuntu -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to snappy in Ubuntu. https://bugs.launchpad.net/bugs/1443557 Title: snappy update error message 'already locked' is confusing To manage notifications about this bug go to: https://bugs.launchpad.net/snappy-ubuntu/+bug/1443557/+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 1443557] [NEW] snappy update error message 'already locked' is confusing
Public bug reported: Running 'snappy update' may issue an 'already locked' error message. mvo explained that this is caued by 'autopilot' running in the background and 'tail /var/log/syslog' contains more details (indeed it does). The message is confusing for a newcomer. ** Affects: snappy (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to snappy in Ubuntu. https://bugs.launchpad.net/bugs/1443557 Title: snappy update error message 'already locked' is confusing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snappy/+bug/1443557/+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 1261338] Re: lxc-stop and even lxc-stop -k can hang
Sorry for not providing timely feedback there (nor a reproducing env). Truth is this hasn't recur so marking invalid seems fair. Thanks for the help nevertheless, if it happens again, I'll make sure to have such a reproducing env before re-opening this bug. -- 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/1261338 Title: lxc-stop and even lxc-stop -k can hang To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1261338/+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 1261338] [NEW] lxc-stop and even lxc-stop -k can hang
Public bug reported: and even 'lxc-stop -k -t timeout' can hang :-/ The context is an automated test run with otto using a lxc-container trigerring a kernel crash on the host. The host is still alive and so is the container but trying to implement a catch-all to stop a container left running is blocked because there is no way in this particular case to stop the container. The only alternative so far is to reboot the host :-/ http://q-jenkins.ubuntu-ci:8080/job/autopilot-trusty-daily_release/label =qa-intel-4000/951/console is one occurrence where the kernel crashed and 'lxc-stop -k -t 120 -n trusty-i386-20131216-0008' hanged requiring the job to be aborted. ** Affects: lxc (Ubuntu) Importance: Undecided Status: New ** Tags: ci-engineering -- 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/1261338 Title: lxc-stop and even lxc-stop -k can hang To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1261338/+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 1227937] Re: lxc-start is unconfined but has a profile defined
@Serge: I encounter the issue in http://10.97.0.1:8080/job/autopilot-saucy-daily_release/label=autopilot- intel/2465/console which runs on intel. I will try to reproduce locally (this happened in the ci lab). -- 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/1227937 Title: lxc-start is unconfined but has a profile defined To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1227937/+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 1157589] Re: kvm hangs for freebsd guests since raring upgrade
Testing done, the bug is present in 3.8.4 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to kvm in Ubuntu. https://bugs.launchpad.net/bugs/1157589 Title: kvm hangs for freebsd guests since raring upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kvm/+bug/1157589/+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 1157589] Re: kvm hangs for freebsd guests since raring upgrade
Fixed upstream, great. Rough estimate about when this will land for raring ? ** Tags added: kernel-fixed-upstream ** Changed in: linux (Ubuntu) Status: Incomplete = Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to kvm in Ubuntu. https://bugs.launchpad.net/bugs/1157589 Title: kvm hangs for freebsd guests since raring upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kvm/+bug/1157589/+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 1157589] Re: kvm hangs for freebsd guests since raring upgrade
** Changed in: linux (Ubuntu) Status: Incomplete = Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to kvm in Ubuntu. https://bugs.launchpad.net/bugs/1157589 Title: kvm hangs for freebsd guests since raring upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kvm/+bug/1157589/+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 1157589] Re: kvm hangs for freebsd guests since raring upgrade
** Attachment added: Freebsd9 xml description https://bugs.launchpad.net/ubuntu/+source/kvm/+bug/1157589/+attachment/3588233/+files/freebsd9.xml -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to kvm in Ubuntu. https://bugs.launchpad.net/bugs/1157589 Title: kvm hangs for freebsd guests since raring upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kvm/+bug/1157589/+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 1157589] Re: kvm hangs for freebsd guests since raring upgrade
** Attachment added: vrish capabilities output https://bugs.launchpad.net/ubuntu/+source/kvm/+bug/1157589/+attachment/3588234/+files/virsh.capabilities -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to kvm in Ubuntu. https://bugs.launchpad.net/bugs/1157589 Title: kvm hangs for freebsd guests since raring upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kvm/+bug/1157589/+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 1157589] Re: kvm hangs for freebsd guests since raring upgrade
As discussed on IRC, doing: sudo kvm -hda freebsd-8.0-64bits.qcow2 -serial stdio doesn't trigger the bug, I'll investigate on which part of the xml is causing the issue and report here. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to kvm in Ubuntu. https://bugs.launchpad.net/bugs/1157589 Title: kvm hangs for freebsd guests since raring upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kvm/+bug/1157589/+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 1157589] Re: kvm hangs for freebsd guests since raring upgrade
apport information ** Tags added: apport-collected third-party-packages ** Description changed: Until I upgraded to raring, freebsd guest has been one of my most stable guest under kvm (and previously under vbox for that matter). Since the upgrade to raring, my existing guest hangs very early in the boot process ending with the following in /var/log/libvirt/qemu/freebsd8.log : 2013-03-20 07:47:53.020+: starting up LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/sbin:/sbin:/bin QEMU_AUDIO_DRV=none /usr/bin/kvm -name freebsd8 -S -M pc-1.0 -m 4096 -smp 2,sockets=2,cores=1,threads=1 -uuid 1babac4e-de14-5f5d-73e9-dfe524966f9a -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/freebsd8.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-shutdown -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -drive file=/caviar3/libvirt/images/freebsd-8.0-64bits.qcow2,if=none,id=drive-ide0-0-0,format=qcow2 -device ide-hd,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0,bootindex=1 -netdev tap,fd=30,id=hostnet0 -device e1000,netdev=hostnet0,id=net0,mac=08:00:27:5f:9f:06,bus=pci.0,addr=0x3 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -vnc 127.0.0.1:0 -vga cirrus -device intel-hda,id=sound0,bus=pci.0,addr=0x4 -device hda-duplex,id=sound0-codec0,bus=sound0.0,cad=0 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x5 W: kvm binary is deprecated, please use qemu-system-x86_64 instead char device redirected to /dev/pts/6 (label charserial0) KVM internal error. Suberror: 1 emulation failure RAX=80855a40 RBX=0009f000 RCX=c080 RDX= RSI= RDI= RBP= RSP= R8 = R9 = R10= R11= R12= R13= R14= R15= RIP=0009f076 RFL=00010086 [--S--P-] CPL=0 II=0 A20=1 SMM=0 HLT=0 ES = f300 DPL=3 DS16 [-WA] CS =0008 00209900 DPL=0 CS64 [--A] SS =9f00 0009f000 f300 DPL=3 DS16 [-WA] DS =0018 00c09300 DPL=0 DS [-WA] FS = f300 DPL=3 DS16 [-WA] GS = f300 DPL=3 DS16 [-WA] LDT= 8200 DPL=0 LDT TR = 8b00 DPL=0 TSS64-busy GDT= 0009f080 0020 IDT= CR0=8011 CR2= CR3=0009c000 CR4=0030 DR0= DR1= DR2= DR3= DR6=0ff0 DR7=0400 EFER=0501 Code=00 00 00 80 0f 22 c0 ea 70 f0 09 00 08 00 48 b8 40 5a 85 80 ff ff ff ff ff e0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 99 20 00 ff ff 00 00 qemu: terminating on signal 15 from pid 2474 2013-03-20 07:49:36.834+: shutting down To isolate the issue (and hoping for some change in more recent freebsd versions) I tried creating a new vm but hit the same issue. Using ftp://ftp.freebsd.org/pub/FreeBSD/releases/amd64/amd64/ISO- IMAGES/9.1/FreeBSD-9.1-RELEASE-amd64-bootonly.iso , I end up with the following /var/log/libvirt/qemu/freebsd9.log which includes the kvm command : 2013-03-20 07:52:03.780+: starting up LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/sbin:/sbin:/bin QEMU_AUDIO_DRV=none /usr/bin/kvm-spice -name freebsd9 -S -M pc-i440fx-1.4 -m 4096 -smp 2,sockets=2,cores=1,threads=1 -uuid 1ae60371-46e3-641b-4d85-9b3e5ac3cb3c -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/freebsd9.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-shutdown -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -drive file=/caviar3/libvirt/images/freebsd9.img,if=none,id=drive-ide0-0-0,format=raw -device ide-hd,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0,bootindex=1 -drive file=/caviar3/libvirt/installers/freebsd/FreeBSD-9.1-RELEASE-amd64-bootonly.iso,if=none,id=drive-ide0-1-0,readonly=on,format=raw -device ide-cd,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0 -netdev tap,fd=30,id=hostnet0 -device e1000,netdev=hostnet0,id=net0,mac=52:54:00:3e:70:67,bus=pci.0,addr=0x3 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -vnc 127.0.0.1:0 -vga cirrus -device intel-hda,id=sound0,bus=pci.0,addr=0x4 -device hda-duplex,id=sound0-codec0,bus=sound0.0,cad=0 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x5 W: kvm binary is deprecated, please use qemu-system-x86_64 instead char device redirected to /dev/pts/6 (label charserial0) KVM internal error. Suberror: 1 emulation failure RAX=80bcccd0
[Bug 1157589] ProcEnviron.txt
apport information ** Attachment added: ProcEnviron.txt https://bugs.launchpad.net/bugs/1157589/+attachment/3588504/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to kvm in Ubuntu. https://bugs.launchpad.net/bugs/1157589 Title: kvm hangs for freebsd guests since raring upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kvm/+bug/1157589/+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 1157589] [NEW] kvm hangs for freebsd guests since raring upgrade
Public bug reported: Until I upgraded to raring, freebsd guest has been one of my most stable guest under kvm (and previously under vbox for that matter). Since the upgrade to raring, my existing guest hangs very early in the boot process ending with the following in /var/log/libvirt/qemu/freebsd8.log : 2013-03-20 07:47:53.020+: starting up LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/sbin:/sbin:/bin QEMU_AUDIO_DRV=none /usr/bin/kvm -name freebsd8 -S -M pc-1.0 -m 4096 -smp 2,sockets=2,cores=1,threads=1 -uuid 1babac4e-de14-5f5d-73e9-dfe524966f9a -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/freebsd8.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-shutdown -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -drive file=/caviar3/libvirt/images/freebsd-8.0-64bits.qcow2,if=none,id=drive-ide0-0-0,format=qcow2 -device ide-hd,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0,bootindex=1 -netdev tap,fd=30,id=hostnet0 -device e1000,netdev=hostnet0,id=net0,mac=08:00:27:5f:9f:06,bus=pci.0,addr=0x3 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -vnc 127.0.0.1:0 -vga cirrus -device intel-hda,id=sound0,bus=pci.0,addr=0x4 -device hda-duplex,id=sound0-codec0,bus=sound0.0,cad=0 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x5 W: kvm binary is deprecated, please use qemu-system-x86_64 instead char device redirected to /dev/pts/6 (label charserial0) KVM internal error. Suberror: 1 emulation failure RAX=80855a40 RBX=0009f000 RCX=c080 RDX= RSI= RDI= RBP= RSP= R8 = R9 = R10= R11= R12= R13= R14= R15= RIP=0009f076 RFL=00010086 [--S--P-] CPL=0 II=0 A20=1 SMM=0 HLT=0 ES = f300 DPL=3 DS16 [-WA] CS =0008 00209900 DPL=0 CS64 [--A] SS =9f00 0009f000 f300 DPL=3 DS16 [-WA] DS =0018 00c09300 DPL=0 DS [-WA] FS = f300 DPL=3 DS16 [-WA] GS = f300 DPL=3 DS16 [-WA] LDT= 8200 DPL=0 LDT TR = 8b00 DPL=0 TSS64-busy GDT= 0009f080 0020 IDT= CR0=8011 CR2= CR3=0009c000 CR4=0030 DR0= DR1= DR2= DR3= DR6=0ff0 DR7=0400 EFER=0501 Code=00 00 00 80 0f 22 c0 ea 70 f0 09 00 08 00 48 b8 40 5a 85 80 ff ff ff ff ff e0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 99 20 00 ff ff 00 00 qemu: terminating on signal 15 from pid 2474 2013-03-20 07:49:36.834+: shutting down To isolate the issue (and hoping for some change in more recent freebsd versions) I tried creating a new vm but hit the same issue. Using ftp://ftp.freebsd.org/pub/FreeBSD/releases/amd64/amd64/ISO- IMAGES/9.1/FreeBSD-9.1-RELEASE-amd64-bootonly.iso , I end up with the following /var/log/libvirt/qemu/freebsd9.log which includes the kvm command : 2013-03-20 07:52:03.780+: starting up LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/sbin:/sbin:/bin QEMU_AUDIO_DRV=none /usr/bin/kvm-spice -name freebsd9 -S -M pc-i440fx-1.4 -m 4096 -smp 2,sockets=2,cores=1,threads=1 -uuid 1ae60371-46e3-641b-4d85-9b3e5ac3cb3c -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/freebsd9.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-shutdown -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -drive file=/caviar3/libvirt/images/freebsd9.img,if=none,id=drive-ide0-0-0,format=raw -device ide-hd,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0,bootindex=1 -drive file=/caviar3/libvirt/installers/freebsd/FreeBSD-9.1-RELEASE-amd64-bootonly.iso,if=none,id=drive-ide0-1-0,readonly=on,format=raw -device ide-cd,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0 -netdev tap,fd=30,id=hostnet0 -device e1000,netdev=hostnet0,id=net0,mac=52:54:00:3e:70:67,bus=pci.0,addr=0x3 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -vnc 127.0.0.1:0 -vga cirrus -device intel-hda,id=sound0,bus=pci.0,addr=0x4 -device hda-duplex,id=sound0-codec0,bus=sound0.0,cad=0 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x5 W: kvm binary is deprecated, please use qemu-system-x86_64 instead char device redirected to /dev/pts/6 (label charserial0) KVM internal error. Suberror: 1 emulation failure RAX=80bcccd0 RBX=0009f000 RCX=c080 RDX= RSI= RDI= RBP= RSP= R8 = R9
[Bug 1007433] Re: zookeeperd not running after installation of zookeeperd
I encounter the same issue while trying to use the same image for juju. If I use a precise image, cloud-init-output.log ends with: Installed /usr/lib/juju/juju Processing dependencies for juju==0.5 Finished processing dependencies for juju==0.5 % Total% Received % Xferd Average Speed TimeTime Time Current Dload Upload Total SpentLeft Speed 0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- 0 10010 100100 0 80 0 --:--:-- --:--:-- --:--:--81 2012-06-01 09:42:15,150 INFO Initializing zookeeper hierarchy 2012-06-01 09:42:15,203 INFO 'initialize' command finished successfully juju-machine-agent start/running, process 4776 juju-provision-agent start/running, process 4779 with the quantal image that's: Installed /usr/lib/juju/juju Processing dependencies for juju==0.5 Finished processing dependencies for juju==0.5 % Total% Received % Xferd Average Speed TimeTime Time Current Dload Upload Total SpentLeft Speed 0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- 0 10010 100100 0118 0 --:--:-- --:--:-- --:--:-- 120 could not connect before timeout 2012-06-01 13:43:21,156 ERROR could not connect before timeout Accordingly, (fuzzily matching the /var/log/syslog files) in precise: Jun 1 09:41:16 server-11237 acpid: 1 rule loaded Jun 1 09:41:16 server-11237 acpid: waiting for events: event logging is off Jun 1 09:41:16 server-11237 cron[874]: (CRON) INFO (Running @reboot jobs) Jun 1 09:41:16 server-11237 kernel: [ 10.366463] init: plymouth-upstart-bridge main process (781) killed by TERM signal Jun 1 09:41:21 server-11237 ntpdate[597]: step time server 91.189.94.4 offset 1.815666 sec Jun 1 09:42:03 server-11237 dhclient: DHCPREQUEST of 10.55.60.51 on eth0 to 10.55.60.1 port 67 in quantal: Jun 1 13:42:04 server-11254 acpid: 1 rule loaded Jun 1 13:42:04 server-11254 acpid: waiting for events: event logging is off Jun 1 13:42:04 server-11254 cron[915]: (CRON) INFO (Running @reboot jobs) Jun 1 13:42:05 server-11254 kernel: [ 10.863797] init: plymouth-stop pre-start process (1010) terminated with status 1 Jun 1 13:42:09 server-11254 ntpdate[669]: step time server 91.189.94.4 offset 1.476571 sec Jun 1 13:42:17 server-11254 ntpdate[1043]: adjust time server 91.189.94.4 offset -0.02 sec Jun 1 13:42:39 server-11254 ntpdate[1565]: adjust time server 91.189.94.4 offset 0.11 sec Jun 1 13:42:49 server-11254 kernel: [ 53.716385] init: zookeeper main process (7600) terminated with status 2 Jun 1 13:42:49 server-11254 kernel: [ 53.716407] init: zookeeper main process ended, respawning Jun 1 13:42:49 server-11254 kernel: [ 53.721173] init: zookeeper main process (7603) terminated with status 2 Jun 1 13:42:49 server-11254 kernel: [ 53.721194] init: zookeeper main process ended, respawning Jun 1 13:42:49 server-11254 kernel: [ 53.726910] init: zookeeper main process (7606) terminated with status 2 Jun 1 13:42:49 server-11254 kernel: [ 53.726933] init: zookeeper main process ended, respawning Jun 1 13:42:49 server-11254 kernel: [ 53.731772] init: zookeeper main process (7610) terminated with status 2 Jun 1 13:42:49 server-11254 kernel: [ 53.731809] init: zookeeper main process ended, respawning Jun 1 13:42:49 server-11254 kernel: [ 53.736305] init: zookeeper main process (7613) terminated with status 2 Jun 1 13:42:49 server-11254 kernel: [ 53.736326] init: zookeeper main process ended, respawning Jun 1 13:42:49 server-11254 kernel: [ 53.745407] init: zookeeper main process (7616) terminated with status 2 Jun 1 13:42:49 server-11254 kernel: [ 53.745429] init: zookeeper main process ended, respawning Jun 1 13:42:49 server-11254 kernel: [ 53.749924] init: zookeeper main process (7619) terminated with status 2 Jun 1 13:42:49 server-11254 kernel: [ 53.749946] init: zookeeper main process ended, respawning Jun 1 13:42:49 server-11254 kernel: [ 53.754772] init: zookeeper main process (7622) terminated with status 2 Jun 1 13:42:49 server-11254 kernel: [ 53.754798] init: zookeeper main process ended, respawning Jun 1 13:42:49 server-11254 kernel: [ 53.759302] init: zookeeper main process (7625) terminated with status 2 Jun 1 13:42:49 server-11254 kernel: [ 53.759327] init: zookeeper main process ended, respawning Jun 1 13:42:49 server-11254 kernel: [ 53.765900] init: zookeeper main process (7628) terminated with status 2 Jun 1 13:42:49 server-11254 kernel: [ 53.765922] init: zookeeper main process ended, respawning Jun 1 13:42:49 server-11254 kernel: [ 53.770424] init: zookeeper main process (7631) terminated with status 2 Jun 1 13:42:49 server-11254 kernel: [ 53.770445] init: zookeeper respawning too fast, stopped Jun 1 13:42:53 server-11254 dhclient: DHCPREQUEST of 10.55.60.114 on eth0
[Bug 959610] Re: keystone is not logging
@Adam: Confirmed, using DEBUG produces output \o/ But DEBUG may not be appropriate in the long run ? Anyway, I'm out of trouble. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to keystone in Ubuntu. https://bugs.launchpad.net/bugs/959610 Title: keystone is not logging To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/959610/+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 959610] Re: keystone is not logging
For the record, trying to apply the moral equivalent of the proposed patch to my config files I still don't get anything written to the log file :-/ -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to keystone in Ubuntu. https://bugs.launchpad.net/bugs/959610 Title: keystone is not logging To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/959610/+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 961277] [NEW] Cannot uninstall keystone
Public bug reported: While trying to uninstall keystone (to start from a clean slate), synaptic complains: (Reading database ... 304179 files and directories currently installed.) Removing keystone ... dpkg: error processing keystone (--remove): subprocess installed pre-removal script returned error exit status 10 No apport report written because MaxReports is reached already postinst called with unknown argument `abort-remove' Errors were encountered while processing: keystone E: Sub-process /usr/bin/dpkg returned an error code (1) A package failed to install. Trying to recover: Trying to force a re-installation instead, it still fails with: Setting up keystone (2012.1~rc1~20120316.2145-0ubuntu1) ... Traceback (most recent call last): File /usr/bin/keystone-manage, line 28, in module cli.main(argv=sys.argv, config_files=config_files) File /usr/lib/python2.7/dist-packages/keystone/cli.py, line 148, in main return run(cmd, (args[:1] + args[2:])) File /usr/lib/python2.7/dist-packages/keystone/cli.py, line 134, in run return CMDS[cmd](argv=args).run() File /usr/lib/python2.7/dist-packages/keystone/cli.py, line 36, in run return self.main() File /usr/lib/python2.7/dist-packages/keystone/cli.py, line 55, in main driver = utils.import_object(getattr(CONF, k).driver) File /usr/lib/python2.7/dist-packages/keystone/common/utils.py, line 58, in import_object __import__(import_str) TypeError: __import__() argument 1 must be string, not None dpkg: error processing keystone (--configure): subprocess installed post-installation script returned error exit status 1 No apport report written because MaxReports is reached already Errors were encountered while processing: keystone E: Sub-process /usr/bin/dpkg returned an error code (1) A package failed to install. Trying to recover: ** Affects: keystone (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to keystone in Ubuntu. https://bugs.launchpad.net/bugs/961277 Title: Cannot uninstall keystone To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/keystone/+bug/961277/+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 961277] Re: Cannot uninstall keystone
Forget the re-install part, I renamed /etc/keystone while hammering, restoring its proper name allow the re-installation to complete. Removing the package is still not possible -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to keystone in Ubuntu. https://bugs.launchpad.net/bugs/961277 Title: Cannot uninstall keystone To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/keystone/+bug/961277/+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 961277] Re: Cannot uninstall keystone
@Soren: Sorry for the confusing bug report, keystone-manage is called while re-installing, not while removing. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to keystone in Ubuntu. https://bugs.launchpad.net/bugs/961277 Title: Cannot uninstall keystone To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/keystone/+bug/961277/+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 922954] Re: keystone has a missing dep on python-prettytable
** Changed in: keystone (Ubuntu) Assignee: (unassigned) = Vincent Ladeuil (vila) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to keystone in Ubuntu. https://bugs.launchpad.net/bugs/922954 Title: keystone has a missing dep on python-prettytable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/keystone/+bug/922954/+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 922954] Re: keystone has a missing dep on python-prettytable
Please re-open this bug as the dependency was added to the wrong section, see https://code.launchpad.net/~vila/ubuntu/precise/keystone/fix-922954/+merge/91457 for an hopefully proper fix. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to keystone in Ubuntu. https://bugs.launchpad.net/bugs/922954 Title: keystone has a missing dep on python-prettytable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/keystone/+bug/922954/+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
