Package: munin-plugins-extra Version: 1.4.5-2 Severity: minor Hello, I have a SuperMicro SYS-5016T-MTFB (motherboard X8STi-F) that has voltage sensors with names like "+5V", "+12V", "-12V", etc.
Setting up ipmi_sensors_ works fine, it creates a good /etc/munin/ipmi file (all meaningful sensors are present), and reports the correct suggestions (ipmi_sensors_u_degrees_c, ipmi_sensors_u_volts, and ipmi_sensors_u_rpm). However when ipmi_sensors_* runs, it complains that ipmitool fails to execute with an error message something to the effect of "invalid argument 1". It has a Python stacktrace and doesn't report any data. The Python code has a line (161) where it's generating a cache file containing the sensor output like: p = Popen(["ipmitool","-I","open","sensor", "get"] + SENSORS, shell=False, stdout=PIPE) Since one of my sensors is named "-12V" it becomes apparent that ipmitool is parsing a -12V argument. Easy fix was to add a "--" argument to that line of Python code: p = Popen(["ipmitool","-I","open","sensor", "get", "--"] + SENSORS, shell=False, stdout=PIPE) After that modification the script runs perfectly. Well not quite perfect, I have one other caveat that's not quite deserving of it's own bug (simple configuration fix)... When running a sensor and the cache gets updated (every 2 minutes), I see some noise in the output about sensors not found: # munin-run --debug --pidebug ipmi_sensor_u_rpm # Processing plugin configuration from /etc/munin/plugin-conf.d/libvirt # Processing plugin configuration from /etc/munin/plugin-conf.d/munin-node # Set /rgid/ruid/egid/euid/ to /115/0/115 115 /0/ # Setting up environment # About to run '/etc/munin/plugins/ipmi_sensor_u_rpm' Sensor data record "System Level" not found! Sensor data record "Current 2" not found! fan1.value 7072 fan2.value 7072 fan3.value 7684 fan4.value 7072 What's happening here is that on my system where there are no watt or amp sensors, the Python code is substituting some default values: "Current 2" and "System Level". And even though I am not graphing these non-existant sensors, the cache file update code is still analyzing these substite sensors. Very easy fix was to add empty configuration lines like: amps = watts = ....to /etc/munin/ipmi. It would save somebody else trouble if the 'suggest' code wrote empty lines like that for sensor unit types it doesn't detect. -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-xen-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages munin-plugins-extra depends on: ii munin-node 1.4.5-2 network-wide graphing framework (n ii perl 5.10.1-14 Larry Wall's Practical Extraction munin-plugins-extra recommends no packages. Versions of packages munin-plugins-extra suggests: pn libnet-netmask-perl <none> (no description available) pn libnet-telnet-perl <none> (no description available) ii python 2.6.5-13 interactive high-level object-orie -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
