Ping me after the new year and we can look at it more. I'd like to see the debug output of a --bridge-sensors with one of those ambient sensors.
That's the one I expected to work. Not what's going on. Could be some subtle bug ... or possibly an internal timeout or something. Al On Fri, 2013-12-20 at 14:33 +0000, Dave Love wrote: > Albert Chu <ch...@llnl.gov> writes: > > > On Thu, 2013-12-19 at 11:56 +0000, Dave Love wrote: > >> I realized that the system that caused the crash has 601 sensors; really. > >> Patch attached. > > > > Well how about that :-) > > I should have apologized for not looking properly to start with, as the > stack had been smashed. > > > Could you try running w/ --bridge-sensors > > That's _very_ slow, and still gives N/A. > > > or the 'assumebmcowner' > > workaround. The sensor isn't owned by the BMC, leading to the N/A. > > The workaround doesn't make any difference. > > I don't know how it's done on the system, and I'm not sure we have > useful technical docs, but the individual BMCs in the component boxes > all report the sensors in all four boxes as far as I can tell. > > This is a bit of an annoyance for our monitoring, but not a big deal, > but I can look again in the new year if you would like to address it. -- Albert Chu ch...@llnl.gov Computer Scientist High Performance Systems Division Lawrence Livermore National Laboratory _______________________________________________ Freeipmi-devel mailing list Freeipmi-devel@gnu.org https://lists.gnu.org/mailman/listinfo/freeipmi-devel
