check_qnap Parameters

Have you done something on your NEMS server to make it more usable for yourself? Want to share your code? I'd love for you to share and may include your ideas in future releases of NEMS.
Post Reply
ChrisD
Junior Member
Posts: 6
Joined: Wed Sep 16, 2020 1:25 pm

check_qnap Parameters

Post by ChrisD »

If your setting up the check_qnap service, here are some parameters that you can enter.

cpuload: check´s the system CPU load in perent
cputemp: check´s the sytem CPU Temperature
systemp: check´s the system Temperature
hdtemp: check´s the Harddive Temperature
diskused: check´s the diskusage on perent
mem: check´s the mem usage in perent
volstatus: check´s the Volume status
fan: check´s the Fan Speed
hdstatus: check´s the Harddive status
cachediskstatus: check´s the Cachedisk status
lunstatus: check´s the LUN status
raidstatus: check´s the Raid status
powerstatus: check´s the Power status
sysinfo: provides the QNAP infos

I have only used the diskused parameter and it works fine.
User avatar
Robbie Ferguson
Posting Freak
Posts: 830
Joined: Wed Mar 07, 2012 3:23 pm
Location: Ontario, Canada
Contact:

[1.6] Re: check_qnap Parameters

Post by Robbie Ferguson »

Thanks ChrisD.

Let's get this added to the docs. I've put it here: https://docs.nemslinux.com/en/latest/ch ... _qnap.html

Cheers!

Robbie // The Bald Nerd
Maxinva
Junior Member
Posts: 1
Joined: Wed Dec 16, 2020 7:09 pm

Re: check_qnap Parameters

Post by Maxinva »

I'm trying to configure this and I'm having the following problems.

1) I configured the check_qnap service for the QNAP server and set the arguments the following way.
ARG1: public
ARG2: diskused
ARG3: 80
ARG4: 95
I believe this references the last four parameters in the command.
./check_qnap <hostname> <community> <part> <warning> <critical>

How is the community defined? I can't find a reference to it in any of the host or service configuration screens. I have used public but not sure if that is right because.

2) When I run
/usr/lib/nagios/plugins/check_qnap3.sh 192.168.XX.XX public diskused 80 95

from the command line on the NEMS server receive the following results

CRITICAL: SNMP to 192.168.XX.XX is not available or wrong community string

Does SNMP need to be configured on the QNAP device to make this work?
User avatar
Robbie Ferguson
Posting Freak
Posts: 830
Joined: Wed Mar 07, 2012 3:23 pm
Location: Ontario, Canada
Contact:

Re: check_qnap Parameters

Post by Robbie Ferguson »

I haven't yet tested it, but plan to before NEMS Linux 1.6 releases - but yes, I imagine you have to enable SNMP on the QNAP device. You'll find it somewhere in the config. Please post back if you figure it out and I'll add your note to the docs.

Cheers.

Robbie // The Bald Nerd
mfata
Junior Member
Posts: 1
Joined: Sat Jan 02, 2021 6:19 am

Re: check_qnap Parameters

Post by mfata »

hi,

I'm newbie to NEMS, running 1.5 on RPi, looking around and experimenting.
It seems check_qnap3.sh Parts are a little different than documented, running the script (on v1.5.2):

Check_QNAP3 1.23.3

Warning: Wrong command line arguments.

Usage: ./check_qnap <hostname> <community> <part> <warning> <critical>

Parts are: sysinfo, systemuptime, temp, cpu, cputemp, freeram, powerstatus, fans, diskused, hdstatus, hd#status, hdtemp, hd#temp, volstatus (Raid Volume Status), vol#status

I initially got errors using for example "cpuload" or "mem", instead of "cpu" and "freeram"

Parts in v1.6 are as reported in documentation?

Thank you
M.
Post Reply