[Bug 230030] Re: php segfaults with readline
According to the Free Software Foundation [1] php CANNOT be legally linked to libreadline, because libreadline is licensed under the GPL and php is licensed under the php license. [1] http://www.gnu.org/licenses/gpl-faq.html -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to php5 in Ubuntu. https://bugs.launchpad.net/bugs/230030 Title: php segfaults with readline To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php5/+bug/230030/+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
[Blueprint servercloud-q-chef] Getting Chef Back Into Ubuntu
Blueprint changed by Bryan McLellan: Work items changed: Work items: [james-page] Generally keep a eye on progress in Debian and ensure syncs/blacklists allow this (esp milestones): TODO [james-page] Sort out solr in Debian to help unblock Debian work: INPROGRESS [btm] Check on whether solr 3.6 could be used with chef: TODO - [btm] Subscribe to relevant packages in ubuntu to help with communications: TODO + [btm] Subscribe to relevant packages in ubuntu to help with communications (chef, ohai, *mixlib*): DONE -- Getting Chef Back Into Ubuntu https://blueprints.launchpad.net/ubuntu/+spec/servercloud-q-chef -- 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
[Blueprint servercloud-q-chef] Getting Chef Back Into Ubuntu
Blueprint changed by Bryan McLellan: Whiteboard changed: Discussion Topics: What issues lead to the packages being removed from precise? + - Fast Chef development cycle over the last two years made current stable branch 0.10.x while precise still had 0.8.16. + - solr package became out of date and broken, which blocked chef-solr [1] How do we ensure that these don't re-occur to ensure the long term viability of chef as part of Ubuntu? - - Maintaining chef in Debian will help with this. - - Recommending users of Ubuntu and Debian to use the packages (instead of gem installing) will also help. + - Maintaining chef in Debian will help with this. +a) The debian pkg-ruby-extras team can use help, especially with the current transition + - rails3 support in debian [2] for Chef 11 + - Recommending users of Ubuntu and Debian to use the packages (instead of gem installing) will also help. +a) The differing release paradigm makes this problematic. With a goal of stability, debian/ubuntu follow a waterfall software development model of heavy testing and then a stable release with minor bug and security fixes as needed. On the contrary, Chef is under continuous development and improvement. The version of Chef in an LTS release will be severely out of date in a year. Providing individual bug patches (diffs) to this package would alone be very resource intensive, but major features will be missing which provides a large documentation issue. use the 'foobarblah' resource, except if you're on Ubuntu LTS, then do it this way, cannot be achieved across all our documentation, let alone the blogs and howto's of the internet. The latter will be improved when we provide versioned documentation. Under the Ubuntu release model, this will necessitate that the user upgrade their distribution whenever they want the latest version of Chef, which is problematic for people running services in a production environment. +b) Debian packages are the recommended installation method for Debian/Ubuntu, but using the Opscode apt repository due to the above issue. +c) The recommended installation method in the future will be our full-stack installer, to provide a stable version of ruby (missing in most distributions, probably due to Ruby's release paradigm) alongside the latest version of Chef in the simplest installation method possible. How software should be installed is a matter of personal preference for many, and Opscode aims to continue supporting distribution level and gem packaging for those who prefer it. + + [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=602697 + [2] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=620253 -- Getting Chef Back Into Ubuntu https://blueprints.launchpad.net/ubuntu/+spec/servercloud-q-chef -- 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
[Blueprint servercloud-q-chef] Getting Chef Back Into Ubuntu
Blueprint changed by Bryan McLellan: Whiteboard changed: Discussion Topics: What issues lead to the packages being removed from precise? - Fast Chef development cycle over the last two years made current stable branch 0.10.x while precise still had 0.8.16. - solr package became out of date and broken, which blocked chef-solr [1] - -- james-page: which version of solr is required to support re-entry - into the archive? is the current version sufficient or do we need to - move to 3.6 (and associated lucene 3.6 release)? I can help with either - scenario and solr 1.4 is not actually 'broken' - just a little - negelected. + -- james-page: which version of solr is required to support re-entry into the archive? is the current version sufficient or do we need to move to 3.6 (and associated lucene 3.6 release)? I can help with either scenario and solr 1.4 is not actually 'broken' - just a little negelected. + -- btm: broken was my summary of BTS #602697 [1] which justified pulling solr from debian squeeze. solr 1.4 should be fine, but we need to review the bugs against solr to ensure this won't happen again in the near future. How do we ensure that these don't re-occur to ensure the long term viability of chef as part of Ubuntu? - Maintaining chef in Debian will help with this. a) The debian pkg-ruby-extras team can use help, especially with the current transition - rails3 support in debian [2] for Chef 11 - Recommending users of Ubuntu and Debian to use the packages (instead of gem installing) will also help. a) The differing release paradigm makes this problematic. With a goal of stability, debian/ubuntu follow a waterfall software development model of heavy testing and then a stable release with minor bug and security fixes as needed. On the contrary, Chef is under continuous development and improvement. The version of Chef in an LTS release will be severely out of date in a year. Providing individual bug patches (diffs) to this package would alone be very resource intensive, but major features will be missing which provides a large documentation issue. use the 'foobarblah' resource, except if you're on Ubuntu LTS, then do it this way, cannot be achieved across all our documentation, let alone the blogs and howto's of the internet. The latter will be improved when we provide versioned documentation. Under the Ubuntu release model, this will necessitate that the user upgrade their distribution whenever they want the latest version of Chef, which is problematic for people running services in a production environment. b) Debian packages are the recommended installation method for Debian/Ubuntu, but using the Opscode apt repository due to the above issue. c) The recommended installation method in the future will be our full-stack installer, to provide a stable version of ruby (missing in most distributions, probably due to Ruby's release paradigm) alongside the latest version of Chef in the simplest installation method possible. How software should be installed is a matter of personal preference for many, and Opscode aims to continue supporting distribution level and gem packaging for those who prefer it. -- james-page: backports might help a bit - which is what currently happens with puppet. But we need to consider ruby version dependencies etc.. if we go down this route. -- james-page: can/did we generate/package documents as part of the package build process? Might help address the documentation concerns for the LTS version and any backports would get revised docs. [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=602697 [2] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=620253 -- Getting Chef Back Into Ubuntu https://blueprints.launchpad.net/ubuntu/+spec/servercloud-q-chef -- 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 579584] Re: setgid, setuid needed by /etc/apparmor.d/abstractions/libvirt-qemu
I don't think this bug hits me on Lucid until I give libvirt a different group for the sock files. It'd be interesting if others seeing this bug are changing this value as well. -- setgid, setuid needed by /etc/apparmor.d/abstractions/libvirt-qemu https://bugs.launchpad.net/bugs/579584 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt in ubuntu. -- 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 607466] Re: libvirt error starting domin: could not remove profile for
libvirt-bin=0.7.5-5ubuntu27 qemu-kvm=0.12.3+noroms-0ubuntu9.2 r...@iadvirt02:~# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 10.04.1 LTS Release:10.04 Codename: lucid r...@iadvirt02:~# uname -a Linux iadvirt02 2.6.32-24-generic #39-Ubuntu SMP Wed Jul 28 05:14:15 UTC 2010 x86_64 GNU/Linux r...@iadvirt02:~# virsh start iadoptdc02 error: Failed to start domain iadoptdc02 error: could not remove profile for 'libvirt-177bb534-7d9c-91ad-e6bf-89cd76d1e1bb' r...@iadvirt02:~# virsh dumpxml iadoptdc02 domain type='kvm' nameiadoptdc02/name uuid177bb534-7d9c-91ad-e6bf-89cd76d1e1bb/uuid memory1048576/memory currentMemory1048576/currentMemory vcpu2/vcpu os type arch='x86_64' machine='pc-0.12'hvm/type boot dev='hd'/ /os features acpi/ apic/ pae/ /features clock offset='localtime'/ on_poweroffdestroy/on_poweroff on_rebootrestart/on_reboot on_crashrestart/on_crash devices emulator/usr/bin/kvm/emulator disk type='file' device='disk' driver name='qemu' type='raw'/ source file='/var/lib/libvirt/images/iadoptdc02.img'/ target dev='hda' bus='ide'/ /disk interface type='bridge' mac address='52:54:00:09:71:b1'/ source bridge='br0.54'/ target dev='vnet0'/ model type='e1000'/ /interface console type='pty' target port='0'/ /console console type='pty' target port='0'/ /console input type='tablet' bus='usb'/ input type='mouse' bus='ps2'/ graphics type='vnc' port='-1' autoport='yes'/ video model type='cirrus' vram='9216' heads='1'/ /video /devices /domain r...@iadvirt02:~# virsh capabilities capabilities host cpu archx86_64/arch modelcore2duo/model topology sockets='4' cores='4' threads='1'/ feature name='lahf_lm'/ feature name='rdtscp'/ feature name='popcnt'/ feature name='dca'/ feature name='xtpr'/ feature name='cx16'/ feature name='tm2'/ feature name='est'/ feature name='vmx'/ feature name='ds_cpl'/ feature name='pbe'/ feature name='tm'/ feature name='ht'/ feature name='ss'/ feature name='acpi'/ feature name='ds'/ /cpu migration_features live/ uri_transports uri_transporttcp/uri_transport /uri_transports /migration_features secmodel modelapparmor/model doi0/doi /secmodel /host guest os_typehvm/os_type arch name='i686' wordsize32/wordsize emulator/usr/bin/qemu/emulator machinepc-0.12/machine machine canonical='pc-0.12'pc/machine machinepc-0.11/machine machinepc-0.10/machine machineisapc/machine domain type='qemu' /domain domain type='kvm' emulator/usr/bin/kvm/emulator machinepc-0.12/machine machine canonical='pc-0.12'pc/machine machinepc-0.11/machine machinepc-0.10/machine machineisapc/machine /domain /arch features cpuselection/ pae/ nonpae/ acpi default='on' toggle='yes'/ apic default='on' toggle='no'/ /features /guest guest os_typehvm/os_type arch name='x86_64' wordsize64/wordsize emulator/usr/bin/qemu-system-x86_64/emulator machinepc-0.12/machine machine canonical='pc-0.12'pc/machine machinepc-0.11/machine machinepc-0.10/machine machineisapc/machine domain type='qemu' /domain domain type='kvm' emulator/usr/bin/kvm/emulator machinepc-0.12/machine machine canonical='pc-0.12'pc/machine machinepc-0.11/machine machinepc-0.10/machine machineisapc/machine /domain /arch features cpuselection/ acpi default='on' toggle='yes'/ apic default='on' toggle='no'/ /features /guest /capabilities ** Changed in: libvirt (Ubuntu) Status: Incomplete = New -- libvirt error starting domin: could not remove profile for https://bugs.launchpad.net/bugs/607466 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt in ubuntu. -- 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 607466] Re: libvirt error starting domin: could not remove profile for
Actually, it does looks like an apparmor problem. Putting Apparmor in complain mode allows the domain to start, returning it to enforce brings back the original state. r...@iadvirt02:~# aa-complain /etc/apparmor.d/usr.sbin.libvirtd Setting /etc/apparmor.d/usr.sbin.libvirtd to complain mode. r...@iadvirt02:~# virsh start iadoptdc02 Domain iadoptdc02 started r...@iadvirt02:~# virsh destroy iadoptdc02 Domain iadoptdc02 destroyed r...@iadvirt02:~# aa-enforce /etc/apparmor.d/usr.sbin.libvirtd Setting /etc/apparmor.d/usr.sbin.libvirtd to enforce mode. r...@iadvirt02:~# virsh start iadoptdc02 error: Failed to start domain iadoptdc02 error: could not remove profile for 'libvirt-177bb534-7d9c-91ad-e6bf-89cd76d1e1bb' audit log: Aug 12 23:48:15 iadvirt02 kernel: [ 1658.487839] type=1505 audit(1281656895.909:705): operation=profile_replace pid=11447 name=/usr/sbin/libvirtd Aug 12 23:48:20 iadvirt02 kernel: [ 1663.423350] device vnet0 entered promiscuous mode Aug 12 23:48:20 iadvirt02 kernel: [ 1663.425192] br0.54: port 2(vnet0) entering forwarding state Aug 12 23:48:20 iadvirt02 kernel: [ 1663.426730] type=1502 audit(1281656900.859:706): operation=chown pid=11458 parent=1 profile=/usr/sbin/libvirtd//null-1a requested_mask=w:: denied_mask=w:: fsuid=0 ouid=0 name=/var/lib/libvirt/images/iadoptdc02.img Aug 12 23:48:20 iadvirt02 kernel: [ 1663.426743] type=1502 audit(1281656900.859:707): operation=capable pid=11458 parent=1 profile=/usr/sbin/libvirtd//null-1a name=chown Aug 12 23:48:20 iadvirt02 kernel: [ 1663.426854] type=1502 audit(1281656900.859:708): operation=open pid=11458 parent=1 profile=/usr/sbin/libvirtd//null-1a requested_mask=::r denied_mask=::r fsuid=116 ouid=0 name=/proc/11458/status Aug 12 23:48:20 iadvirt02 kernel: [ 1663.426996] type=1502 audit(1281656900.859:709): operation=exec pid=11458 parent=1 profile=/usr/sbin/libvirtd//null-1a requested_mask=::x denied_mask=::x fsuid=116 ouid=0 name=/usr/bin/qemu-system-x86_64 name2=/usr/sbin/libvirtd//null-1a//null-1b Aug 12 23:48:20 iadvirt02 kernel: [ 1663.427400] type=1502 audit(1281656900.859:710): operation=open pid=11458 parent=1 profile=/usr/sbin/libvirtd//null-1a//null-1b requested_mask=::r denied_mask=::r fsuid=116 ouid=0 name=/etc/ld.so.cache Aug 12 23:48:20 iadvirt02 kernel: [ 1663.427432] type=1502 audit(1281656900.859:711): operation=open pid=11458 parent=1 profile=/usr/sbin/libvirtd//null-1a//null-1b requested_mask=::r denied_mask=::r fsuid=116 ouid=0 name=/lib/librt-2.11.1.so Aug 12 23:48:20 iadvirt02 kernel: [ 1663.427451] type=1502 audit(1281656900.859:712): operation=file_mmap pid=11458 parent=1 profile=/usr/sbin/libvirtd//null-1a//null-1b requested_mask=::mr denied_mask=::mr fsuid=116 ouid=0 name=/lib/librt-2.11.1.so Aug 12 23:48:20 iadvirt02 kernel: [ 1663.427492] type=1502 audit(1281656900.859:713): operation=open pid=11458 parent=1 profile=/usr/sbin/libvirtd//null-1a//null-1b requested_mask=::r denied_mask=::r fsuid=116 ouid=0 name=/lib/libpthread-2.11.1.so Aug 12 23:48:20 iadvirt02 kernel: [ 1663.427507] type=1502 audit(1281656900.859:714): operation=file_mmap pid=11458 parent=1 profile=/usr/sbin/libvirtd//null-1a//null-1b requested_mask=::mr denied_mask=::mr fsuid=116 ouid=0 name=/lib/libpthread-2.11.1.so Aug 12 23:48:20 iadvirt02 kernel: [ 1663.427553] type=1502 audit(1281656900.859:715): operation=open pid=11458 parent=1 profile=/usr/sbin/libvirtd//null-1a//null-1b requested_mask=::r denied_mask=::r fsuid=116 ouid=0 name=/lib/libaio.so.1.0.1 -- libvirt error starting domin: could not remove profile for https://bugs.launchpad.net/bugs/607466 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt in ubuntu. -- 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 607466] Re: libvirt error starting domin: could not remove profile for
I'm not sure how this state gets created but: r...@iadvirt02:/etc/apparmor.d/libvirt# ls -l total 8 -rw-r--r-- 1 root root 265 2010-07-15 19:44 libvirt-177bb534-7d9c-91ad-e6bf-89cd76d1e1bb -rw-r--r-- 1 root root 164 2010-04-22 16:57 TEMPLATE r...@iadvirt02:/etc/apparmor.d/libvirt# virsh start iadoptdc02 error: Failed to start domain iadoptdc02 error: could not remove profile for 'libvirt-177bb534-7d9c-91ad-e6bf-89cd76d1e1bb' r...@iadvirt02:/etc/apparmor.d/libvirt# rm libvirt-177bb534-7d9c-91ad-e6bf-89cd76d1e1bb r...@iadvirt02:/etc/apparmor.d/libvirt# virsh start iadoptdc02 error: Failed to start domain iadoptdc02 error: could not remove profile for 'libvirt-177bb534-7d9c-91ad-e6bf-89cd76d1e1bb' r...@iadvirt02:/etc/apparmor.d/libvirt# ls TEMPLATE Apparently apparmor still knows about this profile, but I don't know where or how to flush it. -- libvirt error starting domin: could not remove profile for https://bugs.launchpad.net/bugs/607466 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt in ubuntu. -- 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 545302] Re: allow seabios in libvirt apparmor
I made the mistake of assuming that my issue couldn't have been apparmor related because I had executed '/etc/init.d/apparmor stop' to unload profiles to ensure it wasn't an apparmor problem. Apparently this wasn't true, as comment #3 made me go and try the apparmor rules anyway and this resolved the problem after an apparmor restart. -- allow seabios in libvirt apparmor https://bugs.launchpad.net/bugs/545302 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt in ubuntu. -- 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 607466] Re: libvirt error starting domin: could not remove profile for
Yes, although it's working at the moment. domain type='kvm' nameiadoptdc02/name uuid177bb534-7d9c-91ad-e6bf-89cd76d1e1bb/uuid memory1048576/memory currentMemory1048576/currentMemory vcpu2/vcpu os type arch='x86_64' machine='pc-0.12'hvm/type boot dev='hd'/ /os features acpi/ apic/ pae/ /features clock offset='localtime'/ on_poweroffdestroy/on_poweroff on_rebootrestart/on_reboot on_crashrestart/on_crash devices emulator/usr/bin/kvm/emulator disk type='file' device='disk' driver name='qemu' type='raw'/ source file='/var/lib/libvirt/images/iadoptdc02.img'/ target dev='hda' bus='ide'/ /disk interface type='bridge' mac address='52:54:00:09:71:b1'/ source bridge='br0.54'/ model type='e1000'/ /interface console type='pty' target port='0'/ /console console type='pty' target port='0'/ /console input type='tablet' bus='usb'/ input type='mouse' bus='ps2'/ graphics type='vnc' port='-1' autoport='yes'/ video model type='cirrus' vram='9216' heads='1'/ /video /devices /domain -- libvirt error starting domin: could not remove profile for https://bugs.launchpad.net/bugs/607466 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt in ubuntu. -- 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 607466] Re: libvirt error starting domin: could not remove profile for
1) stopped libvirt via the libvirt-bin init script 2) started 'libvirtd -v' manually hoping to see some debugging output 3) started the guest okay. 4) destroyed the guest 5) canceled the manual libvirt 6) started libvirt-bin again with the init script 7) started the guest okay. Note that AppArmor was off for this process, so the workaround was either: a) restarting libvirt b) restarting libvirt with apparmor off (would this matter?) c) started libvirt by hand (clearing something?) d) magic -- libvirt error starting domin: could not remove profile for https://bugs.launchpad.net/bugs/607466 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt in ubuntu. -- 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 462000] Re: apparmor disallows qemu+tcp:// connections
I had to run '/etc/init.d/apparmor reload' after upgrading to the packages in -proposed before libvirt would properly start. ** Attachment added: output of my upgrade session http://launchpadlibrarian.net/35806805/462000.notes -- apparmor disallows qemu+tcp:// connections https://bugs.launchpad.net/bugs/462000 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt in ubuntu. -- 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 484562] [NEW] apparmor prevents libvirt-vnc certificate from being read
Public bug reported: libvirt + kvm need to be able to read the certificates when using TLS to connect to VNC. Nov 17 17:08:09 lasvirt01 kernel: [69476.008895] type=1503 audit(1258506489.178:77): operation=open pid=17104 parent=1 profile =libvirt-600d5dae-6373-107e-5f1b-5010aff3ffed requested_mask=r:: denied_mask=r:: fsuid=0 ouid=0 name=/etc/pki/libvirt-vnc/ca-cert.pem libvirt 0.7.0-1ubuntu13.1 kvm 1:84+dfsg-0ubuntu16+0.11.0+0ubuntu6.3 apparmor 2.3.1+1403-0ubuntu27.2 Add /etc/pki/libvirt-vnc/** r, to /etc/apparmor.d/abstractions /libvirt-qemu ** Affects: libvirt (Ubuntu) Importance: Undecided Status: New -- apparmor prevents libvirt-vnc certificate from being read https://bugs.launchpad.net/bugs/484562 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt in ubuntu. -- 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 379991] Re: Certain VMs do not run under KVM using karmic's kernel
** Attachment added: cpuinfo on karmic w/linux-image-2.6.31-10-generic http://launchpadlibrarian.net/31986084/cpuinfo.379991.txt -- Certain VMs do not run under KVM using karmic's kernel https://bugs.launchpad.net/bugs/379991 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm in ubuntu. -- 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 379991] Re: Certain VMs do not run under KVM using 2.6.30-rc5 kernel
Confirmed on linux-image-2.6.31-9-generic with kvm=1:84+dfsg-0ubuntu16 + libvirt-bin=0.7.0-1ubuntu3 on karmic. WinXP would run through the install but not boot after the reboot. Same with Win7 Then running Win7 from the command line with '-cpu qemu32' allowed it to boot. -- Certain VMs do not run under KVM using 2.6.30-rc5 kernel https://bugs.launchpad.net/bugs/379991 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to kvm in ubuntu. -- 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
Re: [Bug 352841] Re: SCP over IPv6 address is very Slow. Takes Hours
On Fri, Apr 3, 2009 at 5:18 PM, Prasad Tadi pt...@roshitech.com wrote: However, when I run the command on local link (local machine's) , It completes and not even a single trace on tshark ip6 -i eth1 But when I traced on lo, it did show the data. Right, because you're using the local machines link local address. You need to use the local link address of the remote machine you want to copy the file to. I just built two hardy guests using python-vm-builder and ran them under KVM using bridging. I had no problems with sustained traffic ipv6 traffic between the two over scp using the link local addresses. tshark ip6 output on the originator No Errors 16.867469 fe80::250:56ff:fe8d:5c00 - fe80::250:56ff:fe8d:403c SSHv2 [TCP Retransmission] Encrypted request packet len=1428 Actually, that is indicative of an error. A retransmission occurs when the host sending the data doesn't get an acknowledgement that the remote host received the data, so it sends it again. Either the sending host isn't seeing them, or the receiving host isn't sending them. This can be caused by a network or hardware problem on either host or the equipment (or virtualized equipment) in between. On Mon, Apr 6, 2009 at 9:35 AM, Prasad Tadi pt...@roshitech.com wrote: Have a good news. I installed Jaunt (9.04) on a new VM and I could push the Large size files without any issues over IPv6. So it looks like OS/ Kernl level issue. Perhaps, glad it's working for you now though. -- SCP over IPv6 address is very Slow. Takes Hours https://bugs.launchpad.net/bugs/352841 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in ubuntu. -- 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
Re: [Bug 352841] Re: SCP over IPv6 address is very Slow. Takes Hours
On Thu, Apr 2, 2009 at 7:33 PM, Prasad Tadi pt...@roshitech.com wrote: My hardware is little more complicated, I will explain that below... But wants to make sure that I understood Local Link. Link Local is the ipv6 address assigned to the interface that starts with fe80:: [1] You don't have to configure these addresses, and hosts on the same physical network should be able to communicate using them. scp -6 disk0.qcow2 \[fe80::215:c5ff:fee3:f9cd%br0.4\]:/tmp When I copy from one Ubuntu to other Ubuntu server using IPv6, then only the issues shows up. You only see the performance problem when going from Ubuntu 8.04 to 8.04? Have you tried any combinations with other versions of Ubuntu? [1] http://en.wikipedia.org/wiki/IPv6#Link- local_addresses_and_zone_indices -- SCP over IPv6 address is very Slow. Takes Hours https://bugs.launchpad.net/bugs/352841 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in ubuntu. -- 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
Re: [Bug 351378] Re: dhclient fails for virtual interfaces (IP aliases)
On Thu, Apr 2, 2009 at 11:20 PM, Tom Metro tmetro+ubu...@gmail.com wrote: That may be partly right. I see /sbin/dhclient-script contains the comment: # The alias handling in here probably still sucks. -mdz and there's clearly evidence that it is attempting to support virtual interfaces: if [ -n $alias_ip_address ]; then dhclient-script(8) says If an IP alias has been declared in dhclient.conf, its address will be passed in $alias_ip_address, and that ip alias should be deleted from the interface, along with any routes to it. Most likely that comment and surely that code is to support the inclusion of an alias definition in your dhclient.conf(5), as opposed to running dhclient on an alias interface. If you don't use this script, those errors go away. But is that a practical option? Doesn't the script provide a pile of needed glue? Patching the script seems more viable. The script does provide a lot of glue, but working around it as a debugging technique isolates what errors are coming from the script and what errors are coming from the program itself. I don't believe patching the script will do you any good until the 'Bind socket to interface: No such device' error from dhclient is resolved, because it appears to be unable to use the interface to send the DHCP request. I did test and confirm that dhcpcd=1:3.2.3-1.1 does work on alias interfaces on intrepid. Is it a drop-in replacement that works with the rest of the existing infrastructure in Ubuntu, like /etc/network/interfaces? Removing dhcp3-client (which removed ubuntu-minimal) and installing dhcpcd worked just fine with /etc/network/interfaces on a test vm for me about five minutes ago, and thus appears like a clean enough work around. -- dhclient fails for virtual interfaces (IP aliases) https://bugs.launchpad.net/bugs/351378 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dhcp3 in ubuntu. -- 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
Re: [Bug 352841] Re: SCP over IPv6 address is very Slow. Takes Hours
On Fri, Apr 3, 2009 at 12:23 PM, Prasad Tadi pt...@roshitech.com wrote: I am not really an expert, but I think the Local link may use Loop back Link-local is the fe80 addresses that refer to devices on a particular data link, such as a single Ethernet network, or a point-to-point serial connection. If you're using your own link-local address, then yes, that traffic will - I believe - traverse the loopback interface. This is not correct. If you read the link I provided earlier it starts with All interfaces have an associated link-local address. Loopback is it's own interface (lo) and is independent of your ethN interfaces. The loopback interface also has it's own inet6 address (ifconfig lo0 | grep inet6) in the specified ipv6 loopback address range. eth1 Link encap:Ethernet HWaddr 00:50:56:b5:52:c1 inet6 addr: fdf8:c879:493e:1:250:56ff:feb5:52c1/64 Scope:Global inet6 addr: fe80::250:56ff:feb5:52c1/64 Scope:Link The second address, that starts with fe80::, and additionally says Scope: Link is the Link Local address. This is because this address is for the local link only. Try copying between two hosts using these address with Scope:Link to rule out any addressing problems. Because these are local addresses, you may need to specify the interface you want scp to use by adding '%interface' to the end of the address, such as: scp -6 desktone.tar [fdf8:c879:493e:1:250:56ff:feb5:52c1%eth1]:/tmp It may be helpful to run 'sudo tshark ip6' on the originating host while copying the file to look for any network errors. -- SCP over IPv6 address is very Slow. Takes Hours https://bugs.launchpad.net/bugs/352841 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in ubuntu. -- 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
Re: [Bug 351378] Re: dhclient fails for virtual interfaces (IP aliases)
On Fri, Apr 3, 2009 at 1:20 PM, Tom Metro tmetro+ubu...@gmail.com wrote:
Removing ubuntu-minimal sounds like something to be avoided, but there
was mention of people doing that (as a side effect of removing the
wireless package) in the bug this one was split off from, and it didn't
sound like it caused any problems. I'll have to take a look at
ubuntu-minimal to see what it is.
It's a meta package, like installing 'ubuntu-desktop' will install all
of the packages you need for a standard Ubuntu desktop, -minimal will
give you a basic system. Uninstalling it would mean that in the future
if another package was added to to the meta package, you wouldn't get
that additional package on upgrade. You can run 'dpkg-query -f
'${Depends}\n' -W ubuntu-minimal' to see the packages that it
installs. You could also remove the dhcp3-client package with
--force-depends, which just runs the risk that it gets reinstalled
later during an upgrade. There's probably a complex pinning solution
too, but I can't fathom it.
Excellent. Thanks for the suggested workaround. Care to post the
/etc/network/interfaces syntax you used for the virtual interface? (In
my research I ran across about 3 or 4 variations.)
auto eth0
iface eth0 inet dhcp
auto eth0:0
iface eth0:0 inet dhcp
--
dhclient fails for virtual interfaces (IP aliases)
https://bugs.launchpad.net/bugs/351378
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dhcp3 in ubuntu.
--
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 351378] Re: dhclient fails for virtual interfaces (IP aliases)
SIOCSIFFLAGS: Cannot assign requested address SIOCSIFFLAGS: Cannot assign requested address These two errors are because dhclient-script does not support alias interfaces. If you don't use this script, those errors go away. However it's likely dhclient doesn't support alias interfaces at all, a different dhcp client may the solution. # dhclient eth0:0 -sf /bin/true Internet Systems Consortium DHCP Client V3.1.1 Copyright 2004-2008 Internet Systems Consortium. All rights reserved. For info, please visit http://www.isc.org/sw/dhcp/ Bind socket to interface: No such device ** Changed in: dhcp3 (Ubuntu) Status: New = Confirmed -- dhclient fails for virtual interfaces (IP aliases) https://bugs.launchpad.net/bugs/351378 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dhcp3 in ubuntu. -- 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 352841] Re: SCP over IPv6 address is very Slow. Takes Hours
Using only linklocal addresses I've sustained near 40MB/s copying a 10GB file in the following patterns: Ubuntu 8.10 - Ubuntu 9.04 Debian 4.0 - Ubuntu 9.04 Ubuntu 9.04 - Ubuntu 8.10 It seems more likely that your problem would be a hardware issue. Have you tried connecting the two Ubuntu machines directly together to rule out any network equipment between the two? Have you tried to copy from your FreeBSD machine to more than one Ubuntu server to rule out a problem with that installation or hardware? Any other testing that could possibly narrow it down? Thanks! -- SCP over IPv6 address is very Slow. Takes Hours https://bugs.launchpad.net/bugs/352841 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in ubuntu. -- 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 333481] Re: dhcp client can't receive an ip address
I noticed in your lspci output that your Realtek network chipset isn't being detected completely and looked very similar to the comments in Bug 240470, particular this comment [1]. Please make sure that the BIOS on your system has the latest firmware upgrade applied. [1] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/240470/comments/12 -- dhcp client can't receive an ip address https://bugs.launchpad.net/bugs/333481 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dhcp3 in ubuntu. -- 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 306693] Re: open-iscsi upgrade fails to stop iscsid
*** This bug is a duplicate of bug 306678 *** https://bugs.launchpad.net/bugs/306678 #306678 is a problem with the update-rc.d line triggered by an upgrade in the postinst script. If this is a duplicate of anything, I think it's #181188, which resolves iscsid not stopping correctly. However the fix for this bug requires an upgrade and the upgrade path is not clean due to what I've reported in this bug. -- open-iscsi upgrade fails to stop iscsid https://bugs.launchpad.net/bugs/306693 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to open-iscsi in ubuntu. -- 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 306678] [NEW] open-iscsi fails to correctly update rc.d on upgrade
Public bug reported: Binary package hint: open-iscsi When upgrading open-iscsi from 2.0.865-1ubuntu4 to 2.0.870.1-0ubuntu1 it attempts to run: update-rc.d -f remove open-iscsi This fails, as it should be: update-rc.d -f open-iscsi remove Line 58 of open-iscsi.postinst # uname -a Linux file01 2.6.27-10-generic #1 SMP Fri Nov 21 12:00:22 UTC 2008 i686 GNU/Linux # lsb_release -a LSB Version: core-2.0-ia32:core-2.0-noarch:core-3.0-ia32:core-3.0-noarch:core-3.1-ia32:core-3.1-noarch:core-3.2-ia32:core-3.2-noarch Distributor ID: Ubuntu Description:Ubuntu 8.10 Release:8.10 Codename: intrepid ** Affects: open-iscsi (Ubuntu) Importance: Undecided Status: New -- open-iscsi fails to correctly update rc.d on upgrade https://bugs.launchpad.net/bugs/306678 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to open-iscsi in ubuntu. -- 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 306693] [NEW] open-iscsi upgrade fails to stop iscsid
Public bug reported: Binary package hint: open-iscsi On an upgrade from open-iscsi=2.0.865-1ubuntu4 to open- iscsi=2.0.870.1-0ubuntu1, the postrm script for 2.0.865-1ubuntu4 stops iscsid via the initscript, which fails to to all iscsid processes. When apt then tries to run the postinstall script, the init script for open- iscsi fails to start due to the existing process. Work around is to forcibly kill the iscsid processes before upgrade: [EMAIL PROTECTED]:/etc/init.d# apt-get install open-iscsi=2.0.870.1-0ubuntu1 Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: aspell-en ispell ibritish cupsys-common aspell g++-4.2 qstat nagios-plugins-extra libck-connector0 cups-common openssh-blacklist fping libstdc++6-4.2-dev libtiff4 libjpeg62 libcupsimage2 libcupsys2 iamerican libaspell15 Use 'apt-get autoremove' to remove them. The following packages will be upgraded: open-iscsi 1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Need to get 0B/572kB of archives. After this operation, 950kB of additional disk space will be used. (Reading database ... 56874 files and directories currently installed.) Preparing to replace open-iscsi 2.0.865-1ubuntu4 (using .../open-iscsi_2.0.870.1-0ubuntu1_i386.deb) ... * Disconnecting iSCSI targets [ OK ] * Stopping iSCSI initiator service [ OK ] Unpacking replacement open-iscsi ... Processing triggers for man-db ... Setting up open-iscsi (2.0.870.1-0ubuntu1) ... Installing new version of config file /etc/init.d/open-iscsi ... Installing new version of config file /etc/iscsi/iscsid.conf ... update-rc.d: /etc/init.d/remove: file does not exist * Starting iSCSI initiator service iscsid [fail] * Setting up iSCSI targets [ OK ] invoke-rc.d: initscript open-iscsi, action start failed. dpkg: error processing open-iscsi (--configure): subprocess post-installation script returned error exit status 1 Errors were encountered while processing: open-iscsi E: Sub-process /usr/bin/dpkg returned an error code (1) [EMAIL PROTECTED]:/etc/init.d# killall -9 iscsid [EMAIL PROTECTED]:/etc/init.d# apt-get install open-iscsi=2.0.870.1-0ubuntu1 Reading package lists... Done Building dependency tree Reading state information... Done open-iscsi is already the newest version. The following packages were automatically installed and are no longer required: aspell-en ispell ibritish cupsys-common aspell g++-4.2 qstat nagios-plugins-extra libck-connector0 cups-common openssh-blacklist fping libstdc++6-4.2-dev libtiff4 libjpeg62 libcupsimage2 libcupsys2 iamerican libaspell15 Use 'apt-get autoremove' to remove them. 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 1 not fully installed or removed. After this operation, 0B of additional disk space will be used. Setting up open-iscsi (2.0.870.1-0ubuntu1) ... update-rc.d: /etc/init.d/remove: file does not exist * Starting iSCSI initiator service iscsid [ OK ] ln: creating symbolic link `/lib/init/rw/sendsigs.omit.d/iscsid.pid': File exists * Setting up iSCSI targets [ OK ] # uname -a Linux file01 2.6.27-10-generic #1 SMP Fri Nov 21 12:00:22 UTC 2008 i686 GNU/Linux # lsb_release -a LSB Version: core-2.0-ia32:core-2.0-noarch:core-3.0-ia32:core-3.0-noarch:core-3.1-ia32:core-3.1-noarch:core-3.2-ia32:core-3.2-noarch Distributor ID: Ubuntu Description:Ubuntu 8.10 Release:8.10 ** Affects: open-iscsi (Ubuntu) Importance: Undecided Status: New -- open-iscsi upgrade fails to stop iscsid https://bugs.launchpad.net/bugs/306693 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to open-iscsi in ubuntu. -- 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 301898] [NEW] slaptest conversion does not configure monitor module
Public bug reported:
The intrepid package defaults to using -F and /etc/ldap/slapd.d. The
postinst file uses slaptest to try to convert existing configurations to
the newer directory format, however this does not configure the monitor
backend module.
a 'olcDatabase={1}monitor.ldif' file is produced in /etc/ldap/slapd.d,
but not the expected 'cn=module{1}.ldif'
This is particularly troubling as openldap still lacks the proper
documentation for configuring monitoring using the new configuration
layout:
http://www.openldap.org/doc/admin24/guide.html#Monitoring
** Affects: openldap (Ubuntu)
Importance: Undecided
Status: New
--
slaptest conversion does not configure monitor module
https://bugs.launchpad.net/bugs/301898
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openldap in ubuntu.
--
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 301898] Re: slaptest conversion does not configure monitor module
mkdir -p /tmp/slap/slapd.d
# save attached config to /tmp/slap
slaptest -f /tmp/slap/slapd.conf -F /tmp/slap/slapd.d
# works
# Edit /tmp/slapd/slapd.d/cn=config/cn=module{0}.ldif and remove
olcModuleLoad: {1}back_monitor
slaptest -f /tmp/slap/slapd.conf -F /tmp/slap/slapd.d
# does not work, will not modify existing file
** Attachment added: slapd.conf with monitor configuration
http://launchpadlibrarian.net/19918749/slapd.conf
--
slaptest conversion does not configure monitor module
https://bugs.launchpad.net/bugs/301898
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openldap in ubuntu.
--
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
