Jessie users : Upgrade is fixed


#1

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:

apt remove dns-root-data
service dnsmasq start

The bug has been reported to the debian maintainer of dnsmasq. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902341

We are working to indicate dns-root-data conflict with our yunohost package to avoid automatic installation of this package.


Date serveur erronée
Postfix rejette tout suite à MàJ 2.7.14 - Bug+Solution
#2

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.

We are searching a new solution.


#3

The fix has been deployed, you can now upgrade your system safely.


#4

Cool, thanks beaucoup!

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).


#5

Ach, sh!te. I spoke too early… and quite bad, as well: my yunohost runs on a stretch… Sorry for the confusion.

After an upgrade which lasted quite long time:

pierre@linutopch:~$ ping wikipedia.org
ping: wikipedia.org: Nom ou service inconnu
pierre@linutopch:~$ ping google.fr
ping: google.fr: Nom ou service inconnu
pierre@linutopch:~$ # ont-ils fait faillite?...
pierre@linutopch:~$ su
Mot de passe : 
X11 connection rejected because of wrong authentication.
xset:  unable to open display "localhost:10.0"

  # root@linutopch: /home/pierre        < 2018_06_29__17_08_48 >
ifconfig
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.1.100  netmask 255.255.255.0  broadcast 192.168.1.255
        inet6 fe80::ea40:f2ff:fe0b:c896  prefixlen 64  scopeid 0x20<link>
        ether e8:40:f2:0b:c8:96  txqueuelen 1000  (Ethernet)
        RX packets 1525591  bytes 1305359130 (1.2 GiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 1025645  bytes 214961237 (205.0 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 0  (Boucle locale)
        RX packets 1818401  bytes 234109354 (223.2 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 1818401  bytes 234109354 (223.2 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0


  # root@linutopch: /home/pierre        < 2018_06_29__17_08_48 >
# J'accède correctement à mon serveur en passant par de la 3G. Mais lui ne peut apparemment pas voir le reste du monde...

  # root@linutopch: /home/pierre        < 2018_06_29__17_08_48 >
apt update
Err:1 http://security.debian.org stretch/updates InRelease
  Ne parvient pas à résoudre « security.debian.org »
Err:2 http://http.debian.net/debian stretch InRelease
  Ne parvient pas à résoudre « http.debian.net »
Err:3 http://forge.yunohost.org/debian stretch InRelease
  Ne parvient pas à résoudre « forge.yunohost.org »
Err:4 http://http.debian.net/debian stretch-updates InRelease
  Ne parvient pas à résoudre « http.debian.net »
Err:5 http://apt.postgresql.org/pub/repos/apt jessie-pgdg InRelease
  Ne parvient pas à résoudre « apt.postgresql.org »
^Ccture des listes de paquets… 37%

  # root@linutopch: /home/pierre        < 2018_06_29__17_08_48 >
ping apt.postgresql.org
ping: apt.postgresql.org: Nom ou service inconnu

  # root@linutopch: /home/pierre        < 2018_06_29__17_08_48 >
ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=56 time=40.4 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=56 time=39.3 ms
^C
--- 8.8.8.8 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1001ms
rtt min/avg/max/mdev = 39.347/39.881/40.415/0.534 ms

  # root@linutopch: /home/pierre        < 2018_06_29__17_08_48 >
# Je suis rassuré, goût-gueule n'a pas encore fermé.

All this smells like some DNS sickness or so.

Is the inet6 (mentioned in the ifonfig output) normal?


#6

Hellow,

can you check that dnsmasq is running with systemctl status dnsmasq ?

If it’s not running, then try to restart it with systemctl start dnsmasq ?


#7

Oupse.

  # 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.