Hey Chris, I've reproduced this problem in the underlying hostlist library. I'm working with the maintainer of the library to figure out if there is a bug or if there is a hostrange assumption issue. I noticed your range input was:
0001-319 which internally in hostlist will lead to 0001-0319 Is your intent for xxxx[0001-319] to lead to xxxx0318, xxx0319, etc.? Inputting the later also seems to cause an error, so there probably is a bug somewhere, may it be an input checking bug or an output bug. Al On Wed, 2009-10-14 at 09:43 -0700, Al Chu wrote: > Hey Chris, > > On Wed, 2009-10-14 at 11:53 -0400, Chris Harwell wrote: > > Greetings freeipmi users, > > > > I've really enjoyed using freeipmi - it is a great tool. I > > particularly like how the host range syntax works and simplifies > > certain tasks. > > Thanks. > > > I've recently run into a case where freeipmi fails and hope you can > > offer some help or advice. > > > > This fails: > > ipmi-sensors -g Fan -h xxxx[0001-319]-lom --consolidate-output > > --quiet-readings > > also where the second number is 319 fails. > > > > These invocations work: > > ipmi-sensors -g Fan -h xxxx[0001-319]-lom --consolidate-output > > ipmi-sensors -g Fan -h xxxx[0001-318]-lom --consolidate-output > > --quiet-readings > > ipmi-sensors -g Fan -h xxxx[0001-319]-lom > > ipmi-sensors -g Fan -h xxxx[0001-318]-lom --consolidate-output > > ipmi-sensors -g Fan -h xxxx[0001-319]-lom --consolidate-output > > ipmi-sensors -g Fan -h xxxx[0001-319]-lom --quiet-readings > > > > when it fails the output looks like this: > > $ ipmi-sensors -g Fan -h xxxx[0001-319]-lom --consolidate-output > > --quiet-readings > > pstdout_launch: unknown internal error > > > > I encounter this in the several versions I could check quickly 0.6.5, > > 0.7.12 and 0.7.13: > > :bin$ ipmi-sensors -V > > ipmi-sensors - 0.7.13 > > Copyright (C) 2003-2008 FreeIPMI Core Team > > This program is free software; you may redistribute it under the terms of > > the GNU General Public License. This program has absolutely no warranty. > > drdenws02:bin$ ipmi-sensors -g Fan -h drdb[0001-319]-lom -u ADMIN -p > > ADMIN --consolidate-output --quiet-readings > > pstdout_launch: unknown internal error > > > > debug output is copious, the last bit looks like this: > > xxxx0317-lom: IPMI Command Data: > > xxxx0317-lom: ------------------ > > xxxx0317-lom: [ 3Ch] = cmd[ 8b] > > xxxx0317-lom: [ 0h] = comp_code[ 8b] > > xxxx0317-lom: IPMI Trailer: > > xxxx0317-lom: -------------- > > xxxx0317-lom: [ 23h] = checksum2[ 8b] > > pstdout_launch: unknown internal error > > > > Please advise - am I running into a known limitation or just using > > this wrong? Is there other information I ought to provide? > > In all liklihood there is some corner case in the hostrange parsing. > I'll take a look into it and get back to you if I need any more info. > > Thanks, > Al > > > Thanks in advance, > > Chris Harwell > > > > > > _______________________________________________ > > Freeipmi-users mailing list > > [email protected] > > http://**lists.gnu.org/mailman/listinfo/freeipmi-users > > -- Albert Chu [email protected] Computer Scientist High Performance Systems Division Lawrence Livermore National Laboratory _______________________________________________ Freeipmi-users mailing list [email protected] http://lists.gnu.org/mailman/listinfo/freeipmi-users
