Daniel, if this bug is related to your issue you can simply reboot to
fix it. If it's still broken then it's not this issue.
Thanks
--
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:
glib
I'm having issues with DNS over VPN since 2.24-0ubuntu2. I cannot access
the company's internal sites through VPN anymore. Please tell me what
should I post here for more details
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://
This bug was fixed in the package glibc - 2.24-9ubuntu2
---
glibc (2.24-9ubuntu2) zesty; urgency=medium
* debian/patches/any/cvs-resolv-internal-qtype.diff: Revert to avoid
failure in name resolution on upgrades from yakkety (LP: #1674532)
-- Adam Conrad Tue, 21 Mar 2017 15:
@paul-dubs: "dig @8.8.8.8", by definition, completely bypasses the libc
resolver. It makes a direct connection to 8.8.8.8 and queries it. If
that's slow or broken for you, you have a link layer networking issue,
or Google's geo-located 8.8.8.8 near you is broken, or some other
similar thing. It
#Fixed LTS package versions: 2.23-0ubuntu7 (xenial) & 2.19-0ubuntu6.11
(trusty)
@jozznaz, jm7485 & co: You're not alone for me it was way more than 50
boxes where the PHP stuff couldn't resolve names anymore and needed my
attention. Nasty and frustrating for sure ... and i was also swearing ;)
Bu
I am also still seeing problems related to hostname resolution.
Sometimes, a simple 'dig @8.8.8.8 google.com' will take up to 30 seconds
and then timeout, sometimes it works after a long delay, and sometimes
it works as quick as it should.
In any instance where it works, it says that the dns serv
** No longer affects: glibc (Ubuntu Yakkety)
** Changed in: glibc (Ubuntu)
Importance: Undecided => Critical
--
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:
glibc update caused NSS
** No longer affects: eglibc (Ubuntu)
** No longer affects: eglibc (Ubuntu Xenial)
** No longer affects: eglibc (Ubuntu Yakkety)
** No longer affects: glibc (Ubuntu Precise)
** No longer affects: glibc (Ubuntu Trusty)
--
You received this bug notification because you are a member of Ubuntu
Bu
Lukas, if your DNS works but is slow that's probably two junk
nameservers listed in /etc/resolv.conf before one working nameserver. A
full debugging of your DNS is probably out of scope for a bug report; I
suggest heading to askubuntu.com or IRC.
Thanks
--
You received this bug notification beca
and yes, to say as well:
we have 4 servers affected, clients are very upset. We will be disabling
automatic updates.
for the meantime: what is the proper solution to this?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.
http://stackoverflow.com/questions/43053872/file-get-contents-with-full-
url-to-same-server-very-slow-with-php-7-as-of-very-r
it is not even necessary that the DNS lookup doesn't work, it actually
can be just very very slow so it seems to me at least
--
You received this bug notification because
It's still happening to my servers too.
It looks like they are being all hit (12 of them) at the same time. This
is after an apt-get update / upgrade cycle and a reboot.
$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=14.04
DISTRIB_CODENAME=trusty
DISTRIB_DESCRIPTION="Ubuntu 14.04.5 LTS
We are still encountering intermittent DNS resolution issues, even after
an OS reboot. For example:
Net::OpenTimeout: execution expired
/usr/lib/ruby/2.3.0/resolv-replace.rb: 25:in `initialize'
/usr/lib/ruby/2.3.0/resolv-replace.rb: 25:in `initialize'
** Tags added: regression-update
--
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:
glibc update caused NSS ABI break
To manage notifications about this bug go to:
https://bugs.launchpad.
Still getting this despite being on latest. Seems to come and go. I'm
on 14.04.5.
--
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:
glibc update caused NSS ABI break
To manage notifica
I just want to chime in here and say this bug has cost our company
thousands of dollars in lost revenue, and not to mention the unnecessary
cost of debugging time, because it broke two of the most important API
endpoints we use... Stripe for payments and the API for email delivery
with SendGrid, so
After installing libc6 2.23-0ubuntu7, you can check for running
processes that are using a deleted (pre-update) /lib/x86_64-linux-
gnu/libc-2.23.so using lsof:
sudo lsof -d DEL | grep /lib/x86_64-linux-gnu/libc-2.23.so
Those processes need to be restarted to re-link with the fixed libc.
--
You
Hey! Im little bit confused, which version is latest stable release
where bug is fixed?
Im Using
Distributor ID: Ubuntu
Description:Ubuntu 16.04.2 LTS
Release:16.04
Codename: xenial
Package: libc6
Status: install ok installed
Priority: required
Section: libs
Installed-Size: 109
@justin-demaris: Yes, sort of. What happened is that the first update
caused a regression, and the second update reverted that. Any services
that were restarted with the broken update would then have been "re-
broken" with the update that backed out that change until they were
again re-started.
** Information type changed from Public to Public Security
--
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:
glibc update caused NSS ABI break
To manage notifications about this bug go t
For clarities sake, and so I can understand what happened on my servers,
is it correct that this issue cropped up with two different Unattended
installs on two consecutive days? (i.e. the 21st and the 22nd).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
To everyone asking "when will this be fixed", it's fixed. If you're up
to date, the regression is fixed. This doesn't require "nightly"
reboots, it requires one reboot after being fully up to date. Sarcasm
and snark and overstating the issue may make you feel better, but it
doesn't help people w
Taylor - I agree. I have trusted automatic security updates for years. I
have to turn them off and start running updates manually because I can't
trust Ubuntu won't do this again.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:/
Is this the new norm for Ubuntu 14.04? Just restart your entire server
every night? This is the most ridiculous shit I have ever seen in my
life. When will this be fixed?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.lau
Agreed on this one, we're also experiencing production failures, but
they happen every night around 1am and simply restarting apache clears
it up.
>From our logs
Start-Date: 2017-03-21 03:22:40
Commandline: /usr/bin/unattended-upgrade
Upgrade: libc6-dev:amd64 (2.23-0ubuntu3, 2.23-0ubuntu6), libc
Experienced this issue when it brought down production services yesterday,
manifesting itself as the PHP issue described in #1674733.
A reboot temporarily solved the problem but then it reoccurred approximately 18
hours later.
I'm currently unable to provide reproduction steps other than it seem
I'm still seeing this on Ubuntu 16.04 connecting to Amazon RDS as well.
Apache service reloads had temporarily resolved it, but I got a huge
rash of these again across all of my servers during the Unattended
installs again last night.
Start-Date: 2017-03-21 04:30:58
Commandline: /usr/bin/unatte
14.04
Reboot temporarily fixed issue for a few hours, but has resurfaced since.
--
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:
glibc update caused NSS ABI break
To manage notification
I'm also seeing this issue replicated on 14.04.2 -
$ apt-cache show libc6 | grep Version
Version: 2.19-0ubuntu6.11
Version: 2.19-0ubuntu6
$cat /var/log/apt/history.log
...
Start-Date: 2017-03-21 07:11:13
Upgrade: libgnutls-openssl27:amd64 (2.12.23-12ubuntu2.6, 2.12.23-12ubuntu2.7),
multiarch-su
@Adam C.: Thx!
--
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:
glibc update caused NSS ABI break
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source
@robertsv: As mentioned in other comments, just reboot. You'll be fine
from there.
@fariazz: If you're on 15.04, you're not seeing this bug. Also, 15.04
has been out of support for over a year.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed t
My bad, I'm in 15.04.
Any workaround to make things work again?
This is causing severe problems on our end so any advise would be
welcome.
--
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
Same issue on Ubuntu 14.X LTS
After auto upgrade on 2017.03.21 application running on apache and php is
unable some times to connect to db server.
Upgrade log:
Preparing to unpack .../libc6_2.19-0ubuntu6.10_amd64.deb ...
Unpacking libc6:amd64 (2.19-0ubuntu6.10) over (2.19-0ubuntu6.9) ...
Upgrade
I'm having this problem in 14.04 since yesterday, where all my DNS
resolutions take forever, some timeout. I've restarted several times.
This has broken many integrations in our site, is there anything that
can be done to make things work?
This is the version of libc6 that I have:
dpkg -s libc6
"Again, the question is what else needs to be restarted?"
The answer to that is "I don't know", which is why the general
recommendation here should be to just reboot. Basically, any long-
running process with the older libc loaded that tries to do NSS DNS
lookups will fail. This was the bug intr
** Summary changed:
- Ubuntu 14.04 broken during PXE boot
+ glibc update caused NSS ABI break
--
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:
glibc update caused NSS ABI break
To mana
36 matches
Mail list logo
