Need to watch these:
- [Archive.is] Bug 1084419 – Glibc update to 2.27 causes segfault during name resolution
- [WayBack] Bug 1084812 – [aarch64] IPv4 DNS leading to segfaults
A few notes:
- It is inside the glibc name resolution
- IPv6 is OK, IPv4 fails.
- ping/nslookup (which do not depend on glibc) are OK
- there is an intermediate fix requiring direct osc downloads
A simple test case
Failing situation
$ curl --silent --show-error http://example.org > /dev/null
Segmentation fault (core dumped)
Succeeding situation
$ curl --silent --show-error http://example.org > /dev/null
Non related, but in hindsight my own stupid fault during a similar update: a post mortem
I thought I had forgot about the SuSEfirewall2 changes (On my research list: migrate from OpenSuSE SuSEfirewall2 to firewalld) so assumed that was the reason I broke one of my secondaries (which runs on a Raspberry Pi 2):
- https://infrastatus.wiert.me/778601810 246 DNS
- https://infrastatus.wiert.me/778601811 246 SMTP
- https://infrastatus.wiert.me/779973631 246 SSH
Mistakes like these are the reason to have secondaries in the first place https://infrastatus.wiert.me and do port-mortems.
Which is kind of odd, as the SuSEfirewall2
didn’t throw any warnings like at this similar one:
- https://infrastatus.wiert.me/779291536 245 DNS
- https://infrastatus.wiert.me/779973640 245 ping
- https://infrastatus.wiert.me/779291537 245 SMTP
- https://infrastatus.wiert.me/779291542 245 SSH
This one still works because it is on the firewall in front of the Raspberry Pi 2:
(Screenshots of the above URLs are below).
In fact it was another mistake: I had forgotten to make the DHCP lease static, which resulted in a wrong IP address to be assigned upon reboot, instantly making the firewall rules invalid:
I could have fixed this remotely when I had thought about this.
–jeroen