incorporating CoreTemp into Nagios

[James Pratt]

Sure, that should not be too difficult - google around for "Nagios wrapper" or nagios-plugins to see some example wrapper/plugin scripts.

Here's one that monitors hdtemp I found real quick that should show you how it works easy enough -

http://linsec.ca/blog/2008/02/09/hddtemp-wrapper-for-nagios/

cheers,
james

>> -----Original Message-----
>> From: xmanhosting [mailto:anthony at xmanhosting.com.au]
>> Sent: Wednesday, January 06, 2010 11:44 PM
>> To: nagios-users at lists.sourceforge.net
>> Subject: [Nagios-users] incorporating CoreTemp into Nagios
>> 
>> Hello,
>> 
>> I have my cpu temp (coretemp) monitored by on my server by the installation of
>> 
>> rpm -Uvh http://elrepo.org/elrepo-release-0.1-1.el5.elrepo.noarch.rpm
>> 
>> Running 'sensors' from the terminal produces the output:
>> 
>> coretemp-isa-0000
>> Adapter: ISA adapter
>> Core 0: +48°C (high = +100°C)
>> 
>> coretemp-isa-0001
>> Adapter: ISA adapter
>> Core 1: +48°C (high = +100°C)
>> 
>> coretemp-isa-0002
>> Adapter: ISA adapter
>> Core 2: +49°C (high = +100°C)
>> 
>> coretemp-isa-0003
>> Adapter: ISA adapter
>> Core 3: +49°C (high = +100°C)
>> 
>> Does anyone have any idea of how to bring the cpu temp from above into Nagios?
>> 
>> Or is there a tutorial available that someone knows of, of how to do this?
>> 
>> Thanks for any help,
>> 
>> Kind regards,
>> Anthony

------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev 
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null