[Bug 1183123] New: systemd, NetworkManager and nscd - nfs mounts are failing
https://bugzilla.suse.com/show_bug.cgi?id=1183123 Bug ID: 1183123 Summary: systemd, NetworkManager and nscd - nfs mounts are failing Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: screening-team-bugs@suse.de Reporter: opensuse@mike.franken.de QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- Using the combination nfs, systemd, NetworkManager and nscd I always run into the problem, that NetworkManager states the system being online, before it is really online. In this case, all nfs mounts by systemd are failing, because the names of the servers can't be resolved at that time. Later NM's nfs dispatcher script works, but also comes too late for some services, that are started by systemd in the meantime. Using Networkmanager-wait-online for these services doesn't help either, because - as stated above - NM believes it is online long before it really is. Disabling nscd in this case cures the problem. After doing so, even systemd is able to mount the nfs shares. Everything is placed in the correct order. Is this a bug? Or is it ok for this scenario to disable nscd? Or do I have to use special settings for this case? -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1183123 Chenzi Cao <chcao@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |schwab@suse.com Assignee|screening-team-bugs@suse.de |songchuan.kang@suse.com -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1183123 https://bugzilla.suse.com/show_bug.cgi?id=1183123#c1 --- Comment #1 from Jonathan Kang <songchuan.kang@suse.com> --- (In reply to Michael Hirmke from comment #0)
Using the combination nfs, systemd, NetworkManager and nscd I always run into the problem, that NetworkManager states the system being online, before it is really online. In this case, all nfs mounts by systemd are failing, because the names of the servers can't be resolved at that time. Later NM's nfs dispatcher script works, but also comes too late for some services, that are started by systemd in the meantime. Using Networkmanager-wait-online for these services doesn't help either, because - as stated above - NM believes it is online long before it really is.
Disabling nscd in this case cures the problem. After doing so, even systemd is able to mount the nfs shares. Everything is placed in the correct order.
NetworkManager has dropped nscd support quite a long while ago. So I guess it's nscd that interferes DNS resolution.
Is this a bug? Or is it ok for this scenario to disable nscd? Or do I have to use special settings for this case?
What do you use nscd for? You can disable nscd if you don't need it. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1183123 https://bugzilla.suse.com/show_bug.cgi?id=1183123#c2 --- Comment #2 from Michael Hirmke <opensuse@mike.franken.de> --- (In reply to Jonathan Kang from comment #1)
(In reply to Michael Hirmke from comment #0)
Using the combination nfs, systemd, NetworkManager and nscd I always run into the problem, that NetworkManager states the system being online, before it is really online. In this case, all nfs mounts by systemd are failing, because the names of the servers can't be resolved at that time. Later NM's nfs dispatcher script works, but also comes too late for some services, that are started by systemd in the meantime. Using Networkmanager-wait-online for these services doesn't help either, because - as stated above - NM believes it is online long before it really is.
Disabling nscd in this case cures the problem. After doing so, even systemd is able to mount the nfs shares. Everything is placed in the correct order.
NetworkManager has dropped nscd support quite a long while ago. So I guess it's nscd that interferes DNS resolution.
Is this a bug? Or is it ok for this scenario to disable nscd? Or do I have to use special settings for this case?
What do you use nscd for? You can disable nscd if you don't need it.
I don't use it for anything and indeed deactivated it, but the default for Tumbleweed is an activated nscd. So I just wondered what might be wrong in my system. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1183123 https://bugzilla.suse.com/show_bug.cgi?id=1183123#c3 --- Comment #3 from Michael Matz <matz@suse.com> --- (In reply to Jonathan Kang from comment #1)
(In reply to Michael Hirmke from comment #0)
Using the combination nfs, systemd, NetworkManager and nscd I always run into the problem, that NetworkManager states the system being online, before it is really online. In this case, all nfs mounts by systemd are failing, because the names of the servers can't be resolved at that time. Later NM's nfs dispatcher script works, but also comes too late for some services, that are started by systemd in the meantime. Using Networkmanager-wait-online for these services doesn't help either, because - as stated above - NM believes it is online long before it really is.
Disabling nscd in this case cures the problem. After doing so, even systemd is able to mount the nfs shares. Everything is placed in the correct order.
NetworkManager has dropped nscd support quite a long while ago. So I guess it's nscd that interferes DNS resolution.
Define "dropped". What support was there to start with? nscd cannot simply be ignored by NetworkManager, it needs to work together with the system DNS resolver. E.g. if it changes any config behind the back of system DNS resolvers knowledge (for instance by an intermediary like dnsmasq and changing only _its_ config) then nscd needs to be made aware of that, so that it may drop outdated information.
Is this a bug? Or is it ok for this scenario to disable nscd? Or do I have to use special settings for this case?
What do you use nscd for? You can disable nscd if you don't need it.
nscd is a default component of the system. Advising users to disable it is not the right course of action, though it may be used as a work around. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1183123 https://bugzilla.suse.com/show_bug.cgi?id=1183123#c4 --- Comment #4 from Jonathan Kang <songchuan.kang@suse.com> --- (In reply to Michael Hirmke from comment #2)
I don't use it for anything and indeed deactivated it, but the default for Tumbleweed is an activated nscd. So I just wondered what might be wrong in my system.
Can you report this to NetworkManager upstream here[0] so that they can take a further look at this? *[0] https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1183123 https://bugzilla.suse.com/show_bug.cgi?id=1183123#c5 Jonathan Kang <songchuan.kang@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |opensuse@mike.franken.de Flags| |needinfo?(opensuse@mike.fra | |nken.de) --- Comment #5 from Jonathan Kang <songchuan.kang@suse.com> --- Hi Michael Can you add the following to /etc/NetworkManager/NetworkManager.conf
[logging] level=trace
restart NetworkManager, reproduce this and provide the output of "journalctl -b"? Thanks. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1183123 https://bugzilla.suse.com/show_bug.cgi?id=1183123#c6 --- Comment #6 from Michael Hirmke <opensuse@mike.franken.de> --- (In reply to Jonathan Kang from comment #5)
Hi Michael
Can you add the following to /etc/NetworkManager/NetworkManager.conf
[logging] level=trace
restart NetworkManager, reproduce this and provide the output of "journalctl -b"?
Thanks.
Sorry, I'm really busy at the moment. I'll try to reproduce it in a few days. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1183123 https://bugzilla.suse.com/show_bug.cgi?id=1183123#c7 --- Comment #7 from Jonathan Kang <songchuan.kang@suse.com> --- (In reply to Michael Hirmke from comment #6)
Sorry, I'm really busy at the moment. I'll try to reproduce it in a few days.
No problem. Take your time. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1183123 https://bugzilla.suse.com/show_bug.cgi?id=1183123#c8 --- Comment #8 from Michael Hirmke <opensuse@mike.franken.de> --- Due to health problems I was not able to reproduce the problem yet. Might take another 3 months, sry. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠suse.com