Glad to hear you were able to find a solution! Can I lock this thread and mark the issue as resolved?

I notice the command definition for DEV_check_local_disk is asking for 3 args in a non-specific way command_line $USER1$/check_nrpe -H $HOSTADDRESS$ -t 30 -c check_disk -a $ARG1$ $ARG2$ $ARG3$ You could try explicitly declaring the arguments you are sending to the remote machine's check_disk script ...

It could be an iptables rule that is preventing traffic. Try the following command where x.x.x.x is the IP address of the machine you are accessing Nagios from (not the Nagios server itself): iptables -I INPUT 1 -s x.x.x.x -p tcp -m tcp --dport 80 -j ACCEPT That command should put traffic from ip x....

You could try this command definition (note the /* path at the end): command[check_disks]=/usr/lib/nagios/plugins/check_disk -w 20% -c 10% -C -W 20% -K 10% -p /* Here's my test file system: [root@localhost boot]# df -h Filesystem Size Used Avail Use% Mounted on /dev/sda3 18G 4.1G 14G 23% / devtmpfs ...

The JSON Query Generator is super handy for this sort of thing (where x.x.x.x is your Core install): http://x.x.x.x/nagios/jsonquery.html A brief intro to the JSON Query Generator: https://labs.nagios.com/2014/06/19/exploring-the-new-json-cgis-in-nagios-core-4-0-7-part-1/ If you wanted to check if h...

Let us know what you results are!

You could try leaving the critical threshold undefined like so: define service{ use dev_default-service service_description DEV FS: / check_command DEV_check_local_disk!10%!!/ contact_groups TEST-CG servicegroups DEV_FS_Root-SG } This works for me in core for check_local_disk . Your results may vary...

@t3dus,

I'm glad you were able to find a solution! As rhassing pointed out, typically a symlink would be used in favor of moving the file. Is it all right if we lock this topic and mark it as resolved?