RE: dropping bad AgentX request (wrong mode 2)

Hi there,

I took a look at the logs generated, and it looked like somehow commitset was received twice, and the subagent generated the "wrong mode 2" upon receipt of the 2nd commitset.  I was using the net-snmp's snmpset to issue the SET command.

Is there anything I can do to avoid the receipt of the second commitset from AgentX somehow?

Thank you very much for your help!

Yiwen
> agentx/subagent: handling agentx request 
> (req=0x11e,trans=0x11d,sess=0x21)
> agentx/subagent:   -> testset
> agentx/subagent: checking status of session 0x8695c30
> internal:appRunTable:_cache_free: called
> internal:appRunTable:_container_free: called
> verbose:appRunTable:appRunTable_container_free: called
> internal:appRunTable:_cache_load: called
> verbose:appRunTable:appRunTable_container_load: called
> internal:appRunTable:appRunTable_allocate_rowreq_ctx: called
> verbose:appRunTable:appRunTable_rowreq_ctx_init: called
> verbose:appRunTable:appRunTable_indexes_set: called
> verbose:appRunTable:appRunTable_indexes_set_tbl_idx: called
> verbose:appRunTable:appRunTable_index_to_oid: called
> verbose:appRunTable:appRunTable_container_load: inserted 1 records
> internal:appRunTable:_mfd_appRunTable_pre_request: called
> verbose:appRunTable:appRunTable_pre_request: called
> internal:appRunTable:_mfd_appRunTable_object_lookup: called
> verbose:appRunTable:appRunTable_row_prep: called
> internal:appRunTable:_mfd_appRunTable_check_objects: called
> internal:appRunTable:_appRunTable_check_column: called for 8
> verbose:appRunTable:appRunAdminState_check_value: called
> agentx/subagent: synching input, op 0x01
> agentx/subagent: handling agentx subagent set response 
> (mode=162,req=0x11e,trans=0x11d,sess=0x21)
> agentx/subagent:   going from RESERVE1 -> RESERVE2
> agentx/subagent: session 0x8695c30 responded to ping
> internal:appRunTable:_mfd_appRunTable_undo_setup: called
> verbose:appRunTable:appRunTable_allocate_data: called
> verbose:appRunTable:appRunTable_undo_setup: called
> internal:appRunTable:_appRunTable_undo_setup_column: called for 8
> verbose:appRunTable:appRunAdminState_undo_setup: called
> agentx/subagent: handling agentx subagent set response 
> (mode=162,req=0x11e,trans=0x11d,sess=0x21)
> agentx/subagent:   FINISHED
> agentx/subagent: handling agentx request 
> (req=0x11f,trans=0x11d,sess=0x21)
> agentx/subagent:   -> commitset
First commitset received

> internal:appRunTable:_mfd_appRunTable_set_values: called
> internal:appRunTable:_appRunTable_set_column: called for 8
> verbose:appRunTable:appRunAdminState_set: called
> internal:appRunTable:_mfd_appRunTable_check_dependencies: called
> internal:appRunTable:appRunTable_check_dependencies: called
> internal:appRunTable:_mfd_appRunTable_commit: called
> verbose:appRunTable:appRunTable_commit: called
> appRunTable:appRunTable_dirty_set: called. was 0, now 1
> agentx/subagent: handling agentx request 
> (req=0x11f,trans=0x11d,sess=0x21)
> agentx/subagent:   -> commitset
Second commitset received

> dropping bad AgentX request (wrong mode 2)
> agentx/subagent: handling agentx subagent set response 
> (mode=162,req=0x11f,trans=0x11d,sess=0x21)
> agentx/subagent:   FINISHED
> agentx/subagent: handling agentx request 
> (req=0x121,trans=0x11d,sess=0x21)
> agentx/subagent:   -> cleanupset
> agentx/subagent: handling agentx request 
> (req=0x122,trans=0x120,sess=0x21)
> agentx/subagent:   -> testset
> internal:appRunTable:_mfd_appRunTable_irreversible:commit: called
> internal:appRunTable:_mfd_appRunTable_undo_cleanup: called
> verbose:appRunTable:appRunTable_undo_cleanup: called
> verbose:appRunTable:appRunTable_release_data: called
> internal:appRunTable:_mfd_appRunTable_post_request: called
> verbose:appRunTable:appRunTable_post_request: called
> appRunTable:appRunTable_dirty_set: called. was 1, now 0
> agentx/subagent: handling agentx subagent set response 
> (mode=162,req=0x121,trans=0x11d,sess=0x21)
> agentx/subagent:   FINISHED
> internal:appRunTable:_cache_free: called
> internal:appRunTable:_container_free: called
> verbose:appRunTable:appRunTable_container_free: called
> internal:appRunTable:_container_item_free: called
> internal:appRunTable:appRunTable_release_rowreq_ctx: called
> verbose:appRunTable:appRunTable_rowreq_ctx_cleanup: called
> internal:appRunTable:_cache_load: called
> verbose:appRunTable:appRunTable_container_load: called
> verbose:appRunTable:appRunTable_container_load: inserted 0 records
> internal:appRunTable:_mfd_appRunTable_pre_request: called
> verbose:appRunTable:appRunTable_pre_request: called
> internal:appRunTable:_mfd_appRunTable_object_lookup: called
> agentx/subagent: handling agentx subagent set response 
> (mode=162,req=0x122,trans=0x120,sess=0x21)
> agentx/subagent:   FINISHED
> agentx/subagent: handling agentx request 
> (req=0x123,trans=0x120,sess=0x21)
> agentx/subagent:   -> cleanupset
> internal:appRunTable:_mfd_appRunTable_post_request: called
> verbose:appRunTable:appRunTable_post_request: called
> agentx/subagent: handling agentx subagent set response 
> (mode=162,req=0x123,trans=0x120,sess=0x21)
> agentx/subagent:   FINISHED
> ^CappRunTable_subagent: select returns: -1
> agentx/subagent: shutting down session....
> agentx/subagent: closing session
> agentx/subagent: synching input, op 0x01
> agentx/subagent: closed
> agentx/subagent: shut down finished.
> 
------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security 
threats, fraudulent activity, and more. Splunk takes this data and makes 
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2d-c2
_______________________________________________
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