Side note tried to install Director getting this error when creating schema in GUI and choosing the icingaweb_db DB:
Migration 0 failed (SQLSTATE[42S01]: Base table or view already exists: 1050 Table 'director_activity_log' already exists) while running CREATE TABLE director_activity_log ( id BIGINT(20) UNSIGNED AUTO_INCREMENT NOT NULL, object_type VARCHAR(64) NOT NULL, object_name VARCHAR(255) NOT NULL, action_name ENUM('create', 'delete', 'modify') NOT NULL, old_properties TEXT DEFAULT NULL COMMENT 'Property hash, JSON', new_properties TEXT DEFAULT NULL COMMENT 'Property hash, JSON', author VARCHAR(64) NOT NULL, change_time TIMESTAMP NOT NULL DEFAULT CURRENT_TIMESTAMP, checksum VARBINARY(20) NOT NULL, parent_checksum VARBINARY(20) DEFAULT NULL, PRIMARY KEY (id), INDEX sort_idx (change_time), INDEX search_idx (object_name), INDEX search_idx2 (object_type(32), object_name(64), change_time), INDEX search_author (author), INDEX checksum (checksum) ) ENGINE=InnoDB DEFAULT CHARSET=utf8 (Migration.php:60)
Edit: I followed the instructions to create a new database and resource in the GUI and I have Director working. So what do I need to configure to get the -x option to work?
First, If you click on the check that is failing, do you see a link to Inspect? I’m not sure it will work unless the check was created through Director.
Some progress. First the client has firewalld running so I had open TCP ports 5665 & 5666. Now I get a slightly different error, on what happens to be my username’s ID See screenshot. The command that shows with Inspect is: '/usr/lib64/nagios/plugins/check_disk' '-c' '10%' '-w' '20%' '-X' 'none' '-X' 'tmpfs' '-X' 'sysfs' '-X' 'proc' '-X' 'configfs' '-X' 'devtmpfs' '-X' 'devfs' '-X' 'mtmfs' '-X' 'tracefs' '-X' 'cgroup' '-X' 'fuse.gvfsd-fuse' '-X' 'fuse.gvfs-fuse-daemon' '-X' 'fdescfs' '-X' 'overlay' '-X' 'nsfs' '-X' 'squashfs' '-m'
Right that’s what I’m asking for a little guidance on. I created a command template see screenshot:
How do I apply this? On a host? On a Service Template?
-x /run/user/0/doc is not in the command being executed (shown by Inspect). You’ll want to modify the disk command/service to specify that field (see Data Fields). The Service is shows as disk-usage. I’m not sure where the Preview you are sharing fits in. You should not need that command, as Director allows you to add fields as needed rather than hard-coding them for each CheckCommand.
Looks like it, my install years ago didn’t import the arguments/fields (which could have been possible and I just didn’t). What if you add your path there and check Inspect again (should show up)? You’ll have to Deploy the changes from Director as well.
No difference. Just making sure you also noticed when I switched to Director the path was no longer to the ‘0’ root user it’s now my user ID that is getting permission denied.
Update: so this does work for the specified path, but once I added my user ID another user ID appears with permission denied. Does the path take a * to include all? Doesn’t seem to work here:
I re-read the options and it looks like -l is what should do the trick. You’ll still want to exclude by filesystem type (I had to include tracefs, but you’d probably not want some others as well).
"-l" = {
set_if = "$disk_local$"
description = " Only check local filesystems"
}
I was testing as root for -l to work. The issue you said earlier was there were other users. What was ls -l /run/user when it worked versus when it does not work? Or run it with sudo and use -l -x ....
Slight difference, the 2nd command includes a NFS share. Note this is on the Icinga2 host server, but the screenshot is from the client that is being monitored. That always gets permission denied even as root user.
It seems you’ll need access to the doc directory in order to exclude it. If it is not accessible by the user executing the check, the arguments aren’t doing the trick. (I’m assuming uid 18796 is not the user you executed the check as?)
