EDIT: A fix has been deployed you can now upgrade your system safely
Hi,
We have discovered a big issue on the jessie update. It seems there is a bug in an update of the dnsmasq package from debian jessie repo. If you upgrade now, you won’t be able to upgrade next because your server won’t be able to resolve domain name.
To test if you can resolve domain name:
ping wikipedia.org
If you can’t ping correctly and you have upgraded your system yesterday or today, you can try to remove this package to fix the issue:
With 2.7.14.1, we have tried to make YunoHost conflicting with dns-root-data to avoid dns-root-data to be setup, but this package seems setup on a lot of jessie system. So apt say to not upgrade yunohost package.
I noticed this morning that my yunohost box could not ping the web, although the web could access it.
I thought that it was my network’s fault, so, as I do on a strange-behaving laptop, I just dhclient’ed, and it worked (my fixed IP config matches the IP in the box, of course).
# root@linutopch: ~ < 2018_06_29__18_37_37 >
systemctl status dnsmasq
● dnsmasq.service - dnsmasq - A lightweight DHCP and caching DNS server
Loaded: loaded (/lib/systemd/system/dnsmasq.service; enabled; vendor preset: enabled)
Active: failed (Result: timeout) since Thu 2018-06-28 17:26:05 CEST; 1 day 4h ago
Main PID: 18997 (code=exited, status=0/SUCCESS)
Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.
# root@linutopch: ~ < 2018_06_29__18_37_37 >
systemctl start dnsmasq
Job for dnsmasq.service failed because the control process exited with error code.
See "systemctl status dnsmasq.service" and "journalctl -xe" for details.
# root@linutopch: ~ < 2018_06_29__22_02_45 >
systemctl status dnsmasq
● dnsmasq.service - dnsmasq - A lightweight DHCP and caching DNS server
Loaded: loaded (/lib/systemd/system/dnsmasq.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Fri 2018-06-29 22:02:32 CEST; 44s ago
Process: 8281 ExecStart=/etc/init.d/dnsmasq systemd-exec (code=exited, status=2)
Process: 8280 ExecStartPre=/usr/sbin/dnsmasq --test (code=exited, status=0/SUCCESS)
Main PID: 18997 (code=exited, status=0/SUCCESS)
juin 29 22:02:31 linutopch systemd[1]: Starting dnsmasq - A lightweight DHCP and caching DNS server...
juin 29 22:02:31 linutopch dnsmasq[8280]: dnsmasq: vérification de syntaxe OK.
juin 29 22:02:32 linutopch dnsmasq[8281]: dnsmasq: impossible de créer une socket d'écoute pour port 53 : Adresse déjà utilisée
juin 29 22:02:32 linutopch systemd[1]: dnsmasq.service: Control process exited, code=exited status=2
juin 29 22:02:32 linutopch systemd[1]: Failed to start dnsmasq - A lightweight DHCP and caching DNS server.
juin 29 22:02:32 linutopch systemd[1]: dnsmasq.service: Unit entered failed state.
juin 29 22:02:32 linutopch systemd[1]: dnsmasq.service: Failed with result 'exit-code'.
Hmmmm…
Oh wait! Maybe it doesn’t smell as bad as it appears?..
# root@linutopch: ~ < 2018_06_29__22_02_45 >
ping wikipedia.org
PING wikipedia.org (91.198.174.192) 56(84) bytes of data.
64 bytes from text-lb.esams.wikimedia.org (91.198.174.192): icmp_seq=1 ttl=50 time=52.9 ms
64 bytes from text-lb.esams.wikimedia.org (91.198.174.192): icmp_seq=2 ttl=50 time=52.1 ms
64 bytes from text-lb.esams.wikimedia.org (91.198.174.192): icmp_seq=3 ttl=50 time=51.5 ms
^C
--- wikipedia.org ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2002ms
rtt min/avg/max/mdev = 51.583/52.232/52.933/0.612 ms
# root@linutopch: ~ < 2018_06_29__22_02_45 >
Definitely yes: smells good! Ïaisse!
Thanks! ;-D
In doubt, I’ll quickly try a little bit of apt update && apt dist-upgrade. Just in case.