Problem with resolv.conf on NFS root install since march update

[sam_nazarko]

Hi

Hopefully the issue is now addressed with the following commit:

[package] [connman-osmc] Restore default behaviour of writing directly to /etc/resolv.conf prior to ConnMan 1.31

I’d appreciate it if you could test this and provide feedback before we release this as an update to other users. To test this update:

1. Login via the command line
2. Edit the file /etc/apt/sources.list
3. Add the following line: deb http://apt.osmc.tv jessie-devel main
4. Run the following commands to update: sudo apt-get update && sudo apt-get dist-upgrade && reboot
5. Your system should have have received the update.

Please see if the issue is resolved.

I also recommend you edit /etc/apt/sources.list again and remove the line that you added after updating. This will return you to the normal update channel.

[XiMMiX]

Doesn’t work for me unfortunately. After reboot /etc/resolv.conf is still a symlink to /var/run/connman/resolv.conf which doesn’t exist. Restarting connman doesn’t help.

This is with connman 1.3.3-3 and not 1.3.3-2 like the patch you linked:

$ dpkg -l | grep connman
ii  armv7-connman-osmc                   1.3.3-3                            armhf        connman for OSMC

Deleting /etc/resolv.conf now fixes the problem. Once that symlink is gone connman creates (after a restart) a proper /etc/resolv.conf. This does survive a connman restart and full reboot.

[fzinken]

@XiMMiX

Deleting /etc/resolv.conf now fixes the problem. Once that symlink is gone connman creates (after a restart) a proper /etc/resolv.conf. This does survive a connman restart and full reboot.

This is an interisting finding because that didn’t work for me. Let me check again so that I can update Sam.
But also as a message to others please delete the old symlink before reboot.

[XiMMiX]

Maybe you are using 1.3.3-2?
I just checked and I think 1.3.3-3 removes /usr/lib/tmpfiles.d/connman-resolv.conf which is responsible for recreating the /etc/resolv.conf symlink on reboot.

[fzinken]

@XiMMiX

I just checked and I think 1.3.3-3 removes /usr/lib/tmpfiles.d/connman-resolv.conf which is responsible for recreating the /etc/resolv.conf symlink on reboot.

No I am on 1.3.3-3 and I just rechecked, deleted /etc/resolv.conf and rebooted. And now all good!
Maybe it was a mirror not updated earlier.
@sam_nazarko all good your quick fix works.

[sam_nazarko]

The need to delete the symlink should also be fixed in this commit:

[package] [connman-osmc] postinst: delete /etc/resolv.conf if upgrading from < 1.3.3-4, as it will be a symlink

Thanks

Sam

[the_bo]

Will this commit fix issue I’m having with openvpn see below. Also what’s difference between these two Resolv.conf. Seems openvpn uses the second one.

/var/run/connman/resolv.conf
/etc/resolvconf/run/resolv.conf

Prevent resolv.conf being overwritten

Hi Have Openvpn installed. Getting DNS leaks so had to update my ovpn files with script-security 2 up /etc/openvpn/update-resolv-conf down /etc/openvpn/update-resolv-conf After running openvpn get message /etc/resolvconf/update.d/libc: Warning: /etc/resolv.conf is not a symbolic link to /etc/resolvconf/run/resolv.conf I used sudo apt-get install resolv.conf and it works vpn dns correctly in resolv.conf. resolv.conf getting overwritten after awhile with /var/run/connman/resolv.c…

[sam_nazarko]

If it’s an issue caused by the symlink then yes

[XiMMiX]

@sam_nazarko 1.3.3-4 fixes it for me. Thanks!

[JeDaj]

I have updated my RPi few days ago. So far so good.