Also, once I have installed the update on the DNS server, if I run apt-
get update it queries TYPE62321 record.
22-Mar-2017 06:04:37.406 queries: info: client 127.0.0.1#38103
(gb.archive.ubuntu.com.comlaude.lon2): query:
gb.archive.ubuntu.com.comlaude.lon2 IN TYPE62321 + (127.0.0.1)
This server i
Yes, it's known that updating from the version with the regression to
the version that backed it out will cause the same (well, inverse) bug
to appear until services or the machine are restarted. That's
unfortunate, but there's not a whole bunch we can do to mitigate that,
and reverting the regres
To add to that, I just manually updated another running webserver, and
boom. The apache+php webserver uses DNS to resolve the database server,
which it can no longer do after the update, bringing the site down.
It sends these incorrect TYPE62321 DNS queries to our DNS server.
22-Mar-2017 05:33:01
Just like my earlier comment, this _fix_ *broke* a running system after
it was automatically applied.
Start-Date: 2017-03-22 04:17:12
Commandline: /usr/bin/unattended-upgrade
Upgrade: libc6:amd64 (2.23-0ubuntu6, 2.23-0ubuntu7), locales:amd64
(2.23-0ubuntu6, 2.23-0ubuntu7), libc-bin:amd64 (2.23-0
The libc6-udeb_2.19-0ubuntu6.11_amd64.udeb fix that was just released
fixes the name resolution issues and we're able to provision our systems
as normal again.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
This bug was fixed in the package eglibc - 2.15-0ubuntu10.17
---
eglibc (2.15-0ubuntu10.17) precise-security; urgency=medium
* REGRESSION UPDATE: Previous update introduce ABI breakage in
internal glibc query ABI
- Back out patches/any/CVE-2015-5180-regression.diff
(LP
This bug was fixed in the package eglibc - 2.19-0ubuntu6.11
---
eglibc (2.19-0ubuntu6.11) trusty-security; urgency=medium
* REGRESSION UPDATE: Previous update introduced ABI breakage in
internal glibc query ABI
- Back out patches/any/CVE-2015-5180-regression.diff
(LP:
This bug was fixed in the package glibc - 2.23-0ubuntu7
---
glibc (2.23-0ubuntu7) xenial-security; urgency=medium
* REGRESSION UPDATE: Previous update introduced ABI breakage in
internal glibc query ABI
- Revert patches/any/CVE-2015-5180-regression.diff
(LP: #1674532)
** Changed in: glibc (Ubuntu Yakkety)
Status: New => Invalid
** Changed in: glibc (Ubuntu Xenial)
Importance: Undecided => Critical
** Changed in: glibc (Ubuntu Xenial)
Status: New => Confirmed
** Changed in: eglibc (Ubuntu Precise)
Assignee: (unassigned) => Steve Beattie (
** Changed in: glibc (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1674532
Title:
Ubuntu 14.04 broken during PXE boot
To manage notifications about this
** Also affects: glibc (Ubuntu)
Importance: Undecided
Status: New
** Also affects: glibc (Ubuntu Yakkety)
Importance: Undecided
Status: New
** Also affects: eglibc (Ubuntu Yakkety)
Importance: Undecided
Status: New
** Also affects: glibc (Ubuntu Xenial)
Importanc
is it valid to run the broken install, when it breaks manually pull down
the new package that you pushed and install that, then let it continue
with the installation?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchp
Hi, I've put test glibc packages in the ubuntu-security-proposed ppa
https://launchpad.net/~ubuntu-security-
proposed/+archive/ubuntu/ppa/+packages that revert the fix for
CVE-2015-5180. If someone could test that the udeb's from there don't
break your pxe install that would be great.
Quite likely
The IP workaround doesn't work because archive.ubuntu.com is a virutal
host (ie it needs the Host: header in the HTTP request). What I did to
work around that was add this to my preseed.cfg. Adjust as needed
d-i preseed/early_command string echo "91.189.88.161 archive.ubuntu.com"
>> /etc/hosts &&
I just tested the workaround of setting the apt mirror to be an IP
instead of a hostname and it does finish the base install but our
provisioning process is still broken. We have a late_command that gets a
script to do integrations into our environment (AD domain joining,
configuration management,
Just hit this bug with our PXE provisioning system when trying to deploy
14.04. We were deploying without issues days ago.
The syslog from the failed install shows wget to our apt mirror location
working fine until after anna retrieves
libc6-udeb_2.19-0ubuntu6.10_amd64.deb. The subsequent retrieva
Thanks to Eric for suggesting the workaround.
It works if there's no virtual hosting on the mirror. As I manage a
local mirror, I changed my apache configuration and I can install with
my PXE.
Eric.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
I believe changing the preseed.cfg file to use an IP address for the
archive instead of the domain name will work around this; it's not a
good long term solution since it messes up ubuntu's dns load balancing,
but if you need to perform an install this might work. I'm in the
process of verifying th
This issue does not appear to exist in the installer for xenial but
definitely effects the anna-install process for trusty.
The effect is to make the system unable to be installed.
Please see http://termbin.com/1npy which has the output of syslog from
the installer.
--
You received this bug not
Hi,
I have the same problem. I'm unable to install any 14.04 from my PXE
server. The installation proceed as expected until:
DEBUG: retrieving libc6-udeb 2.19-0ubuntu6.10
The next package triggers a:
wget: unable to resolve host address 'fr.archive.ubuntu.com'
Something strange noticed while d
Hi
To extend the info on this one:
unattended-upgrades updated this package today, and caused the same
issue for me, causing servers to stop resolving DNS internally.
Rebooting after installing resolved the issue, suggesting the update
itself is fine, but the process of updating breaks resolution
I confirm same kind of problem in Precise.
After update to -ubuntu6.10 ipv4 become to be preferable protocol even on
ipv6-only servers.
%%
telnet google.com 443
Trying 173.194.222.102...
Trying 173.194.222.101...
Trying 173.194.222.113...
Trying 173.194.222.138...
Trying 173.194.222.139...
Trying
This problem stems from the inclusion of the fix for CVE-2015-5180. The
internal number for A + changed in glibc (from T_UNSPEC=62321 to
T_QUERY_A_AND_=439963904).
In TCPDump, we see queries going out for TYPE62321 (the former internal
number for A+).
I think busybox uses the old sym
Hi Eric, thanks for the rpeort. Sorry you're having difficulties. I can
reproduce the issue with the Ubuntu 14.04 mini.iso from trusty-updates.
** Changed in: eglibc (Ubuntu)
Status: New => Confirmed
** Changed in: eglibc (Ubuntu)
Importance: Undecided => Critical
--
You received this
I am unable to reproduce it with the mini.iso from Ubuntu 12.04, even
though the same problematic patch was backported to that release. It
also does not reproduce with the mini.iso from Ubuntu 16.04.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribe
"Suddenly" refers to the log in which it is happily downloading stuff
from the archive and after successfully downloading and installing the
libc6_2.19-0ubuntu6.10 package it is unable to download the next package
because it can no longer resolve the archive.ubuntu.com name that it had
been resolvi
26 matches
Mail list logo
