Was able to reproduce using the command in /etc/nagios- plugins/config/disk.cfg; I've added this as a test case in the report body.
Adding -X squashfs did nothing, but -X tmpfs worked: # /usr/lib/nagios/plugins/check_disk -w 10 -c 10 -e -X squashfs DISK CRITICAL - free space: /dev 0 MB (100% inode=99%); /dev/lxd 0 MB (100% inode=99%); [...] # /usr/lib/nagios/plugins/check_disk -w 10 -c 10 -e -X tmpfs DISK OK| /=111171MB;119160;119160;0;119170 monitoring-plugins-gu/plugins/check_disk.c includes some filtering code, which skips: * Remote file systems (me_remote) * Pseudo file systems (me_dummy) * Excluded filesystems (fs_exclude_list) * Excluded filesystem types (dp_exclude_list) Looks like by default the fs_exclude_list has only one fs type added to it: np_add_name(&fs_exclude_list, "iso9660"); Maybe a possible patch might be to add tmpfs there too (see attached; untested)? ** Patch added: "check_disk_no_tmpfs.patch" https://bugs.launchpad.net/nagios-charm/+bug/1827159/+attachment/5273538/+files/check_disk_no_tmpfs.patch ** Tags added: server-next -- You received this bug notification because you are a member of Nagios Charm developers, which is subscribed to Nagios Charm. https://bugs.launchpad.net/bugs/1827159 Title: check_all_disks includes squashfs /snap/* which are 100% Status in Nagios Charm: Fix Released Status in monitoring-plugins package in Ubuntu: Triaged Bug description: When using nagios to monitor the Nagios host itself, if the host is not a container, the template for checking the disk space on the Nagios host does not exclude any snap filesystems. This means we get a Critical report if any snap is installed. This can be changed by adding to the check_all_disks command a '-X squashfs', but that command is defined in the nagios plugins package. [Test Case] $ lxc create ubuntu-daily:19.10/amd64 lp1827159 $ lxc exec lp1827159 bash # apt-get -y update # apt-get install monitoring-plugins # /usr/lib/nagios/plugins/check_disk -w 10 -c 10 DISK CRITICAL - free space: / 1903 MB (1% inode=78%); /dev 0 MB (100% inode=99%); /dev/full 16018 MB (100% inode=99%); /dev/null 16018 MB (100% inode=99%); /dev/random 16018 MB (100% inode=99%); /dev/tty 16018 MB (100% inode=99%); /dev/urandom 16018 MB (100% inode=99%); /dev/zero 16018 MB (100% inode=99%); /dev/fuse 16018 MB (100% inode=99%); /dev/net/tun 16018 MB (100% inode=99%); /dev/lxd 0 MB (100% inode=99%); /dev/.lxd-mounts 0 MB (100% inode=99%); /dev/shm 16041 MB (100% inode=99%); /run 3208 MB (99% inode=99%); /run/lock 5 MB (100% inode=99%); /sys/fs/cgroup 16041 MB (100% inode=99%); /snap 1903 MB (1% inode=78%); /run/snapd/ns 3208 MB (99% inode=99%);| /=111171MB;119160;119160;0;119170 /dev=0MB;-10;-10;0;0 /dev/full=0MB;16008;16008;0;16018 /dev/null=0MB;16008;16008;0;16018 /dev/random=0MB;16008;16008;0;16018 /dev/tty=0MB;16008;16008;0;16018 /dev/urandom=0MB;16008;16008;0;16018 /dev/zero=0MB;16008;16008;0;16018 /dev/fuse=0MB;16008;16008;0;16018 /dev/net/tun=0MB;16008;16008;0;16018 /dev/lxd=0MB;-10;-10;0;0 /dev/.lxd-mounts=0MB;-10;-10;0;0 /dev/shm=0MB;16031;16031;0;16041 /run=0MB;3198;3198;0;3208 /run/lock=0MB;-5;-5;0;5 /sys/fs/cgroup=0MB;16031;16031;0;16041 /snap=111171MB;119160;119160;0;119170 /run/snapd/ns=0MB;3198;3198;0;3208 To manage notifications about this bug go to: https://bugs.launchpad.net/nagios-charm/+bug/1827159/+subscriptions -- Mailing list: https://launchpad.net/~nagios-charmers Post to : [email protected] Unsubscribe : https://launchpad.net/~nagios-charmers More help : https://help.launchpad.net/ListHelp
