Performance graph is not working with check_nwc_health

[phyo]

Code: Select all

./check_nwc_health --hostname 10.110.50.17 --protocol 2c --community nagios --mode cpu-load --warning 70% --critical 80% -vvv
I attached the file the output of this command.

Code: Select all

[root@nagios01 libexec]# ./check_nwc_health --version
check_nwc_health $Revision: 2.6.5 $ [http://labs.consol.de/nagios/check_nwc_health]

[Box293]

This error stands out:

Code: Select all

UNKNOWN - cannot write status dir /var/tmp/check_nwc_health! check your filesystem (permissions/usage/integrity) and disk devices, cannot write status file /var/tmp/check_nwc_health/10.110.50.17_cpu-load_protect_01_usage0eb0a38cfbcf77985e4d281b78cc3336! check your filesystem (permissions/usage/integrity) and disk devices, cannot write status dir /var/tmp/check_nwc_health! check your filesystem (permissions/usage/integrity) and disk devices, cannot write status file /var/tmp/check_nwc_health/10.110.50.17_cpu-load_protect_11_usage0eb0a38cfbcf77985e4d281b78cc3336! check your filesystem (permissions/usage/integrity) and disk devices, cannot write status dir /var/tmp/check_nwc_health! check your filesystem (permissions/usage/integrity) and disk devices, cannot write status file /var/tmp/check_nwc_health/10.110.50.17_cpu-load_protect_25_usage0eb0a38cfbcf77985e4d281b78cc3336! check your filesystem (permissions/usage/integrity) and disk devices, cannot write status dir /var/tmp/check_nwc_health! check your filesystem (permissions/usage/integrity) and disk devices, cannot write status file /var/tmp/check_nwc_health/10.110.50.17_cpu-load_protect_36_usage0eb0a38cfbcf77985e4d281b78cc3336! check your filesystem (permissions/usage/integrity) and disk devices, cannot write status dir /var/tmp/check_nwc_health! check your filesystem (permissions/usage/integrity) and disk devices, cannot write status file /var/tmp/check_nwc_health/10.110.50.17_cpu-load_protect_47_usage0eb0a38cfbcf77985e4d281b78cc3336! check your filesystem (permissions/usage/integrity) and disk devices, cannot write status dir /var/tmp/check_nwc_health! check your filesystem (permissions/usage/integrity) and disk devices, cannot write status file /var/tmp/check_nwc_health/10.110.50.17_cpu-load_protect_58_usage0eb0a38cfbcf77985e4d281b78cc3336! check your filesystem (permissions/usage/integrity) and disk devices, cannot write status dir /var/tmp/check_nwc_health! check your filesystem (permissions/usage/integrity) and disk devices, cannot write status file /var/tmp/check_nwc_health/10.110.50.17_cpu-load_protect_69_usage0eb0a38cfbcf77985e4d281b78cc3336! check your filesystem (permissions/usage/integrity) and disk devices, cannot write status dir /var/tmp/check_nwc_health! check your filesystem (permissions/usage/integrity) and disk devices, cannot write status file /var/tmp/check_nwc_health/10.110.50.17_cpu-load_protect_710_usage0eb0a38cfbcf77985e4d281b78cc3336! check your filesystem (permissions/usage/integrity) and disk devices, cannot write status dir /var/tmp/check_nwc_health! check your filesystem (permissions/usage/integrity) and disk devices, cannot write status file /var/tmp/check_nwc_health/10.110.50.17_cpu-load_protect_811_usage0eb0a38cfbcf77985e4d281b78cc3336! check your filesystem (permissions/usage/integrity) and disk devices, cannot write status dir /var/tmp/check_nwc_health! check your filesystem (permissions/usage/integrity) and disk devices, cannot write status file /var/tmp/check_nwc_health/10.110.50.17_cpu-load_protect_912_usage0eb0a38cfbcf77985e4d281b78cc3336! check your filesystem (permissions/usage/integrity) and disk devices, cpu Chassis usage (5 min avg.) is 0.00%, cpu Chassis usage (5 min avg.) is 0.00%, cpu Processor 0/0 usage (5 min avg.) is 0.00%, cpu Processor 0/1 usage (5 min avg.) is 0.00%, cpu Processor 0/2 usage (5 min avg.) is 0.00%, cpu Processor 0/3 usage (5 min avg.) is 0.00%, cpu Processor 0/4 usage (5 min avg.) is 0.00%, cpu Processor 0/5 usage (5 min avg.) is 0.00%, cpu Processor 0/6 usage (5 min avg.) is 0.00%, cpu Processor 0/7 usage (5 min avg.) is 0.00%

What is the output of these commands:

Code: Select all

ls -ald /var/tmp/check_nwc_health/
ls -al /var/tmp/check_nwc_health/

You may need to change the ownership of the directory and files:

Code: Select all

chown -R nagios:nagcmd /var/tmp/check_nwc_health

Does this help?

[phyo]

Code: Select all

[root@nagios01 ~]# ls -ald /var/tmp/check_nwc_health/
drwxr-xr-x 2 nagios users 4096 Jan 28 11:38 /var/tmp/check_nwc_health/

Code: Select all

[root@nagios01 ~]# ls -al /var/tmp/check_nwc_health/
total 80
drwxr-xr-x  2 nagios users 4096 Jan 28 11:38 .
drwxrwxrwt. 3 root   root  4096 May 27 01:44 ..
-rw-r--r--  1 nagios users   72 Jun 10 11:41 10.110.40.26_cpu-load_protect_0168504586_usage0eb0a38cfbcf77985e4d281b78cc3336
-rw-r--r--  1 nagios users   72 Jun 10 11:41 10.110.40.26_cpu-load_protect_1159516845_usage0eb0a38cfbcf77985e4d281b78cc3336
-rw-r--r--  1 nagios users   72 Jun 10 11:41 10.110.40.26_cpu-load_protect_2176960415_usage0eb0a38cfbcf77985e4d281b78cc3336
-rw-r--r--  1 nagios users   72 Jun 10 11:41 10.110.40.26_cpu-load_protect_3200141362_usage0eb0a38cfbcf77985e4d281b78cc3336
-rw-r--r--  1 nagios users   72 Jun 10 11:41 10.110.40.26_cpu-load_protect_416203662_usage0eb0a38cfbcf77985e4d281b78cc3336
-rw-r--r--  1 nagios users   72 Jun 10 11:41 10.110.40.26_cpu-load_protect_559453759_usage0eb0a38cfbcf77985e4d281b78cc3336
-rw-r--r--  1 nagios users   72 Jun 10 11:41 10.110.40.26_cpu-load_protect_638557239_usage0eb0a38cfbcf77985e4d281b78cc3336
-rw-r--r--  1 nagios users   72 Jun 10 11:41 10.110.40.26_cpu-load_protect_756744940_usage0eb0a38cfbcf77985e4d281b78cc3336
-rw-r--r--  1 nagios users   72 Jun 10 11:38 10.110.50.17_cpu-load_protect_01_usage0eb0a38cfbcf77985e4d281b78cc3336
-rw-r--r--  1 nagios users   72 Jun 10 11:38 10.110.50.17_cpu-load_protect_11_usage0eb0a38cfbcf77985e4d281b78cc3336
-rw-r--r--  1 nagios users   72 Jun 10 11:38 10.110.50.17_cpu-load_protect_25_usage0eb0a38cfbcf77985e4d281b78cc3336
-rw-r--r--  1 nagios users   72 Jun 10 11:38 10.110.50.17_cpu-load_protect_36_usage0eb0a38cfbcf77985e4d281b78cc3336
-rw-r--r--  1 nagios users   72 Jun 10 11:38 10.110.50.17_cpu-load_protect_47_usage0eb0a38cfbcf77985e4d281b78cc3336
-rw-r--r--  1 nagios users   72 Jun 10 11:38 10.110.50.17_cpu-load_protect_58_usage0eb0a38cfbcf77985e4d281b78cc3336
-rw-r--r--  1 nagios users   72 Jun 10 11:38 10.110.50.17_cpu-load_protect_69_usage0eb0a38cfbcf77985e4d281b78cc3336
-rw-r--r--  1 nagios users   72 Jun 10 11:38 10.110.50.17_cpu-load_protect_710_usage0eb0a38cfbcf77985e4d281b78cc3336
-rw-r--r--  1 nagios users   72 Jun 10 11:38 10.110.50.17_cpu-load_protect_811_usage0eb0a38cfbcf77985e4d281b78cc3336
-rw-r--r--  1 nagios users   72 Jun 10 11:38 10.110.50.17_cpu-load_protect_912_usage0eb0a38cfbcf77985e4d281b78cc3336
[root@nagios01 ~]#

I have changed the ownership as you suggested.

Code: Select all

chown -R nagios:nagcmd /var/tmp/check_nwc_health

I will monitor the status and will feedback when I have new update.

[lmiltchev]

I will monitor the status and will feedback when I have new update.

Sure. Let us know if you are still having issues.

[phyo]

These solution still not ok. But my collage write the script and solve this issue. Means we don't use the check_nwc_health plugin.

Now we are using our own plugin, then we can see the performance graph.

Thanks.

[lmiltchev]

I am glad you have found your own solution! I will be locking this topic how. If you have any more questions, please start a new thread.