[Nagios-users] SNMP unknown system

2013-09-13 Thread Paul Simons
Hello I have a system running (proprietary OS) for which I have no information except that there is an SNMP client (no MIB, OID, etc.) Can I use NAGIOS to recover what is available? Then I can tailor my SNMP gets. Regards Paul Disclaimer: This e-mail (and any

Re: [Nagios-users] SNMP unknown system

2013-09-13 Thread Lachlan Bowes
Do an snmpwalk of the entire available tree, then see what you have Lachlan On Fri, Sep 13, 2013 at 10:35 PM, Paul Simons paul.sim...@onair.aerowrote: Hello I have a system running (proprietary OS) for which I have no information except that there is an SNMP client (no MIB, OID, etc.)

Re: [Nagios-users] Splunk Integration Question...

2013-09-13 Thread Sean Alderman
From what I can tell, after trying it, the query string appended to the splunk_url parameter referneces Nagios specific things... e.g. https://*splunk_url*/?q=search?%20*hostname*%20* Nagios_command_description * So, the implication is that somehow splunk has data about nagios checks, by name.

[Nagios-users] Odd Problem with check_yum on one server...

2013-09-13 Thread Sean Alderman
Greetings, I'm hoping someone might be able to provide a hint on this issue. Its strange, it happens only on one of my CentOS 6.4 servers. Nagios server reports /usr/bin/yum not found when executing the following test: [root@nagios ~]# sudo -u nagios /usr/lib64/nagios/plugins/check_nrpe -H

Re: [Nagios-users] Odd Problem with check_yum on one server...

2013-09-13 Thread Tech Support
It seems to me that yum is simply located somewhere else on that server. Try which yum. Regards; John From: Sean Alderman [mailto:salderm...@udayton.edu] Sent: Friday, September 13, 2013 10:13 AM To: Nagios Users List Subject: [Nagios-users] Odd Problem with check_yum on one server...

Re: [Nagios-users] Odd Problem with check_yum on one server...

2013-09-13 Thread Sean Alderman
I apologize... I should have pasted that, but I thought the fact that I could execute the check_yum script as the nrpe user on the host with the problem would have implied that it functions as expected. Yum is located where we would expect it to be on a standard CentOS machine. [root@test ~]#