On Tue, Sep 14, 2010 at 11:55 AM, Fulko Hew fulko@gmail.com wrote:
... snip ...
When I ran this test (snmpgetnext), the agent died and needed to be
restarted.
The variable I was querying was:
1.3.6.1.4.1.2021.8.1.103.4294967295 aka 'UCD-SNMP-MIB:extIndex'.
(FYI. it also happens on
On Wed, Sep 15, 2010 at 9:27 AM, Fulko Hew fulko@gmail.com wrote:
On Tue, Sep 14, 2010 at 11:55 AM, Fulko Hew fulko@gmail.com wrote:
... snip ...
When I ran this test (snmpgetnext), the agent died and needed to be
restarted
snmpgetnext -v1 -cpublic -Ir localhost
On 14 September 2010 16:55, Fulko Hew fulko@gmail.com wrote:
When I ran this test, the agent died and needed to be restarted.
The variable I was querying was:
1.3.6.1.4.1.2021.8.1.103.4294967295 aka 'UCD-SNMP-MIB:extIndex'.
Do you get the same problem when querying
On Wed, Sep 15, 2010 at 11:23 AM, Dave Shield d.t.shi...@liverpool.ac.ukwrote:
On 14 September 2010 16:55, Fulko Hew fulko@gmail.com wrote:
When I ran this test, the agent died and needed to be restarted.
The variable I was querying was:
1.3.6.1.4.1.2021.8.1.103.4294967295 aka
On Wed, Sep 15, 2010 at 12:01 PM, Fulko Hew fulko@gmail.com wrote:
On Wed, Sep 15, 2010 at 11:23 AM, Dave Shield
d.t.shi...@liverpool.ac.ukwrote:
On 14 September 2010 16:55, Fulko Hew fulko@gmail.com wrote:
When I ran this test, the agent died and needed to be restarted.
The
I've been coding and testing my 'client agent' test suite,
and while testing it against Net-SNMP (5.4.2.1) on Fedora 8
I've been able to lock up the client.
The test I am performing is:
'Test that end of table handling properly goes to the next variable.'
I do this by:
'Determine the last
