Check Command Output not complete

Icinga Web Modules Icinga Director
1

Good morning everybody,
I have a problem with modifiying the check disk command. I’m trying to exclude a specified partition (with the argument -x or because this didn’t worked I also tried it with -i) and this seems to work. But when I do this, Icinga 2 only gets the information of the first 4 partitions found and doesn’t shows any further partition.
If I execute the check command shown by the “Inspect” option in Icingaweb 2 on my Icinga 2 node with all arguments and as Icinga-User I get the whole output.

Used Versions are:
Icinga2: r2.10.5-1
IcingaWeb2: 2.6.3
Director: 1.6.2

Example:

Output IcingaWeb2:

grafik
grafik.png1045×72 2.65 KB

The executed Command is (shown at “Inspect”) is:
‘/usr/lib/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’ ‘-R’ ‘/’ ‘-i’ ‘^/boot’

Using this command local on the host:

‘/usr/lib/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’ ‘-R’ ‘/’ ‘-i’ ‘^/boot’
DISK OK - free space: / 6606 MB (66% inode=98%); /opt 4380 MB (85% inode=99%); /home 5049 MB (99% inode=99%); /tmp 2002 MB (98% inode=99%); /var/log 10171 MB (99% inode=99%); /test 32673 MB (79% inode=99%);| /=3322MB;7942;8935;0;9928 /opt=728MB;4086;4597;0;5108 /home=49MB;4079;4589;0;5099 /tmp=34MB;1628;1832;0;2036 /var/log=57MB;8182;9205;0;10228 /test=8265MB;32750;36844;0;40938

Has anybody an idea, where I made a mistake?

2

Hi,

what’s the check source of this service? Whenever the output looks different to what expected, I’d verify whether the check really ran on the agent and not on the master.

Also, the service configuration form inside the Director would help (screenshot).

Cheers,
Michael

1 Like
3

Hi Michael,
thank you so much! It was the check source :flushed: Sorry for the stupid question…

4

No worries, that’s a common error everyone has seen at least once. Please do a me a favor and mark the reply as solution (and future solutions as well).

1 Like