Bug 31379

Summary:	network manager warnings in system journal
Product:	Mageia	Reporter:	Mészáros Csaba <csablak>
Component:	RPM Packages	Assignee:	Olav Vitters <olav>
Status:	NEW ---	QA Contact:
Severity:	normal
Priority:	Normal
Version:	8
Target Milestone:	---
Hardware:	All
OS:	Linux
Whiteboard:
Source RPM:	networkmanager-1.26.6-1.1.mga8	CVE:
Status comment:

Description Mészáros Csaba 2023-01-07 10:37:00 CET

I switched to NetworkManger based on this description.
https://wiki.mageia.org/en/Switching_to_networkmanager

However, I get two warnings.
1 warning: 
/var/spool/postfix/etc/resolv.conf and /etc/resolv.conf differ

$ cat /var/spool/postfix/etc/resolv.conf
# Generated by NetworkManager
nameserver 192.168.123.1

https://www.linuxtopia.org/online_books/mail_systems/postfix_documentation/IPV6_README_002.html

$ cat /etc/resolv.conf
# Generated by NetworkManager
nameserver 192.168.123.1
nameserver 2a01:36d:600:71a2:42b0:76ff:fe97:fbb4

2 warning:
NetworkManager[767]: <warn>  [1673081882.8303] ifcfg-rh:     ignoring GATEWAY (/etc/sysconfig/network) for ifcfg-enp0s10 because the connection has no static addresses

Comment 1 Lewis Smith 2023-01-07 20:00:47 CET

Please say whether there are any ill effects from these messages - something does not work as it should; or are they are simply 'there'?

Are you using postfix? Maybe problem 1 is there.

The link you give refers to /etc/postfix/ and IPV6. Not sure of the relevance.

Summary: network warnings => network manager warnings in system journal
CC: (none) => lewyssmith

Comment 2 Mészáros Csaba 2023-01-08 20:15:50 CET

Yes, it's just "there". However, I have probably found why all this is happening.

The NetworkManager rebuilds the /etc/resolv.conf from scratch on startup. It blanks out all the lines except for the first comment line. If the postfix startup script calls for this file on startup in the timeframe that NM is rebuilding /etc/resolv.conf, then your /var/spool/postfix/etc/resolv.conf will have only the first commented line. Making postifx load later in the boot process should help with this.
Well, since this is not a systemd process, where can it be set?
systemctl enable systemd-networkd-wait-online.service ????

The NetworkManger-wait-online.service already enable and run.
I guess the two are not the same, but I'm not at home in this.

Comment 3 Lewis Smith 2023-01-09 19:34:47 CET

Thank you for the further explanation.

Assigning initially to Olav for Network mgr.
If you think the problem is really with Postfix, re-assign the bug to pkg-bugs for that - and perhaps adjust the bug title in that direction.
Same if you think initscripts is the culprit.

CC: lewyssmith => (none)
Assignee: bugsquad => olav

Comment 4 Mészáros Csaba 2023-01-11 18:38:17 CET

Yes. There seems to be a timing problem.
I temporarily inserted a 10 sec wait in the /etc/rc.d/init.d/postfix file. Maybe less is enough. But this way there is no error message and the ipv6 address is also listed in both places. Boot time has not decreased.
start () {
   sleep 10
   local i
....
}
However, when I looked at the openSuse distro, it is already completely replaced with the legacy sysv init postfix systemd version.