Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

volstatus not working properly. #22

Open
fabien4455 opened this issue Jan 25, 2019 · 5 comments
Open

volstatus not working properly. #22

fabien4455 opened this issue Jan 25, 2019 · 5 comments

Comments

@fabien4455
Copy link

fabien4455 commented Jan 25, 2019

Hello ! I have a problem with your script.

Here are my volumes showed in Qnap Web interface :

image

Here is the return of command line :

root@myserver:/usr/lib/nagios/plugins# ./check_qnap 10.4.1.5 public volstatus 10 15
(standard_in) 1: illegal character: S
(standard_in) 1: illegal character: S
(standard_in) 1: syntax error
./check_qnap: line 628: [: : integer expression expected
./check_qnap: line 631: [: : integer expression expected
Volume #1: OK: Ready, Total Size (bytes): 48.5 GB, Free: 31.7 GB (65%), Volume #2: OK: Ready, Total Size (bytes): 491.5 GB, Free: 491.4 GB (99%), Volume #3: CRITICAL: Such, Total Size (bytes): Such Instance, Free: Such Instance (%)|FreeSize_Volume-1=65%;10;15;0;100 FreeSize_Volume-2=99%;10;15;0;100 FreeSize_Volume-3=%;10;15;0;100

I have tried your new version but same problem.

Could you please fix it ? Thank's and have a nice day

@nikband
Copy link
Owner

nikband commented Jan 29, 2019

Hi I thinks that script don't manage correctly size with multiple volumegroups, i have to verify this. Thanks

@ricain59
Copy link

ricain59 commented Jul 9, 2019

Hi,

I've the same problem with 6 volume, return this error. With 4 volume works nice but with more than 4 return this error: (..) (standard_in) 1: illegal character: S (..)

You can resolve this please?

Thank you

@nikband
Copy link
Owner

nikband commented Aug 23, 2019

Sorry in this period i don'd find time for check this script. I have only 1 volume in my qnap :( but there is a bug in code

@mario-van-zadel
Copy link

I have the same issue. The check_qnap3 script returns the following output for my third volume:

Volume #3: CRITICAL: Such, Total Size (bytes): Such Instance, Free: Such Instance (%)

The volumes 1 and 2 are working great.

If I call snmpget -v2c -c ********* 192.168.***.*** 1.3.6.1.4.1.24681.1.2.17.1.6.2 from my nagios instance, the output looks okay:

iso.3.6.1.4.1.24681.1.2.17.1.6.2 = STRING: "Ready"

But if call snmpget -v2c -c ********* 192.168.***.*** 1.3.6.1.4.1.24681.1.2.17.1.6.3 for my third volume, the following string is returned by SNMP:

iso.3.6.1.4.1.24681.1.2.17.1.6.3 = No Such Instance currently exists at this OID

It looks like it's not an issue of check_qnap3. Instead the QNAP seems to be unable to locate the third volume in case of SNMP requests.

In my QNAP config, volume 1 is a thick volume. Volume 2 is a static volume and volume 3 is a thin volume. Maybe it's a problem with the volume type "thin volume". @fabien4455 @ricain59 What's the type of your volume, check_qnap3 is returning an error for? Is it's a thin-volume? Maybe you are able to add some information about your volume configuration so that we are able to locate the problem's root cause.

Best regards
Mario

@adrav
Copy link

adrav commented Aug 5, 2021

Turn off and on SNMP in control panel in QNAP.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants