SteScho / manubulon-snmp

Set of Icinga/Nagios plugins to check hosts and hardware with the SNMP protocol.
GNU General Public License v2.0
73 stars 71 forks source link

Error with check_snmp_process.pl with snmpv3 but not check_snmp_storage.pl #75

Open stephdant opened 4 years ago

stephdant commented 4 years ago

I have configure snmp v3 on a vcenter, it works for check_snmp_storage.pl but not for check_snmp_process.pl with the same configuration

Work check_snmp_storage.pl -H @IP -l $USER4$ -x $USER5$ -X $USER5$ -L sha,aes -m /storage/archive -e -w 90 -c 95 -S 0 -q FixedDisk -f All selected storages (<90%) : OK | '/'=5723.9648MB;9746;10288;0;10829 '/boot'=33.9639MB;108;114;0;120 '/dev'=0.0000MB;7208;7609;0;8009 '/dev/shm'=0.7930MB;7217;7618;0;8019 '/run'=0.6602MB;7217;7618;0;8019 '/storage/autodeploy'=22.4961MB;8949;9446;0;9943 '/storage/core'=1152.6016MB;45235;47748;0;50261 '/storage/db'=278.0000MB;8949;9446;0;9943 '/storage/dblog'=3701.5117MB;13485;14234;0;14983 '/storage/imagebuilder'=22.5000MB;8949;9446;0;9943 '/storage/log'=1864.0938MB;8949;9446;0;9943 '/storage/netdump'=1.2539MB;886;935;0;984 '/storage/seat'=1649.1797MB;22556;23809;0;25062 '/storage/updatemgr'=68.9414MB;90592;95624;0;100657 '/sys/fs/cgroup'=0.0000MB;7217;7618;0;8019 '/tmp'=1.3477MB;7217;7618;0;8019 '/var/spool/snmp'=0.0000MB;1;1;0;1

Don't work ./check_snmp_process3.pl -H @IP -l $USER4$ -x $USER5$ -X $USER5$ -L sha,aes -n -r -v 0 0 0 0 Alarm at 15 SNMPv3 AuthPriv login : $USER4$, sha, aes ERROR: Process name table : No response from remote host "@IP".

Could you help me?

SteScho commented 4 years ago

Hi,

-n needs a process name. Do you forget that or is it just missing in your example?

stephdant commented 4 years ago

hello, Thx for your reply,

The check_snmp_process.pl with this option-n -r -v, list all services in a server.

This command return the same error ./check_snmp_process.pl -H @ip -l $USER4$ -x $USER5$ -X $USER5$ -L sha,aes -n postgres -v

SteScho commented 4 years ago

Unfortunately I don't have a vcenter to test that. It looks like that vcenter did not use the same oid for processes than other systems. Are you able to fix that?