[Bug 651691] Re: Please merge minicom 2.4-4 (universe) from Debian unstable (main)
2.5-2 is in precise. ** Changed in: minicom (Ubuntu) Status: Confirmed = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to minicom in Ubuntu. https://bugs.launchpad.net/bugs/651691 Title: Please merge minicom 2.4-4 (universe) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/minicom/+bug/651691/+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 938485] Re: No keystrokes are sent - no outgoing serial
I seem to be getting this issue as well (on a US Robotics external USB modem). Then I did: sudo apt-get remove modemmanager After that I could start up minicom and enter modem commands (AT$, etc.) ok. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to minicom in Ubuntu. https://bugs.launchpad.net/bugs/938485 Title: No keystrokes are sent - no outgoing serial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/minicom/+bug/938485/+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 1045845] Re: 12.10 guest crash on login when using 12.04 qemu-kvm with cirrus driver
The stack trace matches the trace for bug #1043513. Probably dupes. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1045845 Title: 12.10 guest crash on login when using 12.04 qemu-kvm with cirrus driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1045845/+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 1044318] Re: [SRU] pre-1.5 OVS has trouble with floating ips when pinging from the same box
** Description changed: - Note: OVS from before 1.5, which includes the default versions shipped - with 12.04 and Fedora 17, has a bug that causes it not to work correctly - with floating IPs when the person contacting the floating IP is on the - same box as quantum-l3-agent. + [Impact] + The connection tracking logic using by IPtables gets confused if a packet passes through multiple linux network namespaces on the same host. The reason for this confusion is that OVS is not properly clearing some of the fields in the skb header, meaning the connection tracking ignores this packet, so iptables functionality that relies on this (in particular DNAT and SNAT) do not work. + + In particular, the use of OVS by OpenStack Quantum is critically + affected by this bug. + + [Fix] + The issue has been fixed upstream as of 1.4.3. A minimal 5-liner that clears the appropriate metadata from the skb header. The patch has been cherry-picked and fix released in the current Ubuntu dev. release (12.10). + + [Test Case] + 1. Create external network 40.0.0.0/24 for floating IPs + 2. Assign br-ex the IP 40.0.0.1 + 3. Pinging 40.0.0.1 appears to work, but you're pinging the router, not the VM + 4. Network connectivity to the VM with the floating IP does not work, as expected. + + [Regression Potential] + Minimal. Simple patch that has been cherry-picked from the current upstream stable release of Openvswitch (1.4.3). + + [Original Report] + Note: OVS from before 1.5, which includes the default versions shipped with 12.04 and Fedora 17, has a bug that causes it not to work correctly with floating IPs when the person contacting the floating IP is on the same box as quantum-l3-agent. While not very likely to happen in a production setup, this is fairly common in simple development environments. For example, let's say you create an external network 40.0.0.0/24 for floating IPs. If you then assign br-ex the IP 40.0.0.1, you should be able to reach all of your VMs with floating IPs, but it won't work because of this bug. Oddly, it - will often appear to work if you use ping, but in reality you are pining - the IP address in the router namespace, not the VM. + will often appear to work if you use ping, but in reality you are + pinging the IP address in the router namespace, not the VM. We believe the following OVS commit it required for this to work properly: http://openvswitch.org/cgi- bin/gitweb.cgi?p=openvswitch;a=commitdiff;h=53e6421bc83918ac2d00ba5516f205fa7e394140 We are looking at creating a new stable release on the 1.4.x branch to include this change and plan to work with distros to get it pulled into their packages. - - [IMPACT] - The connection tracking logic using by IPtables gets confused if a packet passes through multiple linux network namespaces on the same host. The reason for this confusion is that OVS is not properly clearing some of the fields in the skb header, meaning the connection tracking ignores this packet, so iptables functionality that relies on this (in particular DNAT and SNAT) do not work. - - In particular, the use of OVS by OpenStack Quantum is critically - affected by this bug. - - [FIX] - The issue has been fixed upstream as of 1.4.3. A minimal 5-liner that clears the appropriate metadata from the skb header. The patch has been cherry-picked and fix released in the current Ubuntu dev. release (12.10). - - [REGRESSION POTENTIAL] - Minimal. Simple patch that has been cherry-picked from the currentl upstream stable release of Openvswitch (1.4.3). ** Changed in: openvswitch (Ubuntu Precise) Status: Confirmed = Triaged ** Changed in: openvswitch (Ubuntu Precise) Importance: Undecided = Medium -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openvswitch in Ubuntu. https://bugs.launchpad.net/bugs/1044318 Title: [SRU] pre-1.5 OVS has trouble with floating ips when pinging from the same box To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1044318/+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 1048787] Re: slapd gives assertions for valid configuration
** Description changed: - The slapd version in Ubuntu precise (2.4.28-1.1ubuntu4.1) suffers from - the same issue that was reported in debian BTS for the debian version - 2.4.28-1.1. + [Impact] + + [Fix] + + [Test Case] + + [Regression Potential] + + [Original Report] + The slapd version in Ubuntu precise (2.4.28-1.1ubuntu4.1) suffers from the same issue that was reported in debian BTS for the debian version 2.4.28-1.1. When configuring the shell backend in slapd.conf the syntax is (see man slapd-shell): add pathname argument... bind pathname argument... compare pathname argument... and so on. That is the path to the script followed by its arguments. This has worked fine in the past. However, the current version 2.4.28-1.1 of the slapd server refuses to start if any arguments are given after the path name in the configuration file, with the following assertion: slapd: ../../../../servers/slapd/config.c:198: config_check_vals: Assertion `c-argc == 2' failed. For the configuration of the shell backend the assertion condition means that it is not possible to pass arguments to the script in the slapd.conf. The man pages documents that this should still be possible, and it has been working with earlier versions. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/1048787 Title: slapd gives assertions for valid configuration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1048787/+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 1050559] Re: Sync cyrus-sasl2 2.1.25.dfsg1-5 (main) from Debian unstable (main)
Hi Logan, would you mind summarizing what the Ubuntu-relevant fixes/changes are for this package, to make sponsoring easier? ** Changed in: cyrus-sasl2 (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cyrus-sasl2 in Ubuntu. https://bugs.launchpad.net/bugs/1050559 Title: Sync cyrus-sasl2 2.1.25.dfsg1-5 (main) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cyrus-sasl2/+bug/1050559/+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 1045845] Re: 12.10 guest crash on login when using 12.04 qemu-kvm with cirrus driver
Please collect a full backtrace on this crash - see http://wiki.ubuntu.com/X/Backtracing for guidance. ** Description changed: On a 12.10 amd64 host with the 12.04 LTS qemu-kvm package (due to bug #1040033) using the cirrus (ie, the default qemu-kvm driver) with an up to date 12.10 guest (machine='pc-1.0'), lightdm starts fine. If I proceed to login, X crashes. If I upgrade qemu-kvm to 1.1~rc+dfsg- 1ubuntu10, I am able to login fine. I don't know why the crash file wasn't uploaded. That said, this happens every time and is easy to reproduce. + + (EE) BUG: triggered 'if (inSignalContext)' + (EE) BUG: ../../os/log.c:472 in LogVMessageVerb() + (EE) Warning: attempting to log data in a signal unsafe manner while in signal context. Please update to check inSignalContext and/or use LogMessageVerbSigSafe() or ErrorFSigSafe(). The offending log format message is: + VMWARE(0): vmmouse enable absolute mode + + (EE) + (EE) Backtrace: + (EE) 0: /usr/bin/X (xorg_backtrace+0x36) [0x7f98382b88c6] + (EE) 1: /usr/bin/X (LogVMessageVerb+0x8c) [0x7f98382c3acc] + (EE) 2: /usr/bin/X (xf86Msg+0x8f) [0x7f98381b034f] + (EE) 3: /usr/lib/xorg/modules/input/vmmouse_drv.so (0x7f9834521000+0x191f) [0x7f983452291f] + (EE) 4: /usr/bin/X (0x7f983811+0x93637) [0x7f98381a3637] + (EE) 5: /usr/bin/X (0x7f983811+0xbcca8) [0x7f98381ccca8] + (EE) 6: /lib/x86_64-linux-gnu/libpthread.so.0 (0x7f9837436000+0xfcb0) [0x7f9837445cb0] + (EE) 7: /lib/x86_64-linux-gnu/libc.so.6 (__select+0x13) [0x7f98361876e3] + (EE) 8: /usr/bin/X (WaitForSomething+0x190) [0x7f98382b5cf0] + (EE) 9: /usr/bin/X (0x7f983811+0x55791) [0x7f9838165791] + (EE) 10: /usr/bin/X (0x7f983811+0x4455a) [0x7f983815455a] + (EE) 11: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xed) [0x7f98360bd76d] + (EE) 12: /usr/bin/X (0x7f983811+0x4489d) [0x7f983815489d] + (EE) + [17.571] (II) XKB: reuse xkmfile /var/lib/xkb/server-B2FC13ED4E00C26DC4C5E2885151412D28B2D8F8.xkm + [19.355] (EE) + [19.355] (EE) Backtrace: + [19.355] (EE) 0: /usr/bin/X (xorg_backtrace+0x36) [0x7f98382b88c6] + [19.356] (EE) 1: /usr/bin/X (0x7f983811+0x1ac6f9) [0x7f98382bc6f9] + [19.356] (EE) 2: /lib/x86_64-linux-gnu/libpthread.so.0 (0x7f9837436000+0xfcb0) [0x7f9837445cb0] + [19.356] (EE) 3: /lib/x86_64-linux-gnu/libc.so.6 (0x7f983609c000+0x911ae) [0x7f983612d1ae] + [19.356] (EE) 4: /usr/lib/xorg/modules/drivers/cirrus_drv.so (cirRefreshArea+0xbe) [0x7f9834f45ebe] + [19.356] (EE) 5: /usr/lib/xorg/modules/libshadowfb.so (0x7f9833cc7000+0x3af3) [0x7f9833ccaaf3] + [19.356] (EE) 6: /usr/bin/X (0x7f983811+0x519fb) [0x7f98381619fb] + [19.356] (EE) 7: /usr/bin/X (0x7f983811+0x55a41) [0x7f9838165a41] + [19.356] (EE) 8: /usr/bin/X (0x7f983811+0x4455a) [0x7f983815455a] + [19.356] (EE) 9: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xed) [0x7f98360bd76d] + [19.356] (EE) 10: /usr/bin/X (0x7f983811+0x4489d) [0x7f983815489d] + [19.356] (EE) + [19.356] (EE) Segmentation fault at address 0x7f9834cb7ee4 + [19.356] + Fatal server error: + [19.356] Caught signal 11 (Segmentation fault). Server aborting + ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xorg 1:7.7+1ubuntu3 ProcVersionSignature: User Name 3.5.0-13.14-generic 3.5.3 Uname: Linux 3.5.0-13-generic x86_64 ApportVersion: 2.5.1-0ubuntu4 Architecture: amd64 CurrentDmesg: [3.509976] init: plymouth-upstart-bridge main process (467) killed by TERM signal Date: Tue Sep 4 09:20:41 2012 DistUpgraded: Fresh install DistroCodename: quantal DistroVariant: ubuntu GraphicsCard: Cirrus Logic GD 5446 [1013:00b8] (prog-if 00 [VGA controller]) Subsystem: Red Hat, Inc Device [1af4:1100] InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Alpha amd64 (20120727.1) Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: Bochs Bochs ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-13-generic root=UUID=864d1ea6-19be-4372-9f05-94f7633a6f7c ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/01/2007 dmi.bios.vendor: Bochs dmi.bios.version: Bochs dmi.chassis.type: 1 dmi.chassis.vendor: Bochs dmi.modalias: dmi:bvnBochs:bvrBochs:bd01/01/2007:svnBochs:pnBochs:pvr:cvnBochs:ct1:cvr: dmi.product.name: Bochs dmi.sys.vendor: Bochs version.compiz: compiz 1:0.9.8.0-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.38-0ubuntu2 version.libgl1-mesa-dri: libgl1-mesa-dri 9.0~git20120821.c1114c61-0ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.0~git20120821.c1114c61-0ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.12.99.905-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati
[Bug 1006738] Re: php5-fpm segfaults with error 4 in libc-2.15.so
** Description changed: + [Impact] + + [Fix] + + [Test Case] + + [Regression Potential] + + [Original Report] + On Ubuntu Server 12.04 on amd64 (Intel Xeon E5620 CPU) php5-fpm randomly crashes with the following message: May 29 06:38:25 srv2 kernel: [315922.148835] php5-fpm[20902]: segfault at 0 ip 7fecd9032558 sp 7fff18136898 error 4 in libc-2.15.so[7fecd8f0+1b3000] May 29 06:38:25 srv2 kernel: [315922.148849] php5-fpm/20902: potentially unexpected fatal signal 11. - May 29 06:38:25 srv2 kernel: [315922.148851] - May 29 06:38:25 srv2 kernel: [315922.148853] CPU 7 + May 29 06:38:25 srv2 kernel: [315922.148851] + May 29 06:38:25 srv2 kernel: [315922.148853] CPU 7 May 29 06:38:25 srv2 kernel: [315922.148854] Modules linked in: vesafb psmouse i7core_edac edac_core ioatdma dca serio_raw joydev mac_hid lp parport usbhid hid e1000e megaraid_sas - May 29 06:38:25 srv2 kernel: [315922.148870] + May 29 06:38:25 srv2 kernel: [315922.148870] May 29 06:38:25 srv2 kernel: [315922.148873] Pid: 20902, comm: php5-fpm Not tainted 3.2.0-24-generic #39-Ubuntu Supermicro X8DTT-H/X8DTT-H May 29 06:38:25 srv2 kernel: [315922.148878] RIP: 0033:[7fecd9032558] [7fecd9032558] 0x7fecd9032557 May 29 06:38:25 srv2 kernel: [315922.148884] RSP: 002b:7fff18136898 EFLAGS: 00010206 May 29 06:38:25 srv2 kernel: [315922.148887] RAX: RBX: 7fecdb38b000 RCX: 0011 May 29 06:38:25 srv2 kernel: [315922.148890] RDX: 0066 RSI: 00af8af5 RDI: May 29 06:38:25 srv2 kernel: [315922.148892] RBP: 023cc228 R08: 0011 R09: May 29 06:38:25 srv2 kernel: [315922.148895] R10: 7fecd9035750 R11: 7fecd9081710 R12: 0001 May 29 06:38:25 srv2 kernel: [315922.148897] R13: R14: R15: 023cc2f0 May 29 06:38:25 srv2 kernel: [315922.148901] FS: 7fecdb382700() GS:8803332e() knlGS: May 29 06:38:25 srv2 kernel: [315922.148904] CS: 0010 DS: ES: CR0: 80050033 May 29 06:38:25 srv2 kernel: [315922.148906] CR2: CR3: 000327434000 CR4: 06e0 May 29 06:38:25 srv2 kernel: [315922.148909] DR0: DR1: DR2: May 29 06:38:25 srv2 kernel: [315922.148912] DR3: DR6: 0ff0 DR7: 0400 May 29 06:38:25 srv2 kernel: [315922.148915] Process php5-fpm (pid: 20902, threadinfo 88032aeec000, task 88032aa55bc0) - May 29 06:38:25 srv2 kernel: [315922.148917] + May 29 06:38:25 srv2 kernel: [315922.148917] May 29 06:38:25 srv2 kernel: [315922.148919] Call Trace: GDB information: Core was generated by `php-fpm: pool mypool '. Program terminated with signal 11, Segmentation fault. #0 __strstr_sse42 (s1=0x0, s2=optimized out) at ../sysdeps/x86_64/multiarch/strstr.c:175 175 ../sysdeps/x86_64/multiarch/strstr.c: No such file or directory. (gdb) bt #0 __strstr_sse42 (s1=0x0, s2=optimized out) at ../sysdeps/x86_64/multiarch/strstr.c:175 #1 0x00736d13 in fpm_status_handle_request () at /build/buildd/php5-5.3.10/sapi/fpm/fpm/fpm_status.c:128 #2 0x0042b4ab in main (argc=11237155, argv=0x0) at /build/buildd/php5-5.3.10/sapi/fpm/fpm/fpm_main.c:1809 - - # uname -a + # uname -a Linux srv2 3.2.0-24-generic #39-Ubuntu SMP Mon May 21 16:52:17 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux # dpkg -l |grep php ii php-apc 3.1.7-1APC (Alternative PHP Cache) module for PHP 5 ii php5-cli5.3.10-1ubuntu3.1 command-line interpreter for the php5 scripting language ii php5-common 5.3.10-1ubuntu3.1 Common files for packages built from the php5 source ii php5-curl 5.3.10-1ubuntu3.1 CURL module for php5 ii php5-dbg5.3.10-1ubuntu3.1 Debug symbols for PHP5 ii php5-fpm5.3.10-1ubuntu3.1 server-side, HTML-embedded scripting language (FPM-CGI binary) ii php5-gd 5.3.10-1ubuntu3.1 GD module for php5 ii php5-mcrypt 5.3.5-0ubuntu1 MCrypt module for php5 ii php5-memcache 3.0.6-1memcache extension module for PHP5 ii php5-mysql 5.3.10-1ubuntu3.1 MySQL module for php5 The crash occurs several times per hour and is repeatable on two different servers with the same software versions. -- 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/1006738 Title: php5-fpm segfaults with error 4 in libc-2.15.so To manage notifications about this bug go
[Bug 671065] Re: deliver broken because dovecot.conf uses !include_try
Unsubscribing sponsors for now; re-subscribe when clint's questions are addressed. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dovecot in Ubuntu. https://bugs.launchpad.net/bugs/671065 Title: deliver broken because dovecot.conf uses !include_try To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dovecot/+bug/671065/+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 994752] Re: lxc-start-ephemeral's use of dhcp lease table is fragile
It appears the package was already uploaded to quantal (#6) and precise (#4) so I take it there's no sponsorship work needed here. -- 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/994752 Title: lxc-start-ephemeral's use of dhcp lease table is fragile To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/994752/+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 998403] Re: ntp in precise has disabled crypto
** Description changed: - Hey, + [Impact] + fill me in with explanation of severity and frequency of bug on users and justification for backporting the fix to the stable release + + [Development Fix] + fill me in with an explanation of how the bug has been addressed in the development branch, including the relevant version numbers of packages modified in order to implement the fix. + + [Stable Fix] + fill me in by pointing out a minimal patch applicable to the stable version of the package. + + [Text Case] + fill me in with detailed *instructions* on how to reproduce the bug. This will be used by people later on to verify the updated package fixes the problem. + 1. + 2. + 3. + Broken Behavior: + Fixed Behavior: + + [Regression Potential] + fill me in with a discussion of likelihood and potential severity of regressions and how users could get inadvertently affected. + + [Original Report]Hey, this is the exact same bug as Debian's #670662 and #671626 but as it affects a stable (LTS) release I thought I would report it too, in case it can be fixed before the next release. Basically a multi-arch change in OpenSSL package disabled the crypto part in ntp, meaning it's not possible anymore to use some kind of protection, wether on the client part or the server part. I'm unsure about tagging it security since it's not really a vulnerability by itself, but you see the point. Attached patch should fix the problem, but the Debian maintainer tagged the bug “pending” so you might want to wait for his fix. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/998403 Title: ntp in precise has disabled crypto To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/998403/+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 994752] Re: lxc-start-ephemeral's use of dhcp lease table is fragile
** Description changed: - When lxc-start-ephemeral is given a command to run (-- do_something) it - wants to use lxc-attach to run the command, but lxc-attach is not ready - yet. Instead, it parses the dhcp leases to figure out the IP for the - container, and then tries to use ssh to run the command. + [Impact] + fill me in with explanation of severity and frequency of bug on users and justification for backporting the fix to the stable release + + [Development Fix] + fill me in with an explanation of how the bug has been addressed in the development branch, including the relevant version numbers of packages modified in order to implement the fix. + + [Stable Fix] + fill me in by pointing out a minimal patch applicable to the stable version of the package. + + [Text Case] + fill me in with detailed *instructions* on how to reproduce the bug. This will be used by people later on to verify the updated package fixes the problem. + 1. + 2. + 3. + Broken Behavior: + Fixed Behavior: + + [Regression Potential] + fill me in with a discussion of likelihood and potential severity of regressions and how users could get inadvertently affected. + + [Original Report]When lxc-start-ephemeral is given a command to run (-- + do_something) it wants to use lxc-attach to run the command, but lxc- + attach is not ready yet. Instead, it parses the dhcp leases to figure + out the IP for the container, and then tries to use ssh to run the + command. Twice today in tests involving lxc-start-ephemeral, the dhcp leases were unavailable and lxc-start-ephemeral failed. The machine was under fairly heavy load and was virtualized (EC2). I'd like to try and make this less fragile. As discussed on IRC, using lxcip (http://bazaar.launchpad.net/~launchpad/lpsetup/trunk/files/head:/lplxcip/) should make this more reliable. Perhaps increasing the timeout in that code might be useful as well. -- 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/994752 Title: lxc-start-ephemeral's use of dhcp lease table is fragile To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/994752/+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 990742] Re: slapd fails to upgrade: requires libsasl2-2 (= 2.1.24) installed
** Description changed: - I was trying to apt-get install dpkg to work around #944452 and got - the following while trying to upgrade slapd: + [Impact] + fill me in with explanation of severity and frequency of bug on users and justification for backporting the fix to the stable release + + [Development Fix] + fill me in with an explanation of how the bug has been addressed in the development branch, including the relevant version numbers of packages modified in order to implement the fix. + + [Stable Fix] + fill me in by pointing out a minimal patch applicable to the stable version of the package. + + [Text Case] + fill me in with detailed *instructions* on how to reproduce the bug. This will be used by people later on to verify the updated package fixes the problem. + 1. + 2. + 3. + Broken Behavior: + Fixed Behavior: + + [Regression Potential] + fill me in with a discussion of likelihood and potential severity of regressions and how users could get inadvertently affected. + + [Original Report]I was trying to apt-get install dpkg to work around + #944452 and got the following while trying to upgrade slapd: Setting up slapd (2.4.28-1.1ubuntu4) ... Use of uninitialized value $type in ucfirst at /usr/share/perl5/Debconf/AutoSelect.pm line 35. Backing up /etc/ldap/slapd.conf in /var/backups/slapd-2.4.21-0ubuntu5.7... done. Moving old database directories to /var/backups: Loading from /var/backups/slapd-2.4.21-0ubuntu5.7: - directory dc=interlinx,dc=bc,dc=ca... failed. Loading the database from the LDIF dump failed with the following error while running slapadd: 4f9c4903 slap_sasl_init: auxprop add plugin failed slapadd: slap_init failed! dpkg: error processing slapd (--configure): subprocess installed post-installation script returned error exit status 1 This looks to be related to http://bugs.debian.org/cgi- bin/bugreport.cgi?bug=665473 where message #10 (http://bugs.debian.org /cgi-bin/bugreport.cgi?bug=665473#10) in that bug says: This looks like a repeat of bug #628237. However, slapd 2.4.28-1.1/amd64 has a dependency on libsasl2-2 (= 2.1.24), ... Looking at the package info for slapd: Package: slapd Priority: optional Section: net Installed-Size: 4064 Maintainer: Ubuntu Developers ubuntu-devel-disc...@lists.ubuntu.com Original-Maintainer: Debian OpenLDAP Maintainers pkg-openldap-de...@lists.alioth.debian.org Architecture: i386 Source: openldap Version: 2.4.28-1.1ubuntu4 Replaces: ldap-utils ( 2.2.23-3), libldap2 Provides: ldap-server, libslapi-2.4-2 Depends: libc6 (= 2.15), libdb5.1, libldap-2.4-2 (= 2.4.28-1.1ubuntu4), libltdl7 (= 2.4.2), libodbc1 (= 2.2.11) | unixodbc (= 2.2.11), libperl5.14 (= 5.14.2), libsasl2-2, libslp1, libwrap0 (= 7.6-4~), coreutils (= 4.5.1-1), psmisc, perl ( 5.8.0) | libmime-base64-perl, adduser, lsb-base (= 3.2-13) We can see that it's not requiring a newer libsasl2-2. At this point I did an apt-get install libsasl2-2 and it installed the new libsasl2-2 and allowed the configuration of slapd to finish. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: slapd 2.4.28-1.1ubuntu4 ProcVersionSignature: Ubuntu 2.6.32-22.36-generic 2.6.32.11+drm33.2 Uname: Linux 2.6.32-22-generic i686 Architecture: i386 Date: Sat Apr 28 15:56:29 2012 ProcEnviron: LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: openldap -- SRU Justification -- [Impact] slapd's maintainer scripts make use of utilities like slapcat and slapadd which require a running slapd server, however, the relationship between slapd and libsasl2-2 packages do not take into account a binary incompatability introduced with 2.4.28-1.1. As a result, libsasl2-2 is not upgraded until after slapd, slapd fails to start (with error msg cited in the bugs), and maintainer scripts fail during upgrades with a debconf error like: http://paste.ubuntu.com/965636/ [Development Fix] The issue has been sorted in Debian and in Quantal with the recent merges. A thorough explanation of the fix is available at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=628237#163 . The solution is to update cyrus-sasl2 with: - Breaks: 'slapd 2.4.25-4' on libsasl2-2 - shlib dependency on 2.1.24 for libsasl2-2 Both of which have been applied to packaging in Debian and synced into Ubuntu Quantal. A no-change rebuild of openldap against the new sasl dependency is required as well. [Stable Fix] The two one-liners from above should be back-ported from 2.1.25.dfsg1-4 packaging and applied to cyrus-sasl2 packaging in Precise. A no-change rebuild of openldap against the newly updated dependency is required as well. [Test Case] To reproduce, install slapd on a lucid installation, populate a minimal LDAP directory and do-release-upgrade. A script to populate a minimal database can be found at http://paste.ubuntu.com/965633/. [Regression Potential]
[Bug 955883] Re: Squid3 Crash assertion failed: comm.cc:349
** Description changed: - The Squid Proxy crash sometimes a day with this Message: + [Impact] + fill me in with explanation of severity and frequency of bug on users and justification for backporting the fix to the stable release + + [Development Fix] + fill me in with an explanation of how the bug has been addressed in the development branch, including the relevant version numbers of packages modified in order to implement the fix. + + [Stable Fix] + fill me in by pointing out a minimal patch applicable to the stable version of the package. + + [Text Case] + fill me in with detailed *instructions* on how to reproduce the bug. This will be used by people later on to verify the updated package fixes the problem. + 1. + 2. + 3. + Broken Behavior: + Fixed Behavior: + + [Regression Potential] + fill me in with a discussion of likelihood and potential severity of regressions and how users could get inadvertently affected. + + [Original Report] + The Squid Proxy crash sometimes a day with this Message: assertion failed: comm.cc:349: !fd_table[fd].closing() In the Squid3 Bug Tracker i see there is the same issue fixed: http://bugs.squid-cache.org/show_bug.cgi?id=3131 Can you please fix this in Ubuntu too ? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid3 in Ubuntu. https://bugs.launchpad.net/bugs/955883 Title: Squid3 Crash assertion failed: comm.cc:349 To manage notifications about this bug go to: https://bugs.launchpad.net/squid/+bug/955883/+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 948461] Re: apt-get hashsum/size mismatch because s3 mirrors don't support http pipelining correctly
** Description changed: + [Impact] + fill me in with explanation of severity and frequency of bug on users and justification for backporting the fix to the stable release + + [Development Fix] + fill me in with an explanation of how the bug has been addressed in the development branch, including the relevant version numbers of packages modified in order to implement the fix. + + [Stable Fix] + fill me in by pointing out a minimal patch applicable to the stable version of the package. + + [Text Case] + fill me in with detailed *instructions* on how to reproduce the bug. This will be used by people later on to verify the updated package fixes the problem. + 1. + 2. + 3. + Broken Behavior: + Fixed Behavior: + + [Regression Potential] + fill me in with a discussion of likelihood and potential severity of regressions and how users could get inadvertently affected. + + [Original Report] [SRU: Cloud-Init] r536 and r537 contains a fix that: - 1.) Disables APT pipelining on first boot for new Cloud Images instances - 2.) Disables APT pipelining on installation for existing cloud-images. + 1.) Disables APT pipelining on first boot for new Cloud Images instances + 2.) Disables APT pipelining on installation for existing cloud-images. The rational for this SRU is due to the Mirror situation for EC2 Cloud images. Currently, the mirrors are proving to have moments of instability that is causing both end-user and development pain. In order to address this, we built out Amazon AWS S3 mirrors. Unfortantly, due to a bug in S3, apt http pipeling does not work with S3. As a result, in order to provide enhanced availability for the Cloud Image repositories in EC2, apt http pipelining needs to be disabled ahead of flipping the new S3 mirrors as the active mirrors. The performance impact of this change is unnoticable and in testing, has proven to provide no ill effect. http pipeplining allows for multiple requests to be made at the same time. The apt change log states that http pipelining is a micro-enhancement and within the EC2 environment shaves a few seconds of many requests. When apt http pipeling works, at best, it saves a few seconds, when it fails against a buggy HTTP1.1 server or behind a proxy that does not support it, the failures are arbitrary and not adiquetly explained. This change will enhance the Cloud Images by making apt request packages sequentially instead of in batches and prevent arbitrary failures caused by non-compliant web servers. Cloud image users, both on EC2 and outside, will benefit from this fix. http://bazaar.launchpad.net/~cloud-init-dev/cloud-init/trunk/revision/536 http://bazaar.launchpad.net/~cloud-init-dev/cloud-init/trunk/revision/537 - ___ apt-get is appears to be mangling the local caching file names, which is appearing as a hashsum or size mismatch. Evidence below: ___ Output of apt-get -y install firefox: Failed to fetch http://us-east-1.ec2.archive.ubuntu.com.s3.amazonaws.com/ubuntu/pool/main/p/python-defer/python-defer_1.0.2+bzr481-1_all.deb Size mismatch Failed to fetch http://us-east-1.ec2.archive.ubuntu.com.s3.amazonaws.com/ubuntu/pool/main/a/aptdaemon/python-aptdaemon_0.43+bzr769-0ubuntu1_all.deb Size mismatch Failed to fetch http://us-east-1.ec2.archive.ubuntu.com.s3.amazonaws.com/ubuntu/pool/main/a/aptdaemon/aptdaemon_0.43+bzr769-0ubuntu1_all.deb Size mismatch Failed to fetch http://us-east-1.ec2.archive.ubuntu.com.s3.amazonaws.com/ubuntu/pool/main/u/ubufox/xul-ext-ubufox_2.0-0ubuntu1_all.deb Size mismatch ___ apt-get -y install firefox with debug for HTTP turned on: Get:63 http://us-east-1.ec2.archive.ubuntu.com.s3.amazonaws.com/ubuntu/ precise/main python-defer all 1.0.2+bzr481-1 [10.9 kB] HTTP/1.1 200 OK^M x-amz-id-2: EXccd6GVMfE6ly4SYdwy313VK42d/gI3ncyxmaotuVIMbBBi6FJkuDYWrzLw7vXE^M x-amz-request-id: 7572BAB5E6FFFAC0^M Date: Tue, 06 Mar 2012 20:06:13 GMT^M Last-Modified: Fri, 03 Feb 2012 08:54:27 GMT^M ETag: 6c07f8db615cc32657b1cc57450a1608^M Accept-Ranges: bytes^M Content-Type: application/x-debian-package^M Content-Length: 15142^M Server: AmazonS3^M ^M Get:64 http://us-east-1.ec2.archive.ubuntu.com.s3.amazonaws.com/ubuntu/ precise/main python-aptdaemon all 0.43+bzr769-0ubuntu1 [80.3 kB] HTTP/1.1 200 OK^M x-amz-id-2: IcNECY1OtzHOXnTnTW3fqoJGyfdODq+qRXXGYTDEOJxfw0CP9UH8EUSllVR3Gf3F^M x-amz-request-id: 5D629E3BA012^M Date: Tue, 06 Mar 2012 20:06:13 GMT^M Last-Modified: Fri, 02 Mar 2012 20:55:40 GMT^M ETag: 501373631a241847cf76d13aea9264b3^M Accept-Ranges: bytes^M Content-Type: application/x-debian-package^M Content-Length: 56824^M Server:
[Bug 955883] Re: Squid3 Crash assertion failed: comm.cc:349
** Description changed: [Impact] - fill me in with explanation of severity and frequency of bug on users and justification for backporting the fix to the stable release + The Squid Proxy crash sometimes a day with this Message: + assertion failed: comm.cc:349: !fd_table[fd].closing() [Development Fix] - fill me in with an explanation of how the bug has been addressed in the development branch, including the relevant version numbers of packages modified in order to implement the fix. + Fixed in http://bugs.squid-cache.org/show_bug.cgi?id=3131, which is part of the 3.1.19 upstream release. The fix checks if the connection is still open and if not it bails out without attempting to read more data. This version was merged from Debian into Precise on Feb 21, 2012 as version 3.1.19-1ubuntu1. [Stable Fix] - fill me in by pointing out a minimal patch applicable to the stable version of the package. + Cherrypick of upstream patch (https://launchpadlibrarian.net/97717160/squid3_fix_955883.patch) applies to the squid3 3.1.14 from oneiric. [Text Case] fill me in with detailed *instructions* on how to reproduce the bug. This will be used by people later on to verify the updated package fixes the problem. 1. 2. 3. - Broken Behavior: - Fixed Behavior: + Broken Behavior: + Fixed Behavior: [Regression Potential] - fill me in with a discussion of likelihood and potential severity of regressions and how users could get inadvertently affected. + fill me in with a discussion of likelihood and potential severity of regressions and how users could get inadvertently affected. [Original Report] The Squid Proxy crash sometimes a day with this Message: assertion failed: comm.cc:349: !fd_table[fd].closing() In the Squid3 Bug Tracker i see there is the same issue fixed: http://bugs.squid-cache.org/show_bug.cgi?id=3131 Can you please fix this in Ubuntu too ? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid3 in Ubuntu. https://bugs.launchpad.net/bugs/955883 Title: Squid3 Crash assertion failed: comm.cc:349 To manage notifications about this bug go to: https://bugs.launchpad.net/squid/+bug/955883/+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 948461] Re: apt-get hashsum/size mismatch because s3 mirrors don't support http pipelining correctly
** Description changed: - SRU Justification + [Problem] + When using S3 mirrors, the apt client requests files A,B,C,D in the same request, but S3 responds with files B,C,D,A or some other arbitrary ordering. Apt then saves the files under the wrong file names. + + This is due to a bug in Amazon AWS S3, where http pipelining does not + work in violation of RFC 2068. apt uses http pipelining currently, so + this prevents apt from using mirrors hosted on S3 cloud instances. + [Impact] - EC2 Instances cannot reliably use the new S3 Mirrors. - - Currently Canonical IS runs mirrors on instances in each EC2 - Availability zone. Ben Howard has put infrastructure in place to run - these mirrors entirely out of Amazon's S3. This will give better - performance and reliability for Ubuntu users in EC2. - - There is a bug in the S3 HTTP implementation that is exposed when using - apt with the pipelining turned on. Therefore, we cannot put these S3 - mirrors in place until after this fix is released. + Blocks use of S3 mirrors for providing ubuntu updates. Affects Hardy, Lucid, Maverick, Oneiric, Natty, and Precise. + + Use of S3 mirrors is considered as a way of enhancing our mirror + services. Currently mirrors have moments of instability, so having the + option of switching to S3 mirrors is very important for update + reliability. [Development Fix] - On installation or upgrade, cloud-init will populate /etc/apt/apt.conf.d/90cloud-init-pipelining with: - //Written by cloud-init per 'apt_pipelining - Acquire::http::Pipeline-Depth 0 - - After that, this will happen only once per instance. The user can disable this function if they do not want it by modifying that file, or by providing cloud-init with userdata like: - #cloud-config - apt_pipelining: 0 - - This was first included in cloud-init upstream at revision 536, and into - Ubuntu precise in 0.6.3~bzr539-0ubuntu1 . - - [1] http://bazaar.launchpad.net/~cloud-init-dev/cloud- - init/trunk/revision/536 + Fixed in Precise's cloud-init as of these comments, which adds an apt_pipelining option, turned off by default but configurable. + http://bazaar.launchpad.net/~cloud-init-dev/cloud-init/trunk/revision/536 + http://bazaar.launchpad.net/~cloud-init-dev/cloud-init/trunk/revision/537 [Stable Fix] - Identical logic and behavior to the upstream fix has been ported back to each of 10.04, 10.10, 11.04, 11.10. + TODO [Text Case] 1) Launch an instance in EC2 - $ ubuntu-ec2-run $SUITE - 2) Select the S3 mirrors: -sed -i.dist s,ec2.archive.ubuntu.com,ec2.archive.ubuntu.com.s3.amazonaws.com,g /etc/apt/sources.list + 2) Run: sed -i s,ec2.archive.ubuntu.com,ec2.archive.ubuntu.com.s3.amazonaws.com,g /etc/apt/sources.list + 3.) Set your apt debug levels to whatever you want 4) Run apt-get -y update - 5) Run apt-get --download-only -y install firefox xorg libreoffice - - Alternatively for 4 and 5 you can just use the attachment 'apt-get - download loop' - - Broken Behavior: - Apt will fail eventually with 'Hash sum Mismatch' or some other download error. - - Fixed Behavior: - Run apt-get download forever with no errors. + 5) Run apt-get -y install firefox xorg libreoffice /tmp/install.log 21 + Broken Behavior: Cached files are being misnamed + Fixed Behavior: Cached files are properly named + + The S3 EC2 mirrors seem to reproduce it most reliably. The downloaded + files are whole and match the proper checksums, but they have the wrong + content. [Regression Potential] - The potential is present for performance regression due to disabling pipelining. - However, enabling pipelining in apt was argued against by Robert Collins, an upstream squid developer. He has stated it is a micro enhancement, and causes significant issues for many clients. - SRU Justification + http pipelining is an optimization technique in apt which allows multiple requests to be made at the same time. When it works, it provides a small performance boost, but when it doesn't the failures are arbitrary and not adequately explained. + + Thus, the expected regression is slightly slower apt behavior for non-S3 + cloud users. However, testing shows the impact is less than a few + seconds so will likely be unnoticed. In the off chance that it does + inadvertently cause non-trivial performance impact, the change is + configurable on a per-host instance. [Original Report] [SRU: Cloud-Init] r536 and r537 contains a fix that: 1.) Disables APT pipelining on first boot for new Cloud Images instances 2.) Disables APT pipelining on installation for existing cloud-images. The rational for this SRU is due to the Mirror situation for EC2 Cloud images. Currently, the mirrors are proving to have moments of instability that is causing both end-user and development pain. In order to address this, we built out Amazon AWS S3 mirrors. Unfortantly, due to a bug in S3, apt http pipeling does not work with
[Bug 948461] Re: apt-get hashsum/size mismatch because s3 mirrors don't support http pipelining correctly
I notice this bug is reported against both apt and cloud-init, but the patches are only for cloud-init. Are there any changes required of apt? If not, perhaps those tasks can all be closed out? -- 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/948461 Title: apt-get hashsum/size mismatch because s3 mirrors don't support http pipelining correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/948461/+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 955883] Re: Squid3 Crash assertion failed: comm.cc:349
I had to rejigger the patch to get it to apply with the proper path. Verified it's the same change as upstream. Packaged as dpatch and verified it builds. Upload sponsored, thanks for your contribution to Ubuntu. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid3 in Ubuntu. https://bugs.launchpad.net/bugs/955883 Title: Squid3 Crash assertion failed: comm.cc:349 To manage notifications about this bug go to: https://bugs.launchpad.net/squid/+bug/955883/+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 922650] Re: Lucid needs the fix for PHP Bug #33210
** Description changed: - Since we're trying keep our cluster running on stock Lucid, is there any - way to get the fix for https://bugs.php.net/bug.php?id=33210 applied to - the php package? This was originally reported here: - https://bugzilla.wikimedia.org/show_bug.cgi?id=31588 + [Impact] + fill me in with explanation of severity and frequency of bug on users and justification for backporting the fix to the stable release + + [Development Fix] + fill me in with an explanation of how the bug has been addressed in the development branch, including the relevant version numbers of packages modified in order to implement the fix. + + [Stable Fix] + fill me in by pointing out a minimal patch applicable to the stable version of the package. + + [Text Case] + fill me in with detailed *instructions* on how to reproduce the bug. This will be used by people later on to verify the updated package fixes the problem. + 1. + 2. + 3. + Broken Behavior: + Fixed Behavior: + + [Regression Potential] + fill me in with a discussion of likelihood and potential severity of regressions and how users could get inadvertently affected. + + [Original Report] + + + Since we're trying keep our cluster running on stock Lucid, is there any way to get the fix for https://bugs.php.net/bug.php?id=33210 applied to the php package? This was originally reported here: https://bugzilla.wikimedia.org/show_bug.cgi?id=31588 -- 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/922650 Title: Lucid needs the fix for PHP Bug #33210 To manage notifications about this bug go to: https://bugs.launchpad.net/php/+bug/922650/+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 907828] Re: tun-based VPNs using the subnet topology are wrongly sending ICMP redirects
** Description changed: - When a tun-based VPN is using the subnet topology, the communication - between clients can confuse the routing code that will wrongly emit ICMP - redirects. This problem is very well described here - http://backreference.org/2010/05/02/controlling-client-to-client- - connections-in-openvpn/. The same link also provides the workaround - (disable ICMP redirect on the TUN device). + [Impact] + fill me in with explanation of severity and frequency of bug on users and justification for backporting the fix to the stable release + + [Development Fix] + fill me in with an explanation of how the bug has been addressed in the development branch, including the relevant version numbers of packages modified in order to implement the fix. + + [Stable Fix] + fill me in by pointing out a minimal patch applicable to the stable version of the package. + + [Text Case] + fill me in with detailed *instructions* on how to reproduce the bug. This will be used by people later on to verify the updated package fixes the problem. + 1. + 2. + 3. + Broken Behavior: + Fixed Behavior: + + [Regression Potential] + fill me in with a discussion of likelihood and potential severity of regressions and how users could get inadvertently affected. + + [Original Report] + When a tun-based VPN is using the subnet topology, the communication between clients can confuse the routing code that will wrongly emit ICMP redirects. This problem is very well described here http://backreference.org/2010/05/02/controlling-client-to-client-connections-in-openvpn/. The same link also provides the workaround (disable ICMP redirect on the TUN device). This problem affects Lucid to Precise (Hardy's version does not support the subnet mode). ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: openvpn 2.1.3-2ubuntu3 ProcVersionSignature: Ubuntu 2.6.38-13.53-generic 2.6.38.8 Uname: Linux 2.6.38-13-generic x86_64 Architecture: amd64 Date: Thu Dec 22 11:34:08 2011 ProcEnviron: - LANGUAGE=en_US:en - LANG=en_US.UTF-8 - SHELL=/bin/bash + LANGUAGE=en_US:en + LANG=en_US.UTF-8 + SHELL=/bin/bash SourcePackage: openvpn UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openvpn in Ubuntu. https://bugs.launchpad.net/bugs/907828 Title: tun-based VPNs using the subnet topology are wrongly sending ICMP redirects To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvpn/+bug/907828/+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 869017] Re: Ubuntu server enables screenblanking, concealing crashdumps (DPMS is not used)
** Package changed: xorg (Ubuntu) = xorg-server (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/869017 Title: Ubuntu server enables screenblanking, concealing crashdumps (DPMS is not used) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/869017/+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 879666] Re: chown error for console.fifo when launching vm
** Description changed: - I saw this once before when I was less confident I knew how to run nova. - I cannot reliably reproduce this problem. Here is the contents of the - directory supposedly containng the missing file: + [Impact] + fill me in with explanation of severity and frequency of bug on users and justification for backporting the fix to the stable release + + [Development Fix] + fill me in with an explanation of how the bug has been addressed in the development branch, including the relevant version numbers of packages modified in order to implement the fix. + + [Stable Fix] + fill me in by pointing out a minimal patch applicable to the stable version of the package. + + [Text Case] + fill me in with detailed *instructions* on how to reproduce the bug. This will be used by people later on to verify the updated package fixes the problem. + 1. + 2. + 3. + Broken Behavior: + Fixed Behavior: + + [Regression Potential] + fill me in with a discussion of likelihood and potential severity of regressions and how users could get inadvertently affected. + + [Original Report] + I saw this once before when I was less confident I knew how to run nova. I cannot reliably reproduce this problem. Here is the contents of the directory supposedly containng the missing file: root@xg11eth0:~# ls -l /var/lib/nova/instances/instance-0001/ total 82492 prw-rw 1 root root0 2011-10-21 16:21 console.fifo.in prw-rw 1 root root0 2011-10-21 16:22 console.fifo.out -rw-rw-r-- 1 nova nova65545 2011-10-21 16:22 console.ring -rw-r--r-- 1 root root 75497472 2011-10-21 16:26 disk -rw-r--r-- 1 root root 12582912 2011-10-21 16:22 disk.local -rw-rw-r-- 1 root root 4732048 2011-10-21 16:21 kernel -rw-rw-r-- 1 nova nova 1750 2011-10-21 16:31 libvirt.xml This was running from packages using oneiric-proposed - 2011-10-21 16:31:54,147 DEBUG nova.utils [-] Running cmd (subprocess): mkdir -p /var/lib/nova/instances/instance-0001/ from (pid=1185) execute /usr/lib/python2.7/dist-package\ s/nova/utils.py:168 2011-10-21 16:31:54,153 INFO nova.virt.libvirt_conn [-] instance instance-0001: Creating image 2011-10-21 16:31:54,153 DEBUG nova.utils [-] Running cmd (subprocess): sudo chown 107 /var/lib/nova/instances/instance-0001/console.fifo from (pid=1185) execute /usr/lib/pyth\ on2.7/dist-packages/nova/utils.py:168 2011-10-21 16:31:54,173 DEBUG nova.utils [-] Result was 1 from (pid=1185) execute /usr/lib/python2.7/dist-packages/nova/utils.py:183 2011-10-21 16:31:54,174 ERROR nova.exception [-] Uncaught exception (nova.exception): TRACE: Traceback (most recent call last): (nova.exception): TRACE: File /usr/lib/python2.7/dist-packages/nova/exception.py, line 98, in wrapped (nova.exception): TRACE: return f(*args, **kw) (nova.exception): TRACE: File /usr/lib/python2.7/dist-packages/nova/virt/libvirt/connection.py, line 676, in spawn (nova.exception): TRACE: block_device_info=block_device_info) (nova.exception): TRACE: File /usr/lib/python2.7/dist-packages/nova/virt/libvirt/connection.py, line 928, in _create_image (nova.exception): TRACE: run_as_root=True) (nova.exception): TRACE: File /usr/lib/python2.7/dist-packages/nova/utils.py, line 191, in execute (nova.exception): TRACE: cmd=' '.join(cmd)) (nova.exception): TRACE: ProcessExecutionError: Unexpected error while running command. (nova.exception): TRACE: Command: sudo chown 107 /var/lib/nova/instances/instance-0001/console.fifo (nova.exception): TRACE: Exit code: 1 (nova.exception): TRACE: Stdout: '' (nova.exception): TRACE: Stderr: chown: cannot access `/var/lib/nova/instances/instance-0001/console.fifo': No such file or directory\n (nova.exception): TRACE: 2011-10-21 16:31:54,192 ERROR nova.compute.manager [-] Instance '1' failed to spawn. Is virtualization enabled in the BIOS? Details: Unexpected error while running command. Command: sudo chown 107 /var/lib/nova/instances/instance-0001/console.fifo Exit code: 1 Stdout: '' Stderr: chown: cannot access `/var/lib/nova/instances/instance-0001/console.fifo': No such file or directory\n (nova.compute.manager): TRACE: Traceback (most recent call last): (nova.compute.manager): TRACE: File /usr/lib/python2.7/dist-packages/nova/compute/manager.py, line 424, in _run_instance (nova.compute.manager): TRACE: network_info, block_device_info) (nova.compute.manager): TRACE: File /usr/lib/python2.7/dist-packages/nova/exception.py, line 129, in wrapped (nova.compute.manager): TRACE: raise Error(str(e)) (nova.compute.manager): TRACE: Error: Unexpected error while running command. (nova.compute.manager): TRACE: Command: sudo chown 107 /var/lib/nova/instances/instance-0001/console.fifo (nova.compute.manager): TRACE: Exit code: 1 (nova.compute.manager): TRACE: Stdout: '' (nova.compute.manager): TRACE: Stderr: chown:
[Bug 726099] Re: libvirtd assert failure: *** glibc detected *** /usr/sbin/libvirtd: realloc(): invalid next size: 0x00007f289004d5e0 ***
Please collect a full backtrace - see http://wiki.ubuntu.com/X/Backtracing for directions. Or, if the libvirt fix solves it sufficiently, and no action is needed for libpciaccess you can close out the libpciaccess task. ** Changed in: libpciaccess (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt in Ubuntu. https://bugs.launchpad.net/bugs/726099 Title: libvirtd assert failure: *** glibc detected *** /usr/sbin/libvirtd: realloc(): invalid next size: 0x7f289004d5e0 *** -- 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 668368] Re: Default [homes] share template uses incorrect %S macro.
According to the upstream bug report: To my understanding, %S (== the name of the service connected to) is appropriate here, since the user connects to a share with name equal to the user's name, so in this special case, %S is the same as the username. So it is unclear if changing from %U to %S is actually appropriate here. Please investigate further and re-subscribe sponsors when a more definitive solution is identified. ** Bug watch added: Samba Bugzilla #7766 https://bugzilla.samba.org/show_bug.cgi?id=7766 ** Changed in: samba (Debian) Importance: Undecided = Unknown ** Changed in: samba (Debian) Status: New = Unknown ** Changed in: samba (Debian) Remote watch: None = Samba Bugzilla #7766 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in Ubuntu. https://bugs.launchpad.net/bugs/668368 Title: Default [homes] share template uses incorrect %S macro. -- 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 700945] Re: backport of patch for error message undefined method `closed?' for Nil:NilClass required.
Hi Oliver, thanks for posting a fix to this bug. Since it sounds like this issue exists only for Lucid, not natty, I'm closing the general task for natty, and leaving the Lucid task open for further work. The debdiff applies, but I think you should use a patch system like quilt rather than patch the sources directly... ** Changed in: puppet (Ubuntu) Status: Triaged = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to puppet in Ubuntu. https://bugs.launchpad.net/bugs/700945 Title: backport of patch for error message undefined method `closed?' for Nil:NilClass required. -- 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 620441] Re: MySQL upstart stop job does not cleanly shutdown mysql
Sponsored upload of SRU patch to lucid-proposed ** Changed in: mysql-dfsg-5.1 (Ubuntu Lucid) Status: Triaged = Fix Committed ** Changed in: mysql-dfsg-5.1 (Ubuntu Lucid) Assignee: (unassigned) = Clint Byrum (clint-fewbar) -- MySQL upstart stop job does not cleanly shutdown mysql https://bugs.launchpad.net/bugs/620441 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mysql-dfsg-5.1 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 366242] Re: after adding samba sharing service, X restart failed on jaunty
We're closing this bug since it is has been some time with no response from the original reporter. However, if the issue still exists please feel free to reopen with the requested information. Also, if you could, please test against the latest development version of Ubuntu, since this confirms the bug is one we may be able to pass upstream for help. ** Changed in: xorg-server (Ubuntu) Status: Incomplete = Expired -- after adding samba sharing service, X restart failed on jaunty https://bugs.launchpad.net/bugs/366242 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba 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 366242] Re: after adding samba sharing service, X restart failed on jaunty
** Tags added: jaunty -- after adding samba sharing service, X restart failed on jaunty https://bugs.launchpad.net/bugs/366242 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba 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 513509] Re: ntp help manual should mention time slewing
** Also affects: ntp (Ubuntu Lucid) Importance: Undecided Status: Confirmed -- ntp help manual should mention time slewing https://bugs.launchpad.net/bugs/513509 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ntp 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 424053] Re: Clarify the offending known_hosts line number when ssh key has changed
I'm moving this from wishlist to legitimate bug because it used to be that the file contained hostnames, so even if you didn't notice the line number you could grep for the machine or its ip. Now this info appears to be hashed so the line number is the only way to know. It would be nice to have some mechanism to update the known_hosts file when a server has changed identities other than having to hand edit this file. For many users the list of hashed data is going to look like line noise. The error message also says you have requested strict checking, however this is misleading - *you* didn't request it, it's the default setting (at least, on Ubuntu). I think the friendliest way to handle this would be something like: An RSA host key for this server was not found in /home/scott/.ssh/known_hosts! To fix this, run the command `ssh-recognize-host [hostname]`, or turn off StrictHostKeyChecking to disable host checking completely. Add correct host key in /home/scott/.ssh/known_hosts to get rid of this message. ** Changed in: openssh (Ubuntu) Importance: Wishlist = Medium -- Clarify the offending known_hosts line number when ssh key has changed https://bugs.launchpad.net/bugs/424053 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 513509] [NEW] ntp help manual should mention time slewing
Public bug reported: Binary package hint: ntp After installing and configuring ntp (and reading the time-admin help manual from the help button), I noticed the time didn't seem to change. I ended up just restarting the service and it updated appropriately. I learned from other sources that this is because rather than change the time all at once, it does it bit by bit (time slewing). It would save some confusion to mention this time slewing behavior in the help documentation alongside the directions for configuring time synchronization. ** Affects: ntp (Ubuntu) Importance: Undecided Status: Confirmed -- ntp help manual should mention time slewing https://bugs.launchpad.net/bugs/513509 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ntp 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 237894] Re: I cannot connect to any server. Conection hangs up at channel 0: open confirm rwindow 0 rmax 32768
** Tags added: kubuntu -- I cannot connect to any server. Conection hangs up at channel 0: open confirm rwindow 0 rmax 32768 https://bugs.launchpad.net/bugs/237894 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 334781] Re: bacula 2.4.4 configuration fails
** Changed in: bacula (Ubuntu) Status: Fix Committed = Fix Released -- bacula 2.4.4 configuration fails https://bugs.launchpad.net/bugs/334781 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bacula 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 318179] Re: Please merge apache2(2.2.11-2)(main) from debian unstable(main)
Looks good, upload sponsored. ** Changed in: apache2 (Ubuntu) Status: Confirmed = Fix Committed -- Please merge apache2(2.2.11-2)(main) from debian unstable(main) https://bugs.launchpad.net/bugs/318179 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to apache2 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 318179] Re: Please merge apache2(2.2.11-2)(main) from debian unstable(main)
Oh, looks like this was already merged on the 17th. ** Changed in: apache2 (Ubuntu) Status: Fix Committed = Fix Released -- Please merge apache2(2.2.11-2)(main) from debian unstable(main) https://bugs.launchpad.net/bugs/318179 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to apache2 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 315774] Re: libsmbclient-dev missing smbc_urlencode in .a in intrepid
** Changed in: samba (Ubuntu) Status: Fix Committed = In Progress -- libsmbclient-dev missing smbc_urlencode in .a in intrepid https://bugs.launchpad.net/bugs/315774 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba 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 249337] Re: bash get_cword: command not found
Thanks, debdiff looks good. Uploaded. ** Changed in: bash-completion (Ubuntu) Status: Confirmed = Fix Committed -- bash get_cword: command not found https://bugs.launchpad.net/bugs/249337 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to postfix 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
