lookup device-id failed: Physical Memory

[tmeto]

hi!

I'm having trouble with a check on a machine with windows 2000. The machine is virtualized and has 2g ram, but at check shows me this error "lookup failed device-id: Physical Memory" and I dont know that can be ...

any ideas?

[slansing]

What check are you running? Can you also show us the command definition and let us know what the command that is actually being run looks like?

[tmeto]

this is what you want to see?

define command{
command_name check_disk_snmp
command_line /usr/bin/perl $USER1$/check_disk_snmp.pl -H $HOSTADDRESS$ -s $ARG1$ -d $ARG2$ -u $ARG3$ -w $ARG4$ -c $ARG5$
}

[slansing]

Yes, can you also share the command definition as it appears in your service's .cfg file? So we can see what you are using for arguments?

[tmeto]

sorry, bad command.

define service{
use generic-service
hostgroup_name COAATM-CHECK
service_description check memoria
check_command check_winmem_snmp!nagiosica!MB!90%!99%
}

and ....

define command{
command_name check_winmem_snmp
command_line /usr/bin/perl $USER1$/check_disk_snmp.pl -H $HOSTADDRESS$ -s $ARG1$ -d phys -u $ARG2$ -w $ARG3$ -c $ARG4$
}

[abrist]

Have you attempted to run the check from the cli?

Code: Select all

/usr/bin/perl /usr/local/nagios/check_disk_snmp.pl -H <ip address of remote host> -s nagiosica -d phys -u MB -w 90% -c 99%

[tmeto]

yes, and.....is the same.

root@xxxxx:/usr/local/nagios/etc/losclientes# /usr/bin/perl /usr/local/nagios/libexec/check_disk_snmp.pl -H 172.16.0.3 -s nagiosica -d phys -u MB -w 90% -c 99%
lookup device-id failed: Physical Memory

[abrist]

I presume that you have configured snmp on the windows server? Do you have any other snmp checks working on the is windows server? Have you looked at using nsclient instead of snmp?

[tmeto]

I can not use nscliente for this case and we have more on that machine check. It may be the version / windows updates? the machine is very old system......

[slansing]

I can not use nscliente for this case and we have more on that machine check. It may be the version / windows updates? the machine is very old system......

Was NSClient++ not installing for you? What version of windows are you running?