12 May
2012

In summer, my web server is at risk of overheating. Today I installed some temperature reporting and recording tools.

For my ubuntu linux, I am using the lm_sensors kernel module. This was installed auptmatically (Ubuntu 10.4).

To report temperatures, the "sensors" command can be used, but first the correct kernel drivers must be loaded. This can be done really easily, and with minimla prior knowledge, by using the command "sensors-detect". All the following
probably needs to be done as super-user.


# sensors-detect


sensors-detect revision 5818 (2010-01-18 17:22:07 +0100)
System: To be Filled To be Filled
Board: Supermicro Inc. Intel 440BX/440GX

Some south bridges, CPUs or memory controllers contain embedded sensors.
Do you want to scan for them? This is totally safe. (YES/no):
Silicon Integrated Systems SIS5595... No
VIA VT82C686 Integrated Sensors... No
.
.
.


After following a lot of simple instructions, I got the correct kernel module
loaded (in my case, a Winbond W83781D). Then I needed to start it by typing:


# service module-init-tools start


response: module-init-tools stop/waiting



# sensors


w83781d-isa-0290
Adapter: ISA adapter
in0: +2.05 V (min = +1.79 V, max = +2.19 V)
in1: +2.06 V (min = +1.79 V, max = +2.19 V)
in2: +3.39 V (min = +2.82 V, max = +3.79 V)
in3: +2.94 V (min = +0.13 V, max = +0.00 V) ALARM
in4: +3.20 V (min = +0.00 V, max = +0.00 V) ALARM
in5: +3.34 V (min = +0.00 V, max = +0.26 V) ALARM
in6: +3.30 V (min = +0.00 V, max = +0.00 V) ALARM
fan1: 3125 RPM (min = 21093 RPM, div = 8) ALARM
fan2: 4115 RPM (min = 21093 RPM, div = 8) ALARM
fan3: 0 RPM (min = -1 RPM, div = 2) ALARM
temp1: +60.0C (high = +0.0C, hyst = +0.0C) ALARM
temp2: +63.0C (high = +70.0C, hyst = +65.0C)
temp3: -48.0C (high = +80.0C, hyst = +75.0C)
cpu0_vid: +2.000 V
beep_enable:enabled



Finally, to record this data and make it accessible via a web interface, I installed munin with the sensors plugin.

Munin works by running on a main (web) server machine, and then contacting munin node processes on each machine being monitored. In my case, the node is configured to include the sensors plugin, which is set up by creating a symbolic link (via ln) from the actual plugin at /usr/share/munin/plugins/sensors_ to a link called sensors_temp (to have munin monitor the temperature). The link command, in my case, was:

ln -s /usr/share/munin/plugins/sensors_ /etc/munin/plugins/sensors_temp

Testing this can be accomplished with munin_run:

# munin-run sensors_temp
temp1.value 60.0
temp2.value 63.5
temp3.value -48.0



For background info, see: http://www.lm-sensors.org/wiki/FAQ/Chapter2


By Gregory Dudek at | Leave a comment |    
Comments
There are no comments.
Trackbacks
Please send trackback to:/blog/246/tbping
There are no trackbacks.
Post your own response

Each comment is manually screened for the presence of appropriate and substantive content, due to a constant onslaught of comment-spam. This means there may be a delay before your comment appears.


(Some kind of name is required, will be visible)

Required, whatever you enter will be visible to other users.


(Optional, used for "mailto" link)

Your email address is not required, but if you insert it it will be displayed so people can contact you.

Answer this question correctly to demonstrate that you are not a dumb spambot.



The title for your comment.



Your comment goes here. All relevant comments are welcome, except for those that simply promote an irrelevant product or else are used to fraudulently inflate the link count to an irrelevant web page. They appear after moderation. Don't forget to also fill in the captcha below or your text will be rejected automatically!

You must answer this question to prove you are human
which has the least friendly public image: 1:collie, 2:beagle, 3:doberman, 4:dachsund, 5:dalmatian?

Answer this question correctly to demonstrate that you are not a dumb spambot.