Page 3 of 4 FirstFirst 1234 LastLast
Results 21 to 30 of 40

Thread: journalctl log flooded with NetworkManager warning

  1. #21

    Default Re: journalctl log flooded with NetworkManager warning

    Quote Originally Posted by dcurtisfra View Post
    Please be aware that, the “postfix” RPM package is recommended by the “patterns-base-enhanced_base” RPM package and suggested by the “openSUSE-release-15.1” RPM package.
    Check with “rpm --query --recommends patterns-base-enhanced_base” and “rpm --query --suggests openSUSE-release-15.1”.
    • You may find that, at some stage YaST Software will automatically re-install the “postfix” RPM package due to the dependencies noted above.
    Thank you. Is it please known reason for this and consequences of missing this package ?

  2. #22
    Join Date
    Aug 2010
    Location
    Chicago suburbs
    Posts
    14,009
    Blog Entries
    3

    Default Re: journalctl log flooded with NetworkManager warning

    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".
    openSUSE Leap 15.2; KDE Plasma 5.18.5;

  3. #23
    Join Date
    Feb 2010
    Location
    Germany
    Posts
    3,194

    Default Re: journalctl log flooded with NetworkManager warning

    Quote Originally Posted by MakeTopSite View Post
    Is it please known reason for this and consequences of missing this package ?
    1. The openSUSE Community decides which packages shall be included in the base system.
    2. 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”:

    Code:
     # systemctl status postfix.service
     # systemctl disable postfix.service

  4. #24

    Default Re: journalctl log flooded with NetworkManager warning

    Quote Originally Posted by nrickert View Post
    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".
    Well, thank you.

    Private data can be probably sent too.

  5. #25
    Join Date
    Jan 2017
    Location
    Nürnberg, Germany
    Posts
    276

    Default Re: journalctl log flooded with NetworkManager warning

    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?

  6. #26

    Default Re: journalctl log flooded with NetworkManager warning

    Quote Originally Posted by unix111 View Post
    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?
    Code:
    $ groups
    users dialout audio video systemd-network bumblebee
    Yes, it does.

  7. #27

    Default Re: journalctl log flooded with NetworkManager warning

    Could this be source of problem ?
    Code:
    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

  8. #28
    Join Date
    Feb 2010
    Location
    Germany
    Posts
    3,194

    Question Re: journalctl log flooded with NetworkManager warning

    Quote Originally Posted by MakeTopSite View Post
    Could this be source of problem ?
    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.

  9. #29

    Default Re: journalctl log flooded with NetworkManager warning

    Quote Originally Posted by dcurtisfra View Post
    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.

    Code:
    # grep -ri 'wlp5s0' /etc/sysconfig/network/
    #
    Code:
    # find /etc/sysconfig/network/ -iname '*wlp*'
    /etc/sysconfig/network/ifcfg-wlp5s0
    #

  10. #30
    Join Date
    Feb 2010
    Location
    Germany
    Posts
    3,194

    Default Re: journalctl log flooded with NetworkManager warning

    @MakeTopSite:

    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”:
    Code:
     # iwconfig
    Assuming that, the WLAN is using another device, the following, which doesn't need the user “root”, may also provide some information:
    Code:
     > ip link ls
    Please also show us the output of:
    Code:
     > ls /sys/class/net

Page 3 of 4 FirstFirst 1234 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •