[collectd] Need help with sensors plugin

Sebastian Harl sh at tokkee.org
Wed Apr 14 09:39:33 CEST 2010


Hi Bruno,

On Tue, Apr 13, 2010 at 10:02:02PM +0200, Bruno Friedmann wrote:
> On 04/13/2010 09:21 PM, Sebastian Harl wrote:
> > On Tue, Apr 13, 2010 at 09:13:18PM +0200, Bruno Friedmann wrote:
> >> I've a server which gives me this with sensors
> >>
> >> sensors
> >> atk0110-acpi-0
> >> Adapter: ACPI interface
> >> Vcore Voltage:     +1.09 V  (min =  +0.85 V, max =  +1.60 V)
> >>  +3.3 Voltage:     +3.26 V  (min =  +2.97 V, max =  +3.63 V)
> >>  +5 Voltage:       +5.12 V  (min =  +4.50 V, max =  +5.50 V)
> >>  +12 Voltage:     +12.16 V  (min = +10.20 V, max = +13.80 V)
> >> CPU FAN Speed:       0 RPM  (min =  600 RPM)
> >> CHASSIS FAN Speed:   0 RPM  (min =  600 RPM)
> >> POWER FAN Speed:     0 RPM  (min =  600 RPM)
> >> CPU Temperature:   +42.0°C  (high = +60.0°C, crit = +95.0°C)
> >> MB Temperature:    +39.0°C  (high = +45.0°C, crit = +95.0°C)
> >>
> >> (Don't worry about the FAN, they are water-cooled :-)
> >>
> >> I've try to activate the sensors plugin but it return errors
> >>
> >> Apr  9 18:39:51 chewbacca collectd[13285]: sensors plugin: lm_sensors reports no features. Data will not be collected.
> >> Apr  9 18:39:51 chewbacca collectd[13285]: read-function of plugin `sensors' failed.
> > 
> > Which versions of collectd and lm-sensors do you use? The sensors plugin
> > is linked against libsensors. Which version is that (`ldd /path/to/
> > sensors.so | grep sensors' should be sufficient)? The functionality of
> > the sensors plugin is fairly limited in case you're using lm-sensors
> > version 3.x and libsensors (soname) version 3 (lm-sensors 2.10), which
> > might explain that behavior.

> ls /usr/lib64/libsensors*
> libsensors.so.3      libsensors.so.3.1.5  libsensors.so.4      libsensors.so.4.2.0

So, this is libsensors soname versions 3 and 4, i.e., lm-sensors 2.10
and 3.x respectively.

> a sensors -v return
> sensors version 3.1.1 with libsensors version 3.1.1
> 
> and finally the ldd
> ldd /usr/lib64/collectd/sensors.so
>         linux-vdso.so.1 =>  (0x00007fffac1ff000)
>         libsensors.so.3 => /usr/lib64/libsensors.so.3 (0x00007ff58e633000)

I.e., libsensors from lm-sensors 2.10. The problem is that lm-sensors
3.x ships a configuration file called sensors3.conf, while 2.10 ships
sensors.conf. Since collectd is linked against 2.10, it expects the
config file to be sensors.conf. I'm not sure if the format of the config
file has changed (but I suppose that this is the case; else the rename
would not make much sense) but you could try to symlink sensors.conf to
sensors3.conf and see if that helps as a work-around for now. I would
not expect too much from that, though.

> I think I've no choice than waiting a new plugin or it's upgrade .

Where did you get collectd from? Did you compile it yourself or do you
use some pre-compiled packages? Which Linux distribution do you use?

Cheers,
Sebastian

-- 
Sebastian "tokkee" Harl +++ GnuPG-ID: 0x8501C7FC +++ http://tokkee.org/

Those who would give up Essential Liberty to purchase a little Temporary
Safety, deserve neither Liberty nor Safety.         -- Benjamin Franklin

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: Digital signature
Url : http://mailman.verplant.org/pipermail/collectd/attachments/20100414/75c343d1/attachment.pgp 


More information about the collectd mailing list