Hi Sebastian,
You could rebuild the package with debugging enabled. Add "confflags += --enable-debug" to debian/rules after line 37 and rerun "debuild -us -uc". Install the package and set the log-level to "debug". As this will produce _a_ _lot_ of output, I suggest to enable the "logfile" plugin, set its "LogLevel" to "debug" and set its "File" config option to "stdout". Then run collectd as "collectd -f > /tmp/collectd.debug" - this will prevent collectd from forking to the background and redirect all output to /tmp/collectd.debug. Kill the process (using Ctrl-C) after about 30-60 seconds and send the output file to this bug report.
You can find the log attached to this email. As far as I can see, the sensors-config is handled correctly?
See my sensors.conf as reference:
chip "fscher-*"
label temp1 "Temp1/CPU"
label temp2 "Temp2/MB"
ignore temp3
label fan1 "Fan1/PS"
label fan2 "Fan2/CPU"
ignore fan3
label in0 "+12V"
label in1 "+5V"
label in2 "Battery"
compute in0 (@ * (49 * 33) / 255) + (0 / 100), (@ - (0 /
100)) * 255 / (49 * 33)
compute in1 (@ * (20 * 33) / 255) + (0 / 100), (@ - (0 /
100)) * 255 / (20 * 33)
compute in2 (@ * (10 * 33) / 255) + (0 / 100), (@ - (0 /
100)) * 255 / (10 * 33)
set pwm1 100
set pwm2 70
I also tested configuring some of the sensors (e.g. Sensor
"fscher-i2c-0-73/fan1") in the plugin-section of collectd.conf, no
change ... hopefully, the logs will help ...
Maybe this issue is related to some old packages in etch in conjunction with the exotic sensor-chip? But I wonder why it does work on my 2nd system (sensors-w83697hf-isa-0290) ...
Cheers, Armin
collectd.debug.gz
Description: GNU Zip compressed data
