Hi Sebastian,
On Fri, Apr 18, 2008 at 09:27:53AM +0200, Sebastian Harl wrote:
On Fri, Apr 18, 2008 at 08:22:07AM +0200, Florian Forster wrote:
Please give the attached patch a try and tell me if it worked or not.
I'm sure Sebastian or some howto can tell you how to do integrate that
into the p
Has anyone of you tested this patch so far? collectd 4.3.3 has just been
released which includes that patch. I'm going to close this bug again in
the next upload but I'd really like some positive feedback before doing
so.
TIA,
Sebastian
Yes, the patch works for me as I already said in
htt
Hi,
On Fri, Apr 18, 2008 at 09:27:53AM +0200, Sebastian Harl wrote:
> On Fri, Apr 18, 2008 at 08:22:07AM +0200, Florian Forster wrote:
> > Please give the attached patch a try and tell me if it worked or not.
> > I'm sure Sebastian or some howto can tell you how to do integrate that
> > into the p
reopen 468143
found 468143 4.3.2-1
tags 468143 + patch pending fixed-upstream
thanks
Hi,
On Fri, Apr 18, 2008 at 08:22:07AM +0200, Florian Forster wrote:
> while writing a reply and interpreting the log output you've provided, I
> stumbled across the bug. The function which is responsible for
> f
Hi Alex,
while writing a reply and interpreting the log output you've provided, I
stumbled across the bug. The function which is responsible for
formatting the chip name does so depending on the type of the chip. The
returned status variable is only set in one out of three branches,
though :/ A sc
On Wednesday 16 April 2008, Sebastian Harl wrote:
> Hrm, just a guess, but could you please try to install some 2.10.x
> version of lm-sensors and try again? Please also try the sensors command
> again. I guess you can get a 2.10.x package from
> http://snapshot.debian.net/.
Tried version 2.10.5,
Hi,
On Wed, Apr 16, 2008 at 10:05:35AM +0200, Alex wrote:
> unfortunately, the updated packages doesn't change anything. Still no sensor
> data logged.
:-/
> There are also multiple versions of libsensors used on my system, as the
> fixes had to do with bugs in libsensors[34], this might be re
Hello,
unfortunately, the updated packages doesn't change anything. Still no sensor
data logged.
There are also multiple versions of libsensors used on my system, as the
fixes had to do with bugs in libsensors[34], this might be relevant
although sensors (libsensors4) and ksensors (libsensors3
On Wednesday 27 February 2008, Sebastian Harl wrote:
> Could you please set the debug level to "info" and check if any messages
> turn up in syslog? I currently have no idea what this might be caused by
> but I will have a closer look at it soonish.
It already is. Collectd is completely silent, ex
Hi Alex,
On Wed, Feb 27, 2008 at 11:13:10AM +0100, Alex Hermann wrote:
> After the upgrade of collectd from 4.2.1-1 to 4.3.0-1, the sensors plugin
> fails to collect data. No messages in syslog or anywhere else. The sensors
> command-line utility still shows all values:
Could you please set the d
Package: collectd
Version: 4.3.0-1
Severity: normal
After the upgrade of collectd from 4.2.1-1 to 4.3.0-1, the sensors plugin
fails to collect data. No messages in syslog or anywhere else. The sensors
command-line utility still shows all values:
$ sensors
asb100-i2c-1-2d
Adapter: SMBus nForce2 ad
11 matches
Mail list logo
