hi dave,

ok, so here's how this section started (CISCO-FLASH-MIB):

ChecksumString ::= TEXTUAL-CONVENTION
         DISPLAY-HINT "x"
         STATUS  current
         DESCRIPTION
                 "Represents the checksum of a file.
                 "
         SYNTAX  OCTET STRING


and here's what it looked like after i made the change you suggested:

ChecksumString ::= TEXTUAL-CONVENTION
         DISPLAY-HINT "1x"
         STATUS  current
         DESCRIPTION
                 "Represents the checksum of a file.
                 "
         SYNTAX  OCTET STRING

and now snmpbulkwalk completes just fine, no hangs

i've backed out the change and replicated the hang


i found a paragraph on DISPLAY-HINT in Perkins/McGinnis ... but i don't 
think i'm wiser for it

anyway, if there's anything i can do to help you track this down 
further, plse let me know.  in any case, thank you for your assistance!

--sk


Dave Shield wrote:
> On 28/09/06, Stuart Kendrick <[EMAIL PROTECTED]> wrote:
>> #2  0x00002b9ec19cdec6 in sprint_realloc_octet_string 
>> (buf=0x7fffe92142d0,
>>      buf_len=0x7fffe92142c8, out_len=0x7fffe92142c0, allow_realloc=1,
>>      var=0x2161cb0, enums=0x0, hint=0x1d4e521 "", units=0x0) at mib.c:525
> 
> I haven't had the chance to look at this dump in detail.
> [It's been manic at work, with the main staff fileserver giving up the
> ghost at regular intervals]
> But I'm somewhat suspicious of that   hint=""  parameter.
> 
>> ok, after some poking ... yes, the walk hangs in different places ...
>> but always within the same MIB.  remove that MIB file ... and presto!
>> the walk completes just fine.
> 
>> i grabbed the latest copy of this MIB file from the manufacturer
>> (CISCO-FLASH-MIB) ... same problem
>>
>> ok, so there's something gross inside this MIB file
> 
> Ummm...
> I can't immediately see anything wrong.
> It might be useful to identify the MIB object that it's trying to work 
> with.
> 
> type "up" twice (to get to level 2), then "p *var"
> What do  name, name_len and name_loc look like?
> 
> The only other thing that springs to mind is to tweak the two
> DISPLAY-HINTs in this MIB file to read "1x:1x" and "1x" respectively
> (rather than "x:x" and "x").   That shouldn't make a difference, but
> it's worth a try.
> 
> Dave

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Net-snmp-users mailing list
Net-snmp-users@lists.sourceforge.net
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users

Reply via email to