A little bit weird - /etc/resolv.conf is not being populated
From the mythv thread - I have just repeated this issue, on Leap 15.1. (I know its EOL, but I don't have a choice).
a) after rebuilding the initrd, the first boot - just the standard template in /etc/resolv.conf, no nameserver. firewalld is running. b) 2nd reboot, no changes. Still an empty /etc/resolv.conf. The wicked lease information is from last night. c) stopped and disabled firewalld, 3rd reboot. Now the lease info was updated and so was /etc/resolv.conf. Weird stuff. d) enabled firewalld and rebooted. Empty /etc/resolv.conf. I would try this out on 15.4 and 15.5, but NFS installations don't work. I guess I could do a zypper dup. Anyone have any suggestion as to how or why firewalld might interfere with the populating of /etc/resolv.conf ?? Surely that's crazy. -- Per Jessen, Zürich (1.5°C) Member, openSUSE Heroes (2016 - present) We're hiring - https://en.opensuse.org/openSUSE:Heroes
On 2/27/23 06:56, Per Jessen wrote:
I would try this out on 15.4 and 15.5, but NFS installations don't work. I guess I could do a zypper dup.
Anyone have any suggestion as to how or why firewalld might interfere with the populating of /etc/resolv.conf ?? Surely that's crazy.
I will look and follow-up with what I did, but I specifically configured how /etc/resolve.conf would be updated to prevent just this weirdness. What I don't recall is what I did (see post about grey beards...) On 15.4, I saw the same behavior, the major problem being an empty resolve.conf that screwed name resolution. What I found is resolve.conf is now more a punching-bag for the various network managers, and some don't use it at all anymore (therein lies the issue) So I configured it to maintain the domain and search config I wanted to it didn't mysteriously end up empty depending on what order or what mood the boot process was in. Will follow-up with the details, but no you are not crazy, and yes I saw the same behavior on 15.4. -- David C. Rankin, J.D.,P.E.
David C. Rankin wrote:
Will follow-up with the details, but no you are not crazy, and yes I saw the same behavior on 15.4.
Interesting, thanks. It sounds like something for a bug report. At first I thought "some sort of fluke", but when it is easily reproduced : On a system that has a "normal" /etc/resolv.conf and firewalld is disabled - systemctl enable firewalld reboot -> empty /etc/resolv.conf (template only). -- Per Jessen, Zürich (0.1°C) Member, openSUSE Heroes (2016 - present) We're hiring - https://en.opensuse.org/openSUSE:Heroes
On 2/28/23 10:00, Per Jessen wrote:
David C. Rankin wrote:
Will follow-up with the details, but no you are not crazy, and yes I saw the same behavior on 15.4.
Interesting, thanks. It sounds like something for a bug report.
At first I thought "some sort of fluke", but when it is easily reproduced :
On a system that has a "normal" /etc/resolv.conf and firewalld is disabled -
systemctl enable firewalld reboot
-> empty /etc/resolv.conf (template only).
That's what I did, I set the immutable attribute on resolv.conf following section 2.1 in https://wiki.archlinux.org/title/Domain_name_resolution -- David C. Rankin, J.D.,P.E.
David C. Rankin composed on 2023-02-28 21:15 (UTC-0600):
I set the immutable attribute on resolv.conf following section 2.1 in https://wiki.archlinux.org/title/Domain_name_resolution
That's what I did for many moons. Eventually I converted all but two (a non-multiboot laptop with wireless, plus my sole desktop installation using DHCP) of my then currently supported installations from whatever they were using to systemd-network. In the process I'd run systemctl list-unit-files | grep solv then disable and mask anything returned that wasn't already. Nothing has been touching any of the copies of my template resolv.conf file, last written 2020-11-30, that all installations (but two) have had in their /etc/s ever since. -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata
David C. Rankin wrote:
That's what I did, I set the immutable attribute on resolv.conf following section 2.1 in https://wiki.archlinux.org/title/Domain_name_resolution
I'm not really interested in solving _my_ problem, that is easily done, I'm more concerned about the general issue. Even if root on NFS is probably not an overly popular setup :-) -- Per Jessen, Zürich (1.4°C) Member, openSUSE Heroes (2016 - present) We're hiring - https://en.opensuse.org/openSUSE:Heroes
On 28.02.2023 04:31, David C. Rankin wrote:
On 15.4, I saw the same behavior,
I just tested and it works here. And as firewalld is active by default and wicked is the default network manager, it is rather hard to believe that it is something fundamentally broken.
the major problem being an empty resolve.conf that screwed name resolution.
That is not the problem, that is just the symptom of a problem.
What I found is resolve.conf is now more a punching-bag for the various network managers, and some don't use it at all anymore (therein lies the issue)
Which issue and wherein it lies?
Andrei Borzenkov wrote:
On 28.02.2023 04:31, David C. Rankin wrote:
On 15.4, I saw the same behavior,
I just tested and it works here. And as firewalld is active by default and wicked is the default network manager, it is rather hard to believe that it is something fundamentally broken.
That was also my first thought. Hence "A little bit weird" .... AFAICT, the only thing that might set these systems apart is that they booting from PXE with root on NFS. -- Per Jessen, Zürich (-0.8°C) Member, openSUSE Heroes (2016 - present) We're hiring - https://en.opensuse.org/openSUSE:Heroes
Per Jessen wrote:
Andrei Borzenkov wrote:
On 28.02.2023 04:31, David C. Rankin wrote:
On 15.4, I saw the same behavior,
I just tested and it works here. And as firewalld is active by default and wicked is the default network manager, it is rather hard to believe that it is something fundamentally broken.
That was also my first thought. Hence "A little bit weird" ....
AFAICT, the only thing that might set these systems apart is that they booting from PXE with root on NFS.
Tomorrow, I think I might take another system and dup it to 15.4, to see if the problem can be reproduced there. -- Per Jessen, Zürich (-0.3°C) Member, openSUSE Heroes (2016 - present) We're hiring - https://en.opensuse.org/openSUSE:Heroes
On 28.02.2023 22:12, Per Jessen wrote:
Andrei Borzenkov wrote:
On 28.02.2023 04:31, David C. Rankin wrote:
On 15.4, I saw the same behavior,
I just tested and it works here. And as firewalld is active by default and wicked is the default network manager, it is rather hard to believe that it is something fundamentally broken.
That was also my first thought. Hence "A little bit weird" ....
AFAICT, the only thing that might set these systems apart is that they booting from PXE with root on NFS.
Well, normally /etc/resolv.conf is updated by netconfig which is called by wicked when interface is configured. With root on NFS interface must be up in initrd already and in initrd there is no netconfig (and location of /etc/resolv.conf is wrong anyway). And during normal system boot interface is already up so I /think/ there is no event triggering netconfig run. Can you show cat /etc/sysconfig/network/ifcfg-XXX (for your interface) journalctl -b --no-pager lsinitrd /boot/initrd-XXX (which modules are there)
On 01.03.2023 07:26, Andrei Borzenkov wrote:
On 28.02.2023 22:12, Per Jessen wrote:
Andrei Borzenkov wrote:
On 28.02.2023 04:31, David C. Rankin wrote:
On 15.4, I saw the same behavior,
I just tested and it works here. And as firewalld is active by default and wicked is the default network manager, it is rather hard to believe that it is something fundamentally broken.
That was also my first thought. Hence "A little bit weird" ....
AFAICT, the only thing that might set these systems apart is that they booting from PXE with root on NFS.
Well, normally /etc/resolv.conf is updated by netconfig which is called by wicked when interface is configured. With root on NFS interface must be up in initrd already and in initrd there is no netconfig (and location of /etc/resolv.conf is wrong anyway). And during normal system boot interface is already up so I /think/ there is no event triggering netconfig run.
Can you show
cat /etc/sysconfig/network/ifcfg-XXX (for your interface) journalctl -b --no-pager lsinitrd /boot/initrd-XXX (which modules are there)
and ls -l /etc/resolv.conf
Andrei Borzenkov wrote:
On 28.02.2023 22:12, Per Jessen wrote:
AFAICT, the only thing that might set these systems apart is that they booting from PXE with root on NFS.
Well, normally /etc/resolv.conf is updated by netconfig which is called by wicked when interface is configured. With root on NFS interface must be up in initrd already and in initrd there is no netconfig (and location of /etc/resolv.conf is wrong anyway). And during normal system boot interface is already up so I /think/ there is no event triggering netconfig run.
That certainly sounds like a possible explanation - yet it works when firewalld is disabled ?
Can you show
cat /etc/sysconfig/network/ifcfg-XXX (for your interface)
BOOTPROTO='dhcp' STARTMODE=nfsroot
journalctl -b --no-pager
https://files.jessen.ch/mythbe2.log
lsinitrd /boot/initrd-XXX (which modules are there)
https://files.jessen.ch/mythbe2.lsinitrd
and ls -l /etc/resolv.conf
https://files.jessen.ch/mythbe2.txt -- Per Jessen, Zürich (0.4°C) Member, openSUSE Heroes (2016 - present) We're hiring - https://en.opensuse.org/openSUSE:Heroes
On Wed, Mar 1, 2023 at 11:06 AM Per Jessen <per@jessen.ch> wrote:
journalctl -b --no-pager
Is it with or without a firewall? Because I do not see any string "firewall" in this log.
Andrei Borzenkov wrote:
On Wed, Mar 1, 2023 at 11:06 AM Per Jessen <per@jessen.ch> wrote:
journalctl -b --no-pager
Is it with or without a firewall? Because I do not see any string "firewall" in this log.
Ah, sorry, that is a working system so no firewall. I'll enable the firewall and boot again. -- Per Jessen, Zürich (2.1°C) Member, openSUSE Heroes (2016 - present) We're hiring - https://en.opensuse.org/openSUSE:Heroes
Per Jessen wrote:
Andrei Borzenkov wrote:
On Wed, Mar 1, 2023 at 11:06 AM Per Jessen <per@jessen.ch> wrote:
journalctl -b --no-pager
Is it with or without a firewall? Because I do not see any string "firewall" in this log.
Ah, sorry, that is a working system so no firewall. I'll enable the firewall and boot again.
This shows the issue in a nutshell - a) enable firewall b) reboot c) empty resolv.conf https://files.jessen.ch/mythbe2-reboot-with-fw.txt boot log: https://files.jessen.ch/mythbe2-with-firewall.log -- Per Jessen, Zürich (1.4°C) Member, openSUSE Heroes (2016 - present) We're hiring - https://en.opensuse.org/openSUSE:Heroes
On Wed, Mar 1, 2023 at 12:12 PM Per Jessen <per@jessen.ch> wrote:
Mar 01 10:02:46 mythbe2 wickedd-nanny[969]: device eth0: call to org.opensuse.Network.Firewall.firewallUp() failed: DBus method call timed out Mar 01 10:02:46 mythbe2 wickedd-nanny[969]: eth0: failed to bring up device, still continuing No idea, org.opensuse prefix implies wicked. Sounds like a wicked issue.
Andrei Borzenkov wrote:
On Wed, Mar 1, 2023 at 12:12 PM Per Jessen <per@jessen.ch> wrote:
Mar 01 10:02:46 mythbe2 wickedd-nanny[969]: device eth0: call to org.opensuse.Network.Firewall.firewallUp() failed: DBus method call timed out Mar 01 10:02:46 mythbe2 wickedd-nanny[969]: eth0: failed to bring up device, still continuing
No idea, org.opensuse prefix implies wicked. Sounds like a wicked issue.
FWIW, problem persists in Leap 15.3 and Leap 15.4. Well, I guess it is too exotic to worry much about. For myself, the problem is "solved" as I won't be using firewalld on these systems anyway. -- Per Jessen, Zürich (3.3°C) Member, openSUSE Heroes (2016 - present) We're hiring - https://en.opensuse.org/openSUSE:Heroes
On 2/27/23 06:56, Per Jessen wrote:
From the mythv thread - I have just repeated this issue, on Leap 15.1. <snip>
I would try this out on 15.4 and 15.5, but NFS installations don't work. I guess I could do a zypper dup.
Anyone have any suggestion as to how or why firewalld might interfere with the populating of /etc/resolv.conf ?? Surely that's crazy.
(resent from gmail -- suddenlinkmail account seems to be on fritz with o.o again...) I will look and follow-up with what I did, but I specifically configured how /etc/resolve.conf would be updated to prevent just this weirdness. What I don't recall is what I did (see post about grey beards...) On 15.4, I saw the same behavior, the major problem being an empty resolve.conf that screwed name resolution. What I found is resolve.conf is now more a punching-bag for the various network managers, and some don't use it at all anymore (therein lies the issue) So I configured it to maintain the domain and search config I wanted to it didn't mysteriously end up empty depending on what order or what mood the boot process was in. Will follow-up with the details, but no you are not crazy, and yes I saw the same behavior on 15.4. -- David C. Rankin, J.D.,P.E.
In data lunedì 27 febbraio 2023 13:56:46 CET, Per Jessen ha scritto:
From the mythv thread - I have just repeated this issue, on Leap 15.1.
(I know its EOL, but I don't have a choice).
a) after rebuilding the initrd, the first boot - just the standard template in /etc/resolv.conf, no nameserver. firewalld is running.
b) 2nd reboot, no changes. Still an empty /etc/resolv.conf.
The wicked lease information is from last night.
c) stopped and disabled firewalld, 3rd reboot.
Now the lease info was updated and so was /etc/resolv.conf. Weird stuff.
d) enabled firewalld and rebooted. Empty /etc/resolv.conf.
I would try this out on 15.4 and 15.5, but NFS installations don't work. I guess I could do a zypper dup.
Anyone have any suggestion as to how or why firewalld might interfere with the populating of /etc/resolv.conf ?? Surely that's crazy.
I did encounter this on 15.1 at the time (way back in time BTW). What helped with me (the only thing that did help) was to erase etc/ resolv.conf and reboot. I never found out what cause this, sorry. But this could (not guarantee) help.
On 27.02.2023 15:56, Per Jessen wrote:
From the mythv thread - I have just repeated this issue, on Leap 15.1. (I know its EOL, but I don't have a choice).
a) after rebuilding the initrd, the first boot - just the standard template in /etc/resolv.conf, no nameserver. firewalld is running.
b) 2nd reboot, no changes. Still an empty /etc/resolv.conf.
The wicked lease information is from last night.
c) stopped and disabled firewalld, 3rd reboot.
Now the lease info was updated and so was /etc/resolv.conf. Weird stuff.
d) enabled firewalld and rebooted. Empty /etc/resolv.conf.
Do you get IP address and gateway(s)?
I would try this out on 15.4 and 15.5, but NFS installations don't work. I guess I could do a zypper dup.
Anyone have any suggestion as to how or why firewalld might interfere with the populating of /etc/resolv.conf ?? Surely that's crazy.
Andrei Borzenkov wrote:
On 27.02.2023 15:56, Per Jessen wrote:
From the mythv thread - I have just repeated this issue, on Leap 15.1. (I know its EOL, but I don't have a choice).
a) after rebuilding the initrd, the first boot - just the standard template in /etc/resolv.conf, no nameserver. firewalld is running.
b) 2nd reboot, no changes. Still an empty /etc/resolv.conf.
The wicked lease information is from last night.
c) stopped and disabled firewalld, 3rd reboot.
Now the lease info was updated and so was /etc/resolv.conf. Weird stuff.
d) enabled firewalld and rebooted. Empty /etc/resolv.conf.
Do you get IP address and gateway(s)?
Nope, just the empty template (full of comments). -- Per Jessen, Zürich (-0.8°C) Member, openSUSE Heroes (2016 - present) We're hiring - https://en.opensuse.org/openSUSE:Heroes
Per Jessen wrote:
Andrei Borzenkov wrote:
On 27.02.2023 15:56, Per Jessen wrote:
From the mythv thread - I have just repeated this issue, on Leap 15.1. (I know its EOL, but I don't have a choice).
a) after rebuilding the initrd, the first boot - just the standard template in /etc/resolv.conf, no nameserver. firewalld is running.
b) 2nd reboot, no changes. Still an empty /etc/resolv.conf.
The wicked lease information is from last night.
c) stopped and disabled firewalld, 3rd reboot.
Now the lease info was updated and so was /etc/resolv.conf. Weird stuff.
d) enabled firewalld and rebooted. Empty /etc/resolv.conf.
Do you get IP address and gateway(s)?
Nope, just the empty template (full of comments).
Sorry, I guess you meant if the network is configured? yes, the network is fine, IP addresses & gateway, I have also checked the wicked lease file, it's good. -- Per Jessen, Zürich (-0.7°C) Member, openSUSE Heroes (2016 - present) We're hiring - https://en.opensuse.org/openSUSE:Heroes
On 2/28/23 11:15 AM, Per Jessen wrote:
Per Jessen wrote:
Andrei Borzenkov wrote:
On 27.02.2023 15:56, Per Jessen wrote:
From the mythv thread - I have just repeated this issue, on Leap 15.1. (I know its EOL, but I don't have a choice).
a) after rebuilding the initrd, the first boot - just the standard template in /etc/resolv.conf, no nameserver. firewalld is running.
b) 2nd reboot, no changes. Still an empty /etc/resolv.conf.
The wicked lease information is from last night.
c) stopped and disabled firewalld, 3rd reboot.
Now the lease info was updated and so was /etc/resolv.conf. Weird stuff.
d) enabled firewalld and rebooted. Empty /etc/resolv.conf.
Do you get IP address and gateway(s)? Nope, just the empty template (full of comments). Sorry, I guess you meant if the network is configured? yes, the network is fine, IP addresses & gateway, I have also checked the wicked lease file, it's good.
If the ifcfg files haven't the stanzas for the resolver, you get that
Bruce Ferrell wrote:
On 2/28/23 11:15 AM, Per Jessen wrote:
Per Jessen wrote:
Andrei Borzenkov wrote:
On 27.02.2023 15:56, Per Jessen wrote:
From the mythv thread - I have just repeated this issue, on Leap 15.1. (I know its EOL, but I don't have a choice).
a) after rebuilding the initrd, the first boot - just the standard template in /etc/resolv.conf, no nameserver. firewalld is running.
b) 2nd reboot, no changes. Still an empty /etc/resolv.conf.
The wicked lease information is from last night.
c) stopped and disabled firewalld, 3rd reboot.
Now the lease info was updated and so was /etc/resolv.conf. Weird stuff.
d) enabled firewalld and rebooted. Empty /etc/resolv.conf.
Do you get IP address and gateway(s)? Nope, just the empty template (full of comments). Sorry, I guess you meant if the network is configured? yes, the network is fine, IP addresses & gateway, I have also checked the wicked lease file, it's good.
If the ifcfg files haven't the stanzas for the resolver, you get that
You mean /etc/sysconfig/network/* ? I don't see any resolver stanzas there. Even so, how does explain that it works when I stop firewealld ? -- Per Jessen, Zürich (1.1°C) Member, openSUSE Heroes (2016 - present) We're hiring - https://en.opensuse.org/openSUSE:Heroes
participants (7)
-
Andrei Borzenkov -
Bruce Ferrell -
David C. Rankin -
David C. Rankin -
Felix Miata -
Per Jessen -
Stakanov