[collectd] A few problems and suggestions

[Florian Forster]

Hi Marco,

On Tue, Mar 18, 2008 at 03:09:04PM +0100, Marco Chiappero wrote:
> I'm running debian lenny with the 2.6.24.3 kernel release and bofh 
> sensors and fancontrol are working. Packages installed:
> 
> libsensors4              1:3.0.1-2
> lm-sensors               1:3.0.1-2

do you compile the daemon yourself? If so, can you provide the file
`config.log' that's generated by the `configure' script? Ideally put it
on a webserver somewhere and provide a link to the file since there's a
size-limit on postings to the mailing list.

If you use a pre-compiled package: Where did you get it from? The
current `unstable' package (Debian Sid) is linked with libsensors3
(1:2.10.3-1), so it's not surprising that this binary doesn't work with
libsensors4.

> > Sorry, but I didn't find a control path in the ping plugin so it can
> > fail without logging at least a warning.
> 
> what can I do to try to make it work?

Load the `logfile' and/or `syslog' plugin, set the log level to `info',
(re)start the daemon and see if anything shows up.
If nothing shows up, make sure you're looking in the right place.
Especially when using `syslog'. If you're absolutely sure that no output
is produced, check if your configuration is sane.

If the daemon stays uncommunicative, get your hands on a version that
has debugging capabilities. You can get them by specifying
`--enable-debug' when configuring the source. (The experimental Debian
package used to have debugging enabled, but the unstable package doesn't
anymore, so Sebastian tells me.) Increase the verbosity by setting the
log level to `debug' and re-run the daemon. If still no output appears,
you should probably go and see a optician ;)

> > What can _we_ do different here? IIrc the hddtemp plugin simply
> > connects to and reads from the hddtempd using a socket.
> 
> Maybe you can help me to understand why polling the server with a bash
> script doesn't affect the drives standby command after some time of
> inactivity like the hddtemp plugin does. It seems that it keeps
> accessing the drives. I'm not blaming you, I'd just like to understand
> why.

I don't know either, sorry :/ Did you check hddtemp's manpage? A quick
search produces this bug report, but unfortunately it doesn't seem to be
resolved: <https://savannah.nongnu.org/bugs/?19150>

Regards,
-octo
-- 
Florian octo Forster
Hacker in training
GnuPG: 0x91523C3D
http://verplant.org/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://mailman.verplant.org/pipermail/collectd/attachments/20080318/ebb34b31/attachment.pgp