[ First - *please* don't mail me privately, without copying
any responses to the mailing list. I don't have the time
or inclination to offer private, unpaid, SNMP consultancy.
Keep discussions to the list, where others can both learn
and offer advice. Thanks. ]
2009/7/7 François Dumont <francoisdumon...@gmail.com>:
>> I'm not familiar with the python interface, so I can't comment on
>> what the underlying problem might be. You may need to try and
>> pin down the exact characteristics that trigger the problem.
>> Is it a particular type of assignment, or a particular value? Does
>> the order in which assignments are applied make a difference?
>> Is it the same behaviour every time, or is there some element of
>> randomness?
>
> The order of assignements doesn't make a difference, the function take all
> parameters you put in and replace it into the session list. For example, if
> you put DestHost = '127.0.0.1', it replaces DestHost = 'localhost' by
> DestHost = '127.0.0.1'. Because of the predefine name (like DestHost), the
> order is not important.
That's not quite what I meant.
For example - the code that you quoted shows an assignment to
rbQoSProfileName (which works) followed by an assignment to
rbQoSProfileType (which fails).
Do you get the same results if the rbQoSProfileType assignment
comes first, before the rbQoSProfileName assignment?
The script also prompts for "Which QoS Profile to edit", which I
presume is the index to the table. You haven't said anything about
what index value(s) you are trying with.
Do you get this behaviour with every row in the table, or just the
one? What about when you try with a non-existing row vs one
that already exists.
> The behaviour is always the same, there is no randomness.
>
> I'm still trying to find the problem by debogging with pdb.
My basic advice would be to try and reduce the program as much
as possible - paring it down to the bare minimum that still triggers
the problem. Ideally with fixed values rather than prompted ones.
Other thoughts:
- it's not entirely clear to me *what* is seeing the segmentation fault.
The script? The agent? or something else....
- if it's the script that crashes, then it would be useful to check whether
this happens before the SET request is sent out, or when it receives the
response.
If this was a command-line problem (or a C-based program), I'd suggest
turning on the raw packet dumps. I'm not sure what facilities are available
via the python interface, but something similar might help clarify exactly
what is happening.
- It might also be worth crafting an equivalent test program using one
of the other APIs (e.g. perl or C) as a comparison.
Dave
------------------------------------------------------------------------------
Enter the BlackBerry Developer Challenge
This is your chance to win up to $100,000 in prizes! For a limited time,
vendors submitting new applications to BlackBerry App World(TM) will have
the opportunity to enter the BlackBerry Developer Challenge. See full prize
details at: http://p.sf.net/sfu/Challenge
_______________________________________________
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
