Op zondag 3 februari 2019 19:20:00 CET schreef Michael Hirmke:

Hi again,

[...]

...

...

This snapshot is exceptional in 3 aspects: I get one additional warning message in my journal:

NetworkManager[1692]: <warn> [1549211353.1343] dns-mgr: could not commit DNS changes: Error calling netconfig: exited with status 20

And /etc/resolv.conf was not updated.

This leads to a problem connecting to my VPN.

Any idea, what might cause this problem? TIA.

running

netconfig update -f

seems to have cured the problem.

/etc/resolv.conf was replaced by a link to /var/run/netconfig/resolv.conf after this command.

Would have been great, if this had happend during update!

[...]

AFAICS it did in my case(s).

...

...

Greetings, Stephan

Bye. Michael.

-- Gertjan Lettink a.k.a. Knurpht openSUSE Board Member openSUSE Forums Team -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org

Op zondag 3 februari 2019 19:45:35 CET schreef Patrick Shanahan:

* Knurpht-openSUSE [02-03-19 13:26]:

...

Op zondag 3 februari 2019 19:20:00 CET schreef Michael Hirmke:

...

Hi again,

[...]

...

...

This snapshot is exceptional in 3 aspects: I get one additional warning message in my journal:

NetworkManager[1692]: <warn> [1549211353.1343] dns-mgr: could not commit DNS changes: Error calling netconfig: exited with status 20

And /etc/resolv.conf was not updated.

This leads to a problem connecting to my VPN.

Any idea, what might cause this problem? TIA.

running

netconfig update -f

seems to have cured the problem.

/etc/resolv.conf was replaced by a link to /var/run/netconfig/resolv.conf after this command.

Would have been great, if this had happend during update!

[...]

AFAICS it did in my case(s).

I also have /var/run/netconfig/resolv.conf which says: ### /etc/resolv.conf is a symlink to /var/run/netconfig/resolv.conf ### autogenerated by netconfig!

but /etc/resolv.conf is NOT a symlink

ls -la /etc/resolv.conf -rw-r--r-- 1 root root 903 Nov 6 20:23 /etc/resolv.conf

file /etc/resolv.conf /etc/resolv.conf: ASCII text Same here. And I can't remember ever seeing it being a symlink. Maybe the result of running TW from it's early days.

-- Gertjan Lettink a.k.a. Knurpht openSUSE Board Member openSUSE Forums Team -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org

Hi, [...]

...

but /etc/resolv.conf is NOT a symlink

ls -la /etc/resolv.conf -rw-r--r-- 1 root root 903 Nov 6 20:23 /etc/resolv.conf

file /etc/resolv.conf /etc/resolv.conf: ASCII text Same here. And I can't remember ever seeing it being a symlink. Maybe the result of running TW from it's early days.

no - this is new. I remember a bug report, where they decided to switch from file to sylmink.

-- Gertjan Lettink a.k.a. Knurpht

Bye. Michael. -- Michael Hirmke -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org

* Michael Hirmke [02-03-19 13:57]:

Hi *,

[...]

...

...

...

/etc/resolv.conf was replaced by a link to /var/run/netconfig/resolv.conf after this command.

Would have been great, if this had happend during update!

[...]

AFAICS it did in my case(s).

...

I also have /var/run/netconfig/resolv.conf which says: ### /etc/resolv.conf is a symlink to /var/run/netconfig/resolv.conf ### autogenerated by netconfig!

...

but /etc/resolv.conf is NOT a symlink

...

ls -la /etc/resolv.conf -rw-r--r-- 1 root root 903 Nov 6 20:23 /etc/resolv.conf

...

file /etc/resolv.conf /etc/resolv.conf: ASCII text

so you probably also have this warning in your journal?

Feb 03 11:12:14 Crash nscd[1043]: 1043 monitoring file `/etc/resolv.conf` (5) ... Feb 03 11:12:47 Crash kernel: Key type dns_resolver registered Feb 03 11:12:47 Crash kernel: NFS: Registering the id_resolver key type Feb 03 11:12:47 Crash kernel: Key type id_resolver registered all that I see -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org

* Michael Hirmke [02-04-19 10:37]:

Hi,

[...]

...

...

so you probably also have this warning in your journal?

...

Feb 03 11:12:14 Crash nscd[1043]: 1043 monitoring file `/etc/resolv.conf` (5) ... Feb 03 11:12:47 Crash kernel: Key type dns_resolver registered Feb 03 11:12:47 Crash kernel: NFS: Registering the id_resolver key type Feb 03 11:12:47 Crash kernel: Key type id_resolver registered

...

all that I see

so it seems, NetworkManager here has some debug mode configured. It was:

NetworkManager[1680]: debug: write_resolv_conf: ' ... ' NetworkManager[1680]: debug: dns settings written to /var/run/netconfig/resolv.conf NetworkManager[1680]: debug: /etc/resolv.conf is a regular file NetworkManager[1680]: ATTENTION: /etc/resolv.conf is not a link to /var/run/netconfig/resolv.conf NetworkManager[1680]: call "netconfig update -f" to adjust /etc/resolv.conf

no, not running NetworkManager on this desktop, wicked. and fwiw, I just updated another desktop and it didn't even create the /var/run/netconfig/resolv.conf. running "netconfig update -f" also failed to create the /var/.. file or the simlink. so I copied /etc/resolv.conf there and created the simlink and ran "netconfig update -f". but it doesn't contain the symlink notice. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org