[Bug 1556563] Re: etckeeper in Xenial wants python2.x
** Tags added: xenial -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to etckeeper in Ubuntu. https://bugs.launchpad.net/bugs/1556563 Title: etckeeper in Xenial wants python2.x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/etckeeper/+bug/1556563/+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 1556563] [NEW] etckeeper in Xenial wants python2.x
Public bug reported: Hi, Xenial now ships without python2.7 by default. Unfortunately, it seems etckeeper still wants to pull in python2.7. Should it be updated to python3? Thanks, Haw ** Affects: etckeeper (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to etckeeper in Ubuntu. https://bugs.launchpad.net/bugs/1556563 Title: etckeeper in Xenial wants python2.x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/etckeeper/+bug/1556563/+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 1541678] [NEW] if-post-down.d/vlan and if-pre-up.d/vlan should support en* interfaces
Public bug reported: Starting with udev v197, systems now use predictable network interface names by default[1]. Unfortunately on my system running Xenial alpha2, it seems vlan doesn't support the generated interface names: | ubuntu@lagertha:/var/log$ dmesg | grep rename | [5.101700] igb :01:00.0 enp1s0: renamed from eth0 | [5.502268] igb :02:00.0 enp2s0: renamed from eth1 | [5.526634] igb :04:00.0 enp4s0: renamed from eth3 | [5.550056] igb :03:00.0 enp3s0: renamed from eth2 Looking at the if-pre-up and if-post-down scripts, it seems it's missing there and only has: | eth*.0*|bond*.0*|wlan*.0*|em*.0*|p[0-9]*.0*) | ... ;; | eth*.*|bond*.*|wlan*.*|em*.*|p[0-9]*.*) | ... ;; """ What precisely has changed in v197? The following different naming schemes for network interfaces are now supported by udev natively: 1. Names incorporating Firmware/BIOS provided index numbers for on-board devices (example: eno1) 2. Names incorporating Firmware/BIOS provided PCI Express hotplug slot index numbers (example: ens1) 3. Names incorporating physical/geographical location of the connector of the hardware (example: enp2s0) 4. Names incorporating the interfaces's MAC address (example: enx78e7d1ea46da) 5. Classic, unpredictable kernel-native ethX naming (example: eth0) """ Here's the package versions: | ubuntu@lagertha:/var/log$ apt-cache policy udev | udev: | Installed: 228-4ubuntu2 | Candidate: 228-5ubuntu1 | Version table: | 228-5ubuntu1 500 | 500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages | *** 228-4ubuntu2 100 | 100 /var/lib/dpkg/status | ubuntu@lagertha:/var/log$ apt-cache policy vlan | vlan: | Installed: 1.9-3.2ubuntu1 | Candidate: 1.9-3.2ubuntu1 | Version table: | *** 1.9-3.2ubuntu1 500 | 500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages | 100 /var/lib/dpkg/status [1]http://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/ ** Affects: vlan (Ubuntu) Importance: Undecided Status: New ** Tags: xenial ** Tags added: xenial ** Description changed: Starting with udev v197, systems now use predictable network interface names by default. Unfortunately on my system running Xenial alpha2, it seems vlan doesn't support the generated interface names: | ubuntu@lagertha:/var/log$ dmesg | grep rename | [5.101700] igb :01:00.0 enp1s0: renamed from eth0 | [5.502268] igb :02:00.0 enp2s0: renamed from eth1 | [5.526634] igb :04:00.0 enp4s0: renamed from eth3 | [5.550056] igb :03:00.0 enp3s0: renamed from eth2 Looking at the if-pre-up and if-post-down scripts, it seems it's missing there and only has: | eth*.0*|bond*.0*|wlan*.0*|em*.0*|p[0-9]*.0*) | ... ;; | eth*.*|bond*.*|wlan*.*|em*.*|p[0-9]*.*) | ... ;; + + Here's the package versions: + + | ubuntu@lagertha:/var/log$ apt-cache policy udev + | udev: + | Installed: 228-4ubuntu2 + | Candidate: 228-5ubuntu1 + | Version table: + | 228-5ubuntu1 500 + | 500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages + | *** 228-4ubuntu2 100 + | 100 /var/lib/dpkg/status + | ubuntu@lagertha:/var/log$ apt-cache policy vlan + | vlan: + | Installed: 1.9-3.2ubuntu1 + | Candidate: 1.9-3.2ubuntu1 + | Version table: + | *** 1.9-3.2ubuntu1 500 + | 500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages + | 100 /var/lib/dpkg/status ** Description changed: Starting with udev v197, systems now use predictable network interface - names by default. Unfortunately on my system running Xenial alpha2, it - seems vlan doesn't support the generated interface names: + names by default[1]. Unfortunately on my system running Xenial alpha2, + it seems vlan doesn't support the generated interface names: | ubuntu@lagertha:/var/log$ dmesg | grep rename | [5.101700] igb :01:00.0 enp1s0: renamed from eth0 | [5.502268] igb :02:00.0 enp2s0: renamed from eth1 | [5.526634] igb :04:00.0 enp4s0: renamed from eth3 | [5.550056] igb :03:00.0 enp3s0: renamed from eth2 Looking at the if-pre-up and if-post-down scripts, it seems it's missing there and only has: | eth*.0*|bond*.0*|wlan*.0*|em*.0*|p[0-9]*.0*) | ... ;; | eth*.*|bond*.*|wlan*.*|em*.*|p[0-9]*.*) | ... ;; + + """ + What precisely has changed in v197? + + The following different naming schemes for network interfaces are now + supported by udev natively: + + 1. Names incorporating Firmware/BIOS provided index numbers for on-board devices (example: eno1) + 2. Names incorporating Firmware/BIOS provided PCI Express hotplug slot index numbers (example: ens1) + 3. Names incorporating physical/geographical location of the connector of the hardware (example: enp2s0) + 4. Names incorporating the interfaces's MAC address (example: enx78e7d1ea46da) + 5. Classic, unpredictable kernel-native
[Bug 1541678] Re: if-post-down.d/vlan and if-pre-up.d/vlan should support en* interfaces
Attached patch makes it work when interface names are enpXsY. It doesn't cover the other cases as per link to PredictableNetworkInterfaceNames. ** Patch added: "enp1s0.patch" https://bugs.launchpad.net/ubuntu/+source/vlan/+bug/1541678/+attachment/4563451/+files/enp1s0.patch -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to vlan in Ubuntu. https://bugs.launchpad.net/bugs/1541678 Title: if-post-down.d/vlan and if-pre-up.d/vlan should support en* interfaces To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vlan/+bug/1541678/+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 1512185] Re: qemu-nbd on ARM64 deadlock? Stuck in rt_sigtimedwait([BUS ALRM IO], ..) and futex(0x7f749ec230, FUTEX_WAIT, ...)
Kernel OOPS on one of the mcdivitts:
| [544599.231964] block nbd0: Attempted send on closed socket
| [544599.231968] block nbd0: Attempted send on closed socket
| [544599.231972] block nbd0: Attempted send on closed socket
| [544599.231975] block nbd0: Attempted send on closed socket
| [544627.046717] INFO: rcu_sched self-detected stall on CPU { 3} (t=15040176
jiffies g=8751031 c=8751030 q=246988591)
| [544627.046719] Task dump for CPU 3:
| [544627.046723] qemu-nbdR running task0 32375 1
0x000a
| [544627.046724] Call trace:
| [544627.046733] [] dump_backtrace+0x0/0x170
| [544627.046737] [] show_stack+0x20/0x2c
| [544627.046740] [] sched_show_task+0xa0/0xf8
| [544627.046742] [] dump_cpu_task+0x44/0x54
| [544627.046745] [] rcu_dump_cpu_stacks+0x98/0xec
| [544627.046747] [] rcu_check_callbacks+0x410/0x740
| [544627.046751] [] update_process_times+0x40/0x74
| [544627.046754] [] tick_sched_handle.isra.15+0x38/0x7c
| [544627.046756] [] tick_sched_timer+0x48/0x84
| [544627.046758] [] __run_hrtimer+0x90/0x1d0
| [544627.046760] [] hrtimer_interrupt+0xec/0x28c
| [544627.046764] [] arch_timer_handler_phys+0x38/0x48
| [544627.046766] [] handle_percpu_devid_irq+0x90/0x12c
| [544627.046769] [] generic_handle_irq+0x38/0x54
| [544627.046770] [] __handle_domain_irq+0x64/0xc0
| [544627.046772] [] gic_handle_irq+0x38/0x88
| [544627.046773] Exception stack(0xffc634947610 to 0xffc634947730)
| [544627.046776] 7600: 00c1a000 ffc0
00c1f000 ffc0
| [544627.046778] 7620: 34947750 ffc6 000ffe0c ffc0 0900
01c0
| [544627.046780] 7640: 0005 004a1870 ffc0 004a1870 ffc0
004a433c ffc0
| [544627.046782] 7660: 00ff 00b5c658 ffc0 6465736f 636f7320
00ba157e
| [544627.046784] 7680: 00ba1449 0006
20666366
| [544627.046786] 76a0: 34393433 30353737 ec9de100 0038d0cb 0023ceec ffc0
004bc7f8
| [544627.046788] 76c0: aff5f5d0 007f 00c1a000 ffc0 00c1f000 ffc0
0140
| [544627.046790] 76e0: 00c1adc0 ffc0 00b7c198 ffc0 0001
00c1f1c0 ffc0
| [544627.046792] 7700: 0003 fff47938 ffcf
34947750 ffc6
| [544627.046793] 7720: 000ffe08 ffc0 34947750 ffc6
| [544627.046795] [] el1_irq+0x64/0xc0
| [544627.046798] [] vprintk_emit+0x33c/0x59c
| [544627.046801] [] dev_vprintk_emit+0xc8/0x204
| [544627.046802] [] dev_printk_emit+0x74/0x84
| [544627.046804] [] __dev_printk+0x54/0x9c
| [544627.046805] [] dev_err+0x70/0x80
| [544627.046814] [] __nbd_ioctl+0x810/0x944 [nbd]
| [544627.046817] [] nbd_ioctl+0x7c/0x228 [nbd]
| [544627.046821] [] blkdev_ioctl+0x1f4/0x770
| [544627.046825] [] block_ioctl+0x50/0x64
| [544627.046829] [] do_vfs_ioctl+0x330/0x5d4
| [544627.046831] [] SyS_ioctl+0x8c/0xa4
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1512185
Title:
qemu-nbd on ARM64 deadlock? Stuck in rt_sigtimedwait([BUS ALRM IO],
..) and futex(0x7f749ec230, FUTEX_WAIT, ...)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1512185/+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 1512185] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1512185/+attachment/4510819/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1512185 Title: qemu-nbd on ARM64 deadlock? Stuck in rt_sigtimedwait([BUS ALRM IO], ..) and futex(0x7f749ec230, FUTEX_WAIT, ...) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1512185/+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 1512185] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1512185/+attachment/4510815/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1512185 Title: qemu-nbd on ARM64 deadlock? Stuck in rt_sigtimedwait([BUS ALRM IO], ..) and futex(0x7f749ec230, FUTEX_WAIT, ...) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1512185/+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 1512185] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1512185/+attachment/4510811/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1512185 Title: qemu-nbd on ARM64 deadlock? Stuck in rt_sigtimedwait([BUS ALRM IO], ..) and futex(0x7f749ec230, FUTEX_WAIT, ...) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1512185/+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 1512185] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1512185/+attachment/4510821/+files/WifiSyslog.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1512185 Title: qemu-nbd on ARM64 deadlock? Stuck in rt_sigtimedwait([BUS ALRM IO], ..) and futex(0x7f749ec230, FUTEX_WAIT, ...) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1512185/+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 1512185] Re: qemu-nbd on ARM64 deadlock? Stuck in rt_sigtimedwait([BUS ALRM IO], ..) and futex(0x7f749ec230, FUTEX_WAIT, ...)
apport information
** Also affects: linux-meta-lts-vivid (Ubuntu)
Importance: Undecided
Status: New
** Tags added: apport-collected trusty uec-images
** Description changed:
Hi,
We're seeing this often on our HP Moonshot ARM64 nova-compute nodes
where qemu-nbd processes would lock up. At the same time, there's also a
bunch of kernel spew as follows:
| [605282.018238] block nbd3: Attempted send on closed socket
| [605282.018242] block nbd3: Attempted send on closed socket
| [605282.018245] block nbd3: Attempted send on closed socket
| [605282.018249] block nbd3: Attempted send on closed socket
swirlix01:
| hloeung@swirlix01:~$ uname -a
| Linux swirlix01 3.19.0-30-generic #34~14.04.1-Ubuntu SMP Fri Oct 2 22:15:46
UTC 2015 aarch64 aarch64 aarch64 GNU/Linux
| hloeung@swirlix01:~$ ps afx | grep qe\\mu-nbd
| 27782 ?Ssl0:00 /usr/bin/qemu-nbd -c /dev/nbd10
/var/lib/nova/instances/ba50751e-56d7-4bc4-8742-1193fe7a138e/disk
| hloeung@swirlix01:~$ sudo cat /proc/$(ps afx | grep qe\\mu-nbd | awk '{
print $1 }')/stack
| [] __switch_to+0x74/0x8c
| [] futex_wait_queue_me+0xf4/0x184
| [] futex_wait+0x154/0x24c
| [] do_futex+0x1a0/0x9ec
| [] SyS_futex+0x98/0x1cc
| [] el0_svc_naked+0x20/0x28
| [] 0x
swirlix08:
| hloeung@swirlix08:~$ uname -a
| Linux swirlix08 3.19.0-31-generic #36~14.04.1-Ubuntu SMP Thu Oct 8 10:50:10
UTC 2015 aarch64 aarch64 aarch64 GNU/Linux
| hloeung@swirlix08:~$ ps afx | grep qe\\mu-nbd
| 31976 ?Ssl0:00 /usr/bin/qemu-nbd -c /dev/nbd6
/var/lib/nova/instances/92ceb061-2ea4-4212-be20-ab0ded6eb3cd/disk
| hloeung@swirlix08:~$ sudo cat /proc/$(ps afx | grep qe\\mu-nbd | awk '{
print $1 }')/stack
| [] __switch_to+0x74/0x8c
| [] futex_wait_queue_me+0xf4/0x184
| [] futex_wait+0x154/0x24c
| [] do_futex+0x1a0/0x9ec
| [] SyS_futex+0x98/0x1cc
| [] el0_svc_naked+0x20/0x28
| [] 0x
swirlix11:
| hloeung@swirlix11:~$ uname -a
| Linux swirlix11 3.19.0-31-generic #36~14.04.1-Ubuntu SMP Thu Oct 8 10:50:10
UTC 2015 aarch64 aarch64 aarch64 GNU/Linux
| hloeung@swirlix11:~$ ps afx | grep qe\\mu-nbd
| 18149 ?Ssl0:00 /usr/bin/qemu-nbd -c /dev/nbd3
/var/lib/nova/instances/84cac137-c1e4-46ac-894a-efcd55ef7e05/disk
| hloeung@swirlix11:~$ sudo cat /proc/$(ps afx | grep qe\\mu-nbd | awk '{
print $1 }'/stack
| hloeung@swirlix11:~$ sudo cat /proc/$(ps afx | grep qe\\mu-nbd | awk '{
print $1 }')/stack
| [] __switch_to+0x74/0x8c
| [] futex_wait_queue_me+0xf4/0x184
| [] futex_wait+0x154/0x24c
| [] do_futex+0x1a0/0x9ec
| [] SyS_futex+0x98/0x1cc
| [] el0_svc_naked+0x20/0x28
| [] 0x
| hloeung@swirlix11:~$ sudo strace -f -p 18149
| Process 18149 attached with 3 threads
| [pid 18150] rt_sigtimedwait([BUS ALRM IO], NULL, NULL, 8
| [pid 18149] futex(0x7f749ec230, FUTEX_WAIT, 18152, NULL
| ... (hangs here) ...
We're using the QEMU package backported from Vivid as per LP:1457639
| hloeung@swirlix11:~$ apt-cache policy qemu-utils
| qemu-utils:
| Installed: 1:2.2+dfsg-5expubuntu9.5+bug1457639~ubuntu14.04.1
| Candidate: 1:2.2+dfsg-5expubuntu9.5+bug1457639~ubuntu14.04.1
| Version table:
| *** 1:2.2+dfsg-5expubuntu9.5+bug1457639~ubuntu14.04.1 0
| 500
http://ppa.launchpad.net/canonical-is-sa/arm64-infra-workarounds/ubuntu/
trusty/main arm64 Packages
- I'm also not sure if this is related to LP:1505564, which is for
- amd64/x86_64.
+ I'm also not sure if this is related to LP:1505564, which is for amd64/x86_64.
+ ---
+ AlsaDevices:
+ total 0
+ crw-rw 1 root audio 116, 1 Oct 25 17:42 seq
+ crw-rw 1 root audio 116, 33 Oct 25 17:42 timer
+ AplayDevices: Error: [Errno 2] No such file or directory
+ ApportVersion: 2.14.1-0ubuntu3.18
+ Architecture: arm64
+ ArecordDevices: Error: [Errno 2] No such file or directory
+ AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
+ CRDA: Error: [Errno 2] No such file or directory
+ DistroRelease: Ubuntu 14.04
+ Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize
libusb: -99
+ Package: qemu (not installed)
+ PciMultimedia:
+
+ ProcEnviron:
+ TERM=xterm
+ PATH=(custom, no user)
+ XDG_RUNTIME_DIR=
+ LANG=en_GB
+ SHELL=/bin/bash
+ ProcFB:
+
+ ProcKernelCmdLine: console=ttyS0,9600n8r ro
+ ProcVersionSignature: Ubuntu 3.19.0-31.36~14.04.1-generic 3.19.8-ckt7
+ RfKill: Error: [Errno 2] No such file or directory
+ Tags: trusty uec-images trusty uec-images
+ Uname: Linux 3.19.0-31-generic aarch64
+ UnreportableReason: This is not an official Ubuntu package. Please remove any
third party package and try again.
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm
+ _MarkForUpload: True
** Attachment added: "BootDmesg.txt"
https://bugs.launchpad.net/bugs/1512185/+attachment/4510810/+files/BootDmesg.txt
--
You
[Bug 1512185] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1512185/+attachment/4510814/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1512185 Title: qemu-nbd on ARM64 deadlock? Stuck in rt_sigtimedwait([BUS ALRM IO], ..) and futex(0x7f749ec230, FUTEX_WAIT, ...) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1512185/+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 1512185] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1512185/+attachment/4510816/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1512185 Title: qemu-nbd on ARM64 deadlock? Stuck in rt_sigtimedwait([BUS ALRM IO], ..) and futex(0x7f749ec230, FUTEX_WAIT, ...) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1512185/+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 1512185] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1512185/+attachment/4510817/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1512185 Title: qemu-nbd on ARM64 deadlock? Stuck in rt_sigtimedwait([BUS ALRM IO], ..) and futex(0x7f749ec230, FUTEX_WAIT, ...) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1512185/+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 1512185] RelatedPackageVersions.txt
apport information ** Attachment added: "RelatedPackageVersions.txt" https://bugs.launchpad.net/bugs/1512185/+attachment/4510818/+files/RelatedPackageVersions.txt -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1512185 Title: qemu-nbd on ARM64 deadlock? Stuck in rt_sigtimedwait([BUS ALRM IO], ..) and futex(0x7f749ec230, FUTEX_WAIT, ...) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1512185/+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 1512185] KvmCmdLine.txt
apport information ** Attachment added: "KvmCmdLine.txt" https://bugs.launchpad.net/bugs/1512185/+attachment/4510813/+files/KvmCmdLine.txt -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1512185 Title: qemu-nbd on ARM64 deadlock? Stuck in rt_sigtimedwait([BUS ALRM IO], ..) and futex(0x7f749ec230, FUTEX_WAIT, ...) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1512185/+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 1512185] UdevLog.txt
apport information ** Attachment added: "UdevLog.txt" https://bugs.launchpad.net/bugs/1512185/+attachment/4510820/+files/UdevLog.txt -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1512185 Title: qemu-nbd on ARM64 deadlock? Stuck in rt_sigtimedwait([BUS ALRM IO], ..) and futex(0x7f749ec230, FUTEX_WAIT, ...) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1512185/+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 1512185] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1512185/+attachment/4510812/+files/IwConfig.txt -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1512185 Title: qemu-nbd on ARM64 deadlock? Stuck in rt_sigtimedwait([BUS ALRM IO], ..) and futex(0x7f749ec230, FUTEX_WAIT, ...) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1512185/+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 1512185] [NEW] qemu-nbd on ARM64 deadlock? Stuck in rt_sigtimedwait([BUS ALRM IO], ..) and futex(0x7f749ec230, FUTEX_WAIT, ...)
Public bug reported:
Hi,
We're seeing this often on our HP Moonshot ARM64 nova-compute nodes
where qemu-nbd processes would lock up. At the same time, there's also a
bunch of kernel spew as follows:
| [605282.018238] block nbd3: Attempted send on closed socket
| [605282.018242] block nbd3: Attempted send on closed socket
| [605282.018245] block nbd3: Attempted send on closed socket
| [605282.018249] block nbd3: Attempted send on closed socket
swirlix01:
| hloeung@swirlix01:~$ uname -a
| Linux swirlix01 3.19.0-30-generic #34~14.04.1-Ubuntu SMP Fri Oct 2 22:15:46
UTC 2015 aarch64 aarch64 aarch64 GNU/Linux
| hloeung@swirlix01:~$ ps afx | grep qe\\mu-nbd
| 27782 ?Ssl0:00 /usr/bin/qemu-nbd -c /dev/nbd10
/var/lib/nova/instances/ba50751e-56d7-4bc4-8742-1193fe7a138e/disk
| hloeung@swirlix01:~$ sudo cat /proc/$(ps afx | grep qe\\mu-nbd | awk '{ print
$1 }')/stack
| [] __switch_to+0x74/0x8c
| [] futex_wait_queue_me+0xf4/0x184
| [] futex_wait+0x154/0x24c
| [] do_futex+0x1a0/0x9ec
| [] SyS_futex+0x98/0x1cc
| [] el0_svc_naked+0x20/0x28
| [] 0x
swirlix08:
| hloeung@swirlix08:~$ uname -a
| Linux swirlix08 3.19.0-31-generic #36~14.04.1-Ubuntu SMP Thu Oct 8 10:50:10
UTC 2015 aarch64 aarch64 aarch64 GNU/Linux
| hloeung@swirlix08:~$ ps afx | grep qe\\mu-nbd
| 31976 ?Ssl0:00 /usr/bin/qemu-nbd -c /dev/nbd6
/var/lib/nova/instances/92ceb061-2ea4-4212-be20-ab0ded6eb3cd/disk
| hloeung@swirlix08:~$ sudo cat /proc/$(ps afx | grep qe\\mu-nbd | awk '{ print
$1 }')/stack
| [] __switch_to+0x74/0x8c
| [] futex_wait_queue_me+0xf4/0x184
| [] futex_wait+0x154/0x24c
| [] do_futex+0x1a0/0x9ec
| [] SyS_futex+0x98/0x1cc
| [] el0_svc_naked+0x20/0x28
| [] 0x
swirlix11:
| hloeung@swirlix11:~$ uname -a
| Linux swirlix11 3.19.0-31-generic #36~14.04.1-Ubuntu SMP Thu Oct 8 10:50:10
UTC 2015 aarch64 aarch64 aarch64 GNU/Linux
| hloeung@swirlix11:~$ ps afx | grep qe\\mu-nbd
| 18149 ?Ssl0:00 /usr/bin/qemu-nbd -c /dev/nbd3
/var/lib/nova/instances/84cac137-c1e4-46ac-894a-efcd55ef7e05/disk
| hloeung@swirlix11:~$ sudo cat /proc/$(ps afx | grep qe\\mu-nbd | awk '{ print
$1 }'/stack
| hloeung@swirlix11:~$ sudo cat /proc/$(ps afx | grep qe\\mu-nbd | awk '{ print
$1 }')/stack
| [] __switch_to+0x74/0x8c
| [] futex_wait_queue_me+0xf4/0x184
| [] futex_wait+0x154/0x24c
| [] do_futex+0x1a0/0x9ec
| [] SyS_futex+0x98/0x1cc
| [] el0_svc_naked+0x20/0x28
| [] 0x
| hloeung@swirlix11:~$ sudo strace -f -p 18149
| Process 18149 attached with 3 threads
| [pid 18150] rt_sigtimedwait([BUS ALRM IO], NULL, NULL, 8
| [pid 18149] futex(0x7f749ec230, FUTEX_WAIT, 18152, NULL
| ... (hangs here) ...
We're using the QEMU package backported from Vivid as per LP:1457639
| hloeung@swirlix11:~$ apt-cache policy qemu-utils
| qemu-utils:
| Installed: 1:2.2+dfsg-5expubuntu9.5+bug1457639~ubuntu14.04.1
| Candidate: 1:2.2+dfsg-5expubuntu9.5+bug1457639~ubuntu14.04.1
| Version table:
| *** 1:2.2+dfsg-5expubuntu9.5+bug1457639~ubuntu14.04.1 0
| 500
http://ppa.launchpad.net/canonical-is-sa/arm64-infra-workarounds/ubuntu/
trusty/main arm64 Packages
I'm also not sure if this is related to LP:1505564, which is for
amd64/x86_64.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Incomplete
** Affects: qemu (Ubuntu)
Importance: Undecided
Status: New
** Also affects: qemu (Ubuntu)
Importance: Undecided
Status: New
** Description changed:
Hi,
We're seeing this often on our HP Moonshot ARM64 nova-compute nodes
where qemu-nbd processes would lock up. At the same time, there's also a
bunch of kernel spew as follows:
| [605282.018238] block nbd3: Attempted send on closed socket
| [605282.018242] block nbd3: Attempted send on closed socket
| [605282.018245] block nbd3: Attempted send on closed socket
| [605282.018249] block nbd3: Attempted send on closed socket
swirlix01:
| hloeung@swirlix01:~$ uname -a
| Linux swirlix01 3.19.0-30-generic #34~14.04.1-Ubuntu SMP Fri Oct 2 22:15:46
UTC 2015 aarch64 aarch64 aarch64 GNU/Linux
| hloeung@swirlix01:~$ ps afx | grep qe\\mu-nbd
| 27782 ?Ssl0:00 /usr/bin/qemu-nbd -c /dev/nbd10
/var/lib/nova/instances/ba50751e-56d7-4bc4-8742-1193fe7a138e/disk
| hloeung@swirlix01:~$ sudo cat /proc/$(ps afx | grep qe\\mu-nbd | awk '{
print $1 }')/stack
| [] __switch_to+0x74/0x8c
| [] futex_wait_queue_me+0xf4/0x184
| [] futex_wait+0x154/0x24c
| [] do_futex+0x1a0/0x9ec
| [] SyS_futex+0x98/0x1cc
| [] el0_svc_naked+0x20/0x28
| [] 0x
swirlix08:
| hloeung@swirlix08:~$ uname -a
| Linux swirlix08 3.19.0-31-generic #36~14.04.1-Ubuntu SMP Thu Oct 8 10:50:10
UTC 2015 aarch64 aarch64 aarch64 GNU/Linux
| hloeung@swirlix08:~$ ps afx | grep qe\\mu-nbd
| 31976 ?Ssl0:00 /usr/bin/qemu-nbd -c /dev/nbd6
/var/lib/nova/instances/92ceb061-2ea4-4212-be20-ab0ded6eb3cd/disk
| hloeung@swirlix08:~$ sudo cat /proc/$(ps afx | grep
[Bug 1457639] Re: qemu-img qcow2 conversion hangs on large core systems
** No longer affects: qemu (Ubuntu Trusty) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1457639 Title: qemu-img qcow2 conversion hangs on large core systems To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1457639/+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 1457639] Re: qemu-img qcow2 conversion hangs on large core systems
Any chance of having the fixes (or fixed version) backported to trusty? We need this for the HP Moonshot hardware we're using in ScalingStack and am currently working around it with a backport of the version in Vivid[1] [1]https://launchpad.net/~canonical-is-sa/+archive/ubuntu/arm64-infra- workarounds/+packages ** Also affects: qemu (Ubuntu Trusty) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1457639 Title: qemu-img qcow2 conversion hangs on large core systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1457639/+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 1456329] Re: Add UEFI ARM64 support to MAAS
Hi, We need this to support HP Moonshot hardware, can this be backported to 1.7 and SRU'ed to trusty? ** Also affects: maas (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1456329 Title: Add UEFI ARM64 support to MAAS To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1456329/+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 1456329] Re: Add UEFI ARM64 support to MAAS
I should mention for ScalingStack BOS01. At present, we're using a custom package in our PPA[1]. [1]https://launchpad.net/~canonical-is-sa/+archive/ubuntu/arm64-infra- workarounds/+packages -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1456329 Title: Add UEFI ARM64 support to MAAS To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1456329/+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 1501135] [NEW] maas-import-pxe-files fails when MAAS_URL is quoted
Public bug reported: Hi, We're trying to import images using 'maas-import-pxe-files' from the CLI but that seems to fail. On further investigation, it seems that it's because MAAS_URL is enclosed in double quotes and the URL it's trying to get to isn't removing it: | root@somehost:/var/log/maas# tail -f /var/log/apache2/*.log -n 0 & | root@somehost:/var/log/maas# maas-import-pxe-files --sources-file /tmp/tmp.Zl6RvzP3yu/boot-images.yaml | | ==> /var/log/apache2/access.log <== | 10.189.73.2 - - [30/Sep/2015:02:09:42 +] "GET /MAAS\"/rpc/ HTTP/1.0" 404 468 "-" "Twisted PageGetter" | Unhandled Error | Traceback (most recent call last): | Failure: twisted.web.error.Error: 404 Not Found | root@somehost:/var/log/apache2# cat /etc/maas/maas_cluster.conf | # This file is used by the cluster controller startup script: | # `maas-provision start-cluster-controller` | # to get the URL to the MAAS region controller's API. Normally, packaging | # will update this file automatically but it may also be configured manually. | MAAS_URL=http://10.189.73.2/MAAS | CLUSTER_UUID="b8215ed4-9998-45fc-ab74-967a3769" The version of MAAS we're running with is as follows: | root@somehost:/var/log/apache2# apt-cache policy maas | maas: | Installed: 1.7.6+bzr3376-0ubuntu2~14.04.1 | Candidate: 1.7.6+bzr3376-0ubuntu2~14.04.1 | Version table: | *** 1.7.6+bzr3376-0ubuntu2~14.04.1 0 | 500 http://archive.ubuntu.com//ubuntu/ trusty-updates/main amd64 Packages |100 /var/lib/dpkg/status ... and finally the sources file specified: | root@somehost:/var/log/apache2# cat /tmp/tmp.Zl6RvzP3yu/boot-images.yaml | - url: "http://maas.ubuntu.com/images/ephemeral-v2/releases/; | keyring: "/usr/share/keyrings/ubuntu-cloudimage-keyring.gpg" | selections: | - release: "trusty" | arches: ["*"] | subarches: ["generic"] | labels: ["release"] Regards, Haw ** Affects: maas Importance: Undecided Status: New ** Affects: maas (Ubuntu) Importance: Undecided Status: New ** Affects: maas (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: maas (Ubuntu) Importance: Undecided Status: New ** Also affects: maas (Ubuntu Trusty) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1501135 Title: maas-import-pxe-files fails when MAAS_URL is quoted To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1501135/+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 1385851] Re: OpenVPN only supports TLS v1.0
Any chance we could backport support for TLS v1.1+ to Trusty LTS? ** Description changed: Hi Guys, Seems the version of OpenVPN we're carrying only supports and/or is able to negotiate TLS v1.0. The patch below has landed in upstream OpenVPN 2.3.3 and replaces TLSv1_server_method() calls with + SSLv23_server_method() and TLSv1_client_method() with SSLv23_client_method(). https://github.com/OpenVPN/openvpn/commit/4b67f9849ab3efe89268e01afddc7795f38d0f64 For example, when OpenVPN tls-ciphers is configured with TLS v1.2 ciphers: | tls-cipher TLS-ECDHE-RSA-WITH-AES-128-GCM-SHA256:TLS-ECDH-RSA-WITH- AES-128-GCM-SHA256:TLS-DHE-RSA-WITH-AES-128-GCM-SHA256:TLS-DHE-RSA-WITH- AES-128-CBC-SHA Logs shows negotiating at TLS v1.0: | Oct 26 21:58:47 ragnar ovpn-canonical[19470]: Control Channel: TLSv1, cipher TLSv1/SSLv3 DHE-RSA-AES128-SHA, 2048 bit RSA When TLS v1.1 and/or v1.2 ciphers are only specified, sessions fail: | Oct 26 21:58:29 ragnar ovpn-canonical[19259]: TLS_ERROR: BIO read tls_read_plaintext error: error:140830B5:SSL routines:SSL3_CLIENT_HELLO:no ciphers available | Oct 26 21:58:29 ragnar ovpn-canonical[19259]: TLS Error: TLS object - incoming plaintext read error | Oct 26 21:58:29 ragnar ovpn-canonical[19259]: TLS Error: TLS handshake failed | Oct 26 21:58:31 ragnar ovpn-canonical[19470]: TLS: Initial packet from [AF_INET]xxx.xxx.xxx.xxx:1194, sid=eca7ea6c 067ea30f Could we please consider either packaging = 2.3.3 or backporting this patch? Thanks, Haw -- 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/1385851 Title: OpenVPN only supports TLS v1.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvpn/+bug/1385851/+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 1465014] Re: after update still vulnerable against LOGJAM
** Bug watch added: Mozilla Bugzilla #1138554 https://bugzilla.mozilla.org/show_bug.cgi?id=1138554 ** Also affects: nss via https://bugzilla.mozilla.org/show_bug.cgi?id=1138554 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nss in Ubuntu. https://bugs.launchpad.net/bugs/1465014 Title: after update still vulnerable against LOGJAM To manage notifications about this bug go to: https://bugs.launchpad.net/nss/+bug/1465014/+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 1386052] Re: pollen fails to log everytime rsyslog package is upgraded or daemon is bounced
Our pollen charm actually ships out an rsyslog config so it's logged to /var/log/pollen/pollen.log. I can confirm that with the latest updates, it's still logging to /var/log/syslog after rsyslog package update. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to pollen in Ubuntu. https://bugs.launchpad.net/bugs/1386052 Title: pollen fails to log everytime rsyslog package is upgraded or daemon is bounced To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pollen/+bug/1386052/+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 1386052] Re: pollen fails to log everytime rsyslog package is upgraded or daemon is bounced
Ah right, so it seems logging location has changed from /var/log/pollen/pollen.log to /var/log/syslog. ** Tags removed: verification-failed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to pollen in Ubuntu. https://bugs.launchpad.net/bugs/1386052 Title: pollen fails to log everytime rsyslog package is upgraded or daemon is bounced To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pollen/+bug/1386052/+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 1465014] Re: after update still vulnerable against LOGJAM
3.19.2 was just released[1] with: Notable Changes in NSS 3.19.2 Bug 1172128 - In NSS 3.19.1, the minimum key sizes that the freebl cryptographic implementation (part of the softoken cryptographic module used by default by NSS) was willing to generate or use was increased - for RSA keys, to 512 bits, and for DH keys, 1023 bits. This was done as part of a security fix for Bug 1138554 / CVE-2015-4000. Applications that requested or attempted to use keys smaller then the minimum size would fail. However, this change in behaviour unintentionally broke existing NSS applications that need to generate or use such keys, via APIs such as SECKEY_CreateRSAPrivateKey or SECKEY_CreateDHPrivateKey. In NSS 3.19.2, this change in freebl behaviour has been reverted. The fix for Bug 1138554 has been moved to libssl, and will now only affect the minimum keystrengths used in SSL/TLS. Note: Future versions of NSS may increase the minimum keysizes required by the freebl module. Consumers of NSS are strongly encouraged to migrate to stronger cryptographic strengths as soon as possible. [1]https://developer.mozilla.org/en-US/docs/Mozilla/Projects/NSS/NSS_3.19.2_release_notes ** CVE added: http://www.cve.mitre.org/cgi- bin/cvename.cgi?name=2015-4000 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nss in Ubuntu. https://bugs.launchpad.net/bugs/1465014 Title: after update still vulnerable against LOGJAM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1465014/+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 1465014] Re: after update still vulnerable against LOGJAM
https://hg.mozilla.org/projects/nss/rev/ae72d76f8d24 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nss in Ubuntu. https://bugs.launchpad.net/bugs/1465014 Title: after update still vulnerable against LOGJAM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1465014/+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 1465014] Re: after update still vulnerable against LOGJAM
Chrome and Firefox both uses NSS. NSS 3.19.1 contains fixes to mitigate logjam by increasing the minimum modulus size for Diffie-Hellman keys to 1023 bits[1]. Maybe we can look into backporting that. [1]https://developer.mozilla.org/en- US/docs/Mozilla/Projects/NSS/NSS_3.19.1_release_notes ** Also affects: nss (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nss in Ubuntu. https://bugs.launchpad.net/bugs/1465014 Title: after update still vulnerable against LOGJAM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1465014/+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 1197884] Re: apache2.2 SSL has no forward-secrecy: need ECDHE keys
https://bz.apache.org/bugzilla/show_bug.cgi?id=49559#c20 ** Bug watch added: bz.apache.org/bugzilla/ #49559 https://bz.apache.org/bugzilla/show_bug.cgi?id=49559 -- 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/1197884 Title: apache2.2 SSL has no forward-secrecy: need ECDHE keys To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1197884/+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 1197884] Re: apache2.2 SSL has no forward-secrecy: need ECDHE keys
With the recently released logjam attack, can we please revisit and increase the priority for, backporting ECDHE support to apache2.2? https://weakdh.org/ http://openssl.org/blog/blog/2015/05/20/logjam-freak-upcoming-changes/ -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to apache2 in Ubuntu. https://bugs.launchpad.net/bugs/1197884 Title: apache2.2 SSL has no forward-secrecy: need ECDHE keys To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1197884/+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 1197884] Re: apache2.2 SSL has no forward-secrecy: need ECDHE keys
FYI, ECDHE-ECDSA-* cipher suites are only enabled when using ECDSA SSL certificates (with RSA being the most common). -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to apache2 in Ubuntu. https://bugs.launchpad.net/bugs/1197884 Title: apache2.2 SSL has no forward-secrecy: need ECDHE keys To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1197884/+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 1385851] Re: OpenVPN only supports TLS v1.0
** Also affects: openvpn (Ubuntu Vivid) Importance: Medium Status: Confirmed -- 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/1385851 Title: OpenVPN only supports TLS v1.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvpn/+bug/1385851/+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 1386052] Re: pollen fails to log everytime rsyslog package is upgraded or daemon is bounced
Since the update, it seems that pollen isn't logging anymore: | -rw-r--r-- 1 syslog adm 276100 Nov 4 06:36 pollen.log-20141104.xz | -rw-r--r-- 1 syslog adm 5665237 Nov 5 06:23 pollen.log-20141105 | -rw-r--r-- 1 syslog adm 703 Nov 5 23:23 pollen.log | ubuntu@juju-machine-2-lxc-1:/var/log/pollen$ ps afxu | grep pollen root 393 0.0 0.0 283676 12648 ?Ssl Aug05 33:22 /var/lib/juju/tools/unit-pollen-2/jujud unit --data-dir /var/lib/juju --unit-name pollen/2 --debug | ubuntu 26609 0.0 0.0 8120 936 pts/0S+ 23:25 0:00 \_ grep --color=auto pollen pollen 26584 1.3 0.0 105380 3424 ?Ssl 23:23 0:01 pollen -http-port=80 -https-port=443 -device=/dev/random -bytes=64 -cert=/etc/pollen/cert.pem -key=/etc/pollen/key.pem | ubuntu@juju-machine-2-lxc-1:/var/log/pollen$ tail pollen.log | Nov 5 15:30:40 juju-machine-2-lxc-1 sudo: ubuntu : TTY=pts/0 ; PWD=/var/log/pollen ; USER=root ; COMMAND=/usr/sbin/service pollen restart | Nov 5 15:30:40 juju-machine-2-lxc-1 pollen[17216]: pollen starting at [1415201440626942702] | Nov 5 23:23:05 juju-machine-2-lxc-1 sudo: ubuntu : TTY=pts/0 ; PWD=/var/log/pollen ; USER=root ; COMMAND=/usr/sbin/service pollen restart | Nov 5 23:23:05 juju-machine-2-lxc-1 pollen[26540]: pollen starting at [1415229785441503131] | Nov 5 23:23:40 juju-machine-2-lxc-1 sudo: ubuntu : TTY=pts/0 ; PWD=/var/log/pollen ; USER=root ; COMMAND=/usr/sbin/service rsyslog restart | Nov 5 23:23:40 juju-machine-2-lxc-1 pollen[26584]: pollen starting at [1415229820178875333] -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to pollen in Ubuntu. https://bugs.launchpad.net/bugs/1386052 Title: pollen fails to log everytime rsyslog package is upgraded or daemon is bounced To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pollen/+bug/1386052/+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 1386052] [NEW] pollen fails to log everytime rsyslog package is upgraded or daemon is bounced
Public bug reported: Hi, Seems pollen fails to log everytime rsyslog packages are upgraded or rsyslog daemon itself is bounced. There's an alert for it, but I don't think it should be set up in such a way that we need to manually bounce the pollen daemon every time rsyslog packages are upgraded. Could you please look into fixing this so pollen itself does something to reconnect to syslog? Thanks, Haw ** Affects: pollen (Ubuntu) Importance: Undecided Status: New ** Description changed: Hi, Seems pollen fails to log everytime rsyslog packages are upgraded or rsyslog daemon itself is bounced. There's an alert for it, but I don't think it should be set up in such a way that we need to manually bounce the pollen daemon every time rsyslog packages are upgraded. + Could you please look into fixing this so pollen itself does something + to reconnect to syslog? + Thanks, Haw -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to pollen in Ubuntu. https://bugs.launchpad.net/bugs/1386052 Title: pollen fails to log everytime rsyslog package is upgraded or daemon is bounced To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pollen/+bug/1386052/+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 1385851] Re: OpenVPN only supports TLS v1.0
** Tags added: trusty utopic ** Patch added: https://github.com/OpenVPN/openvpn/commit/4b67f9849ab3efe89268e01afddc7795f38d0f64; https://bugs.launchpad.net/ubuntu/+source/openvpn/+bug/1385851/+attachment/4246696/+files/4b67f9849ab3efe89268e01afddc7795f38d0f64.patch ** Tags added: patch-accepted-upstream -- 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/1385851 Title: OpenVPN only supports TLS v1.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvpn/+bug/1385851/+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 1385851] [NEW] OpenVPN only supports TLS v1.0
Public bug reported: Hi Guys, Seems the version of OpenVPN we're carrying only supports and/or is able to negotiate TLS v1.0. The patch below has landed in upstream OpenVPN 2.3.3 and replaces TLSv1_server_method() calls with SSLv23_client_method(). https://github.com/OpenVPN/openvpn/commit/4b67f9849ab3efe89268e01afddc7795f38d0f64 For example, when OpenVPN tls-ciphers is configured with TLS v1.2 ciphers: | tls-cipher TLS-ECDHE-RSA-WITH-AES-128-GCM-SHA256:TLS-ECDH-RSA-WITH- AES-128-GCM-SHA256:TLS-DHE-RSA-WITH-AES-128-GCM-SHA256:TLS-DHE-RSA-WITH- AES-128-CBC-SHA Logs shows negotiating at TLS v1.0: | Oct 26 21:58:47 ragnar ovpn-canonical[19470]: Control Channel: TLSv1, cipher TLSv1/SSLv3 DHE-RSA-AES128-SHA, 2048 bit RSA When TLS v1.1 and/or v1.2 ciphers are only specified, sessions fail: | Oct 26 21:58:29 ragnar ovpn-canonical[19259]: TLS_ERROR: BIO read tls_read_plaintext error: error:140830B5:SSL routines:SSL3_CLIENT_HELLO:no ciphers available | Oct 26 21:58:29 ragnar ovpn-canonical[19259]: TLS Error: TLS object - incoming plaintext read error | Oct 26 21:58:29 ragnar ovpn-canonical[19259]: TLS Error: TLS handshake failed | Oct 26 21:58:31 ragnar ovpn-canonical[19470]: TLS: Initial packet from [AF_INET]xxx.xxx.xxx.xxx:1194, sid=eca7ea6c 067ea30f Could we please consider either packaging = 2.3.3 or backporting this patch? Thanks, Haw ** Affects: openvpn (Ubuntu) Importance: Undecided Status: New ** Affects: openvpn (Ubuntu Trusty) Importance: Undecided Status: New ** Affects: openvpn (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: openvpn (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: openvpn (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: openvpn (Ubuntu Vivid) Importance: Undecided Status: New ** Description changed: Hi Guys, Seems the version of OpenVPN we're carrying only supports and/or is able to negotiate TLS v1.0. The patch below has landed in OpenVPN 2.3.3 and replaces TLSv1_server_method() calls with SSLv23_client_method(). https://github.com/OpenVPN/openvpn/commit/4b67f9849ab3efe89268e01afddc7795f38d0f64 + E.g., when OpenVPN tls-ciphers is configured with TLS v1.2 ciphers: + + | tls-cipher TLS-ECDHE-RSA-WITH-AES-128-GCM-SHA256:TLS-ECDH-RSA-WITH- + AES-128-GCM-SHA256:TLS-DHE-RSA-WITH-AES-128-GCM-SHA256:TLS-DHE-RSA-WITH- + AES-128-CBC-SHA + + Logs shows negotiating at TLS v1.0: + + | Oct 26 21:58:47 ragnar ovpn-canonical[19470]: Control Channel: TLSv1, + cipher TLSv1/SSLv3 DHE-RSA-AES128-SHA, 2048 bit RSA + Could we please consider either packaging = 2.3.3 or backporting this patch? - Thanks, Haw ** No longer affects: openvpn (Ubuntu Vivid) -- 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/1385851 Title: OpenVPN only supports TLS v1.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvpn/+bug/1385851/+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 1385851] Re: OpenVPN only supports TLS v1.0
** Description changed: Hi Guys, Seems the version of OpenVPN we're carrying only supports and/or is able - to negotiate TLS v1.0. The patch below has landed in OpenVPN 2.3.3 and - replaces TLSv1_server_method() calls with SSLv23_client_method(). + to negotiate TLS v1.0. The patch below has landed in upstream OpenVPN + 2.3.3 and replaces TLSv1_server_method() calls with + SSLv23_client_method(). https://github.com/OpenVPN/openvpn/commit/4b67f9849ab3efe89268e01afddc7795f38d0f64 - E.g., when OpenVPN tls-ciphers is configured with TLS v1.2 ciphers: + For example, when OpenVPN tls-ciphers is configured with TLS v1.2 + ciphers: | tls-cipher TLS-ECDHE-RSA-WITH-AES-128-GCM-SHA256:TLS-ECDH-RSA-WITH- AES-128-GCM-SHA256:TLS-DHE-RSA-WITH-AES-128-GCM-SHA256:TLS-DHE-RSA-WITH- AES-128-CBC-SHA Logs shows negotiating at TLS v1.0: | Oct 26 21:58:47 ragnar ovpn-canonical[19470]: Control Channel: TLSv1, cipher TLSv1/SSLv3 DHE-RSA-AES128-SHA, 2048 bit RSA + When TLS v1.1 and/or v1.2 ciphers are only specified, sessions fail: + + | Oct 26 21:58:29 ragnar ovpn-canonical[19259]: TLS_ERROR: BIO read tls_read_plaintext error: error:140830B5:SSL routines:SSL3_CLIENT_HELLO:no ciphers available + | Oct 26 21:58:29 ragnar ovpn-canonical[19259]: TLS Error: TLS object - incoming plaintext read error + | Oct 26 21:58:29 ragnar ovpn-canonical[19259]: TLS Error: TLS handshake failed + | Oct 26 21:58:31 ragnar ovpn-canonical[19470]: TLS: Initial packet from [AF_INET]xxx.xxx.xxx.xxx:1194, sid=eca7ea6c 067ea30f + Could we please consider either packaging = 2.3.3 or backporting this patch? Thanks, Haw -- 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/1385851 Title: OpenVPN only supports TLS v1.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvpn/+bug/1385851/+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 1381359] Re: [SRU] ship new public cert
Seems I tried to be clever in providing a bundle without the original CA certificate (we're using almost everywhere else). Unfortunately, pollinate is calling curl with --capath /dev/null so we need to include this. I've created MP:239160 to fix this. Tested as follows: $ curl -A 'pollinate/4.8-0ubuntu1 curl/7.37.1-1ubuntu3 Ubuntu/14.10 GNU/Linux/3.16.0-23-generic/x86_64' -o- -v --trace-time --connect-timeout 3 --max-time 3 --cacert missing-ca-certificate/entropy.ubuntu.com.pem --capath /dev/null https://entropy.ubuntu.com/ | 09:16:55.592055 * Hostname was NOT found in DNS cache | 09:16:55.596308 * Trying 91.189.94.50... | 09:16:55.925350 * Connected to entropy.ubuntu.com (91.189.94.50) port 443 (#0) | 09:16:55.925950 * successfully set certificate verify locations: | 09:16:55.926012 * CAfile: missing-ca-certificate/entropy.ubuntu.com.pem | CApath: /dev/null | 09:16:55.926126 * SSLv3, TLS handshake, Client hello (1): | 09:16:56.261897 * SSLv3, TLS handshake, Server hello (2): | 09:16:56.273468 * SSLv3, TLS handshake, CERT (11): | 09:16:56.274152 * SSLv3, TLS handshake, Server key exchange (12): | 09:16:56.274321 * SSLv3, TLS handshake, Server finished (14): | 09:16:56.284401 * SSLv3, TLS handshake, Client key exchange (16): | 09:16:56.284483 * SSLv3, TLS change cipher, Client hello (1): | 09:16:56.284605 * SSLv3, TLS handshake, Finished (20): | 09:16:56.628377 * SSLv3, TLS change cipher, Client hello (1): | 09:16:56.628494 * SSLv3, TLS handshake, Finished (20): | 09:16:56.628555 * SSL connection using TLSv1.2 / DHE-RSA-AES128-GCM-SHA256 | 09:16:56.628606 * Server certificate: | 09:16:56.628656 *subject: OU=Domain Control Validated; CN=entropy.ubuntu.com | 09:16:56.628702 *start date: 2014-10-14 23:21:25 GMT | 09:16:56.628748 *expire date: 2015-10-15 16:10:53 GMT | 09:16:56.628807 *subjectAltName: entropy.ubuntu.com matched | 09:16:56.628863 *issuer: C=US; ST=Arizona; L=Scottsdale; O=GoDaddy.com, Inc.; OU=http://certs.godaddy.com/repository/; CN=Go Daddy Secure Certificate Authority - G2 | 09:16:56.628909 *SSL certificate verify ok. | 09:16:56.628981 GET / HTTP/1.1 | 09:16:56.628981 User-Agent: pollinate/4.8-0ubuntu1 curl/7.37.1-1ubuntu3 Ubuntu/14.10 GNU/Linux/3.16.0-23-generic/x86_64 | 09:16:56.628981 Host: entropy.ubuntu.com | 09:16:56.628981 Accept: */* | 09:16:56.628981 | 09:16:56.968210 * HTTP 1.0, assume close after body | 09:16:56.968290 HTTP/1.0 400 Bad Request | 09:16:56.968334 Content-Type: text/plain; charset=utf-8 | 09:16:56.968375 Content-Length: 162 | 09:16:56.968417 Date: Tue, 21 Oct 2014 22:16:57 GMT | 09:16:56.968459 X-Cache: MISS from localhost | 09:16:56.968501 X-Cache-Lookup: MISS from localhost:3128 | 09:16:56.968544 Via: 1.0 localhost (squid/3.1.19) | 09:16:56.968587 * HTTP/1.0 connection set to keep alive! | 09:16:56.968628 Connection: keep-alive | 09:16:56.968670 Please use the pollinate client. 'sudo apt-get install pollinate' or download from: https://bazaar.launchpad.net/~pollinate/pollinate/trunk/view/head:/pollinate | 09:16:56.968739 * Connection #0 to host entropy.ubuntu.com left intact Once again, I am really sorry. ** Branch linked: lp:~hloeung/pollinate/missing-ca-certificate -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to pollinate in Ubuntu. https://bugs.launchpad.net/bugs/1381359 Title: [SRU] ship new public cert To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pollinate/+bug/1381359/+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 1197884] Re: apache2.2 SSL has no forward-secrecy: need ECDHE keys
** Changed in: apache2 (Ubuntu Precise) Importance: Undecided = Wishlist -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to apache2 in Ubuntu. https://bugs.launchpad.net/bugs/1197884 Title: apache2.2 SSL has no forward-secrecy: need ECDHE keys To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1197884/+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 1197884] Re: apache2.2 SSL has no forward-secrecy: need ECDHE keys
** Changed in: apache2 (Ubuntu Precise) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to apache2 in Ubuntu. https://bugs.launchpad.net/bugs/1197884 Title: apache2.2 SSL has no forward-secrecy: need ECDHE keys To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1197884/+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 1078213] Re: logs are not logrotated
Err, it's .1 because I manually rotated them -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju in Ubuntu. https://bugs.launchpad.net/bugs/1078213 Title: logs are not logrotated To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1078213/+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 1078213] Re: logs are not logrotated
ubuntu@juju-prod-XX-YYY-machine-0:/var/log/juju$ ls -la total 19790064 drwxr-xr-x 2 syslog adm 4096 Oct 2 07:33 . drwxr-xr-x 11 root root 4096 Oct 2 06:38 .. -rw-r--r-- 1 syslog adm11719171973 Oct 2 07:33 all-machines.log.1 -rw--- 1 syslog syslog 879 Aug 18 20:17 ca-cert.pem -rw-r--r-- 1 root root 1757 Oct 2 07:33 machine-0.log -rw-r--r-- 1 root root8545817300 Oct 2 07:32 machine-0.log.1 -rw--- 1 syslog syslog 830 Aug 18 20:17 rsyslog-cert.pem -rw--- 1 syslog syslog 887 Aug 18 20:17 rsyslog-key.pem u machines: 0: agent-state: started agent-version: 1.18.4.1 dns-name: XXX.XXX.XXX.XXX instance-id: 542c922e-a61d-4062-8efe-54eed8b9b7b8 instance-state: ACTIVE series: precise hardware: arch=amd64 cpu-cores=2 mem=4096M root-disk=51200M -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju in Ubuntu. https://bugs.launchpad.net/bugs/1078213 Title: logs are not logrotated To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1078213/+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 1316404] [NEW] MAAS from cloud-tools-next on precise fails because python-amqp too new
Public bug reported: Hi, We're testing MAAS 1.5 on precise using the cloud-tools-next pocket in the cloud archives. It seems that python-amqp seems too new and MAAS celery services fail because of this: $ sudo service maas-cluster-celery start maas-cluster-celery start/running, process 15005 hloeung@mabolo:/var/log/upstart$ == maas-cluster-celery.log == Traceback (most recent call last): File /usr/bin/celeryd, line 5, in module from pkg_resources import load_entry_point File /usr/lib/python2.7/dist-packages/pkg_resources.py, line 2711, in module parse_requirements(__requires__), Environment() File /usr/lib/python2.7/dist-packages/pkg_resources.py, line 584, in resolve raise DistributionNotFound(req) pkg_resources.DistributionNotFound: amqp=1.0.12,1.1.0 $ dpkg -l | grep amqp ii python-amqp 1.3.3-1ubuntu1~ctools0Low-level AMQP client Downgrading to 1.0.12-0ubuntu1~cloud0 fixes this. Regards, Haw ** Affects: maas Importance: Undecided Status: New ** Affects: maas (Ubuntu) Importance: Undecided Status: New ** Also affects: maas (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1316404 Title: MAAS from cloud-tools-next on precise fails because python-amqp too new To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1316404/+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 1304777] [NEW] entropy.ubuntu.com SSL certificate needs to be updated
Public bug reported: Hi, It seems pollinate ships out SSL certificate for entropy.ubuntu.com. Due to the recent OpenSSL Heartbleed Bug, we've re-keyed the entropy.ubuntu.com certificate and updated so that the service now uses the new certificate/key. Could you please update the pollinate package with the new certificate and chain certificates? Thanks, Haw ** Affects: pollinate (Ubuntu) Importance: Undecided Status: New ** Tags: canonical-webops ** Tags added: canonical-sysadmins ** Tags removed: canonical-sysadmins ** Tags added: canonical-webops -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to pollinate in Ubuntu. https://bugs.launchpad.net/bugs/1304777 Title: entropy.ubuntu.com SSL certificate needs to be updated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pollinate/+bug/1304777/+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 1088720] Re: facter virtual runs lspci unconditionally
Robie, can we backport the fix to Precise? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to facter in Ubuntu. https://bugs.launchpad.net/bugs/1088720 Title: facter virtual runs lspci unconditionally To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/facter/+bug/1088720/+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 1028268] Re: Bareword dns domain makes facter return incorrect info
Looks like this is fixed in facter-1.7.0-1ubuntu1 (saucy):
| elsif domain = Facter::Util::Resolution.exec('dnsdomainname') \
| and domain =~ /.+/
|
| return_value = domain
In facter-1.6.5-1ubuntu1.2 (precise), it looks like this:
| elsif domain = Facter::Util::Resolution.exec('dnsdomainname') \
| and domain =~ /.+\..+/
|
| domain
Regards,
Haw
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to facter in Ubuntu.
https://bugs.launchpad.net/bugs/1028268
Title:
Bareword dns domain makes facter return incorrect info
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/facter/+bug/1028268/+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 1129720] Re: juju instances not including the default security group
** Also affects: juju-core Importance: Undecided Status: New ** Also affects: juju-core (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1129720 Title: juju instances not including the default security group To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1129720/+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 924105] Re: integer out of range errors for fact_values
This happened again today. -- 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/924105 Title: integer out of range errors for fact_values To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/924105/+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 995719] Re: process_name.rb removed in 2.7.11 but still provided by puppet-common
Hi Dave, The package in precise-proposed looks good to me: ubuntu@hloeung-test:~$ apt-cache policy puppet-common puppet-common: Installed: 2.7.11-1ubuntu2.5 Candidate: 2.7.11-1ubuntu2.5 ubuntu@hloeung-test:~$ ls -la /usr/lib/ruby/1.8/puppet/util/instrumentation/listeners total 16 drwxr-xr-x 2 root root 4096 Oct 14 01:15 . drwxr-xr-x 3 root root 4096 Oct 14 01:15 .. -rw-r--r-- 1 root root 637 Oct 13 21:32 log.rb -rw-r--r-- 1 root root 810 Oct 13 21:32 performance.rb ubuntu@hloeung-test:~$ Thanks, Haw ** Tags removed: verification-needed ** Tags added: verification-done -- 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/995719 Title: process_name.rb removed in 2.7.11 but still provided by puppet-common To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/995719/+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 995719] Re: process_name.rb removed in 2.7.11 but still provided by puppet-common
Robie, Marked as Fix Released as requested. What about for Precise? Are we going to backport the fix to Precise? In IS, we currently have puppet ensure that the file is absent / deleted. Regards, Haw ** Changed in: puppet (Ubuntu) Status: Confirmed = 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/995719 Title: process_name.rb removed in 2.7.11 but still provided by puppet-common To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/995719/+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 1227252] Re: Upgrade from precise to precise SRU maas unconditionally disabled system DHCP
** Also affects: maas Importance: Undecided Status: New ** Changed in: maas Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1227252 Title: Upgrade from precise to precise SRU maas unconditionally disabled system DHCP To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1227252/+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 1072813] Re: puppetd hangs/slow downs - already fixed in upstream
*** This bug is a duplicate of bug 995719 *** https://bugs.launchpad.net/bugs/995719 ** This bug has been marked a duplicate of bug 995719 process_name.rb removed in 2.7.11 but still provided by puppet-common -- 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/1072813 Title: puppetd hangs/slow downs - already fixed in upstream To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1072813/+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 1198251] Re: zookeeper package should include logrotate config for /var/log/zookeeper
James,
Looking at one of our bootstrap nodes, it seems we're using the default
shipped with Precise:
ii zookeeper 3.3.5+dfsg1-1ubuntu1
High-performance coordination service for distributed applications
/etc/zookeeper/conf/log4j.properties:
#
# Add ROLLINGFILE to rootLogger to get log file output
#Log DEBUG level and above messages to a log file
log4j.appender.ROLLINGFILE=org.apache.log4j.RollingFileAppender
log4j.appender.ROLLINGFILE.Threshold=DEBUG
log4j.appender.ROLLINGFILE.File=${zookeeper.log.dir}/zookeeper.log
# Max log file size of 10MB
log4j.appender.ROLLINGFILE.MaxFileSize=10MB
# uncomment the next line to limit number of backup files
#log4j.appender.ROLLINGFILE.MaxBackupIndex=10
log4j.appender.ROLLINGFILE.layout=org.apache.log4j.PatternLayout
log4j.appender.ROLLINGFILE.layout.ConversionPattern=%d{ISO8601} - %-5p
[%t:%C{1}@%L] - %m%n
Seems MaxBackupIndex is commented out by default?
Regards,
Haw
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to zookeeper in Ubuntu.
https://bugs.launchpad.net/bugs/1198251
Title:
zookeeper package should include logrotate config for
/var/log/zookeeper
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zookeeper/+bug/1198251/+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 1178506] Re: Cannot switch between juju-0.7 and juju-core
** Project changed: juju-core = juju-core (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1178506 Title: Cannot switch between juju-0.7 and juju-core To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1178506/+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 1178506] Re: Cannot switch between juju-0.7 and juju-core
** Changed in: juju-core (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1178506 Title: Cannot switch between juju-0.7 and juju-core To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1178506/+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 1129735] [NEW] nova --debug fails with ERROR: hasattr(): attribute name must be string
Public bug reported: $ nova --debug list DEBUG (shell:732) hasattr(): attribute name must be string Traceback (most recent call last): File /usr/lib/python2.7/dist-packages/novaclient/shell.py, line 729, in main OpenStackComputeShell().main(sys.argv[1:]) File /usr/lib/python2.7/dist-packages/novaclient/shell.py, line 620, in main cacert=cacert, timeout=timeout) File /usr/lib/python2.7/dist-packages/novaclient/client.py, line 441, in Client return client_class(*args, **kwargs) File /usr/lib/python2.7/dist-packages/novaclient/v1_1/client.py, line 146, in __init__ cacert=cacert) File /usr/lib/python2.7/dist-packages/novaclient/client.py, line 103, in __init__ if hasattr(requests, logging): TypeError: hasattr(): attribute name must be string ERROR: hasattr(): attribute name must be string $ nova --debug flavor-list DEBUG (shell:732) hasattr(): attribute name must be string Traceback (most recent call last): File /usr/lib/python2.7/dist-packages/novaclient/shell.py, line 729, in main OpenStackComputeShell().main(sys.argv[1:]) File /usr/lib/python2.7/dist-packages/novaclient/shell.py, line 620, in main cacert=cacert, timeout=timeout) File /usr/lib/python2.7/dist-packages/novaclient/client.py, line 441, in Client return client_class(*args, **kwargs) File /usr/lib/python2.7/dist-packages/novaclient/v1_1/client.py, line 146, in __init__ cacert=cacert) File /usr/lib/python2.7/dist-packages/novaclient/client.py, line 103, in __init__ if hasattr(requests, logging): TypeError: hasattr(): attribute name must be string ERROR: hasattr(): attribute name must be string ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: python-novaclient 1:2.11.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-6.13-generic 3.8.0-rc7 Uname: Linux 3.8.0-6-generic x86_64 ApportVersion: 2.8-0ubuntu4 Architecture: amd64 Date: Tue Feb 19 14:24:07 2013 MarkForUpload: True PackageArchitecture: all ProcEnviron: LANGUAGE= TERM=xterm PATH=(custom, no user) LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: python-novaclient UpgradeStatus: Upgraded to raring on 2012-12-06 (74 days ago) ** Affects: python-novaclient (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug raring running-unity -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to python-novaclient in Ubuntu. https://bugs.launchpad.net/bugs/1129735 Title: nova --debug fails with ERROR: hasattr(): attribute name must be string To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-novaclient/+bug/1129735/+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 1043292] Re: Hung agent processes
Might also be bug #995719. Can you try remove process_name.rb ? -- 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/1043292 Title: Hung agent processes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1043292/+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 995719] Re: process_name.rb removed in 2.7.11 but still provided by puppet-common
http://projects.puppetlabs.com/issues/12588 http://projects.puppetlabs.com/issues/12181#note-17 http://projects.puppetlabs.com/issues/12310#note-16 -- 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/995719 Title: process_name.rb removed in 2.7.11 but still provided by puppet-common To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/995719/+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 995719] Re: process_name.rb removed in 2.7.11 but still provided by puppet-common
Confirmed removed in Debian upstream - http://packages.debian.org/sid/all/puppet-common/filelist -- 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/995719 Title: process_name.rb removed in 2.7.11 but still provided by puppet-common To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/995719/+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 995719] [NEW] process_name.rb removed in 2.7.11 but still provided by puppet-common
Public bug reported: Hi, This is related to https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/959597 where upstream has removed process_name.rb in 2.7.11 but it is still packaged and provided by puppet-common. Source tarball for 2.7.10 from puppetlabs: [hloeung@darkon puppet-2.7.10]$ find . -type f -name '*process_name*' ./spec/unit/util/instrumentation/listeners/process_name_spec.rb ./lib/puppet/util/instrumentation/listeners/process_name.rb [hloeung@darkon puppet-2.7.10]$ Source tarball for 2.7.11 from puppetlabs: [hloeung@darkon puppet-2.7.11]$ find . -type f -name '*process_name*' [hloeung@darkon puppet-2.7.11]$ [hloeung@darkon puppet-2.7.10]$ dpkg-query -S /usr/lib/ruby/1.8/puppet/util/instrumentation/listeners/process_name.rb puppet-common: /usr/lib/ruby/1.8/puppet/util/instrumentation/listeners/process_name.rb [hloeung@darkon puppet-2.7.10]$ dpkg -l puppet-common Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Description +++-==-==- ii puppet-common 2.7.11-1ubuntu2 Centralized configuration management ** Affects: puppet (Ubuntu) Importance: Undecided Status: Confirmed -- 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/995719 Title: process_name.rb removed in 2.7.11 but still provided by puppet-common To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/995719/+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 959597] Re: missing parenthesis in process_name.rb produces ruby warnings
See also https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/995719 -- 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/959597 Title: missing parenthesis in process_name.rb produces ruby warnings To manage notifications about this bug go to: https://bugs.launchpad.net/puppet/+bug/959597/+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
