Hi All,
for a Unix production server..for memory used
I am unable to see the output state like OK,Warning,Critical.
It is displaying full details correctly but the state of the memory is not printed at the beginning..
host1 is correctly displaying as CRITICAL - <Info>
host2 is not displaying the state ... i'm getting the output as - <info>
I have replaced the plugin used for check_mem in the remote server with a well working one. but no use.
[root@nagxi ~]# /usr/local/nagios/libexec/check_nrpe -H host1 -p 5666 -c check_mem -a '-w 75 -c 90'
CRITICAL - Memory usage: total:65505 MB - used:62410 MB(95.27500%) - free:3095 MB(4.72500%);Top 5 Memory Processes(memKB,pname,pid): 465041KB dw.sapRP2_D21 20048, 84980KB dw.sapRP2_D21 20070, 83078KB dw.sapRP2_D20 17148, 82992KB dw.sapRP2_D20 266, 82622KB dw.sapRP2_D21 17474|Memory usage=62410MB;49128.75;58954.50;0;65505
[root@nagxi ~]# /usr/local/nagios/libexec/check_nrpe -H host2 -p 5666 -c check_mem -a '-w 75 -c 90'
- Memory usage: total:30669 MB - used:23290 MB(75.93900%) - free:7379 MB(24.06100%);Top 5 Memory Processes(memKB,pname,pid): 319419KB en.sapEP2_SCS01 9967, 100384KB ora_pmon_EP2 8934, 99504KB ora_dbrm_EP2 8944, 99472KB ora_mmnl_EP2 8962, 99456KB ora_arc1_EP2 9987|Memory usage=23290MB;23001.75;27602.10;0;30669
[root@nagxi ~]#
Please help mee..
# State - Unable to see it #
Re: # State - Unable to see it #
Very strange. What happens both on host1 and host2 when you run the command defined by check_mem on the command line? Can you post those commands along with their outputs?
Former Nagios employee
Re: # State - Unable to see it #
Some times it is showing the status. but some times it is not...
-
- Posts: 7698
- Joined: Mon Apr 23, 2012 4:28 pm
- Location: Travelling through time and space...
Re: # State - Unable to see it #
Sounds like there are issues on that server making system calls. Do you get the same results when running check_mem manually on the host with troubles? Do you only have this on 2 hosts? If not, are other hosts experiencing this issue? Sounds like host1 is fine, which is another indicator that there may be issues on the actual host2 server.