disk monitor spams system logs about inaccessible mounts

[Ken Sharp]

My syslog fills every two seconds with:

Apr 12 15:13:59 org.mate.panel.applet.MultiLoadAppletFactory[3994]: glibtop(c=4286): [WARNING] statvfs '/var/snap/lxd/common/ns/shmounts' failed: Permission denied
Apr 12 15:13:59 org.mate.panel.applet.MultiLoadAppletFactory[3994]: glibtop(c=4286): [WARNING] statvfs '/var/snap/lxd/common/ns/mntns' failed: Permission denied

I have no idea how to disable this, and it's really not helpful.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: mate-applets 1.20.1-3
ProcVersionSignature: Ubuntu 5.3.0-45.37~18.04.1-generic 5.3.18
Uname: Linux 5.3.0-45-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7.14
Architecture: amd64
CurrentDesktop: MATE
Date: Sun Apr 12 15:13:18 2020
InstallationDate: Installed on 2019-06-09 (307 days ago)
InstallationMedia: Ubuntu-MATE 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
SourcePackage: mate-applets
UpgradeStatus: No upgrade log present (probably fresh install)

[rabin (rabin-redhat-bugs)]

Description of problem:

Based on some Google-ing it seems to be a bug with the system monitor applet,
when the disk i/o monitor is active, journald is filled with this messages.

```
Jul 12 21:59:36 localhost org.mate.panel.applet.MultiLoadAppletFactory[2864]: glibtop(c=3289): [WARNING] statvfs '/run/docker/netns/00d2ed483252' failed: Permission denied
Jul 12 21:59:37 localhost org.mate.panel.applet.MultiLoadAppletFactory[2864]: glibtop(c=3289): [WARNING] statvfs '/var/lib/docker/devicemapper/mnt/8fd774a16ef85394173fbae8e993912adc8618c6eb7d45' failed: Permission denied
```

Version-Release number of selected component (if applicable):

How reproducible:
In my case I started a docker container, and stared getting this messages.

Steps to Reproduce:
1. Add the system resource monitor applet to the panel.
2. Enable Disk activity logging.
3. Start a docker container

Actual results:

- The log is start filling with the above messages.

Expected results:

- Not getting dose WARNING messages.

Additional info:

rpm -qa | grep ^mate
mate-desktop-1.14.1-3.fc24.x86_64
mate-power-manager-1.14.0-1.fc24.x86_64
mate-icon-theme-faenza-1.14.0-1.fc24.noarch
mate-session-manager-1.14.0-1.fc24.x86_64
mate-notification-daemon-1.14.1-1.fc24.x86_64
mate-icon-theme-1.14.0-1.fc24.noarch
mate-media-1.14.0-1.fc24.x86_64
mate-desktop-libs-1.14.1-3.fc24.x86_64
mate-panel-1.14.1-1.fc24.x86_64
mate-utils-common-1.14.0-1.fc24.noarch
mate-control-center-1.14.0-1.fc24.x86_64
mate-menus-libs-1.14.0-1.fc24.x86_64
mate-screenshot-1.14.0-1.fc24.x86_64
mate-calc-1.8.0-5.fc24.x86_64
mate-themes-3.20.9-3.fc24.noarch
mate-applets-1.14.0-1.fc24.x86_64
mate-disk-usage-analyzer-1.14.0-1.fc24.x86_64
mate-panel-libs-1.14.1-1.fc24.x86_64
mate-control-center-filesystem-1.14.0-1.fc24.x86_64
mate-menus-preferences-category-menu-1.14.0-1.fc24.x86_64
mate-backgrounds-1.14.0-1.fc24.noarch
mate-user-guide-1.14.0-1.fc24.noarch
mate-screensaver-1.14.1-1.fc24.x86_64
mate-system-log-1.14.0-1.fc24.x86_64
mate-settings-daemon-1.14.0-1.fc24.x86_64
mate-menus-1.14.0-1.fc24.x86_64
mate-terminal-1.14.0-2.fc24.x86_64
mate-system-monitor-1.14.0-2.fc24.x86_64
mate-search-tool-1.14.0-1.fc24.x86_64
mate-dictionary-1.14.0-1.fc24.x86_64
mate-polkit-1.14.0-1.fc24.x86_64

[rabin (rabin-redhat-bugs)]

still relevant,

rpm -qa | grep -- "mate"

mate-applets-1.16.0-1.fc25.x86_64
libmateweather-1.16.1-1.fc25.x86_64
mate-control-center-1.16.1-1.fc25.x86_64
libmatemixer-1.16.0-1.fc25.x86_64
mate-backgrounds-1.16.0-1.fc25.noarch
mate-user-guide-1.16.0-1.fc25.noarch
mate-panel-1.16.1-1.fc25.x86_64
mate-utils-common-1.16.0-1.fc25.noarch
mate-menus-libs-1.16.0-1.fc25.x86_64
mate-polkit-1.16.0-1.fc25.x86_64
mate-media-1.16.0-1.fc25.x86_64
mate-terminal-1.16.2-1.fc25.x86_64
f25-backgrounds-mate-25.1.1-2.fc25.noarch
mate-notification-daemon-1.16.1-1.fc25.x86_64
mate-panel-libs-1.16.1-1.fc25.x86_64
libmatekbd-1.16.0-1.fc25.x86_64
mate-system-log-1.16.0-1.fc25.x86_64
mate-icon-theme-1.16.0-1.fc25.noarch
mate-power-manager-1.16.2-1.fc25.x86_64
mate-screensaver-1.16.1-1.fc25.x86_64
mate-desktop-libs-1.16.2-1.fc25.x86_64
mate-themes-3.22.8-1.fc25.noarch
mate-control-center-filesystem-1.16.1-1.fc25.x86_64
mate-disk-usage-analyzer-1.16.0-1.fc25.x86_64
mate-settings-daemon-1.16.2-1.fc25.x86_64
mate-menus-1.16.0-1.fc25.x86_64
mate-desktop-1.16.2-1.fc25.x86_64
mate-system-monitor-1.16.0-1.fc25.x86_64
mate-search-tool-1.16.0-1.fc25.x86_64
mate-session-manager-1.16.1-1.fc25.x86_64
mate-menus-preferences-category-menu-1.16.0-1.fc25.x86_64
libmateweather-data-1.16.1-1.fc25.noarch
mate-calc-1.8.0-6.fc25.x86_64

[bcotton (bcotton-redhat-bugs)]

This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora 'version'
of '25'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 25 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

[rabin (rabin-redhat-bugs)]

Still a problem with Fedora 27.

[fedora (fedora-redhat-bugs-1)]

I do not use a docker container so i can't reproduce it.
And i don't see the log messages in a normal MATE installation.

[rabin (rabin-redhat-bugs)]

you can try it by installing docker and run a container,

dnf install docker
systemctl start docker
docker pull docker.io/alpine
docker run -it --rm docker.io/alpine /bin/bash

and look at the logs in journalctl

[fedora (fedora-redhat-bugs-1)]

I only want to reproduce it, ...not to learn to use or debug docker :-)

[root@mother rave]# docker run -it --rm docker.io/alpine /bin/bash
/usr/bin/docker-current: Error response from daemon: oci runtime error: container_linux.go:247: starting container process caused "exec: \"/bin/bash\": stat /bin/bash: no such file or directory".
[root@mother rave]# docker run -it --rm docker.io/alpine /bin/bash
/usr/bin/docker-current: Error response from daemon: oci runtime error: container_linux.go:247: starting container process caused "exec: \"/bin/bash\": stat /bin/bash: no such file or directory".

[rabin (rabin-redhat-bugs)]

my bad alpine don't come with bash, use `sh` instead

# docker run --name test -it --rm docker.io/alpine /bin/sh

you can then stop it with

# docker kill test

[fedora (fedora-redhat-bugs-1)]

Ok,
that works, but i dond see the mentioned warnings in journal...
See my logs.
If i fire up mate-system-monitor from context-menu of monitor applet i get only this one.

Nov 18 19:56:14 mother.mother.loc mate-system-mon[9514]: SELinux was found but is not enabled.

Have you ever tried to disable selinux?

[fedora (fedora-redhat-bugs-1)]

Created attachment 1354912
journal log

[rabin (rabin-redhat-bugs)]

My problem is with "System Monitor" applet when enabling disk activity monitoring
see the linked video on youtube - https://youtu.be/oRWeKEIhNx8

[fedora (fedora-redhat-bugs-1)]

I tried hard but i don't get the warnings when enabling disk activity monitoring in the applet, see my video from f27.
https://www.dropbox.com/s/vy6bv30zesd0u5u/docker-with%20system-monitor-applet.ogv?dl=0
Do i miss something?

Selinux is disabled in this installation too.

[fedora (fedora-redhat-bugs-1)]

[rave@mother ~]$ rpm -qa mate-applets
mate-applets-1.19.2-2.fc27.x86_64
[rave@mother ~]$ uname -r
4.13.12-300.fc27.x86_64

[rabin (rabin-redhat-bugs)]

Yea the steps to produce are the same, but it seems like something is different between our systems.

can you please output you lvs output ?

# lvs

# lvs
  LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert
  home ssd_180 -wi-ao---- 99.71g
  root ssd_180 -wi-ao---- 50.00g
  swap ssd_180 -wi-ao---- <16.77g
  data ssd_500 -wi-ao---- 474.48g
  docker-pool ssd_500 twi-a-t--- 12.39g 78.53 0.40

and the content of your docker config files,

# cat /etc/sysconfig/docker-storage-setup

# Edit this file to override any configuration options specified in
# /usr/lib/docker-storage-setup/docker-storage-setup.
#
# For more details refer to "man docker-storage-setup"

VG=ssd_500

# cat /etc/sysconfig/docker-storage

DOCKER_STORAGE_OPTIONS="--storage-driver devicemapper --storage-opt dm.fs=xfs --storage-opt dm.thinpooldev=/dev/mapper/ssd_500-docker--pool --storage-opt dm.use_deferred_removal=true --storage-opt dm.use_deferred_deletion=true "

Also , I run SELinux in permissive mode.
and i have the same package version as you.

[fedora (fedora-redhat-bugs-1)]

Hmm, i don't use LVM, i use normal storages and of course fdisk -l
don't show me any docker-pool as it isn't set.

[root@mother rave]# cat /etc/sysconfig/docker-storage-setup
# Edit this file to override any configuration options specified in
# /usr/share/container-storage-setup/container-storage-setup.
#
# For more details refer to "man container-storage-setup"
[root@mother rave]# cat /etc/sysconfig/docker-storage
# Do not edit. This file is auto-generated by docker-storage-setup.
DOCKER_STORAGE_OPTIONS=

Well i can create a small partition somewhere for testing, but i don't want to learn how to use docker at the moment ;-)

[fedora (fedora-redhat-bugs-1)]

# A quoted, space-separated list of devices to be used. This currently
# expects the devices to be unpartitioned drives. If "VG" is not specified,
# then use of the root disk's extra space is implied.
#
# DEVS=/dev/vdb

Sorry, this sounds like i need to have a extra hard disk and it isn't possible to use an single partition.

[rabin (rabin-redhat-bugs)]

you can probably use a USB stick for the test ?

[fedora (fedora-redhat-bugs-1)]

ok, can you give working and tested instructions to add a usb-stick as docker image please?

[rabin (rabin-redhat-bugs)]

first let me thank you for agreeing to go over all this steps just to fix this problem.

First stop docker daemon if it is running
# systemctl stop docker

then delete (or move) docker metadata/image folder
# mv /var/lib/docker /var/lib/docker.backup

remove the current config file for docker storage
# rm /etc/sysconfig/docker-storage

next format a usb disk to use lvm (e.g my usb stick is /dev/sdd)

# export USB_STICK=/dev/sdd
# pvcreate $USB_STICK
# vgcreate vg_docker $USB_STICK

now if you type `vgs` you will see that you have a new VolumeGroup named `vg_docker`
# vgs

  VG #PV #LV #SN Attr VSize VFree
  vg_docker 1 1 0 wz--n- 7.45g 4.47g

change the config file `/etc/sysconfig/docker-storage-setup`
and set the variable VG to be the name of the volumegroup we just created.
e.g:
# cat /etc/sysconfig/docker-storage-setup
VG=vg_docker

run the docker storage setup script, which create /etc/sysconfig/docker-storage
# /usr/bin/container-storage-setup

now you can start docker again, and pull a new image

# docker pull alpine
Using default tag: latest
Trying to pull repository registry.fedoraproject.org/alpine ...
Trying to pull repository registry.access.redhat.com/alpine ...
Trying to pull repository docker.io/library/alpine ...
sha256:d6bfc3baf615dc9618209a8d607ba2a8103d9c8a405b3bd8741d88b4bef36478: Pulling from docker.io/library/alpine
b56ae66c2937: Pull complete
Digest: sha256:d6bfc3baf615dc9618209a8d607ba2a8103d9c8a405b3bd8741d88b4bef36478
Status: Downloaded newer image for docker.io/alpine:latest

run the container
# docker run -it --rm --name alpine alpine /bin/sh

and now watch the journald logs, while enabling the disk monitoring

[fedora (fedora-redhat-bugs-1)]

Thanks, for this guide and i can reproduce it now.

Nov 21 16:30:54 mother.mother.loc org.mate.panel.applet.MultiLoadAppletFactory[1514]: glibtop(c=1907): [WARNING] statvfs '/var/lib/docker/devicemapper/mnt/2799eb279404a7a5f3496b6f5b0ce2bc46b88d834663b1' failed: Keine Berechtigung
Nov 21 16:30:55 mother.mother.loc org.mate.panel.applet.MultiLoadAppletFactory[1514]: glibtop(c=1907): [WARNING] statvfs '/var/lib/docker/devicemapper/mnt/2799eb279404a7a5f3496b6f5b0ce2bc46b88d834663b1' failed: Permission denied

Ok, i will post this upstream report

[bcotton (bcotton-redhat-bugs)]

This message is a reminder that Fedora 27 is nearing its end of life.
On 2018-Nov-30 Fedora will stop maintaining and issuing updates for
Fedora 27. It is Fedora's policy to close all bug reports from releases
that are no longer maintained. At that time this bug will be closed as
EOL if it remains open with a Fedora 'version' of '27'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 27 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

[fedora (fedora-redhat-bugs-1)]

Scratch build for f29 for testing a upstream fix https://koji.fedoraproject.org/koji/taskinfo?taskID=32307032

[updates (updates-redhat-bugs)]

mate-applets-1.20.3-2.fc28 has been submitted as an update to Fedora 28. https://bodhi.fedoraproject.org/updates/FEDORA-2019-d11fe2dc8d

[updates (updates-redhat-bugs)]

mate-applets-1.20.3-2.fc29 has been submitted as an update to Fedora 29. https://bodhi.fedoraproject.org/updates/FEDORA-2019-dcb290bedf

[updates (updates-redhat-bugs)]

mate-applets-1.20.3-2.fc29 has been pushed to the Fedora 29 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-dcb290bedf

[updates (updates-redhat-bugs)]

mate-applets-1.20.3-2.fc28 has been pushed to the Fedora 28 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-d11fe2dc8d

[updates (updates-redhat-bugs)]

mate-applets-1.20.3-2.fc28 has been pushed to the Fedora 28 stable repository. If problems still persist, please make note of it in this bug report.

[updates (updates-redhat-bugs)]

mate-applets-1.20.3-2.fc29 has been pushed to the Fedora 29 stable repository. If problems still persist, please make note of it in this bug report.

[Ken Sharp (kennybobs)]

And I've just discovered that my systemd user journal is 112 MB. Filling with this nonsense every two seconds. I'm sure it's doing wonders for my SSD.

I dread to think what would happen if I had multiple users logged in.

[Ken Sharp (kennybobs)]

This should be fixed in version 1.24.0 (Focal).

https://github.com/mate-desktop/mate-applets/commit/736ba510c9d5c55ca5a3a59693ce25fba010ad03

[Ken Sharp (kennybobs)]

Downloaded and installed mate-applets{,-common}-1.24 and forced a reload of the applet. The log file has stopped filling with these two lines.

The lines are still printed when using System Monitor (1.20) but I can live with that as it's not repeated endlessly.

Fixed in Focal+.