Thank you. Is it please known reason for this and consequences of missing this package ?
Some software wants to send email reports of problems, and that needs an email server. If you install a different email server, such as “sendmail” or “exim”, then it won’t reinstall “postfix”.
- The openSUSE Community decides which packages shall be included in the base system.
- Yes, “Postfix” is enabled by default in the “systemd” scheme but, if you have no need for an e-Mail Server on your system, the better method to disable it is, to disable in in “systemd”:
# systemctl status postfix.service
# systemctl disable postfix.service
Well, thank you.
Private data can be probably sent too.
Seeing in the messages that authorisations fail left and right, I’m wondering: is the user a member of the relevant groups?
I couldn’t find any groups related to NetworkManager specifically, but adding your user to the group systemd-network might be worth a try. You can do that in YaST’s »User and Group Management« module.
If you add a completely new test user, does NetworkManager complain the same way?
$ groups
users dialout audio video systemd-network bumblebee
Yes, it does.
Could this be source of problem ?
journalctl -r
Jun 30 12:40:48 lin systemd[1]: Reached target Network.
Jun 30 12:40:48 lin systemd[1]: Started wicked managed network interfaces.
Jun 30 12:40:48 lin wicked[1575]: **wlp5s0** no-device
Jun 30 12:40:48 lin wicked[1575]: wlan0 up
Jun 30 12:40:48 lin wicked[1575]: lo up
If the device “wlp5s0” is not present, what’s the WLAN using?
Please check the network configuration – grep recursively and case insentively through ‘/etc/sysconfig/network/’ for “wlp5s0”.
- Possibly, there’s ab redundant entry in a configuration file.
I’m sorry I don’t understand.
# grep -ri 'wlp5s0' /etc/sysconfig/network/
#
# find /etc/sysconfig/network/ -iname '*wlp*'
/etc/sysconfig/network/ifcfg-wlp5s0
#
You seem to have a redundant configuration file:
- The systemd Journal is clearly indicating that, the device “wlp5s0” doesn’t exist.
Please post the output of, using the user “root”:
# iwconfig
Assuming that, the WLAN is using another device, the following, which doesn’t need the user “root”, may also provide some information:
> ip link ls
Please also show us the output of:
> ls /sys/class/net
# iwconfig
lo no wireless extensions.
wlan0 IEEE 802.11 ESSID:"Wifi"
Mode:Managed Frequency:2.462 GHz Access Point: ______________
Bit Rate=52 Mb/s Tx-Power=15 dBm
Retry short limit:7 RTS thr:off Fragment thr:off
Encryption key:off
Power Management:off
Link Quality=38/70 Signal level=-72 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:2 Invalid misc:51 Missed beacon:0
eth0 no wireless extensions.
ip link ls
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
link/ether ________________ brd ff:ff:ff:ff:ff:ff
3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DORMANT group default qlen 1000
link/ether ____________________ brd ff:ff:ff:ff:ff:ff
ls /sys/class/net
eth0 lo wlan0
Therefore, you have defined a device named “wlp5s0” which doesn’t exist. The system definition of network devices should be as follows:
> ls /etc/sysconfig/network/
config dhcp ifcfg-eth0 ifcfg-lo ifcfg.template ifcfg-wlan0 **if-down.d** **if-up.d** **providers** **scripts**
>
Remove everything else from “/etc/sysconfig/network/”, especially ‘ifcfg-wlp5s0’.
I’ve removed ‘ifcfg-wlp5s0’ only. ifcfg-eth0 was missing.
ls /etc/sysconfig/network/
config dhcp ifcfg-lo ifcfg.template ifcfg-wlan0 if-down.d if-up.d providers scripts
Using YaST, take a look into the Network Settings (in the System section): <https://doc.opensuse.org/documentation/leap/reference/html/book-opensuse-reference/cha-network.html#sec-network-yast>.
- Take a particular look at the “Overview” tab – you’ll find that, the “eth0” interface has been discovered but, never activated …
- If you’ve changed to “Network Manager”, you’ll have to change to “Wicked”, setup “eth0”, save everything, exit Network Settings, enter Network Settings and then, change back to “Network Manager” …
Thank you, I did it successfully.
journalctl -r
Jul 08 07:57:09 lin NetworkManager[1501]: <info> [1594187829.7856] dhcp4 (wlan0): address 10.0.0.34
Jul 08 07:57:09 lin dhclient[3847]: suspect value in domain_name option - discarded
Jul 08 07:57:08 lin nm-dispatcher[3923]: req:3 'connectivity-change': start running ordered scripts...
Jul 08 07:57:08 lin nm-dispatcher[3923]: req:3 'connectivity-change': new request (5 scripts)
Jul 08 07:57:08 lin NetworkManager[1501]: <info> [1594187828.9982] manager: NetworkManager state is now CONNECTED_GLOBAL
Jul 08 07:57:07 lin nm-dispatcher[3923]: req:2 'up' [wlan0]: start running ordered scripts...
Jul 08 07:57:07 lin nm-dispatcher[3923]: req:2 'up' [wlan0]: new request (5 scripts)
Jul 08 07:57:07 lin NetworkManager[1501]: <info> [1594187827.9286] device (wlan0): Activation: successful, device activated.
Jul 08 07:57:07 lin NetworkManager[1501]: <warn> [1594187827.9286] dns-mgr: could not commit DNS changes: Error calling netconfig: exited with status 20
Jul 08 07:57:07 lin NetworkManager[1501]: nisdomainname: you must be root to change the domain name
Jul 08 07:57:07 lin NetworkManager[1501]: call "netconfig update -f" to adjust /etc/resolv.conf
Jul 08 07:57:07 lin NetworkManager[1501]: ATTENTION: /etc/resolv.conf is not a link to /var/run/netconfig/resolv.conf
Jul 08 07:57:07 lin NetworkManager[1501]: <info> [1594187827.6270] policy: set 'Wifi-' (wlan0) as default for IPv6 routing and DNS
Is it needed to do what is recomended in a log ?
- Is there any particular reason for ‘/etc/resolv.conf’ not being a link?
- Are you aware that, ‘/var/run/netconfig/resolv.conf’ is auto-generated by netconfig?
- Are you aware that, all static DNS variables should be defined in ‘/etc/sysconfig/network/config’?
- Have you changed any of the “NETCONFIG_NIS_” variables in ‘/etc/sysconfig/network/config’ away from the default values?
- Are you aware that, the DHCP server which is part of your LAN – usually the router to your ISP – usually defines an IP domain name for the private IP network which is your LAN?
The “NETCONFIG_DNS_STATIC_SEARCHLIST=” parameter of ‘/etc/sysconfig/network/config’ should be a string which is exactly that domain name.
BTW, in ‘/etc/sysconfig/network/config’ you may have to add “-dns-dnsmasq” to the default values of “NETCONFIG_MODULES_ORDER=”.
- But, only if, you don’t want your system to be a lightweight DNS, TFTP, PXE, router advertisement and DHCP server … >:)
Answer to all question is “no”.
I’ve set “NETCONFIG_DNS_STATIC_SEARCHLIST”, called
# netconfig update -f
Link ‘/etc/resolv.conf’ to ‘/var/run/netconfig/resolv.conf’ was created but warning persists:
Jul 10 04:55:30 lin NetworkManager[1508]: <info> [1594349730.0514] device (wlan0): Activation: successful, device activated.
Jul 10 04:55:30 lin NetworkManager[1508]: <warn> [1594349730.0513] dns-mgr: could not commit DNS changes: Error calling netconfig: exited w>
Jul 10 04:55:30 lin NetworkManager[1508]: nisdomainname: you must be root to change the domain name
Jul 10 04:55:30 lin NetworkManager[1508]: call "netconfig update -f" to adjust /etc/resolv.conf
Jul 10 04:55:30 lin NetworkManager[1508]: ATTENTION: /etc/resolv.conf is not a link to /var/run/netconfig/resolv.conf
Does NetworkManager / nisdomainname have enough permission ?
The link is normally created by the package “sysconfig-netconfig” – remove the link and then forcibly reinstall the package:
# zypper install --force sysconfig-netconfig
And then, reboot.
Thank you, it has solved warnings mentioned here https://forums.opensuse.org/showthread.php/538558-journalctl-log-flooded-with-NetworkManager-warning?p=2942824#post2942824.