I am having trouble reproducing this issue using a Bionic Container juju add-model nagios-test juju deploy cs:nagios-37 juju ssh nagios/0 $ snap install hello-world $ mount | grep tracefs
I don't see this alert firing. Did this occur for you on metal or container? I almost wonder if your nagios charm needs to be updated. I see that cs:nagios-33 only excluded squashfs on metal -- but cs:nagios-34 supports exclusion of more filesystem types as you mentioned above. -- 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/1886153 Title: check_all_disks_no_squashfs includes tracefs (/sys/kernel/debug/tracing) Status in Nagios Charm: Confirmed Bug description: Nagios reports a critical failure for "Disk Usage" in the nagios unit itself (localhost) Description CRITICAL: 'Disk Space' on 'nagios/0' Service output DISK CRITICAL - /sys/kernel/debug/tracing is not accessible: Permission denied The check is trying to validate the virtual filesystem, but the nagios user doesn't have permissions: # ls -l /sys/kernel/debug |grep tracing drwx------ 7 root root 0 May 21 2019 tracing Related to LP#1516451 / LP#1827159 which fixes it in upstream (but only for focal I think) and handles it in the charm but just for squashfs (snaps). I think nagios can skip this filesystem. The fix would be similar to the squashfs/snap fix https://git.launchpad.net/charm- nagios/commit/?id=6f5e177f0f718478cbaaab85ab3c32f4ee55bf16, by appending: -X tracefs To manage notifications about this bug go to: https://bugs.launchpad.net/charm-nagios/+bug/1886153/+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
