[Bug 1554227] Re: DHCP unicast requests are not responded to
** Changed in: nova Status: New => Confirmed ** Changed in: nova (Ubuntu) Status: New => Confirmed -- 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/1554227 Title: DHCP unicast requests are not responded to To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1554227/+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 1554540] [NEW] DHCP unicast requests are not responding
Public bug reported: Issue: We run nova-network in VLAN+multi_host mode on Kilo and notice that only one dnsmasq process (either the oldest or newest) on the hypervisor responds to unicast BOOTPREQUESTS. dhclient on VMs will retry until it eventually gives up and broadcasts the request, which is then responded to. Depending on the timing of the DHCP broadcast request, VMs can briefly lose connectivity as they attempt rebinding. According to http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commitdiff;h=9380ba70d67db6b69f817d8e318de5ba1e990b12, it seems that passing "--interface" argument, in addition to "--bind- interfaces" is necessary for dnsmasq to work correctly in VLAN mode. Reproduce steps: 1. Create two tenants 2. Create a VM under each tenant, forcing the VMs to run on a single hypervisor. I tested with a vanilla Ubuntu cloud image, but any other image that uses dhclient should also work. 3. On the hypervisor, run dhcpdump -i for each tenant's bridge interface. On at least one of them, you should see unicast BOOTPREQUEST with no corresponding BOOTPREPLY. dnsmasq will reply when the request eventually hits 255.255.255.255. Nova/Openstack/dnsmasq versions: ii nova-api 1:2015.1.2-0ubuntu2~cloud0 all OpenStack Compute - API frontend ii nova-common 1:2015.1.2-0ubuntu2~cloud0 all OpenStack Compute - common files ii nova-compute 1:2015.1.2-0ubuntu2~cloud0 all OpenStack Compute - compute node base ii nova-compute-libvirt 1:2015.1.2-0ubuntu2~cloud0 all OpenStack Compute - compute node libvirt support ii nova-compute-qemu 1:2015.1.2-0ubuntu2~cloud0 all OpenStack Compute - compute node (QEmu) ii nova-network 1:2015.1.2-0ubuntu2~cloud0 all OpenStack Compute - Network manager ii nova-novncproxy 1:2015.1.2-0ubuntu2~cloud0 all OpenStack Compute - NoVNC proxy ii python-nova 1:2015.1.2-0ubuntu2~cloud0 all OpenStack Compute Python libraries ii python-nova-adminclient 0.1.8-0ubuntu2 amd64 client for administering Openstack Nova ii python-novaclient 1:2.22.0-0ubuntu2~cloud0 all client library for OpenStack Compute API ii dnsmasq-base 2.68-1ubuntu0.1 amd64 Small caching DNS proxy and DHCP/TFTP server ii dnsmasq-utils 2.68-1ubuntu0.1 amd64 Utilities for manipulating DHCP lease ** Affects: nova (Ubuntu) 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/1554540 Title: DHCP unicast requests are not responding To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nova/+bug/1554540/+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 1554540] Re: DHCP unicast requests are not responding
Upstream bug for OpenStack Compute (nova): https://bugs.launchpad.net/nova/+bug/1554227 -- 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/1554540 Title: DHCP unicast requests are not responding To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nova/+bug/1554540/+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 1546735] Re: openipmi package compile without SSL
** Changed in: openipmi (Ubuntu) Assignee: (unassigned) => Eric Desrochers (slashd) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openipmi in Ubuntu. https://bugs.launchpad.net/bugs/1546735 Title: openipmi package compile without SSL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openipmi/+bug/1546735/+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 1546735] Re: openipmi package compile without SSL
** Changed in: openipmi (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openipmi in Ubuntu. https://bugs.launchpad.net/bugs/1546735 Title: openipmi package compile without SSL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openipmi/+bug/1546735/+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 1546735] Re: openipmi package compile without SSL
Debian package for unstable # filename: openipmi-2.0.21/debian/changelog openipmi (2.0.21-1) unstable; urgency=medium ... * enabled openssl. closes: #775847 ... -- Noël Köthe Thu, 25 Feb 2016 12:06:21 +0100 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openipmi in Ubuntu. https://bugs.launchpad.net/bugs/1546735 Title: openipmi package compile without SSL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openipmi/+bug/1546735/+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 1546735] Re: openipmi package compile without SSL
Following a discussion with the Debian distribution maintenance software "Noël Köthe ". SSL support has been enabled by debian upstream maintainer and has now landed in unstable in openipmi-2.0.21. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openipmi in Ubuntu. https://bugs.launchpad.net/bugs/1546735 Title: openipmi package compile without SSL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openipmi/+bug/1546735/+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 1546735] Re: openipmi package compile without SSL
** Tags added: sts -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openipmi in Ubuntu. https://bugs.launchpad.net/bugs/1546735 Title: openipmi package compile without SSL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openipmi/+bug/1546735/+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 1546735] [NEW] openipmi package compile without SSL
Public bug reported:
It has been brought to my attention by the community that package
"openipmi" is build without openssl.
Taken from "openipmi-2.0.18" source code:
--
filename:debian/rules
---
23 config.status: configure
24 dh_testdir
25 dh_autotools-dev_updateconfig
26 # Add here commands to configure the package.
27 CFLAGS="$(CFLAGS)" ./configure --host=$(DEB_HOST_GNU_TYPE) \
28 --build=$(DEB_BUILD_GNU_TYPE) \
29 --prefix=/usr \
==> 30 --without-openssl \
31 --mandir=\$${prefix}/share/man \
32 --infodir=\$${prefix}/share/info \
33 --disable-rpath
--
This prevent some third applications to work as expected such as
Zabbix[1]
There is debian bug[2] filed on 20 Jan 2015 16:57:01 UTC
[1] - https://support.zabbix.com/browse/ZBX-6139
[2] - https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775847
** Affects: openipmi (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openipmi in Ubuntu.
https://bugs.launchpad.net/bugs/1546735
Title:
openipmi package compile without SSL
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openipmi/+bug/1546735/+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 1479652] Re: [patch] ntpd rejects source UDP ports less than 123 as bogus
I confirmed the package "4.2.6.p5+dfsg-3ubuntu8.2" solve the bug in Ubuntu Wily # With port <123 using ntpdate (without patch) 11 Feb 20:30:09 ntpdate[2348]: no server suitable for synchronization found # With port <123 using ntpdate (including patch) 11 Feb 20:32:18 ntpdate[3243]: adjust time server 10.10.10.107 offset 0.002017 sec Eric ** Tags added: verification-done-wily -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1479652 Title: [patch] ntpd rejects source UDP ports less than 123 as bogus To manage notifications about this bug go to: https://bugs.launchpad.net/ntp/+bug/1479652/+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 1479652] Re: [patch] ntpd rejects source UDP ports less than 123 as bogus
I confirmed the package"4.2.6.p3+dfsg-1ubuntu3.9" solved the problem in Ubuntu Precise NTP Version : 1:4.2.6.p3+dfsg-1ubuntu3.1 With no IPTABLES rule ==> Working $ ntpdate x.x.x.x 11 Feb 16:15:19 ntpdate[1243]: adjust time server x.x.x.x offset 0.190571 sec With IPTABLES rule ==> Not working $ iptables -t nat -A POSTROUTING -p UDP --dport 123 -j SNAT --to-source y.y.y.y:100-122 $ntpdate x.x.x.x 11 Feb 16:15:36 ntpdate[1253]: no server suitable for synchronization found With ntp (precise-proposed) + IPTABLE rules ==> Now working NTP version: 1:4.2.6.p3+dfsg-1ubuntu3.9 $ iptables -t nat -A POSTROUTING -p UDP --dport 123 -j SNAT --to-source y.y.y.y:100-122 $ ntpdate x.x.x.x 11 Feb 16:21:26 ntpdate[1986]: adjust time server x.x.x.x offset 0.005394 sec Eric ** Tags added: verification-done-precise -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1479652 Title: [patch] ntpd rejects source UDP ports less than 123 as bogus To manage notifications about this bug go to: https://bugs.launchpad.net/ntp/+bug/1479652/+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 1479652] Re: [patch] ntpd rejects source UDP ports less than 123 as bogus
** Tags removed: verification-done ** Tags added: verification-done-trusty -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1479652 Title: [patch] ntpd rejects source UDP ports less than 123 as bogus To manage notifications about this bug go to: https://bugs.launchpad.net/ntp/+bug/1479652/+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 1479652] Re: [patch] ntpd rejects source UDP ports less than 123 as bogus
It has been brought to my attention ... -- I confirm that the proposed testfix package resolved the issue on Trusty. The test were made on test machines where the client had an iptable postrouting nat forcing the source port to be under 123. - ntpdate command performed on the client machine was successful - tcpdump on the server side confirmed that the source port was under 123. -- ** Tags removed: verification-needed ** Tags added: verification-done ** Tags removed: verification-done ** Tags added: verification-done-trusty ** Tags removed: verification-done-trusty ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1479652 Title: [patch] ntpd rejects source UDP ports less than 123 as bogus To manage notifications about this bug go to: https://bugs.launchpad.net/ntp/+bug/1479652/+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 1479652] Re: [patch] ntpd rejects source UDP ports less than 123 as bogus
** Description changed: [Impact] If an NTP client sends a request with a source port less than 123, the packet is silently ignored by ntpd. This is occurring in our environment due to NAT. [Test Case] The problem can easily be reproduced by having an iptable postrouting nat forcing the source port to be under 123 set on the client. Setup: ==> NTP server = y.y.y.y ntp.conf configured to be a server. ==> NTP client = x.x.x.x "ntpdate" used to submmit requests #iptable setup to force src port to be lower than 123 iptables -t nat -A POSTROUTING -p UDP --dport 123 -j SNAT --to-source x.x.x.x:100-122 + + ## On the client, set to force src port < 123 (without patch) + + $ ntpdate y.y.y.y + ntpdate[]: no server suitable for synchronization found + + ## On the client, set to force src port < 123 (with patch) + + $ ntpdate y.y.y.y + ntpdate[]: adjust time server y.y.y.y offset -0.028483 sec [Regression Potential] The patch comes from upstream: http://bugs.ntp.org/show_bug.cgi?id=2174 A testfix[1] package has been provided to the community before the SRU process to bring more confidence for the patch. Positive feedbacks has been given by the community to confirm the patch addressed the bug [comment #7] [1]- https://launchpad.net/~slashd/+archive/ubuntu/bug1479652 [Original description] [Title copied from Debian bug, which was not filed by me. Description below is mine.] If an NTP client sends a request with a source port less than 123, the packet is silently ignored by ntpd. This is occurring in our environment due to NAT. Attached is the patch already accepted upstream which fixes the issue. I've verified it fixes the problem. Debian has been ignoring this patch for almost 3 years. Can we get this in Ubuntu please? ** Description changed: [Impact] If an NTP client sends a request with a source port less than 123, the packet is silently ignored by ntpd. This is occurring in our environment due to NAT. [Test Case] The problem can easily be reproduced by having an iptable postrouting nat forcing the source port to be under 123 set on the client. Setup: ==> NTP server = y.y.y.y ntp.conf configured to be a server. ==> NTP client = x.x.x.x "ntpdate" used to submmit requests - #iptable setup to force src port to be lower than 123 + #iptable setup to force src port to be lower than 123 iptables -t nat -A POSTROUTING -p UDP --dport 123 -j SNAT --to-source x.x.x.x:100-122 ## On the client, set to force src port < 123 (without patch) $ ntpdate y.y.y.y ntpdate[]: no server suitable for synchronization found ## On the client, set to force src port < 123 (with patch) $ ntpdate y.y.y.y ntpdate[]: adjust time server y.y.y.y offset -0.028483 sec [Regression Potential] The patch comes from upstream: http://bugs.ntp.org/show_bug.cgi?id=2174 A testfix[1] package has been provided to the community before the SRU process to bring more confidence for the patch. Positive feedbacks has been given by the community to confirm the patch addressed the bug [comment #7] [1]- https://launchpad.net/~slashd/+archive/ubuntu/bug1479652 [Original description] [Title copied from Debian bug, which was not filed by me. Description below is mine.] If an NTP client sends a request with a source port less than 123, the packet is silently ignored by ntpd. This is occurring in our environment due to NAT. Attached is the patch already accepted upstream which fixes the issue. I've verified it fixes the problem. Debian has been ignoring this patch for almost 3 years. Can we get this in Ubuntu please? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1479652 Title: [patch] ntpd rejects source UDP ports less than 123 as bogus To manage notifications about this bug go to: https://bugs.launchpad.net/ntp/+bug/1479652/+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 1479652] Re: [patch] ntpd rejects source UDP ports less than 123 as bogus
** Description changed: [Impact] If an NTP client sends a request with a source port less than 123, the packet is silently ignored by ntpd. This is occurring in our environment due to NAT. [Test Case] The problem can easily be reproduced by having an iptable postrouting nat forcing the source port to be under 123 set on the client. + + Setup: + ==> NTP server = y.y.y.y + ntp.conf configured to be a server. + + ==> NTP client = x.x.x.x + "ntpdate" used to submmit requests + + #iptable setup to force src port to be lower than 123 + iptables -t nat -A POSTROUTING -p UDP --dport 123 -j SNAT --to-source 10.55.15.154:100-122 [Regression Potential] The patch comes from upstream: http://bugs.ntp.org/show_bug.cgi?id=2174 A testfix[1] package has been provided to the community before the SRU process to bring more confidence for the patch. Positive feedbacks has been given by the community to confirm the patch addressed the bug [comment #7] [1]- https://launchpad.net/~slashd/+archive/ubuntu/bug1479652 [Original description] [Title copied from Debian bug, which was not filed by me. Description below is mine.] If an NTP client sends a request with a source port less than 123, the packet is silently ignored by ntpd. This is occurring in our environment due to NAT. Attached is the patch already accepted upstream which fixes the issue. I've verified it fixes the problem. Debian has been ignoring this patch for almost 3 years. Can we get this in Ubuntu please? ** Description changed: [Impact] If an NTP client sends a request with a source port less than 123, the packet is silently ignored by ntpd. This is occurring in our environment due to NAT. [Test Case] The problem can easily be reproduced by having an iptable postrouting nat forcing the source port to be under 123 set on the client. Setup: - ==> NTP server = y.y.y.y - ntp.conf configured to be a server. - - ==> NTP client = x.x.x.x - "ntpdate" used to submmit requests + ==> NTP server = y.y.y.y + ntp.conf configured to be a server. - #iptable setup to force src port to be lower than 123 - iptables -t nat -A POSTROUTING -p UDP --dport 123 -j SNAT --to-source 10.55.15.154:100-122 + ==> NTP client = x.x.x.x + "ntpdate" used to submmit requests + + #iptable setup to force src port to be lower than 123 + iptables -t nat -A POSTROUTING -p UDP --dport 123 -j SNAT --to-source x.x.x.x:100-122 [Regression Potential] The patch comes from upstream: http://bugs.ntp.org/show_bug.cgi?id=2174 A testfix[1] package has been provided to the community before the SRU process to bring more confidence for the patch. Positive feedbacks has been given by the community to confirm the patch addressed the bug [comment #7] [1]- https://launchpad.net/~slashd/+archive/ubuntu/bug1479652 [Original description] [Title copied from Debian bug, which was not filed by me. Description below is mine.] If an NTP client sends a request with a source port less than 123, the packet is silently ignored by ntpd. This is occurring in our environment due to NAT. Attached is the patch already accepted upstream which fixes the issue. I've verified it fixes the problem. Debian has been ignoring this patch for almost 3 years. Can we get this in Ubuntu please? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1479652 Title: [patch] ntpd rejects source UDP ports less than 123 as bogus To manage notifications about this bug go to: https://bugs.launchpad.net/ntp/+bug/1479652/+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 1479652] Re: [patch] ntpd rejects source UDP ports less than 123 as bogus
Patch -- Distribution : Precise (12.04) Package version : 4.2.6.p3+dfsg-1ubuntu3.9 -- ** Patch added: "precise_ntp_4.2.6.p3+dfsg-1ubuntu3.9" https://bugs.launchpad.net/ubuntu/precise/+source/ntp/+bug/1479652/+attachment/4556380/+files/lp1479652_precise_3.9.debdiff -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1479652 Title: [patch] ntpd rejects source UDP ports less than 123 as bogus To manage notifications about this bug go to: https://bugs.launchpad.net/ntp/+bug/1479652/+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 1479652] Re: [patch] ntpd rejects source UDP ports less than 123 as bogus
Patch -- Distribution : Wily (15.10) Package version : 4.2.6.p5+dfsg-3ubuntu8.2 -- ** Patch added: "wily_4.2.6.p5+dfsg-3ubuntu8.2" https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1479652/+attachment/4556354/+files/lp1479652_wily_8.2.debdiff -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1479652 Title: [patch] ntpd rejects source UDP ports less than 123 as bogus To manage notifications about this bug go to: https://bugs.launchpad.net/ntp/+bug/1479652/+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 1479652] Re: [patch] ntpd rejects source UDP ports less than 123 as bogus
Patch -- Distribution : Trusty (14.04) Package version : ntp_4.2.6.p5+dfsg-3ubuntu2.14.04.8 -- Note: kick-d is currently working on a merge for Xenial, including this patch. I'm including the .debdiffs for the other distributions (W/T/P) for once the merge for Xenial will be completed. ** Patch added: "trusty_ntp_4.2.6.p5+dfsg-3ubuntu2.14.04.8" https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1479652/+attachment/4556319/+files/lp1479652_trusty_14.04.8.debdiff -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1479652 Title: [patch] ntpd rejects source UDP ports less than 123 as bogus To manage notifications about this bug go to: https://bugs.launchpad.net/ntp/+bug/1479652/+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 1479652] Re: [patch] ntpd rejects source UDP ports less than 123 as bogus
** Tags added: sts -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1479652 Title: [patch] ntpd rejects source UDP ports less than 123 as bogus To manage notifications about this bug go to: https://bugs.launchpad.net/ntp/+bug/1479652/+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 1479652] Re: [patch] ntpd rejects source UDP ports less than 123 as bogus
** Description changed: + [Impact] + + If an NTP client sends a request with a source port less than 123, the packet is silently ignored by ntpd. + This is occurring in our environment due to NAT. + + [Test Case] + + The problem can easily be reproduced by having an iptable postrouting + nat forcing the source port to be under 123 set on the client. + + [Regression Potential] + + The patch comes from upstream + [Bug 2174] http://bugs.ntp.org/show_bug.cgi?id=2174] + + A testfix[1] package has been provided to the community before the SRU + process to bring more confidence for the patch. Positive feedbacks has + been given by the community to confirm the patch addressed the bug + [comment #7] + + [1]- https://launchpad.net/~slashd/+archive/ubuntu/bug1479652 + + [Original description] + [Title copied from Debian bug, which was not filed by me. Description below is mine.] If an NTP client sends a request with a source port less than 123, the packet is silently ignored by ntpd. This is occurring in our environment due to NAT. Attached is the patch already accepted upstream which fixes the issue. I've verified it fixes the problem. Debian has been ignoring this patch for almost 3 years. Can we get this in Ubuntu please? ** Description changed: [Impact] - If an NTP client sends a request with a source port less than 123, the packet is silently ignored by ntpd. - This is occurring in our environment due to NAT. + If an NTP client sends a request with a source port less than 123, the + packet is silently ignored by ntpd. This is occurring in our environment + due to NAT. [Test Case] The problem can easily be reproduced by having an iptable postrouting nat forcing the source port to be under 123 set on the client. [Regression Potential] - The patch comes from upstream + The patch comes from upstream [Bug 2174] http://bugs.ntp.org/show_bug.cgi?id=2174] A testfix[1] package has been provided to the community before the SRU process to bring more confidence for the patch. Positive feedbacks has been given by the community to confirm the patch addressed the bug [comment #7] [1]- https://launchpad.net/~slashd/+archive/ubuntu/bug1479652 [Original description] [Title copied from Debian bug, which was not filed by me. Description below is mine.] If an NTP client sends a request with a source port less than 123, the packet is silently ignored by ntpd. This is occurring in our environment due to NAT. Attached is the patch already accepted upstream which fixes the issue. I've verified it fixes the problem. Debian has been ignoring this patch for almost 3 years. Can we get this in Ubuntu please? ** Description changed: [Impact] If an NTP client sends a request with a source port less than 123, the packet is silently ignored by ntpd. This is occurring in our environment due to NAT. [Test Case] The problem can easily be reproduced by having an iptable postrouting nat forcing the source port to be under 123 set on the client. [Regression Potential] - The patch comes from upstream - [Bug 2174] http://bugs.ntp.org/show_bug.cgi?id=2174] + The patch comes from upstream: http://bugs.ntp.org/show_bug.cgi?id=2174] A testfix[1] package has been provided to the community before the SRU process to bring more confidence for the patch. Positive feedbacks has been given by the community to confirm the patch addressed the bug [comment #7] [1]- https://launchpad.net/~slashd/+archive/ubuntu/bug1479652 [Original description] [Title copied from Debian bug, which was not filed by me. Description below is mine.] If an NTP client sends a request with a source port less than 123, the packet is silently ignored by ntpd. This is occurring in our environment due to NAT. Attached is the patch already accepted upstream which fixes the issue. I've verified it fixes the problem. Debian has been ignoring this patch for almost 3 years. Can we get this in Ubuntu please? ** Description changed: [Impact] If an NTP client sends a request with a source port less than 123, the packet is silently ignored by ntpd. This is occurring in our environment due to NAT. [Test Case] The problem can easily be reproduced by having an iptable postrouting nat forcing the source port to be under 123 set on the client. [Regression Potential] - The patch comes from upstream: http://bugs.ntp.org/show_bug.cgi?id=2174] + The patch comes from upstream: http://bugs.ntp.org/show_bug.cgi?id=2174 A testfix[1] package has been provided to the community before the SRU process to bring more confidence for the patch. Positive feedbacks has been given by the community to confirm the patch addressed the bug [comment #7] [1]- https://launchpad.net/~slashd/+archive/ubuntu/bug1479652 [Original description] [Title copied from Debian bug, which was not filed
[Bug 1479652] Re: [patch] ntpd rejects source UDP ports less than 123 as bogus
I have build a test package for the community to validate it solve the bug before starting the SRU process [1]. The goal of this testfix is only to confirm that this solve the bug and it is not a final solution. Here's what has been brought to my attention about the test package I have provided. --- I confirm that the proposed testfix package resolved the issue. The test were made on test machines where the client had an iptable postrouting nat forcing the source port to be under 123. - ntpdate command performed on the client machine was successful - tcpdump on the server side confirmed that the source port was under 123. Please advise for the next steps Thank-you --- [1] - https://launchpad.net/~slashd/+archive/ubuntu/bug1479652 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1479652 Title: [patch] ntpd rejects source UDP ports less than 123 as bogus To manage notifications about this bug go to: https://bugs.launchpad.net/ntp/+bug/1479652/+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 1479652] Re: [patch] ntpd rejects source UDP ports less than 123 as bogus
** Changed in: ntp (Ubuntu Xenial) Status: New => In Progress ** Changed in: ntp (Ubuntu Wily) Status: New => In Progress ** Changed in: ntp (Ubuntu Precise) Status: New => In Progress ** Changed in: ntp (Ubuntu Trusty) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1479652 Title: [patch] ntpd rejects source UDP ports less than 123 as bogus To manage notifications about this bug go to: https://bugs.launchpad.net/ntp/+bug/1479652/+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 1479652] Re: [patch] ntpd rejects source UDP ports less than 123 as bogus
** Changed in: ntp (Ubuntu Precise) Importance: Undecided => Medium ** Changed in: ntp (Ubuntu Trusty) Importance: Undecided => Medium ** Changed in: ntp (Ubuntu Wily) Importance: Undecided => Medium ** Changed in: ntp (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: ntp (Ubuntu Precise) Assignee: (unassigned) => Eric Desrochers (slashd) ** Changed in: ntp (Ubuntu Trusty) Assignee: (unassigned) => Eric Desrochers (slashd) ** Changed in: ntp (Ubuntu Wily) Assignee: (unassigned) => Eric Desrochers (slashd) ** Changed in: ntp (Ubuntu Xenial) Assignee: (unassigned) => Kick In (kick-d) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1479652 Title: [patch] ntpd rejects source UDP ports less than 123 as bogus To manage notifications about this bug go to: https://bugs.launchpad.net/ntp/+bug/1479652/+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 1498697] Re: Targets are not consistently shown with large numbers of targets
** 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 tgt in Ubuntu. https://bugs.launchpad.net/bugs/1498697 Title: Targets are not consistently shown with large numbers of targets To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tgt/+bug/1498697/+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 1481388] Re: NTP : Use-after-free in routing socket code after dropping root
** 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 the bug report. https://bugs.launchpad.net/bugs/1481388 Title: NTP : Use-after-free in routing socket code after dropping root To manage notifications about this bug go to: https://bugs.launchpad.net/ntp/+bug/1481388/+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 1481388] Re: NTP : Use-after-free in routing socket code after dropping root
** 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 the bug report. https://bugs.launchpad.net/bugs/1481388 Title: NTP : Use-after-free in routing socket code after dropping root To manage notifications about this bug go to: https://bugs.launchpad.net/ntp/+bug/1481388/+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 1481388] Re: NTP : Use-after-free in routing socket code after dropping root
** Tags added: sts -- 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/1481388 Title: NTP : Use-after-free in routing socket code after dropping root To manage notifications about this bug go to: https://bugs.launchpad.net/ntp/+bug/1481388/+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 1423226] Re: package open-vm-tools 2:9.4.0-1280544-5ubuntu6.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2
I had this issue after installing open-vm-tools WITHOUT first removing the version of vmware tools that is VMWare WorkStation automatically downloads and asks you to install. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to open-vm-tools in Ubuntu. https://bugs.launchpad.net/bugs/1423226 Title: package open-vm-tools 2:9.4.0-1280544-5ubuntu6.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1423226/+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 1368815] Re: qemu-img convert intermittently corrupts output images
Closing based on the assumption that a working qemu-img is available now. ** Changed in: cinder Status: Triaged => Won't Fix -- 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/1368815 Title: qemu-img convert intermittently corrupts output images To manage notifications about this bug go to: https://bugs.launchpad.net/cinder/+bug/1368815/+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 1481388] Re: NTP : Use-after-free in routing socket code after dropping root
Here is the rebase debdiff for Vivid ** Patch added: "Rebase Vivid debdiff" https://bugs.launchpad.net/ubuntu/vivid/+source/ntp/+bug/1481388/+attachment/4508498/+files/lp1481388_rebase_vivid.debdiff -- 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/1481388 Title: NTP : Use-after-free in routing socket code after dropping root To manage notifications about this bug go to: https://bugs.launchpad.net/ntp/+bug/1481388/+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 1481388] Re: NTP : Use-after-free in routing socket code after dropping root
Here is the rebase debdiff for Trusty ** Patch added: "Rebase Trusty debdiff" https://bugs.launchpad.net/ubuntu/vivid/+source/ntp/+bug/1481388/+attachment/4508494/+files/lp1481388_rebase_trusty.debdiff -- 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/1481388 Title: NTP : Use-after-free in routing socket code after dropping root To manage notifications about this bug go to: https://bugs.launchpad.net/ntp/+bug/1481388/+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 1481388] Re: NTP : Use-after-free in routing socket code after dropping root
Here is the rebase debdiff for Precise ** Patch added: "Rebase Precise debdiff" https://bugs.launchpad.net/ubuntu/vivid/+source/ntp/+bug/1481388/+attachment/4508496/+files/lp1481388_rebase_precise.debdiff -- 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/1481388 Title: NTP : Use-after-free in routing socket code after dropping root To manage notifications about this bug go to: https://bugs.launchpad.net/ntp/+bug/1481388/+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 1481388] Re: NTP : Use-after-free in routing socket code after dropping root
** Patch removed: "debdiff for precise" https://bugs.launchpad.net/ubuntu/vivid/+source/ntp/+bug/1481388/+attachment/4452908/+files/lp1481388_precise.debdiff ** Patch removed: "debdiff for trusty" https://bugs.launchpad.net/ubuntu/vivid/+source/ntp/+bug/1481388/+attachment/4453392/+files/lp1481388_trusty.debdiff ** Patch removed: "debdiff for vivid" https://bugs.launchpad.net/ubuntu/vivid/+source/ntp/+bug/1481388/+attachment/4456186/+files/lp1481388_vivid.debdiff -- 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/1481388 Title: NTP : Use-after-free in routing socket code after dropping root To manage notifications about this bug go to: https://bugs.launchpad.net/ntp/+bug/1481388/+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 1481388] Re: NTP : Use-after-free in routing socket code after dropping root
Hi Mathew, I have the knowledge of the code, I will rebase the debdiffs for V/T/P Note: I checked and Xenial has the patch already. -- 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/1481388 Title: NTP : Use-after-free in routing socket code after dropping root To manage notifications about this bug go to: https://bugs.launchpad.net/ntp/+bug/1481388/+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 1481388] Re: NTP : Use-after-free in routing socket code after dropping root
Good evening Mathew, Does it mean I need to re-do the debdiffs ? -- 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/1481388 Title: NTP : Use-after-free in routing socket code after dropping root To manage notifications about this bug go to: https://bugs.launchpad.net/ntp/+bug/1481388/+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 1481388] Re: NTP : Use-after-free in routing socket code after dropping root
Good evening Chris, This bug has been brought to my attention by someone in the community. Unfortunately, I never had a confirmation from him if the fix solve his issue or not... but as state in comment #5 & #11, I've been able to reproduce the problem and make sure it addressed the situation. The reproducer is basically to lower down the value of "net.core.[m-r]mem_default" and adding multiples network interface + static route. FYI, the same fix has been also applied in Debian ref: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=795315 Let me know if you need anything else. Thanks ! -- 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/1481388 Title: NTP : Use-after-free in routing socket code after dropping root To manage notifications about this bug go to: https://bugs.launchpad.net/ntp/+bug/1481388/+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 1481388] Re: NTP : Use-after-free in routing socket code after dropping root
** 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 the bug report. https://bugs.launchpad.net/bugs/1481388 Title: NTP : Use-after-free in routing socket code after dropping root To manage notifications about this bug go to: https://bugs.launchpad.net/ntp/+bug/1481388/+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 1510500] [NEW] package mysql-server-5.5 5.5.46-0ubuntu0.14.04.2 [modified: usr/share/mysql/errmsg-utf8.txt] failed to install/upgrade: subprocess installed post-installation script returned error
Public bug reported: None ProblemType: Package DistroRelease: Ubuntu 14.04 Package: mysql-server-5.5 5.5.46-0ubuntu0.14.04.2 [modified: usr/share/mysql/errmsg-utf8.txt] ProcVersionSignature: Ubuntu 3.16.0-51.69~14.04.1-generic 3.16.7-ckt17 Uname: Linux 3.16.0-51-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.16 Architecture: amd64 Date: Tue Oct 27 11:17:32 2015 DuplicateSignature: package:mysql-server-5.5:5.5.46-0ubuntu0.14.04.2 [modified: usr/share/mysql/errmsg-utf8.txt]:subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2015-08-04 (83 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) Logs.var.log.daemon.log: MySQLConf.etc.mysql.conf.d..keepme: MySQLConf.etc.mysql.conf.d.mysqld.safe.syslog.cnf: [mysqld_safe] syslog MySQLVarLibDirListing: ['ibdata1', 'ib_logfile1', 'ib_logfile0', 'mysql', 'debian-5.5.flag', 'performance_schema', 'mysql_upgrade_info'] ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-51-generic.efi.signed root=UUID=55488fcb-04b1-48e2-94dd-ced22b0fc0a9 ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.17.5ubuntu5.4 apt 1.0.1ubuntu2.10 SourcePackage: mysql-5.5 Title: package mysql-server-5.5 5.5.46-0ubuntu0.14.04.2 [modified: usr/share/mysql/errmsg-utf8.txt] failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: mysql-5.5 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package need-duplicate-check third-party-packages trusty -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mysql-5.5 in Ubuntu. https://bugs.launchpad.net/bugs/1510500 Title: package mysql-server-5.5 5.5.46-0ubuntu0.14.04.2 [modified: usr/share/mysql/errmsg-utf8.txt] failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.5/+bug/1510500/+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 1493067] Re: ssh-copy-id fails by making assumptions about the default shell on the remote machine
This should definitely be fixed in ssh-copy-id - making these assumptions is just bad. However, I found a workaround that is convenient for me at least and that I think could be a stopgap for others too, until such time as ssh- copy-id is fixed. I wrote it up here: http://blog.duesenklipper.de/2015/10/05/interactive-fish-without- breaking-sh-scripts.html -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1493067 Title: ssh-copy-id fails by making assumptions about the default shell on the remote machine To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1493067/+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 1498697] Re: Targets are not consistently shown with large numbers of targets
** 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 tgt in Ubuntu. https://bugs.launchpad.net/bugs/1498697 Title: Targets are not consistently shown with large numbers of targets To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tgt/+bug/1498697/+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 1498697] Re: Targets are not consistently shown with large numbers of targets
Source version has been modified for version "1:1.0.17-1ubuntu2.1". Thanks ! ** Patch added: "debdiff for Precise-2" https://bugs.launchpad.net/ubuntu/+source/tgt/+bug/1498697/+attachment/4482207/+files/lp1498697-precise-2.debdiff -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to tgt in Ubuntu. https://bugs.launchpad.net/bugs/1498697 Title: Targets are not consistently shown with large numbers of targets To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tgt/+bug/1498697/+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 1498697] Re: Targets are not consistently shown with large numbers of targets
As per our irc conversation, I'm removing the "2nd debdiff for Vivid" and arges will re-upload the fix with the original patch I posted for Vivid. Sorry for the confusion, and thanks Brian for you feedbacks on this. ** Patch removed: "2nd debdiff for Vivid" https://bugs.launchpad.net/ubuntu/trusty/+source/tgt/+bug/1498697/+attachment/4480119/+files/lp1498697_vivid2.debdiff -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to tgt in Ubuntu. https://bugs.launchpad.net/bugs/1498697 Title: Targets are not consistently shown with large numbers of targets To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tgt/+bug/1498697/+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 1498697] Re: Targets are not consistently shown with large numbers of targets
Hi Brian, I got a discussion with arges yesterday about it. vivid version of tgt didn't build with this error : sbuild-build-depends-tgt-dummy : Depends: libibverbs-dev (>= 1.1.8-1ubuntu1.1) but 1.1.8-1ubuntu1 is to be installed I think it has something to do with this LP patch : LP: https://bugs.launchpad.net/bugs/1409904 PPA: https://launchpad.net/~inaddy/+archive/ubuntu/lp1409904/ This is why the version of libibverbs-dev changed in the Vivid upload. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to tgt in Ubuntu. https://bugs.launchpad.net/bugs/1498697 Title: Targets are not consistently shown with large numbers of targets To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tgt/+bug/1498697/+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 1498697] Re: Targets are not consistently shown with large numbers of targets
2nd debdiff for Vivid (Fixing the unmet depencies of "libibverbs-dev") ** Patch added: "2nd debdiff for Vivid" https://bugs.launchpad.net/ubuntu/trusty/+source/tgt/+bug/1498697/+attachment/4480119/+files/lp1498697_vivid2.debdiff -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to tgt in Ubuntu. https://bugs.launchpad.net/bugs/1498697 Title: Targets are not consistently shown with large numbers of targets To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tgt/+bug/1498697/+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 1498697] Re: Targets are not consistently shown with large numbers of targets
** Tags added: sts -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to tgt in Ubuntu. https://bugs.launchpad.net/bugs/1498697 Title: Targets are not consistently shown with large numbers of targets To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tgt/+bug/1498697/+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 1498697] Re: Targets are not consistently shown with large numbers of targets
debdiff for Precise ** Changed in: tgt (Ubuntu Precise) Status: New => In Progress ** Changed in: tgt (Ubuntu Precise) Importance: Undecided => Medium ** Changed in: tgt (Ubuntu Precise) Assignee: (unassigned) => Eric Desrochers (eric-desrochers-z) ** Patch added: "debdiff for Precise" https://bugs.launchpad.net/ubuntu/vivid/+source/tgt/+bug/1498697/+attachment/4474355/+files/lp1498697_precise.debdiff -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to tgt in Ubuntu. https://bugs.launchpad.net/bugs/1498697 Title: Targets are not consistently shown with large numbers of targets To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tgt/+bug/1498697/+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 1498697] Re: Targets are not consistently shown with large numbers of targets
debdiff for Vivid ** Changed in: tgt (Ubuntu Vivid) Status: New => Confirmed ** Changed in: tgt (Ubuntu Vivid) Assignee: (unassigned) => Eric Desrochers (eric-desrochers-z) ** Changed in: tgt (Ubuntu Vivid) Importance: Undecided => High ** Changed in: tgt (Ubuntu Vivid) Status: Confirmed => In Progress ** Patch added: "debdiff for Vivid" https://bugs.launchpad.net/ubuntu/+source/tgt/+bug/1498697/+attachment/4473745/+files/lp1409904_vivid.debdiff ** Changed in: tgt (Ubuntu Vivid) Importance: High => Medium -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to tgt in Ubuntu. https://bugs.launchpad.net/bugs/1498697 Title: Targets are not consistently shown with large numbers of targets To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tgt/+bug/1498697/+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 1498697] Re: Targets are not consistently shown with large numbers of targets
debdiff for Trusty
** Description changed:
+ SRU JUSTIFICATION
+
+ [Impact]
+
+ * tgtadm returns inconsistents results. Some targets are not
+listed during one run, but are shown by a run immediately after.
+
+ [Test Case]
+
+ * With large number of targets :
+
+ # ./tgtadm -L iscsi --mode target --op show | fgrep -c Target
+ 564
+
+ # dpkg -l | fgrep tgt
+ ii tgt 1:1.0.43-0ubuntu4 amd64 Linux SCSI target user-space tools
+
+ # cat /etc/lsb-release
+ DISTRIB_ID=Ubuntu
+ DISTRIB_RELEASE=14.04
+ DISTRIB_CODENAME=trusty
+ DISTRIB_DESCRIPTION="Ubuntu 14.04.1 LTS"
+
+
+ Buggy 1.0.43 version:
+
+ # for i in {1..100} ; do diff -u <(/usr/sbin/tgtadm -L iscsi --mode target
--op show | fgrep Target) <(/usr/sbin/tgtadm -L iscsi --mode target --op show |
fgrep Target) ; sleep 1 ; done
+ --- /dev/fd/63 2015-09-22 23:05:38.648448562 +
+ +++ /dev/fd/62 2015-09-22 23:05:38.648448562 +
+ @@ -560,3 +560,5 @@
+ Target 574:
iqn.2010-10.org.openstack:volume-7adaa3bc-fafc-4421-baf7-b25102de1922
+ Target 578:
iqn.2010-10.org.openstack:volume-892c6840-ca04-4474-9976-9eaa8b54c4d2
+ Target 579:
iqn.2010-10.org.openstack:volume-d1d8062f-be47-4f33-b5b9-1befdfb09f65
+ +Target 580:
iqn.2010-10.org.openstack:volume-32a9e401-cf44-4f8f-ba93-fd43ff758e45
+ +Target 581:
iqn.2010-10.org.openstack:volume-ddcebcc4-eb13-459e-be1d-2068ee03a4c6
+ --- /dev/fd/63 2015-09-22 23:05:40.720506264 +
+ +++ /dev/fd/62 2015-09-22 23:05:40.720506264 +
+ @@ -560,3 +560,4 @@
+ Target 574:
iqn.2010-10.org.openstack:volume-7adaa3bc-fafc-4421-baf7-b25102de1922
+ Target 578:
iqn.2010-10.org.openstack:volume-892c6840-ca04-4474-9976-9eaa8b54c4d2
+ Target 579:
iqn.2010-10.org.openstack:volume-d1d8062f-be47-4f33-b5b9-1befdfb09f65
+ +Target 580:
iqn.2010-10.org.openstack:volume-32a9e401-cf44-4f8f-ba93-fd43ff758e45
+ --- /dev/fd/63 2015-09-22 23:05:41.752535004 +
+ +++ /dev/fd/62 2015-09-22 23:05:41.752535004 +
+ @@ -560,3 +560,5 @@
+ Target 574:
iqn.2010-10.org.openstack:volume-7adaa3bc-fafc-4421-baf7-b25102de1922
+ Target 578:
iqn.2010-10.org.openstack:volume-892c6840-ca04-4474-9976-9eaa8b54c4d2
+ Target 579:
iqn.2010-10.org.openstack:volume-d1d8062f-be47-4f33-b5b9-1befdfb09f65
+ +Target 580:
iqn.2010-10.org.openstack:volume-32a9e401-cf44-4f8f-ba93-fd43ff758e45
+ +Target 581:
iqn.2010-10.org.openstack:volume-ddcebcc4-eb13-459e-be1d-2068ee03a4c6
+ --- /dev/fd/63 2015-09-22 23:05:43.828592816 +
+ +++ /dev/fd/62 2015-09-22 23:05:43.828592816 +
+ @@ -560,4 +560,3 @@
+ Target 574:
iqn.2010-10.org.openstack:volume-7adaa3bc-fafc-4421-baf7-b25102de1922
+ Target 578:
iqn.2010-10.org.openstack:volume-892c6840-ca04-4474-9976-9eaa8b54c4d2
+ Target 579:
iqn.2010-10.org.openstack:volume-d1d8062f-be47-4f33-b5b9-1befdfb09f65
+ -Target 580:
iqn.2010-10.org.openstack:volume-32a9e401-cf44-4f8f-ba93-fd43ff758e45
+
+ [Regression Potential]
+
+ * None expected, the patch comes from tgt upstream repo and it is
+ already implemented in Ubuntu Wily and Debian.
+
+ [Other Info]
+
+ * The fix has been tested by the community and the fix resolved the issue.
For more details see Comment #4
+
+ [Original Description]
+
With a large number of targets tgtadm --mode target --op show returns
inconsistent results. Some targets are not listed during one run, but
are shown by a run immediately after.
I grabbed the binary from the wily package and I am getting consistent
results, so somewhere between 1.0.43 and 1.0.57 upstream seems to have
patched the bug.
Can we get 1.0.57 (or whatever version has the fix) backported to
trusty?
# ./tgtadm -L iscsi --mode target --op show | fgrep -c Target
564
# dpkg -l | fgrep tgt
ii tgt 1:1.0.43-0ubuntu4 amd64
Linux SCSI target user-space tools
- # cat /etc/lsb-release
+ # cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=14.04
DISTRIB_CODENAME=trusty
DISTRIB_DESCRIPTION="Ubuntu 14.04.1 LTS"
Buggy 1.0.43 version:
# for i in {1..100} ; do diff -u <(/usr/sbin/tgtadm -L iscsi --mode target
--op show | fgrep Target) <(/usr/sbin/tgtadm -L iscsi --mode target --op show |
fgrep Target) ; sleep 1 ; done
--- /dev/fd/632015-09-22 23:05:38.648448562 +
+++ /dev/fd/622015-09-22 23:05:38.648448562 +
@@ -560,3 +560,5 @@
- Target 574:
iqn.2010-10.org.openstack:volume-7adaa3bc-fafc-4421-baf7-b25102de1922
- Target 578:
iqn.2010-10.org.openstack:volume-892c6840-ca04-4474-9976-9eaa8b54c4d2
- Target 579:
iqn.2010-10.org.openstack:volume-d1d8062f-be47-4f33-b5b9-1befdfb09f65
+ Target 574:
iqn.2010-10.org.openstack:volume-7adaa3bc-fafc-4421-baf7-b25102de1922
+ Target 578:
iqn.2010-10.org.openstack:volume-892c6840-ca04-4474-9976-9eaa8b54c4d2
+ Target 579:
iqn.2010-10.org.openstack:volume-d1d8062f-be47-4f33-b5b9-1befdfb09f65
+Target 580:
iqn.2010-10.org.openstack:volume-32a9e401-cf44-4f8f-ba93-fd43ff758e45
+Target 581:
iqn.
[Bug 1498697] Re: Targets are not consistently shown with large numbers of targets
** Tags added: verification-done ** Changed in: tgt (Ubuntu Trusty) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to tgt in Ubuntu. https://bugs.launchpad.net/bugs/1498697 Title: Targets are not consistently shown with large numbers of targets To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tgt/+bug/1498697/+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 1498697] Re: Targets are not consistently shown with large numbers of targets
I'm providing a hotfix[1] for Trusty (14.04) on a ppa[2], based on the upstream commit : 6c4ffa0[3], for the community to test and provide feedbacks before starting the SRU process. This hotfix is only for testing purpose. [1] Version : 1:1.0.43-0ubuntu4.1~14.04.1+20150923lp1498697~1 [2] https://launchpad.net/~eric-desrochers-z/+archive/ubuntu/tgt1498697 [2] 6c4ffa0 tgtadm: fix a bug to read the response buffer -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to tgt in Ubuntu. https://bugs.launchpad.net/bugs/1498697 Title: Targets are not consistently shown with large numbers of targets To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tgt/+bug/1498697/+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 1498697] Re: Targets are not consistently shown with large numbers of targets
** Changed in: tgt (Ubuntu Trusty) Importance: Undecided => High ** Changed in: tgt (Ubuntu Trusty) Status: New => Confirmed ** Changed in: tgt (Ubuntu Trusty) Assignee: (unassigned) => Eric Desrochers (eric-desrochers-z) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to tgt in Ubuntu. https://bugs.launchpad.net/bugs/1498697 Title: Targets are not consistently shown with large numbers of targets To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tgt/+bug/1498697/+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 1481388] Re: NTP : Use-after-free in routing socket code after dropping root
Simon, you may want to add a few ethernet interfaces and static routes. I was able to reproduce it with ~6 network interface. -- 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/1481388 Title: NTP : Use-after-free in routing socket code after dropping root To manage notifications about this bug go to: https://bugs.launchpad.net/ntp/+bug/1481388/+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 1349949] Re: Juju's mongodb does not need to log every command in syslog
** Also affects: juju-core/1.25 Importance: Undecided Status: New ** Changed in: juju-core/1.25 Status: New => Triaged ** Changed in: juju-core/1.25 Importance: Undecided => High ** Changed in: juju-core/1.25 Milestone: None => 1.25-beta1 ** Changed in: juju-core Milestone: 1.25-beta1 => 1.26-alpha1 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mongodb in Ubuntu. https://bugs.launchpad.net/bugs/1349949 Title: Juju's mongodb does not need to log every command in syslog To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1349949/+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 1481388] Re: NTP : Use-after-free in routing socket code after dropping root
** Changed in: ntp (Ubuntu Wily) Importance: Low => Medium -- 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/1481388 Title: NTP : Use-after-free in routing socket code after dropping root To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1481388/+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 1481388] Re: NTP : Use-after-free in routing socket code after dropping root
debdiff for wily ** Patch added: "debdiff for wily" https://bugs.launchpad.net/ubuntu/vivid/+source/ntp/+bug/1481388/+attachment/4456187/+files/lp1481388_wily.debdiff ** Changed in: ntp (Ubuntu Wily) Status: Confirmed => In Progress -- 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/1481388 Title: NTP : Use-after-free in routing socket code after dropping root To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1481388/+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 1481388] Re: NTP : Use-after-free in routing socket code after dropping root
debdiff for vivid ** Patch added: "debdiff for vivid" https://bugs.launchpad.net/ubuntu/vivid/+source/ntp/+bug/1481388/+attachment/4456186/+files/lp1481388_vivid.debdiff -- 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/1481388 Title: NTP : Use-after-free in routing socket code after dropping root To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1481388/+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 1481388] Re: NTP : Use-after-free in routing socket code after dropping root
** Patch removed: "debdiff for Vivid" https://bugs.launchpad.net/ubuntu/vivid/+source/ntp/+bug/1481388/+attachment/4455714/+files/lp1481388_vivid.debdiff -- 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/1481388 Title: NTP : Use-after-free in routing socket code after dropping root To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1481388/+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 1481388] Re: NTP : Use-after-free in routing socket code after dropping root
debdiff for Vivid ** Patch added: "debdiff for Vivid" https://bugs.launchpad.net/ubuntu/precise/+source/ntp/+bug/1481388/+attachment/4455714/+files/lp1481388_vivid.debdiff ** Changed in: ntp (Ubuntu Vivid) Status: Confirmed => In Progress ** Changed in: ntp (Ubuntu Vivid) Importance: Undecided => Medium -- 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/1481388 Title: NTP : Use-after-free in routing socket code after dropping root To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1481388/+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 1481388] Re: NTP : Use-after-free in routing socket code after dropping root
debdiff for trusty ** Patch added: "1:4.2.6.p5+dfsg-3ubuntu2.14.04.4" https://bugs.launchpad.net/ubuntu/precise/+source/ntp/+bug/1481388/+attachment/4453392/+files/lp1481388_trusty.debdiff ** Changed in: ntp (Ubuntu Trusty) Status: Confirmed => In Progress ** Changed in: ntp (Ubuntu Trusty) Importance: Undecided => Medium -- 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/1481388 Title: NTP : Use-after-free in routing socket code after dropping root To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1481388/+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 1481388] Re: NTP : Use-after-free in routing socket code after dropping root
I also noticed the situation can be reproduced at boot if the value of "net.core.rmem_default" is too low. I reproduced it by only lowering the "net.core.rmem_default = 2000" value with 6 network interface at boot. ntpd[851]: ntp_io: estimated max descriptors: 1024, initial socket boundary: 16 ntpd[851]: Listen and drop on 0 v4wildcard 0.0.0.0 UDP 123 ntpd[851]: Listen and drop on 1 v6wildcard :: UDP 123 ntpd[851]: Listen normally on 2 eth1 192.168.1.10 UDP 123 ntpd[851]: Listen normally on 3 eth2 192.168.2.10 UDP 123 ntpd[851]: Listen normally on 4 eth3 192.168.3.10 UDP 123 ntpd[851]: Listen normally on 5 eth4 192.168.4.10 UDP 123 ntpd[851]: Listen normally on 6 eth5 192.168.5.10 UDP 123 ntpd[851]: Listen normally on 7 eth6 192.168.6.10 UDP 123 ntpd[851]: peers refreshed ntpd[851]: Listening on routing socket on fd #24 for interface updates ntpd[851]: Deferring DNS for 0.ubuntu.pool.ntp.org 1 ntpd[851]: Deferring DNS for 1.ubuntu.pool.ntp.org 1 ntpd[851]: Deferring DNS for 2.ubuntu.pool.ntp.org 1 ntpd[851]: Deferring DNS for 3.ubuntu.pool.ntp.org 1 ntpd[851]: Deferring DNS for ntp.ubuntu.com 1 ntpd[864]: signal_no_reset: signal 17 had flags 400 ===> ntpd[851]: i/o error on routing socket No buffer space available - disabling <=== -- 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/1481388 Title: NTP : Use-after-free in routing socket code after dropping root To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1481388/+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 1481388] Re: NTP : Use-after-free in routing socket code after dropping root
debdiff for precise -- 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/1481388 Title: NTP : Use-after-free in routing socket code after dropping root To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1481388/+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 1481388] Re: NTP : Use-after-free in routing socket code after dropping root
debdiff for precise ** Description changed: + [Impact] + + * User experienced repeated segfaults at the same instruction pointer + + i/o error on routing socket No buffer space available - disabling + segfault at 31 ip 0031 sp 79f11788 error 14 in libpthread-2.15.so[7f967a5d9000+18000] + + The remove_ and delete_ functions remove the current element from the + asyncio_reader_list, and free it, respectively. + + We then return back to the loop at the top, wherein the asyncio_reader variable still points at the now-freed element, whose contents are (in theory) now scrambled + by having link pointers, etc, from internal malloc state overlaying the data. + + [Test Case] + + You can easily reproduce the bug by : + + - Lowering the sysctl value net.core.rmem_max + + $ sysctl -w net.core.wmem_max= + This sets the max OS send buffer size for all types of connections. + + - Adding multiple network interfaces and static routes. + + [Regression Potential] + + None expected since the fix is already available upstream + (https://github.com/ntp-project/ntp.git) and Debian package. + + If after installing the patch, user are receiving this kind of message in /var/log/syslog : "routing socket reports: No buffer space available". + The next step, would be to increase the "net.core.rmem_max" and "net.core.wmem_max" values equally until the "routing socket reports: No buffer space available" message no longer showed up. + + [Other Info] + + NTP upstream (https://github.com/ntp-project/ntp.git) + [Bug 2224] Use-after-free in routing socket code after dropping root. - Commit: d6df9d3 + [Bug 2890] Ignore ENOBUFS on routing netlink socket. - Commit: db47bd4 + + The use-after-free bug has been fix in Debian release (closes: #795315) + Will submit the ignore-ENOBUFS-on-routing-netlink-socket in Debian in the next days. + + [Original Description] + We have 1 server (among hundreds) that its ntp service is crashing. A few minute/seconds after a start attempts we can see the following in syslog: ntpd[2729]: peers refreshed ntpd[2729]: Listening on routing socket on fd #49 for interface updates ntpd[2729]: i/o error on routing socket No buffer space available - disabling kernel: [157516.495224] ntpd[2729]: segfault at 31 ip 0031 sp 79f11788 error 14 in libpthread-2.15.so[7f967a5d9000+18000] OS: Ubuntu 12.04.4 LTS Kernel: 3.11.0-19-generic I tried to compare it to other servers, and the only thing I could find that is different is that while it's up (before it crashes) I can see the following when running "lsof | grep ntp": ntpd 2729 ntp 49u sock 0,7 0t0 2473952565 can't identify protocol. ** Tags added: verification-done ** Changed in: ntp (Ubuntu Precise) Status: Confirmed => In Progress -- 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/1481388 Title: NTP : Use-after-free in routing socket code after dropping root To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1481388/+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 1481388] Re: NTP : Use-after-free in routing socket code after dropping root
debdiff for precise ** Patch added: "debdiff for precise" https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1481388/+attachment/4452908/+files/lp1481388_precise.debdiff -- 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/1481388 Title: NTP : Use-after-free in routing socket code after dropping root To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1481388/+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 1481388] Re: NTP : Use-after-free in routing socket code after dropping root
debdiff for precise -- 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/1481388 Title: NTP : Use-after-free in routing socket code after dropping root To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1481388/+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 1481388] Re: NTP : Use-after-free in routing socket code after dropping root
** Changed in: ntp (Ubuntu Precise) Importance: Undecided => Medium ** Changed in: ntp (Ubuntu Vivid) Status: New => Confirmed -- 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/1481388 Title: NTP : Use-after-free in routing socket code after dropping root To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1481388/+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 1481388] Re: NTP : Use-after-free in routing socket code after dropping root
** Changed in: ntp (Ubuntu Precise) Assignee: (unassigned) => Eric Desrochers (eric-desrochers-z) ** Changed in: ntp (Ubuntu Vivid) Assignee: (unassigned) => Eric Desrochers (eric-desrochers-z) ** Changed in: ntp (Ubuntu Precise) Status: New => Confirmed -- 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/1481388 Title: NTP : Use-after-free in routing socket code after dropping root To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1481388/+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 1481388] Re: NTP : Use-after-free in routing socket code after dropping root
I was able to reproduce the problem on PRECISE (12.04) by lowering the kernel parameter value "net.core.rmem_max". And then test my .deb build on my PPA[1] with the following upstream commits : - d6df9d3 [Bug 2224] Use-after-free in routing socket code after dropping root. - db47bd4 [Bug 2890] Ignore ENOBUFS on routing netlink socket. What the patch does ? === The program first "read" from the fd. On success, the number of bytes written into buf is returned. On error, the call returns −1 and sets errno If the call returns -1, then there is a verification to validate if the errno == ENOBUFS and then send to syslog the following message : "routing socket reports: No buffer space available" Otherwise, if errno is NOT ENOBUFS, then it close the socket (remove_asyncio_reader(reader);) and free the memory space (delete_asyncio_reader(reader);) And send to syslog the following message : i/o error on routing socket No buffer space available - disabling Before this patch, no matter what was the errno, it was automatically close() and free() without validation if ENOBUFS or not. To summarize, the patch allow the program to not close() and free() the socket when the a errno == ENOBUFS occur, but still send a message in syslog to notify the administrator. === If after installing the patch, you are receiving this kind of message in /var/log/syslog : "routing socket reports: No buffer space available" The next step, would be to increase the "net.core.rmem_max" and "net.core.wmem_max"values equally until the "routing socket reports: No buffer space available" message no longer showed up. [1] 1:4.2.6.p3+dfsg-1ubuntu3.4+20150820lp1481388~2 https://launchpad.net/~eric-desrochers-z/+archive/ubuntu/lp1481388 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1481388 Title: NTP : Use-after-free in routing socket code after dropping root To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1481388/+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 1473022] Re: Openstack Kilo :Nova-api fails to call compute node
I am also seeing this intermittently when running nova commands via the
command line on Centos 7.1
For example when running nova --debug list:
DEBUG (session:195) REQ: curl -g -i -X GET https://x.x.x.x:35357/v2.0 -H
"Accept: application/json" -H "User-Agent: python-keystoneclient"
INFO (connectionpool:735) Starting new HTTPS connection (1): x.x.x.x
DEBUG (connectionpool:383) "GET /v2.0 HTTP/1.1" 200 347
DEBUG (session:224) RESP: [200] content-length: 347 set-cookie: node=mgmt03;
path=/ vary: X-Auth-Token server: Apache/2.4.6 (CentOS) OpenSSL/1.0.1e-fips
mod_wsgi/3.4 Python/2.7.5 date: Thu, 06 Aug 2015 01:08:21 GMT content-type:
application/json x-openstack-request-id:
req-73b79363-f7b8-4a97-a8a7-f96c93c41f18
RESP BODY: {"version": {"status": "stable", "updated": "2014-04-17T00:00:00Z",
"media-types": [{"base": "application/json", "type":
"application/vnd.openstack.identity-v2.0+json"}], "id": "v2.0", "links":
[{"href": "https://x.x.x.x:35357/v2.0/";, "rel": "self"}, {"href":
"http://docs.openstack.org/";, "type": "text/html", "rel": "describedby"}]}}
DEBUG (v2:76) Making authentication request to https://x.x.x.x:35357/v2.0/tokens
DEBUG (connectionpool:383) "POST /v2.0/tokens HTTP/1.1" 200 2727
DEBUG (iso8601:184) Parsed 2015-08-06T02:08:21Z into {'tz_sign': None,
'second_fraction': None, 'hour': u'02', 'daydash': u'06', 'tz_hour': None,
'month': None, 'timezone': u'Z', 'second': u'21', 'tz_minute': None, 'year':
u'2015', 'separator': u'T', 'monthdash': u'08', 'day': None, 'minute': u'08'}
with default timezone
DEBUG (iso8601:140) Got u'2015' for 'year' with default None
DEBUG (iso8601:140) Got u'08' for 'monthdash' with default 1
DEBUG (iso8601:140) Got 8 for 'month' with default 8
DEBUG (iso8601:140) Got u'06' for 'daydash' with default 1
DEBUG (iso8601:140) Got 6 for 'day' with default 6
DEBUG (iso8601:140) Got u'02' for 'hour' with default None
DEBUG (iso8601:140) Got u'08' for 'minute' with default None
DEBUG (iso8601:140) Got u'21' for 'second' with default None
DEBUG (session:195) REQ: curl -g -i -X GET
https://x.x.x.x:8774/v2/7c289b706e644980ac5b9a36874cdeff/servers/detail -H
"User-Agent: python-novaclient" -H "Accept: application/json" -H "X-Auth-Token:
{SHA1}618596dc30335e9c814b1daf459b81ce99431e91"
INFO (connectionpool:735) Starting new HTTPS connection (1): x.x.x.x
DEBUG (connectionpool:383) "GET
/v2/7c289b706e644980ac5b9a36874cdeff/servers/detail HTTP/1.1" 401 23
DEBUG (session:224) RESP:
DEBUG (v2:76) Making authentication request to https://x.x.x.x:35357/v2.0/tokens
DEBUG (connectionpool:383) "POST /v2.0/tokens HTTP/1.1" 200 2727
DEBUG (connectionpool:383) "GET
/v2/7c289b706e644980ac5b9a36874cdeff/servers/detail HTTP/1.1" 500 128
DEBUG (session:224) RESP:
DEBUG (shell:914) The server has either erred or is incapable of performing the
requested operation. (HTTP 500) (Request-ID:
req-a2b6989f-19b8-453e-bf93-34fa50a108e2)
Traceback (most recent call last):
File "/usr/lib/python2.7/site-packages/novaclient/shell.py", line 911, in main
OpenStackComputeShell().main(argv)
File "/usr/lib/python2.7/site-packages/novaclient/shell.py", line 838, in main
args.func(self.cs, args)
File "/usr/lib/python2.7/site-packages/novaclient/v2/shell.py", line 1377, in
do_list
sort_dirs=sort_dirs)
File "/usr/lib/python2.7/site-packages/novaclient/v2/servers.py", line 583,
in list
return self._list("/servers%s%s" % (detail, query_string), "servers")
File "/usr/lib/python2.7/site-packages/novaclient/base.py", line 64, in _list
_resp, body = self.api.client.get(url)
File "/usr/lib/python2.7/site-packages/keystoneclient/adapter.py", line 170,
in get
return self.request(url, 'GET', **kwargs)
File "/usr/lib/python2.7/site-packages/novaclient/client.py", line 96, in
request
raise exceptions.from_response(resp, body, url, method)
ClientException: The server has either erred or is incapable of performing the
requested operation. (HTTP 500) (Request-ID:
req-a2b6989f-19b8-453e-bf93-34fa50a108e2)
on the mgmt03 node in /var/log/nova/nova-api.log I see:
2015-08-06 13:08:22.890 7373 DEBUG keystoneclient.session
[req-a2b6989f-19b8-453e-bf93-34fa50a108e2 03d24899e1d24a22bc1fae13dcc62fee
7c289b706e644980ac5b9a36874cdeff - - -] REQ: curl -g -i -X GET
https://x.x.x.x:9696/v2.0/ports.json?device_id=a5a4cfd3-8ca0-4e93-9c6b-2fb02b73f9c5&device_id=54d1d328-fef7-40a1-9311-eadc204bbfe5&device_id=6d4f76d6-4362-402a-b369-c69d7154f671
-H "User-Agent: python-neutronclient" -H "Accept: application/json" -H
"X-Auth-Token: {SHA1}c114cb664ce090f96baf5cfeb8096690b480eb38"
_http_log_request /usr/lib/python2.7/site-packages/keystoneclient/session.py:195
2015-08-06 13:08:22.894 7373 ERROR nova.api.openstack
[req-a2b6989f-19b8-453e-bf93-34fa50a108e2 03d24899e1d24a22bc1fae13dcc62fee
7c289b706e644980ac5b9a36874cdeff - - -] Caught error: []
2015-08-06 13:08:22.894 7373 TRACE nova.api.openstack Traceback (most recent
call last):
2015-08-06 13:08:22.894 7373 TRACE nova.api.openst
[Bug 1451091] Re: new upstream version 5.2.2
Strongswan 5.3.2 is out now. What would it take to pull it in? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to strongswan in Ubuntu. https://bugs.launchpad.net/bugs/1451091 Title: new upstream version 5.2.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/strongswan/+bug/1451091/+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 1470277] [NEW] strongswan apparmor profile doesn't permit xauth-pam
Public bug reported: When using the strongswan xauth-pam plugin I get an error at startup regarding missing capabilities and the plugin doesn't load. --- xauth-pam plugin requires CAP_AUDIT_WRITE capability plugin 'xauth-pam': failed to load - xauth_pam_plugin_create returned NULL --- If I add "capability audit_write," to /etc/apparmor.d/local/usr.lib.ipsec.charon it works. I would expect the plugin to work without modifying the local apparmor profile. Package info: strongswan: Installed: 5.1.2-0ubuntu2.3 Candidate: 5.1.2-0ubuntu2.3 strongswan-plugin-xauth-pam: Installed: 5.1.2-0ubuntu2.3 Candidate: 5.1.2-0ubuntu2.3 Ubuntu info: Description: Ubuntu 14.04.2 LTS Release: 14.04 ** Affects: strongswan (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to strongswan in Ubuntu. https://bugs.launchpad.net/bugs/1470277 Title: strongswan apparmor profile doesn't permit xauth-pam To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/strongswan/+bug/1470277/+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 1214379] Re: pinger crashed with SIGSEGV in malloc_consolidate()
Got a similar crash in 14.04 while using Synaptic to perform an upgrade. Have version 0.8.6 of squid-deb-proxy and squid-deb-proxy-client installed. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid3 in Ubuntu. https://bugs.launchpad.net/bugs/1214379 Title: pinger crashed with SIGSEGV in malloc_consolidate() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1214379/+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 1302963] Re: Calendar() class can not be initialized
On 14.04 pip --upgrade parsedatetime appears to work. Additionally installing from sources with latest version works. Just make certain you dont have old copies of the library laying around. Then actual route I got to the fix involved removing the library from /usr/lib and /usr/local/lib and then installing via pip. To check the solution via sources I installed the version installed via pip and installed then from sources. So both options worked for me on 14.04 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to parsedatetime in Ubuntu. https://bugs.launchpad.net/bugs/1302963 Title: Calendar() class can not be initialized To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/parsedatetime/+bug/1302963/+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 1409639] Re: juju needs to support systemd for >= vivid
** Tags added: systemd vivid -- 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/1409639 Title: juju needs to support systemd for >= vivid To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1409639/+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 1150720] Re: [SRU] There is now a dependency on paramiko v1.8.0
Cinder now depends on paramiko >=1.13.0. ** Changed in: cinder Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cinder in Ubuntu. https://bugs.launchpad.net/bugs/1150720 Title: [SRU] There is now a dependency on paramiko v1.8.0 To manage notifications about this bug go to: https://bugs.launchpad.net/cinder/+bug/1150720/+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 1409639] Re: juju needs to support systemd for >= vivid
** Changed in: juju-core Milestone: 1.23 => 1.23-beta1 -- 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/1409639 Title: juju needs to support systemd for >= vivid To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1409639/+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 1409639] Re: juju needs to support systemd for >= vivid
It will also be worth looking into the impact of systemd on existing charms that get published for vivid. -- 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/1409639 Title: juju needs to support systemd for >= vivid To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1409639/+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 1409639] Re: juju needs to support systemd for >= vivid
the last of the patches to add systemd support in juju (including on vivid) has landed. There are a couple of caveats we need to look into though: * vivid LXC containers on non-vivid hosts don't work correctly out of the box. This has an impact on local provider (I've been testing in a vivid KVM). See https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1347020 * vivid (and later) may be configured to boot with upstart (e.g. after an upgrade?). We are looking at adding a feature flag to support that use case (which I expect will be an uncommon one). ** Changed in: juju-core Status: In Progress => Fix Committed ** Changed in: juju-core Assignee: (unassigned) => Eric Snow (ericsnowcurrently) -- 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/1409639 Title: juju needs to support systemd for >= vivid To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1409639/+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 1409639] Re: juju needs to support systemd for >= vivid
We've landed a patch for systemd support in juju. We are currently working through a couple of minor bugs before calling it good. ** 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-core in Ubuntu. https://bugs.launchpad.net/bugs/1409639 Title: juju needs to support systemd for >= vivid To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1409639/+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 1409639] Re: juju needs to support systemd for >= vivid
Right now we (juju core) are scoping out the effort to add systemd support to juju in time for the feature freeze. We'll update here as we move forward. Note that, as Andrew said, we have some of the work done already (though not merged yet). It's likely the trickiest part, so the remainder of the work should be of the add-systemd-support-wherever-we-support- upstart variety. Also note that our upstart configs are dynamically generated. -- 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/1409639 Title: juju needs to support systemd for >= vivid To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1409639/+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 444349] FW:12/25/2014 8:47:18 AM x
http://www.rrzconsulting.com/kc/feccfweurdhsabfpshznnphtidsfwycpxxqglx.cgaiwowlrpahfxiujvtvcjqjiox eric.speas -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mysql-dfsg-5.1 in Ubuntu. https://bugs.launchpad.net/bugs/444349 Title: package mysql-server failed to install/upgrade: skip-bdb option not supported To manage notifications about this bug go to: https://bugs.launchpad.net/mysql-server/+bug/444349/+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 1024475] Re: libnss-ldap causes boot hang on Ubuntu 12.04 Precise
OK, so it appears that libnss-ldapd also works for me. (looks more like RH anyway). -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libnss-ldap in Ubuntu. https://bugs.launchpad.net/bugs/1024475 Title: libnss-ldap causes boot hang on Ubuntu 12.04 Precise To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libnss-ldap/+bug/1024475/+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 1024475] Re: libnss-ldap causes boot hang on Ubuntu 12.04 Precise
Dang! this is not a little thing! How does one get some attention on this issue? What does it take to get this bug fixed? Anyone? - This has and is causing me countless hours. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libnss-ldap in Ubuntu. https://bugs.launchpad.net/bugs/1024475 Title: libnss-ldap causes boot hang on Ubuntu 12.04 Precise To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libnss-ldap/+bug/1024475/+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 1404351] [NEW] krb5-config missing debconf-set-selections variable
Public bug reported: krb5-config.config seams to be missing a variable as there is no way to stop a dialog box from poping up in my script for installing Kerberos 5. I am using Ubuntu 14.04.01 LTS I get error message:Use of uninitialized value $admin in string eq at /var/lib/dpkg/info/krb5-config.config line 171, line 20. Then I get dialog box titled: "Configuring krb5-admin-server" Stating: Setting up a Kerberos Realm This package contains the administrative tools required to run the Kerberos master server.However, installing this package does not automatically set up a Kerberos realm. This can be done later by running the "krb5_newrealm" command. Please also read the /usr/share/doc/krb5-kdc/README.KDC file and the administration guide found in the krb5-doc package. Then I get error when it setting up: Setting up krb5-config (2.3) ... Use of uninitialized value $admin in string eq at /var/lib/dpkg/info/krb5-config.config line 171, line 19. I have in my script the following setting: #Kerberos 5 Settings. echo -e "krb5-config krb5-config/kerberos_servers string $fqdn" | debconf-set-selections echo -e "krb5-config krb5-config/default_realm string $Realm" | debconf-set-selections echo -e "heimdal-kdc heimdal/realm string $Realm" | debconf-set-selections echo -e "krb5-config krb5-config/admin_server string $fqdn" | debconf-set-selections echo -e "krb5-config krb5-config/dns_for_default boolean true" | debconf-set-selections echo -e "krb5-config krb5-config/add_servers boolean true" | debconf-set-selections I found all these debconf-set-selections, but changing any other setting do not stop the dialog box from coming up. ran debconf-get-selections | grep krb5-config krb5-config krb5-config/read_conf boolean true krb5-config krb5-config/default_realm string TEETER.HOME krb5-config krb5-config/add_servers boolean true krb5-config krb5-config/admin_serverstring krb5-config krb5-config/kerberos_serversstring krb5-config krb5-config/dns_for_default boolean true krb5-config krb5-config/add_servers_realm string TEETER.HOME I could work around by forcing noninteractive, but shouldn't there be a way to trun off the dialog box? ** Affects: kerberos-configs (Ubuntu) Importance: Undecided Status: New ** Description changed: krb5-config.config seams to be missing a variable as there is no way to stop a dialog box from poping up in my script for installing Kerberos 5. + I am using Ubuntu 14.04.01 LTS I get error message:Use of uninitialized value $admin in string eq at /var/lib/dpkg/info/krb5-config.config line 171, line 20. Then I get dialog box titled: "Configuring krb5-admin-server" Stating: - Setting up a Kerberos Realm + Setting up a Kerberos Realm - This package contains the administrative tools required to run the Kerberos master server.However, installing this package does not automatically set up a Kerberos realm. This can be done later by running the "krb5_newrealm" command. + This package contains the administrative tools required to run the Kerberos master server.However, installing this package does not automatically set up a Kerberos realm. This can be done later by running the "krb5_newrealm" command. Please also read the /usr/share/doc/krb5-kdc/README.KDC file and the administration guide found in the krb5-doc package. - - + Then I get error when it setting up: Setting up krb5-config (2.3) ... Use of uninitialized value $admin in string eq at /var/lib/dpkg/info/krb5-config.config line 171, line 19. I have in my script the following setting: - #Kerberos 5 Settings. - echo -e "krb5-config krb5-config/kerberos_servers string $fqdn" | debconf-set-selections + #Kerberos 5 Settings. + echo -e "krb5-config krb5-config/kerberos_servers string $fqdn" | debconf-set-selections echo -e "krb5-config krb5-config/default_realm string $Realm" | debconf-set-selections echo -e "heimdal-kdc heimdal/realm string $Realm" | debconf-set-selections - echo -e "krb5-config krb5-config/admin_server string $fqdn" | debconf-set-selections + echo -e "krb5-config krb5-config/admin_server string $fqdn" | debconf-set-selections echo -e "krb5-config krb5-config/dns_for_default boolean true" | debconf-set-selections echo -e "krb5-config krb5-config/add_servers boolean true" | debconf-set-selections I found all these debconf-set-selections, but changing any other setting do not stop the dialog box from coming up. ran debconf-get-selections | grep krb5-config krb5-config krb5-config/read_conf boolean true krb5-config krb5-config/default_realm string TEETER.HOME krb5-config krb5-config/add
[Bug 1394206] [NEW] package ssl-cert 1.0.34 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: The error appears for all updates. ProblemType: Package DistroRelease: Ubuntu 14.10 Package: ssl-cert 1.0.34 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 Uname: Linux 3.16.0-25-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 Date: Wed Nov 19 06:58:24 2014 DuplicateSignature: package:ssl-cert:1.0.34:subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2014-07-31 (110 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) PackageArchitecture: all SourcePackage: ssl-cert Title: package ssl-cert 1.0.34 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to utopic on 2014-10-27 (22 days ago) ** Affects: ssl-cert (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package utopic -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ssl-cert in Ubuntu. https://bugs.launchpad.net/bugs/1394206 Title: package ssl-cert 1.0.34 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ssl-cert/+bug/1394206/+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 1379761] Re: Asset compression does not happen unless debug mode is enabled
additional note: when you do offline compression and stuff get's moved into the static folder, using the --runserver cli to start up django will not serve out the /static url. for this type of use, I believe it's expected that apache would serve out those assets from the ./static folder (which is how I do work, with modwsgi etc) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to horizon in Ubuntu. https://bugs.launchpad.net/bugs/1379761 Title: Asset compression does not happen unless debug mode is enabled To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1379761/+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 1379761] Re: Asset compression does not happen unless debug mode is enabled
it works for me, following these steps: Change local settings, have the following at the top of the file: DEBUG = False TEMPLATE_DEBUG = DEBUG COMPRESS_OFFLINE = True Then I run these commands: tools/with_venv.sh python manage.py collectstatic --noinput tools/with_venv.sh python manage.py compress --force The compress step produces this to the console: Invalid template /home/eric/work/public/horizon/horizon/templates/horizon/common/_formset_table_row.html: Invalid block tag: 'blocktrans', expected 'empty' or 'endfor' Found 'compress' tags in: /home/eric/work/public/horizon/openstack_dashboard/templates/_stylesheets.html /home/eric/work/public/horizon/horizon/templates/horizon/_conf.html /home/eric/work/public/horizon/horizon/templates/horizon/_scripts.html Compressing... done Compressed 4 block(s) from 3 template(s). eric@eric-VirtualBox:~/work/public/horizon$ While there is an error / warning, it does complete ok and is useable. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to horizon in Ubuntu. https://bugs.launchpad.net/bugs/1379761 Title: Asset compression does not happen unless debug mode is enabled To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1379761/+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 1379761] Re: Asset compression does not happen unless debug mode is enabled
git describe 2014.2.rc1-145-g123840a that is my current version where it works -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to horizon in Ubuntu. https://bugs.launchpad.net/bugs/1379761 Title: Asset compression does not happen unless debug mode is enabled To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1379761/+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
Re: [Bug 1356715] Re: package apache2 2.4.6-2ubuntu2.2 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1
This is correct indeed: I am using a non standard module mod_ip but my issue is that the installer did not display any warning at all and basically mostly abort in the middle... -éric On 14/08/14 11:39, "Robie Basak" <1356...@bugs.launchpad.net> wrote: >Thank you for your report. > >This looks like a local configuration problem, rather than a bug in >Ubuntu. > >Specifically, it looks like your issue is with mod_ip, which does not >ship with Ubuntu's Apache packaging. > >You can find pointers to get help for this sort of problem here: >http://www.ubuntu.com/support/community > >Since we use this bug tracker to track bugs in Ubuntu, rather than >configuration problems, I'm marking this bug as Invalid. This helps us >to focus on fixing bugs in Ubuntu. > >If you believe that this is really a bug, then you may find it helpful >to read "How to report bugs effectively" >http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful >if you would then provide a more complete description of the problem, >explain why you believe this is a bug in Ubuntu rather than a problem >specific to your system, and then change the bug status back to New. > >** Changed in: apache2 (Ubuntu) > Status: New => Invalid > >-- >You received this bug notification because you are subscribed to the bug >report. >https://bugs.launchpad.net/bugs/1356715 > >Title: > package apache2 2.4.6-2ubuntu2.2 failed to install/upgrade: > ErrorMessage: subprocess installed post-installation script returned > error exit status 1 > >Status in ³apache2² package in Ubuntu: > Invalid > >Bug description: > Setting up apache2 (2.4.6-2ubuntu2.2) ... > apache2: Syntax error on line 239 of /etc/apache2/apache2.conf: Syntax >error on line 1 of /etc/apache2/mods-enabled/ip.load: Cannot load >/usr/lib/apache2/modules/mod_ip.so into server: >/usr/lib/apache2/modules/mod_ip.so: undefined symbol: ap_log_rerror > ERROR: Config file userdir.conf not properly enabled: >/etc/apache2/mods-enabled/userdir.conf is a real file, not touching it > dpkg: error processing apache2 (--configure): > subprocess installed post-installation script returned error exit >status 1 > dpkg: dependency problems prevent configuration of libapache2-mod-php5: > libapache2-mod-php5 depends on apache2 (>= 2.4); however: >Package apache2 is not configured yet. > > dpkg: error processing libapache2-mod-php5 (--configure): > dependency problems - leaving unconfigured > dpkg: dependency problems prevent configuration of apache2-mpm-prefork: > apache2-mpm-prefork depends on apache2 (= 2.4.6-2ubuntu2.2); however: >Package apache2 is not configured yet. > > dpkg: error processing apache2-mpm-prefork (--configure): > dependency problems - leaving unconfigured > Errors were encountered while processing: > apache2 > libapache2-mod-php5 > apache2-mpm-prefork > > Upgrade complete > > The upgrade has completed but there were errors during the upgrade > process. > > ProblemType: Package > DistroRelease: Ubuntu 13.10 > Package: apache2 2.4.6-2ubuntu2.2 > Uname: Linux 3.2.13-grsec--grs-ipv6-64 x86_64 > Apache2ConfdDirListing: False > Apache2Modules: > Error: command ['/usr/sbin/apachectl', '-D DUMP_MODULES'] failed with >exit code 1: apache2: Syntax error on line 239 of >/etc/apache2/apache2.conf: Syntax error on line 1 of >/etc/apache2/mods-enabled/ip.load: Cannot load >/usr/lib/apache2/modules/mod_ip.so into server: >/usr/lib/apache2/modules/mod_ip.so: undefined symbol: ap_log_rerror > Action '-D DUMP_MODULES' failed. > The Apache error log may have more information. > ApportVersion: 2.12.5-0ubuntu2.2 > Architecture: amd64 > Date: Thu Aug 14 00:06:11 2014 > DuplicateSignature: package:apache2:2.4.6-2ubuntu2.2:ErrorMessage: >subprocess installed post-installation script returned error exit status 1 > ErrorMessage: ErrorMessage: subprocess installed post-installation >script returned error exit status 1 > MarkForUpload: True > SourcePackage: apache2 > Title: package apache2 2.4.6-2ubuntu2.2 failed to install/upgrade: >ErrorMessage: subprocess installed post-installation script returned >error exit status 1 > UpgradeStatus: Upgraded to saucy on 2014-08-13 (0 days ago) > modified.conffile..etc.apache2.apache2.conf: [modified] > modified.conffile..etc.apache2.mods.available.negotiation.conf: >[modified] > modified.conffile..etc.apache2.mods.available.ssl.conf: [modified] > modified.conffile..etc.apache2.ports.conf: [modified] > modified.conffile..etc.apache2.sites.available.000.default.conf: >[modified] > modified.conffile..etc.apache2.sites.available.default.ssl.conf: >[modified] > modified.conffile..etc.logrotate.d.apache2: [modified] > mtime.conffile..etc.apache2.apache2.conf: 2013-10-21T18:49:55.969673 > mtime.conffile..etc.apache2.mods.available.negotiation.conf: >2013-05-27T19:29:00.557090 > mtime.conffile..etc.apache2.mods.available.ssl.conf: >2013-05-13T08:05:55.822911 > mtime.conffile..etc.apache2.ports.conf: 2014-
[Bug 1356715] [NEW] package apache2 2.4.6-2ubuntu2.2 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1
Public bug reported: Setting up apache2 (2.4.6-2ubuntu2.2) ... apache2: Syntax error on line 239 of /etc/apache2/apache2.conf: Syntax error on line 1 of /etc/apache2/mods-enabled/ip.load: Cannot load /usr/lib/apache2/modules/mod_ip.so into server: /usr/lib/apache2/modules/mod_ip.so: undefined symbol: ap_log_rerror ERROR: Config file userdir.conf not properly enabled: /etc/apache2/mods-enabled/userdir.conf is a real file, not touching it dpkg: error processing apache2 (--configure): subprocess installed post-installation script returned error exit status 1 dpkg: dependency problems prevent configuration of libapache2-mod-php5: libapache2-mod-php5 depends on apache2 (>= 2.4); however: Package apache2 is not configured yet. dpkg: error processing libapache2-mod-php5 (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of apache2-mpm-prefork: apache2-mpm-prefork depends on apache2 (= 2.4.6-2ubuntu2.2); however: Package apache2 is not configured yet. dpkg: error processing apache2-mpm-prefork (--configure): dependency problems - leaving unconfigured Errors were encountered while processing: apache2 libapache2-mod-php5 apache2-mpm-prefork Upgrade complete The upgrade has completed but there were errors during the upgrade process. ProblemType: Package DistroRelease: Ubuntu 13.10 Package: apache2 2.4.6-2ubuntu2.2 Uname: Linux 3.2.13-grsec--grs-ipv6-64 x86_64 Apache2ConfdDirListing: False Apache2Modules: Error: command ['/usr/sbin/apachectl', '-D DUMP_MODULES'] failed with exit code 1: apache2: Syntax error on line 239 of /etc/apache2/apache2.conf: Syntax error on line 1 of /etc/apache2/mods-enabled/ip.load: Cannot load /usr/lib/apache2/modules/mod_ip.so into server: /usr/lib/apache2/modules/mod_ip.so: undefined symbol: ap_log_rerror Action '-D DUMP_MODULES' failed. The Apache error log may have more information. ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Thu Aug 14 00:06:11 2014 DuplicateSignature: package:apache2:2.4.6-2ubuntu2.2:ErrorMessage: subprocess installed post-installation script returned error exit status 1 ErrorMessage: ErrorMessage: subprocess installed post-installation script returned error exit status 1 MarkForUpload: True SourcePackage: apache2 Title: package apache2 2.4.6-2ubuntu2.2 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to saucy on 2014-08-13 (0 days ago) modified.conffile..etc.apache2.apache2.conf: [modified] modified.conffile..etc.apache2.mods.available.negotiation.conf: [modified] modified.conffile..etc.apache2.mods.available.ssl.conf: [modified] modified.conffile..etc.apache2.ports.conf: [modified] modified.conffile..etc.apache2.sites.available.000.default.conf: [modified] modified.conffile..etc.apache2.sites.available.default.ssl.conf: [modified] modified.conffile..etc.logrotate.d.apache2: [modified] mtime.conffile..etc.apache2.apache2.conf: 2013-10-21T18:49:55.969673 mtime.conffile..etc.apache2.mods.available.negotiation.conf: 2013-05-27T19:29:00.557090 mtime.conffile..etc.apache2.mods.available.ssl.conf: 2013-05-13T08:05:55.822911 mtime.conffile..etc.apache2.ports.conf: 2014-08-05T13:09:09.716262 mtime.conffile..etc.apache2.sites.available.000.default.conf: 2014-08-05T09:47:31.499686 mtime.conffile..etc.apache2.sites.available.default.ssl.conf: 2014-06-16T21:51:36.320478 mtime.conffile..etc.logrotate.d.apache2: 2013-05-26T19:24:27.464225 ** Affects: apache2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package saucy -- 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/1356715 Title: package apache2 2.4.6-2ubuntu2.2 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1356715/+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 1257186] Re: memory leakage messages
This importance of this bug should probably be reexamined, because it has impact on other softwares, like Netatalk. It prevents AFP shares from being accessible and make Netatalk totally useless. Here is a syslog trace where Netatalk crash because of this bug : May 17 10:48:29 ace-of-spades afpd[3498]: === May 17 10:48:29 ace-of-spades afpd[3498]: INTERNAL ERROR: Signal 11 in pid 3498 (2.2.2) May 17 10:48:29 ace-of-spades afpd[3498]: === May 17 10:48:29 ace-of-spades afpd[3498]: BACKTRACE: 3 stack frames: May 17 10:48:29 ace-of-spades afpd[3498]: #0 /usr/sbin/afpd(netatalk_panic+0x1f) [0x7f4acaaf08bf] May 17 10:48:29 ace-of-spades afpd[3498]: #1 /usr/sbin/afpd(+0x549bc) [0x7f4acaaf09bc] May 17 10:48:29 ace-of-spades afpd[3498]: #2 /lib/x86_64-linux-gnu/libc.so.6(+0x36ff0) [0x7f4ac9440ff0] See this bug report : https://bugs.launchpad.net/ubuntu/+source/netatalk/+bug/810732 Disabling SMB password synchronization (for example with pam-auth- update) not onyl remove the error message of this bug but also restore Netatalk behavior. -- 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/1257186 Title: memory leakage messages To manage notifications about this bug go to: https://bugs.launchpad.net/samba/+bug/1257186/+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 444349] eric.speas
http://perren-online.ch/pznnogbw/gluhhjetjnghvwpngrahlfym.ovwkscdo -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mysql-dfsg-5.1 in Ubuntu. https://bugs.launchpad.net/bugs/444349 Title: package mysql-server failed to install/upgrade: skip-bdb option not supported To manage notifications about this bug go to: https://bugs.launchpad.net/mysql-server/+bug/444349/+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 1304150] [NEW] apt-get upgrade didn't handle missing config file gracefully
Public bug reported: When there was a conflict between my etckeeper.conf and the dpkg-dist version, I edited etckeeper.conf.dpkg-dist, intending to accept that version of the file. But I absent-mindedly deleted the original etckeeper.conf and renamed the .dpkg-dist version to that. Then I pressed Y (keep packaged version). Apt-get upgrade noticed the file was missing but didn't handle it very gracefully -- it didn't offer me the chance to make my selection again and/or rename or copy the file. I think it would be nice if it gave such options. ProblemType: Package DistroRelease: Ubuntu 13.10 Package: etckeeper 1.4ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-48.72-generic 3.5.7.31 Uname: Linux 3.5.0-48-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Mon Apr 7 22:15:49 2014 DuplicateSignature: package:etckeeper:1.4ubuntu1:ErrorMessage: unable to install `/etc/etckeeper/etckeeper.conf.dpkg-new' as `/etc/etckeeper/etckeeper.conf': No such file or directory ErrorMessage: ErrorMessage: unable to install `/etc/etckeeper/etckeeper.conf.dpkg-new' as `/etc/etckeeper/etckeeper.conf': No such file or directory MarkForUpload: True PackageArchitecture: all SourcePackage: etckeeper Title: package etckeeper 1.4ubuntu1 failed to install/upgrade: ErrorMessage: unable to install `/etc/etckeeper/etckeeper.conf.dpkg-new' as `/etc/etckeeper/etckeeper.conf': No such file or directory UpgradeStatus: Upgraded to saucy on 2014-04-08 (0 days ago) mtime.conffile..etc.etckeeper.etckeeper.conf: 2013-04-12T00:48:41.577989 ** Affects: etckeeper (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package saucy -- 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/1304150 Title: apt-get upgrade didn't handle missing config file gracefully To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/etckeeper/+bug/1304150/+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 1024475] Re: libnss-ldap causes boot hang on Ubuntu 12.04 Precise
Got bit by this, too; however, in my case it's adding "ldap" to the hosts line that got me into trouble. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libnss-ldap in Ubuntu. https://bugs.launchpad.net/bugs/1024475 Title: libnss-ldap causes boot hang on Ubuntu 12.04 Precise To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libnss-ldap/+bug/1024475/+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 1273462] [NEW] Upstart job config and init.d script are incompatible with each other
Public bug reported: Description:Ubuntu 13.10 Release:13.10 mysql-server-5.5: Installed: 5.5.35-0ubuntu0.13.10.1 Candidate: 5.5.35-0ubuntu0.13.10.1 Version table: *** 5.5.35-0ubuntu0.13.10.1 0 500 http://us-east-1.ec2.archive.ubuntu.com/ubuntu/ saucy-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu/ saucy-security/main amd64 Packages 100 /var/lib/dpkg/status 5.5.32-0ubuntu7 0 500 http://us-east-1.ec2.archive.ubuntu.com/ubuntu/ saucy/main amd64 Packages In Ubuntu 13.10, the Upstart job and the init.d script do not work properly. In previous versions, the init.d script was a symlink to the wrapper script around upstart (/lib/init/upstart-job). This conflict means that if the server was started using the init.d script, upstart does not recognize that the server is running and will attempt to start a second instance of mysqld. Also problematic is that if the upstart job is started using the service or start commands, the init.d script's "stop" function runs a mysql shutdown, but upstart simply restarts mysqld (because it's marked respawn in the upstart config). ** Affects: mysql-5.5 (Ubuntu) Importance: Undecided Status: New ** Tags: init scripts upstart -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mysql-5.5 in Ubuntu. https://bugs.launchpad.net/bugs/1273462 Title: Upstart job config and init.d script are incompatible with each other To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.5/+bug/1273462/+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 1266127] Re: Use strutils.to_slug() instead of utils.slugify()
** Also affects: python-cinderclient Importance: Undecided Status: New ** Changed in: python-cinderclient Assignee: (unassigned) => ChrisBuccella (chris-buccella) ** Changed in: python-cinderclient Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to python-cinderclient in Ubuntu. https://bugs.launchpad.net/bugs/1266127 Title: Use strutils.to_slug() instead of utils.slugify() To manage notifications about this bug go to: https://bugs.launchpad.net/python-cinderclient/+bug/1266127/+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 582119] Re: package postfix 2.7.0-1 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 2
*** This bug is a duplicate of bug 512096 *** https://bugs.launchpad.net/bugs/512096 ** Changed in: postfix (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to postfix in Ubuntu. https://bugs.launchpad.net/bugs/582119 Title: package postfix 2.7.0-1 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/582119/+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 1185261] [NEW] MaaS nodes being enlisted with multiple network cards fail to commission
Public bug reported: Allowing MaaS to do it's own DHCP/DNS but isolating it onto its own network segment and having nodes with two network interfaces (one interface connected to the network segment the Maas controllers are on and the second interface connected to another (different) network segment that has external internet access) results in failure to commission nodes properly. The nodes correctly start up, contact the server, boot and sit...eventually printing various apt-get error messages about being unable to connect to external sites before ultimately powering off and changing the state on the Nodes page from commissioning to ready. It seems that only one interface is being brought up (the one that contacted the MaaS controller) and the other one is ignored. This was tested on a fresh 12.04.2 server install and using the MaaS stable PPA package version 1.2+bzr1373+dfsg-0ubuntu1~12.04.1~ppa1. ** 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/1185261 Title: MaaS nodes being enlisted with multiple network cards fail to commission To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1185261/+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 967410] Re: Windows clients cannot connect to shared printers
Thanks for fixing this! I'm looking forward to getting my printer working. I assume that once the fix is released, I'll get it with the standard "apt-get update" and "apt-get upgrade" operation? -- 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/967410 Title: Windows clients cannot connect to shared printers To manage notifications about this bug go to: https://bugs.launchpad.net/samba/+bug/967410/+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
Re: [Qemu-devel] [Bug 1025244] Re: qcow2 image increasing disk size above the virtual limit
On 01/02/2013 08:50 AM, Stefan Hajnoczi wrote: > On Tue, Dec 18, 2012 at 10:18:20AM -, Andy Menzel wrote: >> Any solution right now? I have a similar problem like Todor Andreev; >> Our daily backup of some virtual machines (qcow2) looks like that: >> >> 1. shutdown the VM >> 2. create a snapshot via: "qemu-img snapshot -c nameofsnapshot..." >> 3. boot the VM >> 4. backup the snapshot to another virtual disk via: "qemu-img convert -f >> qcow2 -O qcow2 -s nameofsnapshot..." >> 5. DELETE the snapshot from VM via: qemu-img snapshot -d nameofsnapshot... > > It's not safe to modify the qcow2 file while the guest is running. This > means Step 5 is not really safe and could result in an inconsistent > image. > > This may also be causing the problem: the QEMU process has a variable > with the next free cluster index. Since Step 5 runs as a separate > process it does not update the QEMU process' next free cluster index > variable. QEMU doesn't know that there are now free clusters within the > image file because you updated the file behind QEMU's back - the result > is that it grows the file. > > Please try deleting the last backup snapshot between Step 1 and Step 2. > This way you'll free the space while QEMU isn't accessing the image > file. When you boot up the image file again QEMU should reuse the freed > clusters. You might also want to try modifying step 5 to use the HMP delvm monitor command from within the running qemu rather than going behind qemu's back with a qemu-img invocation. That's how libvirt deletes internal snapshots from a running qemu. Also, there are patches currently under review that are talking about creating a QMP counterpart to the delvm monitor command. -- Eric Blake eblake redhat com+1-919-301-3266 Libvirt virtualization library http://libvirt.org -- 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/1025244 Title: qcow2 image increasing disk size above the virtual limit To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1025244/+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 1090297] [NEW] MAAS "View Documentation" link points to unrelated version of docs
Public bug reported: Hi, in the MAAS Dashboard, there's a link "View Documentation". This points to the upstream page: https://wiki.ubuntu.com/ServerTeam/MAAS/. This offers a manual redirect to http://maas.ubuntu.com. This appears to be documentation from the current daily build, and will contain information that's probably not relevant to the installed version. Also, the documentation for any particular version, such as the one in Precise, appears to only be available by checking out the sources and building the documentation manually. It would be better if the docs for a particular version were installed with MAAS, and the documentation link would point to that version, stored locally. Alternatively, http://maas.ubuntu.com/ could host docs for all supported versions. Thanks, Eric ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: maas 0.1+bzr482+dfsg-0ubuntu1 ProcVersionSignature: User Name 3.2.0-33.52-virtual 3.2.31 Uname: Linux 3.2.0-33-virtual x86_64 ApportVersion: 2.0.1-0ubuntu15 Architecture: amd64 Date: Fri Dec 14 10:10:11 2012 MAASLog: MAASPservLog: MarkForUpload: True PackageArchitecture: all ProcEnviron: TERM=xterm LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: python-django-maas 0.1+bzr482+dfsg-0ubuntu1 apparmor 2.7.102-0ubuntu3.4 SourcePackage: maas UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.maas.maas.local.settings.py: [modified] modified.conffile..etc.maas.pserv.yaml: [modified] modified.conffile..etc.maas.txlongpoll.yaml: [modified] mtime.conffile..etc.maas.maas.local.settings.py: 2012-11-29T15:38:03.325629 mtime.conffile..etc.maas.pserv.yaml: 2012-11-29T15:25:01.925860 mtime.conffile..etc.maas.txlongpoll.yaml: 2012-11-29T15:25:12.577860 ** Affects: maas (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug precise ** Description changed: Hi, - in the MAAS Dashboard, there's a link "View Documentation". This - points to the upstream page: https://wiki.ubuntu.com/ServerTeam/MAAS/. + in the MAAS Dashboard, there's a link "View Documentation". This + points to the upstream page: https://wiki.ubuntu.com/ServerTeam/MAAS/. - This offers a manual redirect to http://maas.ubuntu.com. This is - appears to be documentation from the current daily build, and will - contain information that's probably not relevant to the installed - version. + This offers a manual redirect to http://maas.ubuntu.com. This + appears to be documentation from the current daily build, and will + contain information that's probably not relevant to the installed + version. - Also, the documentation for any particular version, such as the one - in Precise, appears to only be available by checking out the sources + Also, the documentation for any particular version, such as the one + in Precise, appears to only be available by checking out the sources and building the documentation manually. - It would be better if the docs for a particular version were installed - with MAAS, and the documentation link would point to that version, + It would be better if the docs for a particular version were installed + with MAAS, and the documentation link would point to that version, stored locally. Alternatively, http://maas.ubuntu.com/ could host docs for all supported versions. Thanks, Eric ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: maas 0.1+bzr482+dfsg-0ubuntu1 ProcVersionSignature: User Name 3.2.0-33.52-virtual 3.2.31 Uname: Linux 3.2.0-33-virtual x86_64 ApportVersion: 2.0.1-0ubuntu15 Architecture: amd64 Date: Fri Dec 14 10:10:11 2012 MAASLog: - + MAASPservLog: - + MarkForUpload: True PackageArchitecture: all ProcEnviron: - TERM=xterm - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=xterm + LANG=en_US.UTF-8 + SHELL=/bin/bash RelatedPackageVersions: - python-django-maas 0.1+bzr482+dfsg-0ubuntu1 - apparmor 2.7.102-0ubuntu3.4 + python-django-maas 0.1+bzr482+dfsg-0ubuntu1 + apparmor 2.7.102-0ubuntu3.4 SourcePackage: maas UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.maas.maas.local.settings.py: [modified] modified.conffile..etc.maas.pserv.yaml: [modified] modified.conffile..etc.maas.txlongpoll.yaml: [modified] mtime.conffile..etc.maas.maas.local.settings.py: 2012-11-29T15:38:03.325629 mtime.conffile..etc.maas.pserv.yaml: 2012-11-29T15:25:01.925860 mtime.conffile..etc.maas.txlongpoll.yaml: 2012-11-29T15:25:12.577860 -- 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/1090297 Title: MAAS "View Documentation" link points to unrelated version of docs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1090297/+subscriptions -- Ubun
