No idea what particular component / update caused that though, or even how to find out.
Rich.
On Wed, May 05, 2021 at 09:41:48AM +0100, Richard W.M. Jones wrote:
No idea what particular component / update caused that though, or even how to find out.
So it started with:
localhost.localdomain systemd-hostnamed[1796302]: Hostname set to <localhost.localdomain> (static)
but this seems uncorrelated with any package installation or removal. After this systemd and NetworkManager appear to be battling with each other to set the hostname. I have hundreds of messages like this:
May 04 13:52:08 localhost.localdomain NetworkManager[1503]: <info> [1620132728.1664] policy: set-hostname: set hostname to 'pick' (from DHCPv4) May 04 13:52:08 localhost.localdomain systemd[1]: Starting Hostname Service... May 04 13:52:08 localhost.localdomain systemd[1]: Started Hostname Service. May 04 13:52:08 localhost.localdomain systemd-hostnamed[4074869]: Hostname set to <localhost.localdomain> (static) ... May 04 13:52:47 localhost.localdomain NetworkManager[1503]: <info> [1620132767.0935] policy: set-hostname: current hostname was changed outside NetworkManager: 'localhost.localdomain' May 04 13:52:47 localhost.localdomain NetworkManager[1503]: <info> [1620132767.0938] policy: set-hostname: set hostname to 'pick' (from DHCPv4)
Setting the hostname now through hostnamectl hasn't calmed things down, now they're battling to set the hostname to 'pick' (NM) or 'pick.home.annexia.org' (systemd).
Is this a bug? What component would it be filed against?
Rich.
On Wed, May 05, 2021 at 10:03:29AM +0100, Richard W.M. Jones wrote:
On Wed, May 05, 2021 at 09:41:48AM +0100, Richard W.M. Jones wrote:
No idea what particular component / update caused that though, or even how to find out.
So it started with:
localhost.localdomain systemd-hostnamed[1796302]: Hostname set to <localhost.localdomain> (static)
but this seems uncorrelated with any package installation or removal. After this systemd and NetworkManager appear to be battling with each other to set the hostname. I have hundreds of messages like this:
May 04 13:52:08 localhost.localdomain NetworkManager[1503]: <info> [1620132728.1664] policy: set-hostname: set hostname to 'pick' (from DHCPv4) May 04 13:52:08 localhost.localdomain systemd[1]: Starting Hostname Service... May 04 13:52:08 localhost.localdomain systemd[1]: Started Hostname Service. May 04 13:52:08 localhost.localdomain systemd-hostnamed[4074869]: Hostname set to <localhost.localdomain> (static) ... May 04 13:52:47 localhost.localdomain NetworkManager[1503]: <info> [1620132767.0935] policy: set-hostname: current hostname was changed outside NetworkManager: 'localhost.localdomain' May 04 13:52:47 localhost.localdomain NetworkManager[1503]: <info> [1620132767.0938] policy: set-hostname: set hostname to 'pick' (from DHCPv4)
Setting the hostname now through hostnamectl hasn't calmed things down, now they're battling to set the hostname to 'pick' (NM) or 'pick.home.annexia.org' (systemd).
Is this a bug? What component would it be filed against?
I assume you had 'localhost.localdomain' in /etc/hostname, and now you have 'pick.home.annexia.org' after the call to 'hostnamectl set-hostname'. This sounds like a bug in NM then, because the static configuration in /etc/ should take precedence, so NM shouldn't set the hostname at all.
If it's not too much trouble, could you attach the output from 'busctl introspect org.freedesktop.hostname1 /org/freedesktop/hostname1 org.freedesktop.hostname1', ideally without NM running, so we know what hostnamed thinks on its own?
Zbyszek
On Wed, May 05, 2021 at 09:16:38AM +0000, Zbigniew Jędrzejewski-Szmek wrote:
I assume you had 'localhost.localdomain' in /etc/hostname, and now you have 'pick.home.annexia.org' after the call to 'hostnamectl set-hostname'. This sounds like a bug in NM then, because the static configuration in /etc/ should take precedence, so NM shouldn't set the hostname at all.
This is possible, yes.
If it's not too much trouble, could you attach the output from 'busctl introspect org.freedesktop.hostname1 /org/freedesktop/hostname1 org.freedesktop.hostname1', ideally without NM running, so we know what hostnamed thinks on its own?
With NM disabled:
$ busctl introspect org.freedesktop.hostname1 /org/freedesktop/hostname1 org.freedesktop.hostname1 | cat NAME TYPE SIGNATURE RESULT/VALUE FLAGS .GetProductUUID method b ay - .SetChassis method sb - - .SetDeployment method sb - - .SetHostname method sb - - .SetIconName method sb - - .SetLocation method sb - - .SetPrettyHostname method sb - - .SetStaticHostname method sb - - .Chassis property s "desktop" emits-change .DefaultHostname property s "fedora" const .Deployment property s "" emits-change .HardwareModel property s "" const .HardwareVendor property s "" const .HomeURL property s "https://fedoraproject.org/" const .Hostname property s "pick.home.annexia.org" emits-change .HostnameSource property s "static" emits-change .IconName property s "computer-desktop" emits-change .KernelName property s "Linux" const .KernelRelease property s "5.11.0-0.rc3.122.fc34.x86_64" const .KernelVersion property s "#1 SMP Mon Jan 11 15:10:32 UTC 2021" const .Location property s "" emits-change .OperatingSystemCPEName property s "cpe:/o:fedoraproject:fedora:35" const .OperatingSystemPrettyName property s "Fedora 35 (Workstation Edition Prerele… const .PrettyHostname property s "" emits-change .StaticHostname property s "pick.home.annexia.org" emits-change
Should we move this discussion to a BZ?
Rich.
On Wed, May 05, 2021 at 12:28:56PM +0100, Richard W.M. Jones wrote:
On Wed, May 05, 2021 at 09:16:38AM +0000, Zbigniew Jędrzejewski-Szmek wrote:
I assume you had 'localhost.localdomain' in /etc/hostname, and now you have 'pick.home.annexia.org' after the call to 'hostnamectl set-hostname'. This sounds like a bug in NM then, because the static configuration in /etc/ should take precedence, so NM shouldn't set the hostname at all.
This is possible, yes.
If it's not too much trouble, could you attach the output from 'busctl introspect org.freedesktop.hostname1 /org/freedesktop/hostname1 org.freedesktop.hostname1', ideally without NM running, so we know what hostnamed thinks on its own?
With NM disabled:
$ busctl introspect org.freedesktop.hostname1 /org/freedesktop/hostname1 org.freedesktop.hostname1 | cat NAME TYPE SIGNATURE RESULT/VALUE FLAGS .GetProductUUID method b ay - .SetChassis method sb - - .SetDeployment method sb - - .SetHostname method sb - - .SetIconName method sb - - .SetLocation method sb - - .SetPrettyHostname method sb - - .SetStaticHostname method sb - - .Chassis property s "desktop" emits-change .DefaultHostname property s "fedora" const .Deployment property s "" emits-change .HardwareModel property s "" const .HardwareVendor property s "" const .HomeURL property s "https://fedoraproject.org/" const .Hostname property s "pick.home.annexia.org" emits-change .HostnameSource property s "static" emits-change .IconName property s "computer-desktop" emits-change .KernelName property s "Linux" const .KernelRelease property s "5.11.0-0.rc3.122.fc34.x86_64" const .KernelVersion property s "#1 SMP Mon Jan 11 15:10:32 UTC 2021" const .Location property s "" emits-change .OperatingSystemCPEName property s "cpe:/o:fedoraproject:fedora:35" const .OperatingSystemPrettyName property s "Fedora 35 (Workstation Edition Prerele… const .PrettyHostname property s "" emits-change .StaticHostname property s "pick.home.annexia.org" emits-change
Looks all legit.
Should we move this discussion to a BZ?
+1
Zbyszek
-
Richard W.M. Jones -
Zbigniew Jędrzejewski-Szmek