Synology status

RAID status health not working, disk 11 is faulty. Synology model: "DS3615xs" Synology s/n: "foobar" DSM Version: "DSM 6.2-25556" DSM update: Unavailable System Status: Normal Temperature: 40 (Normal) Power Status: Normal System Fan Status: Normal CPU Fan Status: Normal Number of disks: 12 "Drive 1" (model: "WD4002FYYZ-01B7CB0") status:Normal temperature:34 "Drive 2" (model: "WD4002FYYZ-01B7CB0") status:Normal temperature:34 "Drive 3" (model: "WD4002FYYZ-01B7CB0") status:Normal temperature:34 "Drive 4" (model: "WD4002FYYZ-01B7CB0") status:Normal temperature:35 "Drive 5" (model: "WD4002FYYZ-01B7CB0") status:Normal temperature:34 "Drive 6" (model: "WD4002FYYZ-01B7CB0") status:Normal temperature:35 "Drive 7" (model: "WD4002FYYZ-01B7CB0") status:Normal temperature:33 "Drive 8" (model: "WD4002FYYZ-01B7CB0") status:Normal temperature:35 "Drive 9" (model: "WD4002FYYZ-01B7CB0") status:Normal temperature:34 "Drive 10" (model: "WD4002FYYZ-01B7CB0") status:Normal temperature:35 "Drive 11" (model: "WD4002FYYZ-01B7CB0") status:Normal temperature:35 "Drive 12" (model: "WD4002FYYZ-01B7CB0") status:Normal temperature:34 Number of RAID volume: 2 "Volume 1" status:Normal 8% used "Storage Pool 1" status:Normal OK - Synology "DS3615xs" (s/n: "foobar", "DSM 6.2-25556") is in good health I tried every edit suggested in the comment section.

If your synology has docker or some similar active the script will fail because it will find multiple /volume1 instances. To prevent this change the line #317 to: (in which you excluded /volume1/ (the last slash and thus only grep /volume1) storageID[$i]=$(echo "$syno_diskspace" | grep "= "?/${storageName[$i]}"?" | grep -v "= "?/volume1/"?" | cut -d "=" -f1 | rev | cut -d "." -f1 | rev)

This worked for me on DSM 5.2 On DSM 6 I get this error Any ideas ? peter@rcapp04:/srv/docker/volumes/nagios/opt/Custom-Nagios-Plugins$ docker exec -it nagios4 bash root@rcapp04-nagios:/# cd /opt/Custom-Nagios-Plugins/ root@rcapp04-nagios:/opt/Custom-Nagios-Plugins# ./check_snmp_synology -2 public -h rcdata02 -t raid ./check_snmp_synology: line 368: 54 55 58 .1.3.6.1.2.1.25.2.1.4 .1.3.6.1.2.1.25.2.1.4 .1.3.6.1.2.1.25.2.1.4 /volume1/@docker /volume1/@docker/btrfs /volume1/@docker/containers/41582c69eb60f17066850470fdfb150a20a445882d30a6083c4fbb59a9b4293c/mounts/shm 8192 Bytes 8192 Bytes 4096 Bytes 2108048671 2108048671 16384 367403977 367403977 367403977 0 * 100 / 54 55 58 .1.3.6.1.2.1.25.2.1.4 .1.3.6.1.2.1.25.2.1.4 .1.3.6.1.2.1.25.2.1.4 /volume1/@docker /volume1/@docker/btrfs /volume1/@docker/containers/41582c69eb60f17066850470fdfb150a20a445882d30a6083c4fbb59a9b4293c/mounts/shm 8192 Bytes 8192 Bytes 4096 Bytes 2108048671 2108048671 2108048671 16384 367403977 367403977 0: syntax error in expression (error token is "55 58 .1.3.6.1.2.1.25.2.1.4 .1.3.6.1.2.1.25.2.1.4 .1.3.6.1.2.1.25.2.1.4 /volume1/@docker /volume1/@docker/btrfs /volume1/@docker/containers/41582c69eb60f17066850470fdfb150a20a445882d30a6083c4fbb59a9b4293c/mounts/shm 8192 Bytes 8192 Bytes 4096 Bytes 2108048671 2108048671 16384 367403977 367403977 367403977 0 * 100 / 54 55 58 .1.3.6.1.2.1.25.2.1.4 .1.3.6.1.2.1.25.2.1.4 .1.3.6.1.2.1.25.2.1.4 /volume1/@docker /volume1/@docker/btrfs /volume1/@docker/containers/41582c69eb60f17066850470fdfb150a20a445882d30a6083c4fbb59a9b4293c/mounts/shm 8192 Bytes 8192 Bytes 4096 Bytes 2108048671 2108048671 2108048671 16384 367403977 367403977 0")

To fix this error I think there should be a space after /${storageName[$i]} in line 317 to prevent the grep for /volume1 also matching /volume10. storageID[$i]=$(echo "$syno_diskspace" | grep "= "?/${storageName[$i]}"?" | cut -d "=" -f1 | rev | cut -d "." -f1 | rev)

This plugin works well on DSM 6.2. Below are the commands: ./check_snmp_synology -2 public -h 172.16.1.62 -t disk Number of disks: 4 "Drive 1" (model: "WD2RX-68EUZN0 ") status:Normal temperature:28 "Drive 2" (model: "WD2RX-68EUZN0 ") status:Normal temperature:29 "Drive 3" (model: "WD2RX-68EUZN0 ") status:Normal temperature:29 "Drive 4" (model: "WD2RX-68EUZN0 ") status:Normal temperature:29 ################################ ./check_snmp_synology -2 public -h 172.16.1.62 -t temperature Temperature: 40 (Normal) OK - Synology is in good health ################################ ./check_snmp_synology -2 public -h 172.16.1.62 -t system Synology model: "DS918+" Synology s/n: "" System Status: Normal OK - Synology is in good health ################################

Added additional UPS OIDs/stats, added output for performance data for system temperature and UPS Link: https://github.com/cottington/nagios-Synology

Update of the improvement of Corben2 correction and optimisation of snmpwalk. Link : https://github.com/Dermone/nagios-Synology Correct this error : /check_snmp_synology: line 227: [: : integer expression expected /check_snmp_synology: line 227: [: : integer expression expected /check_snmp_synology: line 227: [: : integer expression expected

Script works well. I've made some changes to it though. I changed it to correctly get the volume usage in DSM 6.2, and I've changed it to split up the check types so that different checks can be different services in Nagios. My changed version can be found here: https://github.com/corben2/check_snmp_synology

As per PiotrM89's suggestion back in 2017, using snmpbulkwalk fixed my timeout issues. Try changing the following on Line 25 SNMPWALK=$(which snmpwalk) to SNMPWALK=$(which snmpbulkwalk)

I would give this an excellent rating, but this is the only plugin out of 56 hosts that gives me any grief. I get the random SNMP timeouts sporadically throughout the day. I have investigates a rolling tcp dump to see if its on the network end, its not (as 30+ other hosts are in the same data center and do not have this issue, plugged into the same switch, with the same load balancing issues). I even disabled the dual NIC on the Synology RS2414RP+ (DSM 6.0.3-8754 Update 8) to see if somehow the load balancing or something goofy was hanging it up. Not it either, I see someone below me has the identical issue. I have tried disabling different aspects of this plugin as well to see if these stop, they don't. These spam repeatedly: (Service check timed out after 180.01 seconds) (Service check timed out after 180.01 seconds) (Service check timed out after 180.01 seconds) After expanding to 180s I figured this would resolve the issue, it didn't either. I love the visibility it gives, I just feel like its getting hung up on something.

--- /usr/lib64/nagios/plugins/check_snmp_synology~ 2018-12-07 19:11:35.231831343 +0000 +++ /usr/lib64/nagios/plugins/check_snmp_synology 2019-01-30 21:23:40.471135880 +0000 @@ -307,3 +307,8 @@ - RAIDName[$i]=$(echo "$syno" | grep $OID_RAIDName.$(($i-1)) | cut -d "=" -f2) - RAIDStatus[$i]=$(echo "$syno" | grep $OID_RAIDStatus.$(($i-1)) | cut -d "=" -f2 | sed 's/^[ t]*//;s/[ t]*$//') - + # modified by William Yang / DataPulse + # the regexes below were not anchored on the tail end, which created situations where + # a record could contain multiple lines. Caused a lot of heartache. Adding the + # anchor [^.0-9] ensures no subsquent numeral or OID component is matched, causing + # the code to be much more resilient. We added 10 volumes one maintenance window, + # and we had to track this down.... + RAIDName[$i]=$(echo "$syno" | grep "$OID_RAIDName.$(($i-1))[^.0-9]" | cut -d "=" -f2) + RAIDStatus[$i]=$(echo "$syno" | grep "$OID_RAIDStatus.$(($i-1))[^.0-9]" | cut -d "=" -f2 | sed 's/^[ t]*//;s/[ t]*$//') @@ -317,0 +323,2 @@

This plugin used to work very well for many different Syno models. But since the update to DSM 6.2-23824, the requests via this plugin seem to take forever, and we get timeouts for all NAS systems. Can this please be analyzed and the plugin updated?

I am giving this a not perfect score and would change it in a heartbeat if the max number of disks were updated to support 52. I was able to monitor health of the device and disks of a few of my devices, but the majority of our devices have more than 52 disks.

I am using this plugin with success on many Nagios instances. However now I tried it against RS818+ with 6.2-23824, and getting error same as man_al describes: CRITICAL - Problem with SNMP request, check user/password/host Analyzing this problem, SNMPWALK runs up to.1.3.6.1.4.1.6574.5.1.1.8.9 = 2, then times out. Timeout: No Response from which following test evaluates as error and exits with exit code 2.

I am getting an error trying to run this on a NAS with 12 disks. ./check_snmp_synology: line 227: [: : integer expression expected ./check_snmp_synology: line 288: [: : integer expression expected ./check_snmp_synology: line 288: [: : integer expression expected ./check_snmp_synology: line 288: [: : integer expression expected ./check_snmp_synology: line 288: [: : integer expression expected ./check_snmp_synology: line 288: [: : integer expression expected ./check_snmp_synology: line 288: [: : integer expression expected ./check_snmp_synology: line 288: [: : integer expression expected ./check_snmp_synology: line 288: [: : integer expression expected ./check_snmp_synology: line 288: [: : integer expression expected ./check_snmp_synology: line 288: [: : integer expression expected ./check_snmp_synology: line 288: [: : integer expression expected ./check_snmp_synology: line 288: [: : integer expression expected ./check_snmp_synology: line 324: 36 37 38 39 40 51 52 53 .1.3.6.1.2.1.25.2.1.4 .1.3.6.1.2.1.25.2.1.4 .1.3.6.1.2.1.25.2.1.4 .1.3.6.1.2.1.25.2.1.4 .1.3.6.1.2.1.25.2.1.4 .1.3.6.1.2.1.25.2.1.4 .1.3.6.1.2.1.25.2.1.4 .1.3.6.1.2.1.25.2.1.4 /tmp /run /dev/shm /sys/fs/cgroup /run/cgmanager/fs /volume2 /volume1 /volume3 4096 Bytes 4096 Bytes 4096 Bytes 4096 Bytes 4096 Bytes 4096 Bytes 4096 Bytes 4096 Bytes 502328 502328 502328 1 25 1449963710 959068290 959019398 308048 5815 16191 1 0 0 22540 601869912 30464948 * 100 / 36 37 38 39 40 51 52 53 .1.3.6.1.2.1.25.2.1.4 .1.3.6.1.2.1.25.2.1.4 .1.3.6.1.2.1.25.2.1.4 .1.3.6.1.2.1.25.2.1.4 .1.3.6.1.2.1.25.2.1.4 .1.3.6.1.2.1.25.2.1.4 .1.3.6.1.2.1.25.2.1.4 .1.3.6.1.2.1.25.2.1.4 /tmp /run /dev/shm /sys/fs/cgroup /run/cgmanager/fs /volume2 /volume1 /volume3 4096 Bytes 4096 Bytes 4096 Bytes 4096 Bytes 4096 Bytes 4096 Bytes 4096 Bytes 4096 Bytes 596382 502328 502328 502328 1 25 1449963710 959068290 959019398 5815 16191 1 0 0 22540 601869912 30464948: syntax error in expression (error token is "37 38 39 40 51 52 53 .1.3.6.1.2.1.25.2.1.4 .1.3.6.1.2.1.25.2.1.4 .1.3.6.1.2.1.25.2.1.4 .1.3.6.1.2.1.25.2.1.4 .1.3.6.1.2.1.25.2.1.4 .1.3.6.1.2.1.25.2.1.4 .1.3.6.1.2.1.25.2.1.4 .1.3.6.1.2.1.25.2.1.4 /tmp /run /dev/shm /sys/fs/cgroup /run/cgmanager/fs /volume2 /volume1 /volume3 4096 Bytes 4096 Bytes 4096 Bytes 4096 Bytes 4096 Bytes 4096 Bytes 4096 Bytes 4096 Bytes 502328 502328 502328 1 25 1449963710 959068290 959019398 308048 5815 16191 1 0 0 22540 601869912 30464948 * 100 / 36 37 38 39 40 51 52 53 .1.3.6.1.2.1.25.2.1.4 .1.3.6.1.2.1.25.2.1.4 .1.3.6.1.2.1.25.2.1.4 .1.3.6.1.2.1.25.2.1.4 .1.3.6.1.2.1.25.2.1.4 .1.3.6.1.2.1.25.2.1.4 .1.3.6.1.2.1.25.2.1.4 .1.3.6.1.2.1.25.2.1.4 /tmp /run /dev/shm /sys/fs/cgroup /run/cgmanager/fs /volume2 /volume1 /volume3 4096 Bytes 4096 Bytes 4096 Bytes 4096 Bytes 4096 Bytes 4096 Bytes 4096 Bytes 4096 Bytes 596382 502328 502328 502328 1 25 1449963710 959068290 959019398 5815 16191 1 0 0 22540 601869912 30464948")

The plugin works very fine - but since we've been updated to DSM 6.2-23739 on our RS3614xs+ we get the following message: ./check_snmp_synology -2 public -h 192.168.x.x CRITICAL - Problem with SNMP request, check user/password/host SNMP Community is right and snmpwalk works. Any idea?

I'd be interested in your code changes fledorze, removing/ignoring elements may help with the some of the timeout issues.

I added more generic options -r and -e to include/exclude elements, in replacement of -i option that allows to ignore DSM updates only. Tell me if you want the code.

Could someone please write a step by step guide to get this installed on a nagios core ubuntu server please thanks.

Quite a nice plugin to use and works fine. I modified it by adding perfdata for system temperature, volume usage, cpu usage and mem usage aswell additional arguments for cpu und mem usage thresholds.

It works perfectly!! Thank you a lot!

I suggest to change snmpwalk to snmpbulkwalk in script. An execution of the script will be a much faster.

Not sure if this is still any use to anyone but I fixed the missing volume disk space bug by removing a $ symbol from line 317. Original Line: storageID[$i]=$(echo "$syno_diskspace" | grep "= "?/${storageName[$i]}$"?" | cut -d "=" -f1 | rev | cut -d "." -f1 | rev) Replaced with: storageID[$i]=$(echo "$syno_diskspace" | grep "= "?/${storageName[$i]}"?" | cut -d "=" -f1 | rev | cut -d "." -f1 | rev) I am not sure if this will break anything else but it seems to be doing what I need it to now.

For anybody else who has a problem with the correct volume usage reporting, open the script and replace the line 317: storageID[$i]=$(echo "$syno_diskspace" | grep "= "?/${storageName[$i]}$"?" | cut -d "=" -f1 | rev | cut -d "." -f1 | rev) with this: storageID[$i]=$(echo "$syno_diskspace" | grep "= "/${storageName[$i]}"" | cut -d "=" -f1 | rev | cut -d "." -f1 | rev) and you should now get the correct volume usage (in percent) and the correct return state (depending on your -w and -c parameters).

Volume free space is not working. Status is always Normal. We are using this call: check_snmp_synology -u my_user -p my_pass -h my_host -v -i Also I tried call like this: check_snmp_synology -u my_user -p my_pass -h my_host -w 85 -c 90 -v -i verbose output: Synology model: "RS3617xs+" DSM Version: "DSM 6.1-15152" DSM update: Available System Status: Normal Temperature: 32 (Normal) Power Status: Normal System Fan Status: Normal CPU Fan Status: Normal Number of disks: 12 "Disk 1" (model: "WD4001FFSX-68JNUN0 ") status:Normal temperature:29 "Disk 2" (model: "WD4001FFSX-68JNUN0 ") status:Normal temperature:27 "Disk 3" (model: "WD4001FFSX-68JNUN0 ") status:Normal temperature:27 "Disk 4" (model: "WD4001FFSX-68JNUN0 ") status:Normal temperature:27 "Disk 5" (model: "WD4001FFSX-68JNUN0 ") status:Normal temperature:30 "Disk 6" (model: "WD4001FFSX-68JNUN0 ") status:Normal temperature:28 "Disk 7" (model: "WD4001FFSX-68JNUN0 ") status:Normal temperature:27 "Disk 8" (model: "WD4001FFSX-68JNUN0 ") status:Normal temperature:28 "Disk 9" (model: "WD4001FFSX-68JNUN0 ") status:Normal temperature:31 "Disk 10" (model: "WD4001FFSX-68JNUN0 ") status:Normal temperature:28 "Disk 11" (model: "WD4001FFSX-68JNUN0 ") status:Normal temperature:28 "Disk 12" (model: "WD4001FFSX-68JNUN0 ") status:Normal temperature:28 Number of RAID volume: 1 "Volume 1" status:Normal OK - Synology "RS3617xs+ is in good health NAS storage is on 92%. Also I check on 4 NAS different models: Synology model: "RS3617xs+" Synology model: "RS2414+" Synology model: "RS2212+" Synology model: "RS3412xs" With 2 different DSM: DSM Version: "DSM 6.1-15152" DSM Version: "DSM 6.1-15047" Did some one find solution for this?

We've been using this for a while, but we've just noticed that the volume space doesn't seem to raise warnings (just status:Normal) : Here's the verbose output. Synology model: "RS3614xs+" Synology s/n: "1620M9N181700" DSM Version: "DSM 6.1-15152" DSM update: Available System Status: Normal Temperature: 42 (Normal) Power Status: Normal System Fan Status: Normal CPU Fan Status: Normal Number of disks: 12 "Disk 1" (model: "ST6000VN0001-1SF17Z ") status:Initialized temperature:41 "Disk 2" (model: "ST6000VN0001-1SF17Z ") status:Normal temperature:42 "Disk 3" (model: "ST6000VN0001-1SF17Z ") status:Normal temperature:42 "Disk 4" (model: "ST6000VN0001-1SF17Z ") status:Normal temperature:40 "Disk 5" (model: "ST6000VN0001-1SF17Z ") status:Normal temperature:42 "Disk 6" (model: "ST6000VN0001-1SF17Z ") status:Normal temperature:42 "Disk 7" (model: "ST6000VN0001-1SF17Z ") status:Normal temperature:42 "Disk 8" (model: "ST6000VN0001-1SF17Z ") status:Normal temperature:41 "Disk 9" (model: "ST6000VN0001-1SF17Z ") status:Normal temperature:41 "Disk 10" (model: "ST6000VN0001-1SF17Z ") status:Normal temperature:42 "Disk 11" (model: "ST6000VN0001-1SF17Z ") status:Normal temperature:42 "Disk 12" (model: "ST6000VN0001-1SF17Z ") status:Normal temperature:40 Number of RAID volume: 2 "Volume 1" status:Normal "Disk Group 1" status:Normal WARNING - Synology "RS3614xs+" (s/n: "1620M9N181700", "DSM 6.1-15152"), DSM update available According to the web interface of the device, volume on is 93% full. Any ideas?

First of all, fantastic plugin. Very extensive. However I found an issue with it. When polling a device running DSM 6.1, it returns integer expression expected. Breaking the script down, the syno variable isn't populated. Basically, snmpget times out. This appears to be due to amount of OIDs I'm querying. There is 12 disks in the system so there is around 50+ oids. I kept rerunning snmpget, removing a oid until it returned data and it was around 42. Using Ubuntu 16.04, snmpget 5.7.2

Problems are fixed fast.

Hello! I have some problems with this script, it seems something it's wrong, shows me the advise: "(No output on stdout) stderr: /usr/local/nagios/libexec/check_snmp_synology: line 323: 53" What's wrong? Thanks!!!

When i use the script with your command and snmpv3 and my DS411 with DSM 6.0.2 there comes the following error: "CRITICAL - Problem with SNMP request" try many things, but i think its a bug in your check_snmp_synology. And yes, i use your newest version.

Hi, is there any way to change the Port from 161 to another one? Regards.

The plugin works great! I had some requirements which the plugin didn't meet. Therefore, I have added some minor improvements such as separated command line options for DSM Update and enable performance data, etc. The author didn't respond to my mail. Therefore, I have published my version on GitHub, see: https://github.com/exensio/synology-nagios-plugin

Thank you for this plugin ;) I modify it in order to ignore DSM updates. It works perfectly. These are the lines for add option -I to ignore DSM updates : ... case $DSMUpgradeAvailable in "1") DSMUpgradeAvailable="Available"; healthWarningStatus=1; updateMessage="DSM update available";; "2") DSMUpgradeAvailable="Unavailable"; healthWarningStatus=0; updateMessage="Update unavailable";; "3") DSMUpgradeAvailable="Connecting"; healthWarningStatus=0; updateMessage="Update in progress";; "4") DSMUpgradeAvailable="Disconnected"; healthWarningStatus=1; updateMessage="DSM Update Disconnected";; "5") DSMUpgradeAvailable="Others"; healthWarningStatus=1; updateMessage="Check DSM Update";; esac if [ "$ignoreUpdate" = "yes" ] ; then healthWarningStatus=0; healthString="$healthString, Info : $updateMessage"; else healthString="$healthString, $updateMessage"; fi ... and on the last lines, I modify the output for Ok status : ... if [ "$healthCriticalStatus" = "0" ] && [ "$healthWarningStatus" = "0" ] ; then echo "OK - $healthString Appliance is in good health" exit 0 fi ...

Hello, Your plugin works rather fine but I have a problem: when I mount an USB drive. The USB drive is mounted in the /volume1/usbdrive and the script fails. We have a recurring warning from your plugin saying that DSM update is disconnected. I think that's because Synology has its servers down. People can have the Syno out of network so I think it will be nice to be able to disable this warning. Another request: will it be possible to only select some tests? For example I will be interested in no dsm update tests or different volumes warning/critical levels... Thank you for the plugin

nice plugin, monitoring two RS3412, until today without problems. today added another volume (the 10th) and script says now: ./check_snmp_synology: line 307: 49 .1.3.6.1.2.1.25.2.1.4 /volume10 4096 Bytes 438650334 648744698 3576310 * 100 / 49 .1.3.6.1.2.1.25.2.1.4 /volume10 4096 Bytes 1032116978 438650334 3576310: syntax error: invalid arithmetic operator (error token is ".1.3.6.1.2.1.25.2.1.4 /volume10 4096 Bytes 438650334 648744698 3576310 * 100 / 49 .1.3.6.1.2.1.25.2.1.4 /volume10 4096 Bytes 1032116978 438650334 3576310") tried to find on myself, but as not a programer, no chance.. :) any help very appreciated, regards martin

Very strange value for temperature: Synology model: "RS814" Synology s/n: "14A0LZN498800" DSM Version: "DSM 5.1-5022" DSM update: Unavailable System Status: Normal Temperature: 72 (CRITICAL) Power Status: Normal System Fan Status: Normal CPU Fan Status: Normal Number of disks: 4 "Disk 1" (model: "WD40EFRX-68WT0N0 ") status:Normal temperature:39 "Disk 2" (model: "WD40EFRX-68WT0N0 ") status:Normal temperature:40 "Disk 3" (model: "WD40EFRX-68WT0N0 ") status:Normal temperature:40 "Disk 4" (model: "WD40EFRX-68WT0N0 ") status:Normal temperature:38 Number of RAID volume: 1 "Volume 1" status:Normal 40% used What is the difference with disk values?

I can do a SNMP walk but I always get the next error: CRITICAL - Problem with SNMP request I already tried with different Synology's.

Hello, Im sorry I am a very beginner in nagios. I paste your script into /usr/local/nagios/libexec but when I execute ./check_snmp_synology -h myip I got -bash: ./check_snmp_synology: No files or folders of this type Could you please help me ?

Hello Jan, I have the same problem. My Synology displays: WARNING - Synology "RS2414rp+" (s/n: "XXXXXXXXXX", "DSM 5.1-5022") needs to be updated. Could you please explain to me, how do you have solved the problem ? What do you have change between line 119 to 123 ? Thanks for your answer.

Hello, great usefull plugin... there is perhabs a bug. for the parameter OID_upgradeAvailable set you between line 119 to 123 all status of the parameter healthStatus on 3. This give all time a warning to do updates. I changed in a other version for me that only by the status updates available the warning comes to do the updates.

Thanks for the plugin! The RAID status did not work for me at first, you can find a fix at http://pastebin.com/tubJnGxi. Most of the diff stems from the corrected intendation. Basically I just put a for loop around outputting the RAID status.

Good plugin, works well! I added a few things to the plugin: - Read DSM update status, flags a warning when DSM is out of date - Connects via SNMP v3 (more secure) - When using verbose mode the plugin will now first output the device status. This give you a better oversight in the WebUI. Script can be find here: http://pastebin.com/THUfEuNy Have fun :)

I don't suppose someone could show me their entry into the .cfg file they use please ? Still new to this and would really like to monitor the DiskStation in our office. Thank you.

Works as advertised. Any advice on making the complete verbose output display in Nagios?

... so that I can see it in the host list? Thank you for any hint! Kind regards Mirko

I have tested it with DS1511+ and DSM4.3 and it works (you can update your testes list if you like). I have 1 disk marked as hot spare, which has status Initialized, which is fine. The script reported this as Critical in Nagios so I modified it not to do that. Thanks for the script! Cheers

I must agree with user rrubel: considering a non initialized hot spare as a critical error is just plain wrong. So thanks go to user mtominsk for pointing out the lines of code that needed to be changed. And just to be fair with all respect to the Nagios Plugin Developing Guideline: this check totally lacks a critical and a warning switch which would really make sense when monitoring temperatures. So I really cannot consider this as a "good" nagios plugin, only average, because I cannnot define any limits. But it is still a good starting point for people who do not fear bash scripts. Sadly, the author does not seem to be very active so be prepared to make your own changes to the script. Successfully tested and used on Ubuntu 10.04.4 TLS with Nagios Core 3.2 and a Synology RS3412RPxs in Cluster-Mode.

Unfortunately i didn't get ist to work. a-team@nagios:/usr/lib/nagios3$ ./check_synology -h shiva ./check_synology: line 29: syntax error near unexpected token `(' The line 29 in the script is: ./check_synology: line 29: `OID_RAIDStatus="1.3.6.1.4.1.6574.3.1.1.1" usage() {' OID_RAIDStatus="1.3.6.1.4.1.6574.3.1.1.1" usage() { It would be nice if anybody can give advise.

Very useful plugin. Because Synology changed the way how spare disks are handled, I had to make some changes regarding the "initialized" Status which is interpreted as critical. Here are my changes on your script, maybe useful for one or two: if [ "${diskStatus[$i]}" != "1" ] && [ "${diskStatus[$i]}" != "2" ] ; then # if [ "${diskStatus[$i]}" = "2" ] ; then diskStatus[$i]="Initialized"; fi if [ "${diskStatus[$i]}" = "3" ] ; then diskStatus[$i]="NotInitialized"; fi if [ "${diskStatus[$i]}" = "4" ] ; then diskStatus[$i]="SystemPartitionFailed"; fi if [ "${diskStatus[$i]}" = "5" ] ; then diskStatus[$i]="Crashed"; fi healthStatus=2 healthString="$healthString, problem with ${diskID[$i]} (model:${diskModel[$i]}) status:${diskStatus[$i]} temperature:${diskTemp[$i]} C " elif [ "${diskStatus[$i]}" = "2" ] ; then diskStatus[$i]="Initialized"; else diskStatus[$i]="Normal" fi if [ "$verbose" = "yes" ] ; then echo "${diskID[$i]} (model:${diskModel[$i]}) status:${diskStatus[$i]} temperature:${diskTemp[$i]} C" ; fi done

Great plugin! Checks all of the vital statistics and properly returns status codes to Nagios. All it took to get working was turning SNMP on in the Synology settings.

If you're using FreeBSD (maybe OS X) as Nagios server there are a few changes that are needed to get this working. First change the location of bash, snmpwalk and snmpget in the file. bash is located /usr/local/bin/bash snmpwalk /usr/local/bin/snmpwalk snmpget /usr/local/bin/snmpget FreeBSD uses 'jot' instead of 'seq' so change all occurrences of seq to jot. Jot has a slightly different syntax. e.g. change line 76 for i in `seq 1 $nbDisk`; to for i in `jot - 1 $nbDisk`; mh

This tool provides pretty much all the status information you can get from your Synology box when run in Verbose mode, or has a nice single-line summary in normal mode. I'm using this on an 1812+. Two comments though: -- the location of snmpwalk and snmpget are hard-coded into the script so the script won't run if your system installs them in a different location, and there's not a good error message telling you they can't be found. I replaced those lines with a call to 'which snmpwalk' and 'which snmpget' which will at least pick up a version somewhere on your path. -- The section that monitors disk health is too strict when determining status. Drives that are set up as hot spares don't have to be "normal" -- they can be just initialized or even uninitialized and not be considered a failed unit. I had to modify that section as well to prevent critical failures due to the hot spare drives. At the least, those shouldn't be critical errors. Otherwise, this is a useful and informative plugin.