journalctl log flooded with NetworkManager warning

[MakeTopSite]

Dec 21 19:36:42 lin NetworkManager[7615]: <warn>  [1576953402.6235] error requesting auth for org.freedesktop.NetworkManager.enable-disable-connectivity-check: Authorization check failed: Failed to open file “/proc/17814/status”: No such file or directory 
Dec 21 19:36:42 lin NetworkManager[7615]: <warn>  [1576953402.6231] error requesting auth for org.freedesktop.NetworkManager.enable-disable-statistics: Authorization check failed: Failed t>
Dec 21 19:36:42 lin NetworkManager[7615]: <warn>  [1576953402.6227] error requesting auth for org.freedesktop.NetworkManager.checkpoint-rollback: Authorization check failed: Failed to open>
Dec 21 19:36:42 lin NetworkManager[7615]: <warn>  [1576953402.6224] error requesting auth for org.freedesktop.NetworkManager.reload: Authorization check failed: Failed to open file “/proc/>
Dec 21 19:36:42 lin NetworkManager[7615]: <warn>  [1576953402.6220] error requesting auth for org.freedesktop.NetworkManager.settings.modify.global-dns: Authorization check failed: Failed >
Dec 21 19:36:42 lin NetworkManager[7615]: <warn>  [1576953402.6216] error requesting auth for org.freedesktop.NetworkManager.settings.modify.hostname: Authorization check failed: Failed to>
Dec 21 19:36:42 lin NetworkManager[7615]: <warn>  [1576953402.6213] error requesting auth for org.freedesktop.NetworkManager.settings.modify.own: Authorization check failed: Failed to open>
Dec 21 19:36:42 lin NetworkManager[7615]: <warn>  [1576953402.6209] error requesting auth for org.freedesktop.NetworkManager.settings.modify.system: Authorization check failed: Failed to o>
Dec 21 19:36:42 lin NetworkManager[7615]: <warn>  [1576953402.6205] error requesting auth for org.freedesktop.NetworkManager.wifi.share.open: Authorization check failed: Failed to open fil>
Dec 21 19:36:42 lin NetworkManager[7615]: <warn>  [1576953402.6202] error requesting auth for org.freedesktop.NetworkManager.wifi.share.protected: Authorization check failed: Failed to ope>
Dec 21 19:36:42 lin NetworkManager[7615]: <warn>  [1576953402.6197] error requesting auth for org.freedesktop.NetworkManager.network-control: Authorization check failed: Failed to open fil>
Dec 21 19:36:42 lin NetworkManager[7615]: <warn>  [1576953402.6194] error requesting auth for org.freedesktop.NetworkManager.enable-disable-wimax: Authorization check failed: Failed to ope>
Dec 21 19:36:42 lin NetworkManager[7615]: <warn>  [1576953402.6190] error requesting auth for org.freedesktop.NetworkManager.enable-disable-wwan: Authorization check failed: Failed to open>
Dec 21 19:36:41 lin NetworkManager[7615]: <warn>  [1576953401.5963] error requesting auth for org.freedesktop.NetworkManager.enable-disable-connectivity-check: Authorization check failed: >
...
...
...

Anyone know please what to do ?

[nrickert]

I am not seeing anything like that.

Is your network actually working? It would help to know what is working and what isn’t working.

[MakeTopSite]

@nrickert

I am not seeing anything like that.

Is your network actually working? It would help to know what is working and what isn’t working.

Yes.

The only problem I notice sometime is a lower wifi signal strength. I don’t know why is this happening.

[deano_ferrari]

@MakeTopSite

Yes.

The only problem I notice sometime is a lower wifi signal strength. I don’t know why is this happening.

Hardware and driver details might be useful…

/usr/sbin/hwinfo --wlan

Also

/usr/sbin/iwconfig

You can get some realtime signal level information using…

watch "/usr/sbin/iwconfig |grep -i link"

[MakeTopSite]

# /usr/sbin/hwinfo --wlan
07: PCI 500.0: 0282 WLAN controller                             
  [Created at pci.386]
  Unique ID: ... 
  Parent ID: ...
  SysFS ID: /devices/pci0000:00/0000:00:1c.3/0000:05:00.0
  SysFS BusID: 0000:05:00.0
  Hardware Class: network
  Model: "Intel Centrino Wireless-N 135 BGN"
  Vendor: pci 0x8086 "Intel Corporation"
  Device: pci 0x0892 "Centrino Wireless-N 135"
  SubVendor: pci 0x8086 "Intel Corporation"
  SubDevice: pci 0x0062 "Centrino Wireless-N 135 BGN"
  Revision: 0xc4
  Driver: "iwlwifi"
  Driver Modules: "iwlwifi"
  Device File: wlan0
  Features: WLAN
  Memory Range: 0xf..00000-0xf..01fff (rw,non-prefetchable)
  IRQ: 29 (no events)
  HW Address: ...
  Permanent HW Address: ...
  Link detected: yes
  WLAN channels: 1 2 3 4 5 6 7 8 9 10 11 12 13
  WLAN frequencies: 2.412 2.417 2.422 2.427 2.432 2.437 2.442 2.447 2.452 2.457 2.462 2.467 2.472
  WLAN encryption modes: WEP40 WEP104 TKIP CCMP
  WLAN authentication modes: open sharedkey wpa-psk wpa-eap
  Module Alias: "pci:..."
  Driver Info #0:
    Driver Status: iwlwifi is active
    Driver Activation Cmd: "modprobe iwlwifi"
  Config Status: cfg=new, avail=yes, need=no, active=unknown
  Attached to: #1 (PCI bridge)


# /usr/sbin/iwconfig
lo        no wireless extensions.

wlan0     IEEE 802.11  ESSID:"..."  
          Mode:Managed  Frequency:2.447 GHz  Access Point: ...   
          Bit Rate=57.8 Mb/s   Tx-Power=15 dBm   
          Retry short limit:7   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:off
          Link Quality=39/70  Signal level=-71 dBm  
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:2  Invalid misc:195   Missed beacon:0

eth0      no wireless extensions.


# watch "/usr/sbin/iwconfig |grep -i link"
lo        no wireless extensions.

eth0      no wireless extensions.

Link Quality=40/70  Signal level=-70 dBm

[deano_ferrari]

The received signal level is a little low (and that can obviously depend on the distance from the associated access point), but the link quality is within the acceptable range. Do you have any specific concerns with the connectivity?

[MakeTopSite]

@deano_ferrari

The received signal level is a little low (and that can obviously depend on the distance from the associated access point), but the link quality is within the acceptable range. Do you have any specific concerns with the connectivity?

I’m OK with it if it is not a security risk. Logs would be much more readable without these repeated warnings.

[karlmistelberger]

@MakeTopSite

I’m OK with it if it is not a security risk. Logs would be much more readable without these repeated warnings.

You may override default log level of any service: Adjust or silence a systemd service’s logging levels | Ctrl blog

[MakeTopSite]

@karlmistelberger

You may override default log level of any service: Adjust or silence a systemd service’s logging levels | Ctrl blog

Thank you. I’ve tried

LogLevelMax=3

and

LogLevelMax=2

and

LogLevelMax=1

and

LogLevelMax=0

but it isn’t working.

[tsu2]

@MakeTopSite

Dec 21 19:36:42 lin NetworkManager[7615]: <warn>  [1576953402.6235] error requesting auth for org.freedesktop.NetworkManager.enable-disable-connectivity-check: Authorization check failed: Failed to open file “/proc/17814/status”: No such file or directory 
Dec 21 19:36:42 lin NetworkManager[7615]: <warn>  [1576953402.6231] error requesting auth for org.freedesktop.NetworkManager.enable-disable-statistics: Authorization check failed: Failed t>
Dec 21 19:36:42 lin NetworkManager[7615]: <warn>  [1576953402.6227] error requesting auth for org.freedesktop.NetworkManager.checkpoint-rollback: Authorization check failed: Failed to open>
Dec 21 19:36:42 lin NetworkManager[7615]: <warn>  [1576953402.6224] error requesting auth for org.freedesktop.NetworkManager.reload: Authorization check failed: Failed to open file “/proc/>
Dec 21 19:36:42 lin NetworkManager[7615]: <warn>  [1576953402.6220] error requesting auth for org.freedesktop.NetworkManager.settings.modify.global-dns: Authorization check failed: Failed >
Dec 21 19:36:42 lin NetworkManager[7615]: <warn>  [1576953402.6216] error requesting auth for org.freedesktop.NetworkManager.settings.modify.hostname: Authorization check failed: Failed to>
Dec 21 19:36:42 lin NetworkManager[7615]: <warn>  [1576953402.6213] error requesting auth for org.freedesktop.NetworkManager.settings.modify.own: Authorization check failed: Failed to open>
Dec 21 19:36:42 lin NetworkManager[7615]: <warn>  [1576953402.6209] error requesting auth for org.freedesktop.NetworkManager.settings.modify.system: Authorization check failed: Failed to o>
Dec 21 19:36:42 lin NetworkManager[7615]: <warn>  [1576953402.6205] error requesting auth for org.freedesktop.NetworkManager.wifi.share.open: Authorization check failed: Failed to open fil>
Dec 21 19:36:42 lin NetworkManager[7615]: <warn>  [1576953402.6202] error requesting auth for org.freedesktop.NetworkManager.wifi.share.protected: Authorization check failed: Failed to ope>
Dec 21 19:36:42 lin NetworkManager[7615]: <warn>  [1576953402.6197] error requesting auth for org.freedesktop.NetworkManager.network-control: Authorization check failed: Failed to open fil>
Dec 21 19:36:42 lin NetworkManager[7615]: <warn>  [1576953402.6194] error requesting auth for org.freedesktop.NetworkManager.enable-disable-wimax: Authorization check failed: Failed to ope>
Dec 21 19:36:42 lin NetworkManager[7615]: <warn>  [1576953402.6190] error requesting auth for org.freedesktop.NetworkManager.enable-disable-wwan: Authorization check failed: Failed to open>
Dec 21 19:36:41 lin NetworkManager[7615]: <warn>  [1576953401.5963] error requesting auth for org.freedesktop.NetworkManager.enable-disable-connectivity-check: Authorization check failed: >
...
...
...

Anyone know please what to do ?

Recommend actually reading the log events…
I see two types in what you posted (so don’t know if you’ve posted everything relevant or not).

1. When a connectivity check is actually made, the PiD file which represents the expected process is not found.
2. Some kind of request to actually do the connectivity check is failing because it’s not being authorized.

At the 30,000 foot level,
You should probably identify why a connectivity check is even being made… Are you invoking your Network Manager through something else? It’s not enough to simply identify your network hardware, this is ordinarily a software problem. Are you running some kind of netowrking software issued by a Vendor like Cisco or a VPN manager or something else? What did you install on your machine that has anything to do with networking?

As for troubleshooting the specific entries, you might start by looking at your logs more closely… look at your bootlog and the hundred or so lines that precede the entries you posted. Often knowing what happened just before your problem entries can tell you a lot about what might have preceded and been a possible direct cause.

The first error about a PiD file not found should probably considered in the following order…

• Is a connectivity check proper? Is it being invoked by something that shouldn’t even be running on your machine?
• If you don’t think that anything was installed on your machine properly, the next step is to consider it might be a misconfiguration, and possibly also by bad code.It’s a common mistake in code running on *NIX to instantiate something but not set the PiD… so the sytem assigns some random PiD number that is available but the code might know what it is, and be expecting something permanently set. It’s up to you how far you want to troubleshoot this or report a bug.

The second error will depend on what kind of software is trying to do the connectivity check. Again, depending on your willingness to spend effort on this and your skill level, you may want to simply report as a bug.

TSU

[dcurtisfra]

@MakeTopSite

Dec 21 19:36:42 lin NetworkManager[7615]: <warn>  [1576953402.6235] error requesting auth for org.freedesktop.NetworkManager.enable-disable-connectivity-check: Authorization check failed: Failed to open file “/proc/17814/status”: No such file or directory 

Whatever it was, that had the PID «Process Identification Number» “17814”, seems to have crashed or, disappeared, without crashing …

• Take a look in ‘/var/lib/systemd/coredump/’ to see if the offending application had dumped core via systemd or, not …
• With the user “root”, use the systemd Core Dump utility to examine what happened:

 # coredumpctl info 17814

(With the user “root”) A list of known Core Dumps can be obtained by means of “coredumpctl list” – where “missing” is noted, the “core” file is no longer present in ‘/var/lib/systemd/coredump/’ but, systemd will still have stored most of the relevant crash information in the Journal.

[dcurtisfra]

@MakeTopSite:

BTW, the default openSUSE behaviour is, to restrict the storage time of core files located in ‘/var/lib/systemd/coredump/’ to 3 days – “usr/lib/tmpfiles.d/systemd.conf”.

[MakeTopSite]

@tsu2

Recommend actually reading the log events…
I see two types in what you posted (so don’t know if you’ve posted everything relevant or not).

I’ve posted everything relevant by selecting screen output & Ctrl-C & Ctrl-V. Output was wider than screen width so I couldn’t copy everything. Missing text is the same and repeats so I copied it for first line only.

Warnings repeats too so I’ve ommitted repeated warnings.

This precedes network warnings (another time, network warnings starts at 07:08:18):

Jan 30 07:07:43 lin systemd[6581]: Started Accessibility services bus.
Jan 30 07:07:43 lin dbus-daemon[6642]: [session uid=1000 pid=6642] Successfully activated service 'org.a11y.Bus'
Jan 30 07:07:43 lin systemd[6581]: Starting Accessibility services bus...

@tsu2

You should probably identify why a connectivity check is even being made… Are you invoking your Network Manager through something else? It’s not enough to simply identify your network hardware, this is ordinarily a software problem. Are you running some kind of netowrking software issued by a Vendor like Cisco or a VPN manager or something else? What did you install on your machine that has anything to do with networking?

I’m not aware of anything.

@tsu2

• Is a connectivity check proper? Is it being invoked by something that shouldn’t even be running on your machine?

I’m not aware of anything wrong.

@tsu2

• If you don’t think that anything was installed on your machine properly, the next step is to consider it might be a misconfiguration, and possibly also by bad code.It’s a common mistake in code running on *NIX to instantiate something but not set the PiD… so the sytem assigns some random PiD number that is available but the code might know what it is, and be expecting something permanently set. It’s up to you how far you want to troubleshoot this or report a bug.

The second error will depend on what kind of software is trying to do the connectivity check. Again, depending on your willingness to spend effort on this and your skill level, you may want to simply report as a bug.

TSU

Thank you, I’ll try to find something.

[MakeTopSite]

@dcurtisfra

Whatever it was, that had the PID «Process Identification Number» “17814”, seems to have crashed or, disappeared, without crashing …

• Take a look in ‘/var/lib/systemd/coredump/’ to see if the offending application had dumped core via systemd or, not …
• With the user “root”, use the systemd Core Dump utility to examine what happened:

 # coredumpctl info 17814

(With the user “root”) A list of known Core Dumps can be obtained by means of “coredumpctl list” – where “missing” is noted, the “core” file is no longer present in ‘/var/lib/systemd/coredump/’ but, systemd will still have stored most of the relevant crash information in the Journal.

I’m sorry nothing was found.

[MakeTopSite]

@dcurtisfra

@MakeTopSite:

BTW, the default openSUSE behaviour is, to restrict the storage time of core files located in ‘/var/lib/systemd/coredump/’ to 3 days – “usr/lib/tmpfiles.d/systemd.conf”.

Thank you, yes I have default value.

[dcurtisfra]

@MakeTopSite

I’m sorry nothing was found.

Then, whatever it was that disappeared – it didn’t crash.
And, the NetworkManager “Enable/Disable connectivity check" wanted to check it’s status but, it was gone …

So, it seems that, there was a Network Connection but, it disconnected, for whatever reason.

• Is the machine a mobile device and, is it moving
  ?

[HR][/HR]One explanation is, that it’s a mobile device, moving at say 100 or 200 km/h and, the network connection is being handed off from one radio cell to the next …

[MakeTopSite]

@dcurtisfra

Then, whatever it was that disappeared – it didn’t crash.
And, the NetworkManager “Enable/Disable connectivity check" wanted to check it’s status but, it was gone …

So, it seems that, there was a Network Connection but, it disconnected, for whatever reason.

• Is the machine a mobile device and, is it moving
  ?

[HR][/HR]One explanation is, that it’s a mobile device, moving at say 100 or 200 km/h and, the network connection is being handed off from one radio cell to the next …

No

No
(The message you have entered is too short. Please lengthen your message to at least 10 characters.)

[dcurtisfra]

@MakeTopSite:

OK, the system ain’t moving anywhere …

Then, if a process simply disappears/dies without cleaning up it’s dependencies, there’s possibly something incompatible in your current installation.

1. Please check your installation repositories – “zypper repos --uri” – anything which ain’t “leap/15.1/” is suspect – please check very carefully …
2. Refresh the RPM database – “zypper refresh” – and then, please check that the RPM database isn’t corrupt and, rebuild it: “rpm --rebuilddb”.
3. Please perform an initial Repository verification: “zypper verify”.
4. Please check that all the installed files match to the RPM database: “rpm --verify --all”.
5. Please check for orphaned packages: either, with YaST or, with “zypper packages --orphaned”.
6. Make sure that, the “tmp” directories are clean: “systemctl start systemd-tmpfiles-clean.service”.
7. Make sure that, the user’s Cache directory is clean: “~/.cache/”.
8. Logout and then reboot.

[MakeTopSite]

@dcurtisfra

@MakeTopSite:

OK, the system ain’t moving anywhere …

Then, if a process simply disappears/dies without cleaning up it’s dependencies, there’s possibly something incompatible in your current installation.

1. Please check your installation repositories – “zypper repos --uri” – anything which ain’t “leap/15.1/” is suspect – please check very carefully …
2. Refresh the RPM database – “zypper refresh” – and then, please check that the RPM database isn’t corrupt and, rebuild it: “rpm --rebuilddb”.
3. Please perform an initial Repository verification: “zypper verify”.
4. Please check that all the installed files match to the RPM database: “rpm --verify --all”.
5. Please check for orphaned packages: either, with YaST or, with “zypper packages --orphaned”.
6. Make sure that, the “tmp” directories are clean: “systemctl start systemd-tmpfiles-clean.service”.
7. Make sure that, the user’s Cache directory is clean: “~/.cache/”.
8. Logout and then reboot.

Warnings have disappeared after removing postfix and correcting wicked configuration.

Then I have tried commands you have suggested. Results seemed to be ok.

rpm --verify --all
SM5....T.  c /etc/libvirt/nwfilter/allow-arp.xml
SM5....T.  c /etc/libvirt/nwfilter/allow-dhcp-server.xml
SM5....T.  c /etc/libvirt/nwfilter/allow-dhcp.xml
SM5....T.  c /etc/libvirt/nwfilter/allow-incoming-ipv4.xml
SM5....T.  c /etc/libvirt/nwfilter/allow-ipv4.xml
SM5....T.  c /etc/libvirt/nwfilter/clean-traffic-gateway.xml
SM5....T.  c /etc/libvirt/nwfilter/clean-traffic.xml
SM5....T.  c /etc/libvirt/nwfilter/no-arp-ip-spoofing.xml
SM5....T.  c /etc/libvirt/nwfilter/no-arp-mac-spoofing.xml
SM5....T.  c /etc/libvirt/nwfilter/no-arp-spoofing.xml
SM5....T.  c /etc/libvirt/nwfilter/no-ip-multicast.xml
SM5....T.  c /etc/libvirt/nwfilter/no-ip-spoofing.xml
SM5....T.  c /etc/libvirt/nwfilter/no-mac-broadcast.xml
SM5....T.  c /etc/libvirt/nwfilter/no-mac-spoofing.xml
SM5....T.  c /etc/libvirt/nwfilter/no-other-l2-traffic.xml
SM5....T.  c /etc/libvirt/nwfilter/no-other-rarp-traffic.xml
SM5....T.  c /etc/libvirt/nwfilter/qemu-announce-self-rarp.xml
SM5....T.  c /etc/libvirt/nwfilter/qemu-announce-self.xml
.M.......  g /run/lirc
.M....G..  g /etc/brlapi.key
....L....  c /etc/pam.d/common-account
....L....  c /etc/pam.d/common-auth
....L....  c /etc/pam.d/common-password
....L....  c /etc/pam.d/common-session
.M....G..  g /var/log/lastlog
S.5....T.  c /etc/pam.d/login
S.5....T.  c /etc/pam.d/xdm
S.5....T.  c /etc/security/pam_mount.conf.xml
....L....    /usr/share/java/xml-commons-apis.jar
....L....  d /usr/share/man/man1/ftp.1.gz
S.5....T.  c /etc/default/tlp
.......T.    /usr/lib64/gconv/gconv-modules.cache
S.5....T.  c /etc/pulse/client.conf
.M.......  c /var/log/audit/audit.log
.M.......  g /usr/share/fonts/75dpi/encodings.dir
.M.......  g /usr/share/fonts/75dpi/fonts.scale
.M.......  g /usr/share/fonts/misc/encodings.dir
.M.......  g /usr/share/fonts/misc/fonts.scale
.M.......  g /var/lib/GeoIP/GeoIP.dat
S.5....T.    /usr/share/icewm/themes/Infadel2/Overloaded.theme
.M...U...    /var/cache/cups
.M.......  g /etc/mpv/scripts
S.5....T.  c /etc/ntp.conf
.M.......  g /var/lib/ca-certificates/ca-bundle.pem
.M.......  g /var/lib/ca-certificates/java-cacerts
.M.......  g /var/log/alternatives.log
....L....    /etc/ImageMagick-7
.M.......  g /usr/share/fonts/100dpi/encodings.dir
.M.......  g /usr/share/fonts/100dpi/fonts.scale
.M.......  g /usr/share/fonts/Type1/encodings.dir
.M.......  g /usr/share/fonts/cyrillic/encodings.dir
.M.......  g /usr/share/fonts/cyrillic/fonts.scale
.M.......  g /usr/share/fonts/truetype/encodings.dir
S.5....T.  c /etc/sysconfig/SuSEfirewall2
S.5....T.  c /etc/plymouth/plymouthd.conf
.....UG..  g /run/lightdm
S.5....T.  c /etc/fonts/conf.d/10-rendering-options.conf
S.5....T.  c /etc/fonts/conf.d/58-family-prefer-local.conf
.M.......  g /etc/udev/hwdb.bin
S.5....T.  c /etc/pam.d/sudo
.M.......  g /etc/iscsi/initiatorname.iscsi
.M.......  g /boot/grub2/grub.cfg
S.5....T.  c /etc/default/grub
.......T.  c /etc/login.defs
.M.......  g /var/lib/kerberos/krb5
.M.......  g /var/lib/kerberos/krb5/user
.M.......  c /etc/X11/xorg.conf.d/00-keyboard.conf
.M.......  c /etc/locale.conf
.M.......  c /etc/machine-id
.M.......  c /etc/vconsole.conf
.M.......  g /var/lib/systemd/random-seed
.M.......  g /run/avahi-daemon
.M.......  g /etc/xml/catalog-d.xml
.M.......  g /etc/mpv/scripts
SM5....T.  c /etc/fonts/conf.d/30-metric-aliases.conf
.M.......  g /run/mcelog
.M.......  g /run/cryptsetup

Then I have tried to reproduce this warning by undoing wrong wicked configuration, but warnings have never appeared again.

[dcurtisfra]

@MakeTopSite

Warnings have disappeared after removing postfix

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.