lm-sensors not working with nagios

hondo · 04-27-2007, 10:44 AM

Hi

I cant get lm-sensors to work with nagios. I need the lm-sensors package to be able to monitor hardware on computers and to do that with nagios i use the check_sensors plugin. This plugin requires lm-sensors set up properly which doesnt seem to be do-able(?).

I first compiled the lastest version of lm-sensors with the necessary packages required for an lm-sensors installation (i have 2.6 kernel, so i2c should not be necessary but the libraries were installed=.

When i ran "sensors-detect" it started the config wizard, but couldnt detect anything.

So i thought, i might as well just apt the package in since im using debian. So i did, but i got the same problem when issuing "sensors-detect" this time, it doesnt detect anything and i also ran the command "apt-get build-dep lm-sensors" so all dependencies should be resolved. Still nothing is detected.

Is there any way to get lm-sensors to work with the "check_sensors" plugin in nagios? Help is appericiated since i would really like to be able to monitor all hardware.

Brian1 · 04-27-2007, 12:08 PM

lmsensors will only work with certain chipsets. Is the shipset on the motherboard workable with lmsensors? Not all boards have the ability under linux. Posting info about the board and chipset might help to figure it out.

Brian

hondo · 04-27-2007, 12:23 PM

Here is the information about the board and other hardware:

Code:

0000:00:00.0 Host bridge: Intel Corp. Mobile Memory Controller Hub (rev 03)
        Subsystem: Asustek Computer, Inc.: Unknown device 10c7
        Flags: bus master, fast devsel, latency 0
        Capabilities: [e0] #09 [2109]

0000:00:02.0 VGA compatible controller: Intel Corp. Mobile Graphics Controller (rev 03) (prog-if 00 [VGA])
        Subsystem: Asustek Computer, Inc.: Unknown device 1882
        Flags: bus master, fast devsel, latency 0, IRQ 11
        Memory at feb80000 (32-bit, non-prefetchable) [size=512K]
        I/O ports at ec00 [size=8]
        Memory at d0000000 (32-bit, prefetchable) [size=256M]
        Memory at feb40000 (32-bit, non-prefetchable) [size=256K]
        Capabilities: [d0] Power Management version 2

0000:00:02.1 Display controller: Intel Corp. Mobile Graphics Controller (rev 03)
        Subsystem: Asustek Computer, Inc.: Unknown device 1882
        Flags: bus master, fast devsel, latency 0
        Memory at fea80000 (32-bit, non-prefetchable) [size=512K]
        Capabilities: [d0] Power Management version 2

0000:00:1b.0 0403: Intel Corp. 82801FB/FBM/FR/FW/FRW (ICH6 Family) High Definition Audio Controller (rev 04)
        Subsystem: Asustek Computer, Inc.: Unknown device 10c3
        Flags: bus master, fast devsel, latency 0, IRQ 11
        Memory at feb38000 (64-bit, non-prefetchable) [size=16K]
        Capabilities: [50] Power Management version 2
        Capabilities: [60] Message Signalled Interrupts: 64bit+ Queue=0/0 Enable-
        Capabilities: [70] #10 [0091]

0000:00:1d.0 USB Controller: Intel Corp. 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #1 (rev 04) (prog-if 00 [UHCI])
        Subsystem: Asustek Computer, Inc.: Unknown device 10c7
        Flags: bus master, medium devsel, latency 0, IRQ 201
        I/O ports at e400 [size=32]

0000:00:1d.1 USB Controller: Intel Corp. 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #2 (rev 04) (prog-if 00 [UHCI])
        Subsystem: Asustek Computer, Inc.: Unknown device 10c7
        Flags: bus master, medium devsel, latency 0, IRQ 209
        I/O ports at e480 [size=32]

0000:00:1d.2 USB Controller: Intel Corp. 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #3 (rev 04) (prog-if 00 [UHCI])
        Subsystem: Asustek Computer, Inc.: Unknown device 10c7
        Flags: bus master, medium devsel, latency 0, IRQ 177
        I/O ports at e800 [size=32]

0000:00:1d.3 USB Controller: Intel Corp. 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #4 (rev 04) (prog-if 00 [UHCI])
        Subsystem: Asustek Computer, Inc.: Unknown device 10c7
        Flags: bus master, medium devsel, latency 0, IRQ 217
        I/O ports at e880 [size=32]

0000:00:1d.7 USB Controller: Intel Corp. 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB2 EHCI Controller (rev 04) (prog-if 20 [EHCI])
        Subsystem: Asustek Computer, Inc.: Unknown device 10c7
        Flags: bus master, medium devsel, latency 0, IRQ 201
        Memory at feb3fc00 (32-bit, non-prefetchable) [size=1K]
        Capabilities: [50] Power Management version 2
        Capabilities: [58] #0a [20a0]

0000:00:1e.0 PCI bridge: Intel Corp. 82801 PCI Bridge (rev d4) (prog-if 01 [Subtractive decode])
        Flags: bus master, fast devsel, latency 0
        Bus: primary=00, secondary=01, subordinate=02, sec-latency=32
        I/O behind bridge: 0000d000-0000dfff
        Memory behind bridge: fe800000-fe8fffff
        Prefetchable memory behind bridge: 0000000020000000-0000000021f00000
        Capabilities: [50] #0d [0000]

0000:00:1f.0 ISA bridge: Intel Corp. 82801FBM (ICH6M) LPC Interface Bridge (rev 04)
        Flags: bus master, medium devsel, latency 0

0000:00:1f.1 IDE interface: Intel Corp. 82801FB/FBM/FR/FW/FRW (ICH6 Family) IDE Controller (rev 04) (prog-if 8a [Master SecP PriP])
        Subsystem: Asustek Computer, Inc.: Unknown device 10c7
        Flags: bus master, medium devsel, latency 0, IRQ 177
        I/O ports at <unassigned>
        I/O ports at <unassigned>
        I/O ports at <unassigned>
        I/O ports at <unassigned>
        I/O ports at ffa0 [size=16]

0000:01:03.0 CardBus bridge: Ricoh Co Ltd RL5c476 II (rev b3)
        Subsystem: Asustek Computer, Inc.: Unknown device 10c7
        Flags: bus master, medium devsel, latency 32, IRQ 169
        Memory at fe800000 (32-bit, non-prefetchable) [size=4K]
        Bus: primary=01, secondary=02, subordinate=05, sec-latency=176
        Memory window 0: 20000000-21fff000 (prefetchable)
        Memory window 1: 22000000-23fff000
        I/O window 0: 0000d000-0000d0ff
        I/O window 1: 0000d400-0000d4ff
        16-bit legacy interface ports at 0001

0000:01:03.1 FireWire (IEEE 1394): Ricoh Co Ltd R5C552 IEEE 1394 Controller (rev 08) (prog-if 10 [OHCI])
        Subsystem: Asustek Computer, Inc.: Unknown device 10c7
        Flags: bus master, medium devsel, latency 64, IRQ 185
        Memory at fe8fd800 (32-bit, non-prefetchable) [size=2K]
        Capabilities: [dc] Power Management version 2

0000:01:03.2 0805: Ricoh Co Ltd: Unknown device 0822 (rev 17)
        Subsystem: Asustek Computer, Inc.: Unknown device 10c7
        Flags: bus master, medium devsel, latency 64, IRQ 4
        Memory at fe8fe000 (32-bit, non-prefetchable) [size=256]
        Capabilities: [80] Power Management version 2

0000:01:03.3 System peripheral: Ricoh Co Ltd: Unknown device 0592 (rev 08)
        Flags: medium devsel, IRQ 4
        Memory at fe8fe400 (32-bit, non-prefetchable) [size=256]
        Capabilities: [80] Power Management version 2

0000:01:03.4 System peripheral: Ricoh Co Ltd: Unknown device 0852 (rev 03)
        Subsystem: Asustek Computer, Inc.: Unknown device 10c7
        Flags: medium devsel, IRQ 4
        Memory at fe8fe800 (32-bit, non-prefetchable) [size=256]
        Capabilities: [80] Power Management version 2

0000:01:04.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)
        Subsystem: Asustek Computer, Inc.: Unknown device 1045
        Flags: bus master, medium devsel, latency 64, IRQ 193
        I/O ports at d800 [size=256]
        Memory at fe8fec00 (32-bit, non-prefetchable) [size=256]
        Capabilities: [50] Power Management version 2

0000:01:05.0 Network controller: Intel Corp. PRO/Wireless 2200BG (rev 05)
        Subsystem: Intel Corp.: Unknown device 2701
        Flags: bus master, medium devsel, latency 64, IRQ 3
        Memory at fe8ff000 (32-bit, non-prefetchable) [size=4K]
        Capabilities: [dc] Power Management version 2

JimBass · 04-27-2007, 08:23 PM

Since "unknown device" appears after everything you have in your list, I'd say chances are your board is not yet supported by lm-sensors. Get on the archive of and join their mailing list. Sometimes the reason a board won't work is just because nobody had their hands on one to test out. It also is possible the board won't "play nice" with linux, in which case lm-sensors won't work. It won't work with about half of the devices on my IBM thinkpad T42, and that is fairly common, and made by a very linux friendly company. It more or less is a crapshoot, unless you know ahead that you want lm-sensors to work, so you make sure the board you buy is supported by it.

Peace,
JimBass

hondo · 04-28-2007, 08:52 AM

Hmm, ok. Thanks for the answers. So i guess my board just isnt supported yet. I wanted to do this to make sure that i can set up lm-sensors with the check_sensors plugin so it works in nagios.

When i was one of the tech staff during an event we had some rack servers that, out of what i can remember, worked without any problems with showing the status of the hardware in nagios. So i didnt anticipate any problems with this on my machine, but i now know a little more about this. Maybe ill get onto that mailing list and let them know about the board on my machine.

JimBass · 04-28-2007, 09:41 AM

Nagios is a great tool. I use it at work all the time, more for network monitoring than individual system monitoring. If lm_sensors works, it follows that nagios can grab that data with the plugin and use it. I hope you're able to get some info from the lm_sensors team and see how close you can get things. If it is just that they need info from users, you may be able to get your board included.

So in short, all hope is not lost, but getting it to work will require some form of work.

Peace,
JimBass

hondo · 04-29-2007, 12:39 PM

JimBass: Ok, we used nagios to monitor core switches and routers as well as hosts on the event. When im monitoring hosts and services in nagios its no problem, but i also monitor a router which always is in the "PENDING" state, i have checked the IP-address, but it doesnt seem like there is anything wrong in the config of the router. I use check-host-alive to just check that the router is up and running internally, but it somehow never seems to check this. Do you know what this can be?

JimBass · 04-29-2007, 01:23 PM

You'd have to post the nagios.cfg, hosts.cfg, services.cfg at a bare minimum, or at least the parts in those files that relate to this router.

Also, I'd suggest starting a new thread, as this question has nothing to do with the original.

Peace,
JimBass

patoy · 07-15-2008, 03:22 AM

For my part, lm-sensors is able to display data but in nagios it displays: SENSOR CRITICAL - Sensor alarm detected! and the other one is WARNING - sensors returned state 1

grishu · 11-17-2010, 03:54 PM

How did you managed to fix this issue? I am also facing the same.

Regards,
RG