Re: snmpd crash after "response to proxy request illegal. We're screwed"

Dave Shield <[email protected]>
Newsgroups gmane.network.net-snmp.user
Message-ID <[email protected]>
On 30 March 2011 09:20, Tomasz Chmielewski <[email protected]> wrote:
> Below, two outputs ending with crash:

> Sending 147 bytes to UDP: [127.0.0.1]:1611->[0.0.0.0]:0
> 0000: 30 81 90 02  01 01 04 06  70 75 62 6C  69 63 A0 81    0.......public..
> 0016: 82 02 04 49  42 E3 A5 02  01 00 02 01  00 30 74 30    ...IB........0t0
> 0032: 0E 06 0A 2B  06 01 04 01  82 89 77 0A  09 05 00 30    ...+......w....0
> 0048: 0E 06 0A 2B  06 01 04 01  82 89 77 0A  06 05 00 30    ...+......w....0
> 0064: 0E 06 0A 2B  06 01 04 01  82 89 77 0A  02 05 00 30    ...+......w....0
> 0080: 10 06 0C 2B  06 01 04 01  82 89 77 0A  0D 01 03 05    ...+......w.....
> 0096: 00 30 10 06  0C 2B 06 01  04 01 82 89  77 0A 0D 01    .0...+......w...
> 0112: 02 05 00 30  0E 06 0A 2B  06 01 04 01  82 89 77 0A    ...0...+......w.
> 0128: 06 05 00 30  0E 06 0A 2B  06 01 04 01  82 89 77 0A    ...0...+......w.
> 0144: 01 05 00                                              ...
>
>
> Received 45 byte packet from UDP: [127.0.0.1]:1611->[0.0.0.0]:29711
> 0000: 30 2B 02 01  01 04 06 70  75 62 6C 69  63 A2 1E 02    0+.....public...
> 0016: 04 49 42 E3  A5 02 01 00  02 01 00 30  10 30 0E 06    .IB........0.0..
> 0032: 0A 2B 06 01  04 01 82 89  77 0A 09 81  00             .+......w....

OK - that's definitely useful.
It looks as if the response that comes back is bogus.

What seems to be happening is that the proxied agent (running on port
1161) is asked for several varbinds,   but only returns a value (actually
the exception noSuchInstance) for the first one.
   The Net-SNMP agent is expecting to get a value (or exception) for
*each* of the requested varbinds,   and gets confused when the second
and subsequent varbinds simply aren't there.

You're quite correct - the agent shouldn't crash.   But there's definitely
something wrong with the proxied application.


Let's just check exactly what's happening, by taking the Net-SNMP agent
out of the equation.
Can you please try the following requests, and let us know what response
you get:

   -   snmpget -v 2c -c public  localhost:1161 .1.3.6.1.4.1.34039.10.9

   -   snmpget -v 2c -c public  localhost:1161 .1.3.6.1.4.1.34039.10.9
 .1.3.6.1.4.1.34039.10.9

   -   snmpgetnext -v 2c -c public  localhost:1161 .1.3.6.1.4.1.34039.10.8

   -   snmpgetnext -v 2c -c public  localhost:1161
.1.3.6.1.4.1.34039.10.8  .1.3.6.1.4.1.34039.10.1

   -   snmpgetnext -v 2c -c public  localhost:1161 .1.3.6.1.4.1.34039.10

   -   snmpwalk -v 2c -c public  localhost:1161 .1.3.6.1.4.1.34039.10

Thanks

Dave

------------------------------------------------------------------------------
Enable your software for Intel(R) Active Management Technology to meet the
growing manageability and security demands of your customers. Businesses
are taking advantage of Intel(R) vPro (TM) technology - will your software 
be a part of the solution? Download the Intel(R) Manageability Checker 
today! http://p.sf.net/sfu/intel-dev2devmar
_______________________________________________
Net-snmp-users mailing list
[email protected]
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.