[Bug 1078213] Re: logs are not logrotated
$ du -hs /var/log/juju/ 6.9G/var/log/juju/ System installed on 2014-06-02. -- 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
** Changed in: juju-core Assignee: (unassigned) = Nate Finch (natefinch) ** Changed in: juju-core Status: Triaged = In Progress -- 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 1348142] Re: Please merge nagios-nrpe 2.15-1 (main) from Debian unstable (main)
** Branch linked: lp:ubuntu/utopic-proposed/nagios-nrpe -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nagios-nrpe in Ubuntu. https://bugs.launchpad.net/bugs/1348142 Title: Please merge nagios-nrpe 2.15-1 (main) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nagios-nrpe/+bug/1348142/+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 1346056] Re: Sync python-wsme 0.6-3 (main) from Debian unstable (main)
This bug was fixed in the package python-wsme - 0.6-3 Sponsored for Jackson Doak (noskcaj) --- python-wsme (0.6-3) unstable; urgency=medium * Drop depends on the removed python3-ipaddr if not building in Wheezy, and rely on ipaddress included in python3.3 and later (Closes: #748472). Thanks to Scott Kitterman deb...@kitterman.com for his report and help. -- Thomas Goirand z...@debian.org Wed, 21 May 2014 18:55:35 +0800 ** Changed in: python-wsme (Ubuntu) Status: New = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to python-wsme in Ubuntu. https://bugs.launchpad.net/bugs/1346056 Title: Sync python-wsme 0.6-3 (main) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-wsme/+bug/1346056/+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 1348517] [NEW] Unable to start vsftpd on Ubuntu 14.04 Amazon/EC2
Public bug reported: Fresh install of Ubuntu 14.4 - Ubuntu- trusty-14.04-amd64-server-20140607.1 sudo su apt-get update apt-get install vsftpd edit /etc/vsftpd.conf and added 3 lines listen_port=12345 pasv_min_port=34700 pasv_max_port=34800 service vsftpd start vsftpd not started log on /var/log/syslog Jul 25 07:38:44 ip-1-1-1-1 kernel: [3660071.626254] BUG: Bad page map in process vsftpd pte:8965 pmd:241dd067 Jul 25 07:38:44 ip-1-1-1-1 kernel: [3660071.626275] page:ea00 count:-99 mapcount:-99 mapping: (null) index:0x0 Jul 25 07:38:44 ip-1-1-1-1 kernel: [3660071.626282] page flags: 0x10(dirty) Jul 25 07:38:44 ip-1-1-1-1 kernel: [3660071.626290] addr:7f41cfeb3000 vm_flags:08100071 anon_vma:88000432d380 mapping: (null) index:7f41cfeb3 Jul 25 07:38:44 ip-1-1-1-1 kernel: [3660071.626300] CPU: 0 PID: 22121 Comm: vsftpd Tainted: GB3.13.0-29-generic #53-Ubuntu Jul 25 07:38:44 ip-1-1-1-1 kernel: [3660071.626303] 880004291d80 880004331c70 8171a214 7f41cfeb3000 Jul 25 07:38:44 ip-1-1-1-1 kernel: [3660071.626307] 880004331cb8 81174653 800e15aed965 0007f41cfeb3 Jul 25 07:38:44 ip-1-1-1-1 kernel: [3660071.626310] 8800241dd598 ea00 7f41cfeb3000 7f41cfeb4000 Jul 25 07:38:44 ip-1-1-1-1 kernel: [3660071.626313] Call Trace: Jul 25 07:38:44 ip-1-1-1-1 kernel: [3660071.626324] [8171a214] dump_stack+0x45/0x56 Jul 25 07:38:44 ip-1-1-1-1 kernel: [3660071.626331] [81174653] print_bad_pte+0x1a3/0x250 Jul 25 07:38:44 ip-1-1-1-1 kernel: [3660071.626334] [81176037] unmap_page_range+0x717/0x7f0 Jul 25 07:38:44 ip-1-1-1-1 kernel: [3660071.626337] [81176191] unmap_single_vma+0x81/0xf0 Jul 25 07:38:44 ip-1-1-1-1 kernel: [3660071.626341] [81177209] unmap_vmas+0x49/0x90 Jul 25 07:38:44 ip-1-1-1-1 kernel: [3660071.626344] [811803bc] exit_mmap+0x9c/0x170 Jul 25 07:38:44 ip-1-1-1-1 kernel: [3660071.626349] [8106482c] mmput+0x5c/0x120 Jul 25 07:38:44 ip-1-1-1-1 kernel: [3660071.626353] [81069bbc] do_exit+0x26c/0xa50 Jul 25 07:38:44 ip-1-1-1-1 kernel: [3660071.626358] [8109dd94] ? vtime_account_user+0x54/0x60 Jul 25 07:38:44 ip-1-1-1-1 kernel: [3660071.626364] [8114d62f] ? context_tracking_user_exit+0x4f/0xc0 Jul 25 07:38:44 ip-1-1-1-1 kernel: [3660071.626367] [8106a41f] do_group_exit+0x3f/0xa0 Jul 25 07:38:44 ip-1-1-1-1 kernel: [3660071.626371] [8106a494] SyS_exit_group+0x14/0x20 Jul 25 07:38:44 ip-1-1-1-1 kernel: [3660071.626376] [8172adff] tracesys+0xe1/0xe6 Jul 25 07:38:44 ip-1-1-1-1 kernel: [3660071.626479] BUG: Bad rss-counter state mm:8800042a7880 idx:0 val:-1 Jul 25 07:38:44 ip-1-1-1-1 kernel: [3660071.626489] BUG: Bad rss-counter state mm:8800042a7880 idx:1 val:1 Jul 25 07:38:44 ip-1-1-1-1 kernel: [3660071.661115] BUG: Bad page map in process vsftpd pte:8965 pmd:04336067 Jul 25 07:38:44 ip-1-1-1-1 kernel: [3660071.661135] page:ea00 count:-100 mapcount:-100 mapping: (null) index:0x0 Jul 25 07:38:44 ip-1-1-1-1 kernel: [3660071.661142] page flags: 0x14(referenced|dirty) Jul 25 07:38:44 ip-1-1-1-1 kernel: [3660071.661153] addr:7f8e82b3b000 vm_flags:08100071 anon_vma:88000432dbc0 mapping: (null) index:7f8e82b3b Jul 25 07:38:44 ip-1-1-1-1 kernel: [3660071.661163] CPU: 0 PID: 22125 Comm: vsftpd Tainted: GB3.13.0-29-generic #53-Ubuntu Jul 25 07:38:44 ip-1-1-1-1 kernel: [3660071.661165] 880004291900 880004351c70 8171a214 7f8e82b3b000 Jul 25 07:38:44 ip-1-1-1-1 kernel: [3660071.661169] 880004351cb8 81174653 800e15aed965 0007f8e82b3b Jul 25 07:38:44 ip-1-1-1-1 kernel: [3660071.661172] 8800043369d8 ea00 7f8e82b3b000 7f8e82b3c000 Jul 25 07:38:44 ip-1-1-1-1 kernel: [3660071.661175] Call Trace: Jul 25 07:38:44 ip-1-1-1-1 kernel: [3660071.661187] [8171a214] dump_stack+0x45/0x56 Jul 25 07:38:44 ip-1-1-1-1 kernel: [3660071.661193] [81174653] print_bad_pte+0x1a3/0x250 Jul 25 07:38:44 ip-1-1-1-1 kernel: [3660071.661196] [81176037] unmap_page_range+0x717/0x7f0 Jul 25 07:38:44 ip-1-1-1-1 kernel: [3660071.661200] [81176191] unmap_single_vma+0x81/0xf0 Jul 25 07:38:44 ip-1-1-1-1 kernel: [3660071.661203] [81177209] unmap_vmas+0x49/0x90 Jul 25 07:38:44 ip-1-1-1-1 kernel: [3660071.661206] [811803bc] exit_mmap+0x9c/0x170 Jul 25 07:38:44 ip-1-1-1-1 kernel: [3660071.661211] [8106482c] mmput+0x5c/0x120 Jul 25 07:38:44 ip-1-1-1-1 kernel: [3660071.661214] [81069bbc] do_exit+0x26c/0xa50 Jul 25 07:38:44 ip-1-1-1-1 kernel: [3660071.661219] [8109dd94] ? vtime_account_user+0x54/0x60 Jul 25 07:38:44 ip-1-1-1-1 kernel: [3660071.661226] [8114d62f] ? context_tracking_user_exit+0x4f/0xc0 Jul 25 07:38:44 ip-1-1-1-1 kernel: [3660071.661229] [8106a41f]
[Bug 1325560] Re: kvm virtio netdevs lose network connectivity under enough load
Hi Matt, should these packages be upgraded in host or in kvm vm? Thanks -- 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/1325560 Title: kvm virtio netdevs lose network connectivity under enough load To manage notifications about this bug go to: https://bugs.launchpad.net/libvirt/+bug/1325560/+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 1348551] [NEW] qemu-kvm upstart configuration from qemu-system-x86 relies on binary from qemu-kvm
Public bug reported: qemu-kvm is a transitional package, so can be removed in which case qemu-kvm defaults won't ever get applied: start on runlevel [2345] pre-start script # Silently exit if the package isn't installed anymore if [ ! -e /usr/bin/kvm ]; then exit 0 fi ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: qemu-system-x86 2.0.0+dfsg-2ubuntu1 ProcVersionSignature: User Name 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 Date: Fri Jul 25 09:20:35 2014 SourcePackage: qemu UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: qemu (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty uec-images -- 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/1348551 Title: qemu-kvm upstart configuration from qemu-system-x86 relies on binary from qemu-kvm To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1348551/+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 1325560] Re: kvm virtio netdevs lose network connectivity under enough load
Sorry, see it. Should on host. -- 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/1325560 Title: kvm virtio netdevs lose network connectivity under enough load To manage notifications about this bug go to: https://bugs.launchpad.net/libvirt/+bug/1325560/+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 1348142] Re: Please merge nagios-nrpe 2.15-1 (main) from Debian unstable (main)
This bug was fixed in the package nagios-nrpe - 2.15-1ubuntu1
---
nagios-nrpe (2.15-1ubuntu1) utopic; urgency=low
[ Liam Young ]
LP: #1348142
* Merge from Debian unstable (2.15-1). Remaining changes:
- debian/{rules,control}: Add hardening-includes to gain PIE security
builds.
* Changes gained from Debian:
- 01_nodevrandom-and-docoptions.dpatch: Patch dropped. Debian are
no longer carrying this patch and it does not seem to be needed.
'l' is now listed as a doc option and it seems that using urandom
for seeding srand is unlikely to realistically exhaust a machines
entropy as was mentioned in Debian Bug #333552.
- debian/patches/00list: 04_weird_output.dpatch dropped
- debian/patches/05_pid_privileges.dpatch: Patch now matches debian
- debian/patches/09_noremove_pid.dpatch: Patch now matches debian
nagios-nrpe (2.15-1) unstable; urgency=high
* [f2cea9f] Imported Upstream version 2.15
* [023e909] Disable command-args in nrpe. (Closes: #745272)
* [6369220] Use restorecon to set SE Linux context on $PIDDIR
(Closes: #679241)
* [a484e7d] Switch order of nagios-plugins recommends to prefer -basic.
(Closes: #752243)
* [b1ef043] Don't recommend a core implementation for the plugin
* [16dbf01] Remove obsolete patch
* [694b804] Remove luk from uploaders. (Closes: #719636)
* [28d9004] Remove obsolete patch
* [86ea67e] 08_CVE-2013-1362.dpatch is now obsolete
* [74e3b07] Refresh patches
* [1258ab2] Reword NEWS entry
* [744eec6] configure is buggy: --disable- in fact enables a feautre.
* [eec54b6] Adjust README.Debian for the removal or argument processing
-- Liam Young liam.yo...@canonical.com Thu, 24 Jul 2014 12:39:39 +0100
** Changed in: nagios-nrpe (Ubuntu)
Status: Confirmed = Fix Released
** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2013-1362
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nagios-nrpe in Ubuntu.
https://bugs.launchpad.net/bugs/1348142
Title:
Please merge nagios-nrpe 2.15-1 (main) from Debian unstable (main)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nagios-nrpe/+bug/1348142/+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 1348608] Re: package snmpd 5.4.3~dfsg-2.4ubuntu1.2 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 127
Salut tout le monde, quelqu'un peut-il m'aider à régler ce problème c'est vraiment urgent merci. Débutante en NAgios ** Changed in: net-snmp (Ubuntu) Status: New = Invalid ** Converted to question: https://answers.launchpad.net/ubuntu/+source/net-snmp/+question/252166 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to net-snmp in Ubuntu. https://bugs.launchpad.net/bugs/1348608 Title: package snmpd 5.4.3~dfsg-2.4ubuntu1.2 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 127 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/net-snmp/+bug/1348608/+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 1348608] [NEW] package snmpd 5.4.3~dfsg-2.4ubuntu1.2 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 127
Public bug reported: Je n'arrive pas à désinstaller ou réinstaller le paquet snmpd ProblemType: Package DistroRelease: Ubuntu 12.04 Package: snmpd 5.4.3~dfsg-2.4ubuntu1.2 ProcVersionSignature: Ubuntu 3.2.0-23.36-generic-pae 3.2.14 Uname: Linux 3.2.0-23-generic-pae i686 ApportVersion: 2.0.1-0ubuntu5 AptOrdering: snmpd: Remove Architecture: i386 Date: Tue Jul 22 11:44:19 2014 DpkgTerminalLog: Removing snmpd ... /etc/init.d/snmpd: 25: /etc/default/snmpd: disk: not found invoke-rc.d: initscript snmpd, action stop failed. dpkg: error processing snmpd (--remove): subprocess installed pre-removal script returned error exit status 127 ErrorMessage: subprocess installed pre-removal script returned error exit status 127 InstallationMedia: Ubuntu 12.04 Precise - Build i386 LIVE Binary 20120426-12:41 SourcePackage: net-snmp Title: package snmpd 5.4.3~dfsg-2.4ubuntu1.2 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 127 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: net-snmp (Ubuntu) Importance: Undecided Status: Invalid ** Tags: apport-package i386 precise -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to net-snmp in Ubuntu. https://bugs.launchpad.net/bugs/1348608 Title: package snmpd 5.4.3~dfsg-2.4ubuntu1.2 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 127 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/net-snmp/+bug/1348608/+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 1348608] Re: package snmpd 5.4.3~dfsg-2.4ubuntu1.2 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 127
Salut tout le monde, y'aura pas quelqu'un qui pourra m'aider à fixer ça :/ c'est urgent, HELP !!! -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to net-snmp in Ubuntu. https://bugs.launchpad.net/bugs/1348608 Title: package snmpd 5.4.3~dfsg-2.4ubuntu1.2 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 127 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/net-snmp/+bug/1348608/+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 1331467] Re: [MIR] python-mccabe
Moved to main. ** Changed in: python-mccabe (Ubuntu) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to python-mccabe in Ubuntu. https://bugs.launchpad.net/bugs/1331467 Title: [MIR] python-mccabe To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-mccabe/+bug/1331467/+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 1348551] Re: qemu-kvm upstart configuration from qemu-system-x86 relies on binary from qemu-kvm
qemu-kvm is not a transitional package (check utopic), but obviously this is non-ideal. The sysvinit script checks /dev/kvm instead. That would be fine for newer systems, but older systems where kvm is not auto-loaded at boot would suffer. I'm not sure if we actually support any such systems any more. -- 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/1348551 Title: qemu-kvm upstart configuration from qemu-system-x86 relies on binary from qemu-kvm To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1348551/+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 1348551] Re: qemu-kvm upstart configuration from qemu-system-x86 relies on binary from qemu-kvm
** Changed in: qemu (Ubuntu) Importance: Undecided = Medium ** Changed in: qemu (Ubuntu) Status: New = Triaged -- 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/1348551 Title: qemu-kvm upstart configuration from qemu-system-x86 relies on binary from qemu-kvm To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1348551/+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 1348551] Re: qemu-kvm upstart configuration from qemu-system-x86 relies on binary from qemu-kvm
** Also affects: qemu (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: qemu (Ubuntu Trusty) Importance: Undecided = High ** Changed in: qemu (Ubuntu) Importance: Medium = High -- 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/1348551 Title: qemu-kvm upstart configuration from qemu-system-x86 relies on binary from qemu-kvm To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1348551/+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 1212823] Re: saucy armhf container does not start
** Changed in: qemu (Ubuntu) Status: Fix Committed = Fix Released -- 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/1212823 Title: saucy armhf container does not start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1212823/+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 1348551] Re: qemu-kvm upstart configuration from qemu-system-x86 relies on binary from qemu-kvm
** Description changed: + === + SRU Justification + Impact: users do not get KSM auto-enabled if they only install qemu-system-x86 + Development fix: have the qemu-kvm upstart job run if qemu-system-x86 is installed, not only if kvm is installed + Stable fix: same as devel fix + Test case: sudo apt-get install qemu-system-x86; cat /sys/kernel/mm/ksm/run - this should be 1, but will be 0 with this bug unless qemu-kvm package is installed. + Regression potential: there should be none + === + qemu-kvm is a transitional package, so can be removed in which case qemu-kvm defaults won't ever get applied: start on runlevel [2345] pre-start script # Silently exit if the package isn't installed anymore if [ ! -e /usr/bin/kvm ]; then exit 0 fi ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: qemu-system-x86 2.0.0+dfsg-2ubuntu1 ProcVersionSignature: User Name 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 Date: Fri Jul 25 09:20:35 2014 SourcePackage: qemu 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 qemu in Ubuntu. https://bugs.launchpad.net/bugs/1348551 Title: qemu-kvm upstart configuration from qemu-system-x86 relies on binary from qemu-kvm To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1348551/+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 1348672] [NEW] virsh memtune fails with LXC guests (lxcDomainGetMemoryParameters)
Public bug reported: [ubuntu 14.04 amd64 on Mac Mini, fully up to date] The virsh memtune function (see ftp://libvirt.org/libvirt/virshcmdref/html/sect-memtune.html) completely fails with LXC guests; it looks to be some sort of protocol/ABI problem. $ virsh -c lxc: ... virsh # memtune gold-lxc-20140717 error: Unable to get number of memory parameters error: unsupported flags (0x4) in function lxcDomainGetMemoryParameters Here is the XML for this guest: virsh # dumpxml gold-lxc-20140717 domain type='lxc' id='6265' namegold-lxc-20140717/name uuidb2a02d49-bb1e-4aec-81d1-58910892780e/uuid memory unit='KiB'327680/memory currentMemory unit='KiB'327680/currentMemory vcpu placement='static'1/vcpu resource partition/machine/partition /resource os type arch='x86_64'exe/type init/sbin/init/init /os clock offset='utc'/ on_poweroffdestroy/on_poweroff on_rebootrestart/on_reboot on_crashdestroy/on_crash devices emulator/usr/lib/libvirt/libvirt_lxc/emulator filesystem type='mount' accessmode='passthrough' source dir='/data1/lxc/gold-20140717/rootfs'/ target dir='/'/ /filesystem interface type='bridge' mac address='52:54:5d:00:0a:88'/ source bridge='br-lan'/ target dev='vnet0'/ /interface console type='pty' tty='/dev/pts/1' source path='/dev/pts/1'/ target type='lxc' port='0'/ alias name='console0'/ /console /devices seclabel type='none'/ /domain ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: libvirt-bin 1.2.2-0ubuntu13.1.1 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 Date: Fri Jul 25 14:25:11 2014 InstallationDate: Installed on 2014-07-16 (8 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS Trusty Tahr - Release amd64 (20140416.2) SourcePackage: libvirt UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.libvirt.qemu.conf: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/qemu.conf'] ** Affects: libvirt (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- 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/1348672 Title: virsh memtune fails with LXC guests (lxcDomainGetMemoryParameters) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1348672/+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 1348688] [NEW] LXC does not limit swap usage (memory.memsw.limit_in_bytes missing)
Public bug reported:
(Sorry I'm not sure exactly what package to report this against - kernel
perhaps? libvirt is what I was using to replicate the problem)
Host platform: ubuntu 14.04 amd64, Mac Mini, 16GB RAM.
Short version: create an LXC domain with memtune swap_hard_limit set
in the XML:
domain type='lxc'
namegold-lxc-20140717/name
uuidb2a02d49-bb1e-4aec-81d1-58910892780e/uuid
memory unit='KiB'327680/memory
currentMemory unit='KiB'327680/currentMemory
memtune
swap_hard_limit unit='KiB'131072/swap_hard_limit
/memtune
...
(full version at end of this report)
Now try to start it:
$ virsh -c lxc: start gold-lxc-20140717error: Failed to start domain
gold-lxc-20140717
error: internal error: guest failed to start: Unable to write to
'/sys/fs/cgroup/memory/machine/gold-lxc-20140717.libvirt-lxc/memory.memsw.limit_in_bytes':
No such file or directory
The reason this matters is because otherwise the LXC memory limit
applies only to real RAM used. If the guest exceeds this it can still
use as much swap space as it likes, and is therefore effectively
unlimited (and can happily DoS the swap disk).
Long version:
I created an ubuntu 14.04 i386 VM image using python-vmbuilder,
loopback-mounted it with qemu-nbd, and rsync'd it to create a root
filesystem for an LXC guest.
Then defined a guest using libvirt XML and started it using virsh -c
lxc: start domain (as per XML at end but without the memtune
section). It starts successfully, networking is fine, I can get a
console etc.
Now, the libvirt XML description says the guest's memory limit is 320MB:
memory unit='KiB'327680/memory
currentMemory unit='KiB'327680/currentMemory
and indeed the cgroups setting has been set:
$ cat
/sys/fs/cgroup/memory/machine/gold-lxc-20140717.libvirt-lxc/memory.limit_in_bytes
335544320
However inside the guest I can happily allocate as much memory as I
like, up to just under 4GB, which is the limit for a 32-bit guest.
Here's the test program I ran in the guest (usemem.c):
#include stdlib.h
#include unistd.h
#include stdio.h
int main(void)
{
char *p;
int i,j;
int ok=0, fail=0;
for (i=0; i4096; i++) {
p = malloc(1024*1024);
if (p) {
ok++;
for (j=0; j1024*1024; j++)
p[j] = rand();
}
else
fail++;
}
fprintf(stderr, Done: %d ok, %d fail\n, ok, fail);
sleep(600);
return fail ? 1 : 0;
}
Result from running:
Done: 4076 ok, 20 fail
View from the host:
nsrc@kit1:~/workshop-kit$ ps auxwww | grep usemem | grep -v grep
nsrc 10506 96.1 1.3 4192152 224776 ? S+ 14:41 0:55 ./usemem
$ cat
/sys/fs/cgroup/memory/machine/gold-lxc-20140717.libvirt-lxc/memory.limit_in_bytes
335544320
$ cat
/sys/fs/cgroup/memory/machine/gold-lxc-20140717.libvirt-lxc/memory.max_usage_in_bytes
335544320
$ cat
/sys/fs/cgroup/memory/machine/gold-lxc-20140717.libvirt-lxc/memory.usage_in_bytes
292331520
You can see there's definitely 4GB in use by this process, and yet the
cgroup thinks less than 280MB is in use, which is below the 320MB limit.
However if you look at swap usage in the host while the memory suck
program is running:
$ free
total used free sharedbuffers cached
Mem: 163383003066952 13271348 1684 1355121489268
-/+ buffers/cache:1442172 14896128
Swap: 166789083971248 12707660
and after it has terminated:
$ free
total used free sharedbuffers cached
Mem: 163383002774440 13563860 1684 1355441489188
-/+ buffers/cache:1149708 15188592
Swap: 16678908 5484 16673424
i.e. the LXC guest used nearly 4GB of swap, and then gave it up when it
terminated.
Additional info:
cgroup view from inside the guest:
$ cat /proc/self/cgroup
11:name=systemd:/
10:hugetlb:/
9:perf_event:/machine/gold-lxc-20140717.libvirt-lxc
8:blkio:/machine/gold-lxc-20140717.libvirt-lxc
7:freezer:/machine/gold-lxc-20140717.libvirt-lxc
6:devices:/machine/gold-lxc-20140717.libvirt-lxc
5:memory:/machine/gold-lxc-20140717.libvirt-lxc
4:cpuacct:/machine/gold-lxc-20140717.libvirt-lxc
3:cpu:/machine/gold-lxc-20140717.libvirt-lxc
2:cpuset:/machine/gold-lxc-20140717.libvirt-lxc
cgroup settings visible in the host:
$ ls /sys/fs/cgroup/memory/machine/gold-lxc-20140717.libvirt-lxc/
cgroup.clone_children memory.limit_in_bytes
cgroup.event_controlmemory.max_usage_in_bytes
cgroup.procsmemory.move_charge_at_immigrate
memory.failcnt memory.numa_stat
memory.force_empty memory.oom_control
memory.kmem.failcnt memory.pressure_level
memory.kmem.limit_in_bytes memory.soft_limit_in_bytes
memory.kmem.max_usage_in_bytes memory.stat
memory.kmem.slabinfomemory.swappiness
memory.kmem.tcp.failcnt memory.usage_in_bytes
memory.kmem.tcp.limit_in_bytes
[Bug 1348698] [NEW] libvirtd with lxc: cannot destroy domain (apparmor blocks kill signal)
Public bug reported: Host: ubuntu 14.04 amd64, Mac mini 16GB. * Prepare an Ubuntu 14.04 guest rootfs * Define an LXC instance using libvirt XML (see below) * virsh start -c lxc: domain * virsh destroy -c lxc: domain gives the following error: $ virsh -c lxc: destroy gold-lxc-20140717 error: Failed to destroy domain gold-lxc-20140717 error: Failed to kill process 18636: Permission denied and the following logged in /var/log/syslog on the host: Jul 25 15:21:22 kit1 kernel: [ 7735.523579] type=1400 audit(1406301682.520:40): apparmor=DENIED operation=signal profile=/sbin/dhclient pid=17503 comm=libvirtd requested_mask=receive denied_mask=receive signal=term peer=/usr/sbin/libvirtd Jul 25 15:21:22 kit1 kernel: [ 7735.523756] type=1400 audit(1406301682.520:41): apparmor=DENIED operation=signal profile=/sbin/dhclient pid=17503 comm=libvirtd requested_mask=receive denied_mask=receive signal=term peer=/usr/sbin/libvirtd The guest has an eth0 vnet NIC which is attached to a bridge on the host, and picks up an IP address through DHCP. It appears that libvirtd is being prevented from shutting down this dhclient process by apparmor, and this in turn aborts the whole 'destroy' operation. Workaround: kill the dhclient process by hand, before issuing the virsh destroy. (There is unfortunately no lxc:///session like qemu:///session to bypass libvirtd). Full XML: domain type='lxc' id='16776' namegold-lxc-20140717/name uuidb2a02d49-bb1e-4aec-81d1-58910892780e/uuid memory unit='KiB'327680/memory currentMemory unit='KiB'327680/currentMemory memtune hard_limit unit='KiB'524288/hard_limit /memtune vcpu placement='static'1/vcpu resource partition/machine/partition /resource os type arch='x86_64'exe/type init/sbin/init/init /os clock offset='utc'/ on_poweroffdestroy/on_poweroff on_rebootrestart/on_reboot on_crashdestroy/on_crash devices emulator/usr/lib/libvirt/libvirt_lxc/emulator filesystem type='mount' accessmode='passthrough' source dir='/data1/lxc/gold-20140717/rootfs'/ target dir='/'/ /filesystem interface type='bridge' mac address='52:54:5d:00:0a:88'/ source bridge='br-lan'/ target dev='vnet0'/ /interface console type='pty' tty='/dev/pts/1' source path='/dev/pts/1'/ target type='lxc' port='0'/ alias name='console0'/ /console /devices seclabel type='none'/ /domain ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: libvirt-bin 1.2.2-0ubuntu13.1.1 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 Date: Fri Jul 25 15:18:44 2014 InstallationDate: Installed on 2014-07-16 (8 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS Trusty Tahr - Release amd64 (20140416.2) SourcePackage: libvirt UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.libvirt.qemu.conf: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/qemu.conf'] ** Affects: libvirt (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- 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/1348698 Title: libvirtd with lxc: cannot destroy domain (apparmor blocks kill signal) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1348698/+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 1219658] Re: Wrong image size using rbd backend for libvirt
Rafael, this needs to have an SRU testcase as in: https://wiki.ubuntu.com/StableReleaseUpdates chuck ** Also affects: nova (Ubuntu Trusty) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/1219658 Title: Wrong image size using rbd backend for libvirt To manage notifications about this bug go to: https://bugs.launchpad.net/nova/havana/+bug/1219658/+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 1346528] Re: maas-dhcp fails to install if isc-dhcp-server is not yet fully installed
FWIW, this happened again just now with an earlier (non PPA I guess) version of maas-dhcp: Setting up isc-dhcp-server (4.2.4-7ubuntu12) ... isc-dhcp-server start/running, process 11190 isc-dhcp-server6 stop/pre-start, process 11233 Setting up maas-dhcp (1.5.2+bzr2282-0ubuntu0.2) ... stop: Unknown instance: invoke-rc.d: initscript isc-dhcp-server, action stop failed. dpkg: error processing package maas-dhcp (--configure): subprocess installed post-installation script returned error exit status 1 -- 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/1346528 Title: maas-dhcp fails to install if isc-dhcp-server is not yet fully installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1346528/+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 1348791] Re: celeryd crashed with SystemError in /usr/lib/python2.7/dist-packages/zope/security/checker.py: dynamic module not initialized properly
*** This bug is a duplicate of bug 1348347 *** https://bugs.launchpad.net/bugs/1348347 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1348347, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Tags removed: need-duplicate-check ** Changed in: celery (Ubuntu) Importance: Undecided = Medium ** Attachment removed: ProcMaps.txt https://bugs.launchpad.net/bugs/1348791/+attachment/4162977/+files/ProcMaps.txt ** Attachment removed: ProcStatus.txt https://bugs.launchpad.net/bugs/1348791/+attachment/4162978/+files/ProcStatus.txt ** This bug has been marked a duplicate of private bug 1348347 ** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to celery in Ubuntu. https://bugs.launchpad.net/bugs/1348791 Title: celeryd crashed with SystemError in /usr/lib/python2.7/dist- packages/zope/security/checker.py: dynamic module not initialized properly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/celery/+bug/1348791/+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 198351] Re: fusesmb/smbnetfs SIGABORT in getattr() because libsmbclient is not thread safe
** Changed in: debian Status: Fix Committed = Fix Released -- 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/198351 Title: fusesmb/smbnetfs SIGABORT in getattr() because libsmbclient is not thread safe To manage notifications about this bug go to: https://bugs.launchpad.net/samba/+bug/198351/+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 1348386] Re: lxc template fails to stop
Hi - Please let us know if that does not suffice, and we need to do the fallback when lxc detects -c is not a device. I'll remove the lxc task in the meantime. ** No longer affects: lxc (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1348386 Title: lxc template fails to stop To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1348386/+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 1325025] Re: juju-core does not depend on distro-info
Hello Robie, or anyone else affected, Accepted juju-core into trusty-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/juju-core/1.18.4 +dfsg-0ubuntu0.14.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: juju-core (Ubuntu Trusty) Status: New = Fix Committed ** Tags added: verification-needed -- 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/1325025 Title: juju-core does not depend on distro-info To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1325025/+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 1329302] Re: juju-core 1.18.4 MRE tracker
Hello Robie, or anyone else affected, Accepted juju-core into trusty-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/juju-core/1.18.4 +dfsg-0ubuntu0.14.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: juju-core (Ubuntu Trusty) Status: Triaged = Fix Committed ** Tags added: verification-needed -- 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/1329302 Title: juju-core 1.18.4 MRE tracker To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1329302/+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 1329302] Re: juju-core 1.18.4 MRE tracker
** Branch linked: lp:ubuntu/trusty-proposed/juju-core -- 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/1329302 Title: juju-core 1.18.4 MRE tracker To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1329302/+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 1325025] Re: juju-core does not depend on distro-info
** Branch linked: lp:ubuntu/trusty-proposed/juju-core -- 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/1325025 Title: juju-core does not depend on distro-info To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1325025/+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 1348830] [NEW] nova interface attach command fails in 14.04 with 2014.1.1: error: libvirtError: internal error: unable to execute QEMU command 'getfd': No file descriptor supplied via SCM_RIGHTS
Public bug reported:
On 14.04 ubuntu with icehouse bug fix release (2014.1.1), nova
interface-attach command is failing (used to work well in previous
versions), while trying to attach an interface to a live VM.
Here is the exception in the nova-compute.log file:
2014-07-25 13:55:07.762 8546 ERROR nova.virt.libvirt.driver
[req-e55e6443-9067-44fd-b0bc-21d102307c2a 03a68cb6d8354bbbae9011bacacea4f8
fde333f66694463ea8f2ff994d97998a] [instance:
759578c6-0d08-4bb9-b571-686296d07059] attaching network adapter failed.
2014-07-25 13:55:08.161 8546 ERROR oslo.messaging.rpc.dispatcher [-] Exception
during message handling: nova.objects.instance.Instance object at
0x7fe48cfcce50
2014-07-25 13:55:08.161 8546 TRACE oslo.messaging.rpc.dispatcher Traceback
(most recent call last):
2014-07-25 13:55:08.161 8546 TRACE oslo.messaging.rpc.dispatcher File
/usr/lib/python2.7/dist-packages/oslo/messaging/rpc/dispatcher.py, line 133,
in _dispatch_and_reply
2014-07-25 13:55:08.161 8546 TRACE oslo.messaging.rpc.dispatcher
incoming.message))
2014-07-25 13:55:08.161 8546 TRACE oslo.messaging.rpc.dispatcher File
/usr/lib/python2.7/dist-packages/oslo/messaging/rpc/dispatcher.py, line 176,
in _dispatch
2014-07-25 13:55:08.161 8546 TRACE oslo.messaging.rpc.dispatcher return
self._do_dispatch(endpoint, method, ctxt, args)
2014-07-25 13:55:08.161 8546 TRACE oslo.messaging.rpc.dispatcher File
/usr/lib/python2.7/dist-packages/oslo/messaging/rpc/dispatcher.py, line 122,
in _do_dispatch
2014-07-25 13:55:08.161 8546 TRACE oslo.messaging.rpc.dispatcher result =
getattr(endpoint, method)(ctxt, **new_args)
2014-07-25 13:55:08.161 8546 TRACE oslo.messaging.rpc.dispatcher File
/usr/lib/python2.7/dist-packages/nova/compute/manager.py, line 393, in
decorated_function
2014-07-25 13:55:08.161 8546 TRACE oslo.messaging.rpc.dispatcher return
function(self, context, *args, **kwargs)
2014-07-25 13:55:08.161 8546 TRACE oslo.messaging.rpc.dispatcher File
/usr/lib/python2.7/dist-packages/nova/compute/manager.py, line 4344, in
attach_interface
2014-07-25 13:55:08.161 8546 TRACE oslo.messaging.rpc.dispatcher
self.driver.attach_interface(instance, image_meta, network_info[0])
2014-07-25 13:55:08.161 8546 TRACE oslo.messaging.rpc.dispatcher File
/usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py, line 1423, in
attach_interface
2014-07-25 13:55:08.161 8546 TRACE oslo.messaging.rpc.dispatcher raise
exception.InterfaceAttachFailed(instance)
2014-07-25 13:55:08.161 8546 TRACE oslo.messaging.rpc.dispatcher
InterfaceAttachFailed: nova.objects.instance.Instance object at 0x7fe48cfcce50
I modified the nova/virt/libvirt/driver.py to add a LOG.exception() to
track where and why the interface failed and I saw the following
exception:
2014-07-25 13:56:23.878 7143 ERROR nova.virt.libvirt.driver
[req-aa938b8a-f31d-4b85-8d29-291bc3acd2ba 03a68cb6d8354bbbae9011bacacea4f8
fde333f66694463ea8f2ff994d97998a] attach failed
2014-07-25 13:56:23.878 7143 TRACE nova.virt.libvirt.driver Traceback (most
recent call last):
2014-07-25 13:56:23.878 7143 TRACE nova.virt.libvirt.driver File
/usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py, line 1418, in
attach_interface
2014-07-25 13:56:23.878 7143 TRACE nova.virt.libvirt.driver
virt_dom.attachDeviceFlags(cfg.to_xml(), flags)
2014-07-25 13:56:23.878 7143 TRACE nova.virt.libvirt.driver File
/usr/lib/python2.7/dist-packages/eventlet/tpool.py, line 179, in doit
2014-07-25 13:56:23.878 7143 TRACE nova.virt.libvirt.driver result =
proxy_call(self._autowrap, f, *args, **kwargs)
2014-07-25 13:56:23.878 7143 TRACE nova.virt.libvirt.driver File
/usr/lib/python2.7/dist-packages/eventlet/tpool.py, line 139, in proxy_call
2014-07-25 13:56:23.878 7143 TRACE nova.virt.libvirt.driver rv =
execute(f,*args,**kwargs)
2014-07-25 13:56:23.878 7143 TRACE nova.virt.libvirt.driver File
/usr/lib/python2.7/dist-packages/eventlet/tpool.py, line 77, in tworker
2014-07-25 13:56:23.878 7143 TRACE nova.virt.libvirt.driver rv =
meth(*args,**kwargs)
2014-07-25 13:56:23.878 7143 TRACE nova.virt.libvirt.driver File
/usr/lib/python2.7/dist-packages/libvirt.py, line 513, in attachDeviceFlags
2014-07-25 13:56:23.878 7143 TRACE nova.virt.libvirt.driver if ret == -1:
raise libvirtError ('virDomainAttachDeviceFlags() failed', dom=self)
2014-07-25 13:56:23.878 7143 TRACE nova.virt.libvirt.driver libvirtError:
internal error: unable to execute QEMU command 'getfd': No file descriptor
supplied via SCM_RIGHTS
Compute node setup:
1) Release of ubuntu:
Description:Ubuntu 14.04 LTS
Release:14.04
2) dpkg --list | grep qemu
ii ipxe-qemu 1.0.0+git-2013.c3d1e78-2ubuntu1 all
PXE boot firmware - ROM images for qemu
ii qemu-keymaps2.0.0+dfsg-2ubuntu1.1 all
QEMU keyboard maps
ii qemu-kvm2.0.0+dfsg-2ubuntu1.1
amd64
[Bug 1347322] Re: juju ssh results in a panic: runtime error
With sinzui's help I have compiled the latest version of Juju 1.20.2 with the gccgo-4.9_4.9.1-1ubuntu3_ppc64el.deb. NOT able to reproduce the “juju ssh” panic/problem having several ssh sessions open simultaneously and having output streaming for over 2 hours. For clarity and review here are the details of how we build the deb packages for Juju with the gccgo 4.9.1 compiler on the CI machine stilson-09 (a P8 64k page size machine). ubuntu@stilson-09:~⟫ uname -a Linux stilson-09 3.13.0-24-generic #47-Ubuntu SMP Fri May 2 23:29:18 UTC 2014 ppc64le ppc64le ppc64le GNU/Linux ubuntu@stilson-09:~⟫ getconf PAGE_SIZE 65536 ubuntu@stilson-09:~⟫ more /proc/cpuinfo processor : 0 cpu : POWER8E (raw), altivec supported clock : 4116.00MHz revision: 2.0 (pvr 004b 0200) processor : 1 cpu : POWER8E (raw), altivec supported clock : 4116.00MHz revision: 2.0 (pvr 004b 0200) timebase: 51200 platform: pSeries model : IBM pSeries (emulated by qemu) machine : CHRP IBM pSeries (emulated by qemu) Downloaded the following packages from: https://launchpad.net/ubuntu/utopic/ppc64el/gccgo-4.9/4.9.1-1ubuntu3 binutils_2.24.51.20140709-1ubuntu1_ppc64el.deb cpp-4.9_4.9.1-1ubuntu3_ppc64el.deb gcc-4.9_4.9.1-1ubuntu3_ppc64el.deb gcc-4.9-base_4.9.1-1ubuntu3_ppc64el.deb gccgo-4.9_4.9.1-1ubuntu3_ppc64el.deb libatomic1_4.9.1-1ubuntu3_ppc64el.deb libgcc1_4.9.1-1ubuntu3_ppc64el.deb libgcc-4.9-dev_4.9.1-1ubuntu3_ppc64el.deb libgo5_4.9.1-1ubuntu3_ppc64el.deb libgomp1_4.9.1-1ubuntu3_ppc64el.deb libitm1_4.9.1-1ubuntu3_ppc64el.deb Installed the packages on stilson-09: ubuntu@stilson-09:~/gccgo⟫ sudo dpkg -i *.deb ubuntu@stilson-09:~/gccgo⟫ dpkg -l | grep gcc ii gcc4:4.8.2-1ubuntu6 ppc64el GNU C compiler ii gcc-4.84.8.3-3ubuntu0.2 ppc64el GNU C compiler ii gcc-4.8-base:ppc64el 4.8.3-3ubuntu0.2 ppc64el GCC, the GNU Compiler Collection (base package) ii gcc-4.94.9.1-1ubuntu3 ppc64el GNU C compiler ii gcc-4.9-base:ppc64el 4.9.1-1ubuntu3 ppc64el GCC, the GNU Compiler Collection (base package) ii gccgo 4:4.9-1ubuntu6 ppc64el Go compiler, based on the GCC backend ii gccgo-4.9 4.9.1-1ubuntu3 ppc64el GNU Go compiler ii gccgo-go 1.2.1-0ubuntu1 ppc64el Go tool for use with gccgo ii libgcc-4.8-dev:ppc64el 4.8.3-3ubuntu0.2 ppc64el GCC support library (development files) ii libgcc-4.9-dev:ppc64el 4.9.1-1ubuntu3 ppc64el GCC support library (development files) ii libgcc1:ppc64el1:4.9.1-1ubuntu3 ppc64el GCC support library Built Juju from source on stilson-09: sinzui ~/Work/juju-release-tools/make-source-packages.bash stable juju-core_1.20.2.tar.gz 'Curtis Hovey curtis.ho...@canonical.com' 1340893 1345014 1344940 1345832 1307434 1347371 1337091 1342747 1343301 1341589 sinzui ~/Work/juju-release-tools/build-package-with-dsc.bash ubuntu@stilson-09 '' /home/curtis/Downloads/tmp.WUZeXOfFz1/juju-core_1.20.2-0ubuntu1~14.04.1~juju1.dsc Resulting in: ubuntu@stilson-09:~⟫ ls -l juju-build total 17332 -rw-r--r-- 1 ubuntu ubuntu 6944 Jul 25 15:05 juju_1.20.2-0ubuntu1~14.04.1~juju1_all.deb drwxrwxr-x 7 ubuntu ubuntu 4096 Jul 25 15:04 juju-core-1.20.2 -rw--- 1 ubuntu ubuntu 8356 Jul 25 15:04 juju-core_1.20.2-0ubuntu1~14.04.1~juju1.debian.tar.gz -rw--- 1 ubuntu ubuntu 1183 Jul 25 15:04 juju-core_1.20.2-0ubuntu1~14.04.1~juju1.dsc -rw-rw-r-- 1 ubuntu ubuntu 3133 Jul 25 15:05 juju-core_1.20.2-0ubuntu1~14.04.1~juju1_ppc64el.changes -rw-r--r-- 1 ubuntu ubuntu 14341816 Jul 25 15:05 juju-core_1.20.2-0ubuntu1~14.04.1~juju1_ppc64el.deb -rw-rw-r-- 1 ubuntu ubuntu 3354392 Jul 25 15:03 juju-core_1.20.2.orig.tar.gz -rw-r--r-- 1 ubuntu ubuntu 7020 Jul 25 15:05 juju-local_1.20.2-0ubuntu1~14.04.1~juju1_all.deb -rw-r--r-- 1 ubuntu ubuntu 7022 Jul 25 15:05 juju-local-kvm_1.20.2-0ubuntu1~14.04.1~juju1_all.deb I copied these deb packages to stilson-01: ubuntu@stilson-01:~$ ls -l juju-build total 14032 -rw-r--r-- 1 ubuntu ubuntu 6944 Jul 25 15:21 juju_1.20.2-0ubuntu1~14.04.1~juju1_all.deb -rw-r--r-- 1 ubuntu ubuntu 14341816 Jul 25 15:22 juju-core_1.20.2-0ubuntu1~14.04.1~juju1_ppc64el.deb -rw-r--r-- 1 ubuntu ubuntu 7020 Jul 25 15:22 juju-local_1.20.2-0ubuntu1~14.04.1~juju1_all.deb -rw-r--r-- 1 ubuntu ubuntu 7022 Jul 25 15:22 juju-local-kvm_1.20.2-0ubuntu1~14.04.1~juju1_all.deb Installed the deb packages on stilson-01: sudo dpkg -i *.deb ubuntu@stilson-01:~$ dpkg -l | grep juju ii juju
[Bug 1348830] Re: nova interface attach command fails in 14.04 with 2014.1.1: error: libvirtError: internal error: unable to execute QEMU command 'getfd': No file descriptor supplied via SCM_RIGHTS
** Description changed:
On 14.04 ubuntu with icehouse bug fix release (2014.1.1), nova
interface-attach command is failing (used to work well in previous
versions), while trying to attach an interface to a live VM.
Here is the exception in the nova-compute.log file:
2014-07-25 13:55:07.762 8546 ERROR nova.virt.libvirt.driver
[req-e55e6443-9067-44fd-b0bc-21d102307c2a 03a68cb6d8354bbbae9011bacacea4f8
fde333f66694463ea8f2ff994d97998a] [instance:
759578c6-0d08-4bb9-b571-686296d07059] attaching network adapter failed.
2014-07-25 13:55:08.161 8546 ERROR oslo.messaging.rpc.dispatcher [-]
Exception during message handling: nova.objects.instance.Instance object at
0x7fe48cfcce50
2014-07-25 13:55:08.161 8546 TRACE oslo.messaging.rpc.dispatcher Traceback
(most recent call last):
2014-07-25 13:55:08.161 8546 TRACE oslo.messaging.rpc.dispatcher File
/usr/lib/python2.7/dist-packages/oslo/messaging/rpc/dispatcher.py, line 133,
in _dispatch_and_reply
2014-07-25 13:55:08.161 8546 TRACE oslo.messaging.rpc.dispatcher
incoming.message))
2014-07-25 13:55:08.161 8546 TRACE oslo.messaging.rpc.dispatcher File
/usr/lib/python2.7/dist-packages/oslo/messaging/rpc/dispatcher.py, line 176,
in _dispatch
2014-07-25 13:55:08.161 8546 TRACE oslo.messaging.rpc.dispatcher return
self._do_dispatch(endpoint, method, ctxt, args)
2014-07-25 13:55:08.161 8546 TRACE oslo.messaging.rpc.dispatcher File
/usr/lib/python2.7/dist-packages/oslo/messaging/rpc/dispatcher.py, line 122,
in _do_dispatch
2014-07-25 13:55:08.161 8546 TRACE oslo.messaging.rpc.dispatcher result =
getattr(endpoint, method)(ctxt, **new_args)
2014-07-25 13:55:08.161 8546 TRACE oslo.messaging.rpc.dispatcher File
/usr/lib/python2.7/dist-packages/nova/compute/manager.py, line 393, in
decorated_function
2014-07-25 13:55:08.161 8546 TRACE oslo.messaging.rpc.dispatcher return
function(self, context, *args, **kwargs)
2014-07-25 13:55:08.161 8546 TRACE oslo.messaging.rpc.dispatcher File
/usr/lib/python2.7/dist-packages/nova/compute/manager.py, line 4344, in
attach_interface
2014-07-25 13:55:08.161 8546 TRACE oslo.messaging.rpc.dispatcher
self.driver.attach_interface(instance, image_meta, network_info[0])
2014-07-25 13:55:08.161 8546 TRACE oslo.messaging.rpc.dispatcher File
/usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py, line 1423, in
attach_interface
2014-07-25 13:55:08.161 8546 TRACE oslo.messaging.rpc.dispatcher raise
exception.InterfaceAttachFailed(instance)
2014-07-25 13:55:08.161 8546 TRACE oslo.messaging.rpc.dispatcher
InterfaceAttachFailed: nova.objects.instance.Instance object at 0x7fe48cfcce50
I modified the nova/virt/libvirt/driver.py to add a LOG.exception() to
track where and why the interface failed and I saw the following
exception:
2014-07-25 13:56:23.878 7143 ERROR nova.virt.libvirt.driver
[req-aa938b8a-f31d-4b85-8d29-291bc3acd2ba 03a68cb6d8354bbbae9011bacacea4f8
fde333f66694463ea8f2ff994d97998a] attach failed
2014-07-25 13:56:23.878 7143 TRACE nova.virt.libvirt.driver Traceback (most
recent call last):
2014-07-25 13:56:23.878 7143 TRACE nova.virt.libvirt.driver File
/usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py, line 1418, in
attach_interface
2014-07-25 13:56:23.878 7143 TRACE nova.virt.libvirt.driver
virt_dom.attachDeviceFlags(cfg.to_xml(), flags)
2014-07-25 13:56:23.878 7143 TRACE nova.virt.libvirt.driver File
/usr/lib/python2.7/dist-packages/eventlet/tpool.py, line 179, in doit
2014-07-25 13:56:23.878 7143 TRACE nova.virt.libvirt.driver result =
proxy_call(self._autowrap, f, *args, **kwargs)
2014-07-25 13:56:23.878 7143 TRACE nova.virt.libvirt.driver File
/usr/lib/python2.7/dist-packages/eventlet/tpool.py, line 139, in proxy_call
2014-07-25 13:56:23.878 7143 TRACE nova.virt.libvirt.driver rv =
execute(f,*args,**kwargs)
2014-07-25 13:56:23.878 7143 TRACE nova.virt.libvirt.driver File
/usr/lib/python2.7/dist-packages/eventlet/tpool.py, line 77, in tworker
2014-07-25 13:56:23.878 7143 TRACE nova.virt.libvirt.driver rv =
meth(*args,**kwargs)
2014-07-25 13:56:23.878 7143 TRACE nova.virt.libvirt.driver File
/usr/lib/python2.7/dist-packages/libvirt.py, line 513, in attachDeviceFlags
2014-07-25 13:56:23.878 7143 TRACE nova.virt.libvirt.driver if ret == -1:
raise libvirtError ('virDomainAttachDeviceFlags() failed', dom=self)
2014-07-25 13:56:23.878 7143 TRACE nova.virt.libvirt.driver libvirtError:
internal error: unable to execute QEMU command 'getfd': No file descriptor
supplied via SCM_RIGHTS
-
Compute node setup:
1) Release of ubuntu:
Description: Ubuntu 14.04 LTS
Release: 14.04
2) dpkg --list | grep qemu
ii ipxe-qemu 1.0.0+git-2013.c3d1e78-2ubuntu1
all PXE boot firmware - ROM images for qemu
ii qemu-keymaps2.0.0+dfsg-2ubuntu1.1
all QEMU
Re: [Bug 1347322] Re: juju ssh results in a panic: runtime error
btw. This has nothing to do with ssh, it is to do with the length of time the juju cli process is running for. Normally this is a very short period, but juju ssh forks ssh as a child then waits for it to finish. The crash is caused by a bug in the previous runtime (compiled statically into the binary) when the garbage collector had been running for long enough to call madvise(DONT_NEED, ...) with the wrong page size. On Sat, Jul 26, 2014 at 8:22 AM, Matt Bruzek matthew.bru...@canonical.com wrote: With sinzui's help I have compiled the latest version of Juju 1.20.2 with the gccgo-4.9_4.9.1-1ubuntu3_ppc64el.deb. NOT able to reproduce the “juju ssh” panic/problem having several ssh sessions open simultaneously and having output streaming for over 2 hours. For clarity and review here are the details of how we build the deb packages for Juju with the gccgo 4.9.1 compiler on the CI machine stilson-09 (a P8 64k page size machine). ubuntu@stilson-09:~⟫ uname -a Linux stilson-09 3.13.0-24-generic #47-Ubuntu SMP Fri May 2 23:29:18 UTC 2014 ppc64le ppc64le ppc64le GNU/Linux ubuntu@stilson-09:~⟫ getconf PAGE_SIZE 65536 ubuntu@stilson-09:~⟫ more /proc/cpuinfo processor : 0 cpu : POWER8E (raw), altivec supported clock : 4116.00MHz revision: 2.0 (pvr 004b 0200) processor : 1 cpu : POWER8E (raw), altivec supported clock : 4116.00MHz revision: 2.0 (pvr 004b 0200) timebase: 51200 platform: pSeries model : IBM pSeries (emulated by qemu) machine : CHRP IBM pSeries (emulated by qemu) Downloaded the following packages from: https://launchpad.net/ubuntu/utopic/ppc64el/gccgo-4.9/4.9.1-1ubuntu3 binutils_2.24.51.20140709-1ubuntu1_ppc64el.deb cpp-4.9_4.9.1-1ubuntu3_ppc64el.deb gcc-4.9_4.9.1-1ubuntu3_ppc64el.deb gcc-4.9-base_4.9.1-1ubuntu3_ppc64el.deb gccgo-4.9_4.9.1-1ubuntu3_ppc64el.deb libatomic1_4.9.1-1ubuntu3_ppc64el.deb libgcc1_4.9.1-1ubuntu3_ppc64el.deb libgcc-4.9-dev_4.9.1-1ubuntu3_ppc64el.deb libgo5_4.9.1-1ubuntu3_ppc64el.deb libgomp1_4.9.1-1ubuntu3_ppc64el.deb libitm1_4.9.1-1ubuntu3_ppc64el.deb Installed the packages on stilson-09: ubuntu@stilson-09:~/gccgo⟫ sudo dpkg -i *.deb ubuntu@stilson-09:~/gccgo⟫ dpkg -l | grep gcc ii gcc4:4.8.2-1ubuntu6 ppc64el GNU C compiler ii gcc-4.84.8.3-3ubuntu0.2 ppc64el GNU C compiler ii gcc-4.8-base:ppc64el 4.8.3-3ubuntu0.2 ppc64el GCC, the GNU Compiler Collection (base package) ii gcc-4.94.9.1-1ubuntu3 ppc64el GNU C compiler ii gcc-4.9-base:ppc64el 4.9.1-1ubuntu3 ppc64el GCC, the GNU Compiler Collection (base package) ii gccgo 4:4.9-1ubuntu6 ppc64el Go compiler, based on the GCC backend ii gccgo-4.9 4.9.1-1ubuntu3 ppc64el GNU Go compiler ii gccgo-go 1.2.1-0ubuntu1 ppc64el Go tool for use with gccgo ii libgcc-4.8-dev:ppc64el 4.8.3-3ubuntu0.2 ppc64el GCC support library (development files) ii libgcc-4.9-dev:ppc64el 4.9.1-1ubuntu3 ppc64el GCC support library (development files) ii libgcc1:ppc64el1:4.9.1-1ubuntu3 ppc64el GCC support library Built Juju from source on stilson-09: sinzui ~/Work/juju-release-tools/make-source-packages.bash stable juju-core_1.20.2.tar.gz 'Curtis Hovey curtis.ho...@canonical.com' 1340893 1345014 1344940 1345832 1307434 1347371 1337091 1342747 1343301 1341589 sinzui ~/Work/juju-release-tools/build-package-with-dsc.bash ubuntu@stilson-09 '' /home/curtis/Downloads/tmp.WUZeXOfFz1/juju-core_1.20.2-0ubuntu1~14.04.1~juju1.dsc Resulting in: ubuntu@stilson-09:~⟫ ls -l juju-build total 17332 -rw-r--r-- 1 ubuntu ubuntu 6944 Jul 25 15:05 juju_1.20.2-0ubuntu1~14.04.1~juju1_all.deb drwxrwxr-x 7 ubuntu ubuntu 4096 Jul 25 15:04 juju-core-1.20.2 -rw--- 1 ubuntu ubuntu 8356 Jul 25 15:04 juju-core_1.20.2-0ubuntu1~14.04.1~juju1.debian.tar.gz -rw--- 1 ubuntu ubuntu 1183 Jul 25 15:04 juju-core_1.20.2-0ubuntu1~14.04.1~juju1.dsc -rw-rw-r-- 1 ubuntu ubuntu 3133 Jul 25 15:05 juju-core_1.20.2-0ubuntu1~14.04.1~juju1_ppc64el.changes -rw-r--r-- 1 ubuntu ubuntu 14341816 Jul 25 15:05 juju-core_1.20.2-0ubuntu1~14.04.1~juju1_ppc64el.deb -rw-rw-r-- 1 ubuntu ubuntu 3354392 Jul 25 15:03 juju-core_1.20.2.orig.tar.gz -rw-r--r-- 1 ubuntu ubuntu 7020 Jul 25 15:05 juju-local_1.20.2-0ubuntu1~14.04.1~juju1_all.deb -rw-r--r-- 1 ubuntu ubuntu 7022 Jul 25 15:05 juju-local-kvm_1.20.2-0ubuntu1~14.04.1~juju1_all.deb I copied these deb
[Bug 1323011] Re: no msg in /var/log/apache2/error.log but session lost ?
[Expired for apache2 (Ubuntu) because there has been no activity for 60 days.] ** Changed in: apache2 (Ubuntu) Status: Incomplete = Expired -- 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/1323011 Title: no msg in /var/log/apache2/error.log but session lost ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1323011/+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
