Re: core dump while agentx subagent destroy a row with rowstatus

On Wed, 3 Nov 2010 18:34:58 +0100 Claus wrote: CK> It happens while de-allocate an index of a shared table which was CK> never allocated. CK> The core dump does not ocure every time, its depends on the agentx CK> traffic so far, CK> but the session times out and the subagent mib vars are never

Re: core dump while agentx subagent destroy a row with rowstatus

I create a row with set the RowStatus = createAndGo, set > the > CK> row object (in my example a DisplayString). > CK> Than I destroy this row again. > CK> > CK> While de-register the row, while working on the snmpset > CK> request ...RowStatus = destroy > CK> th

Re: core dump while agentx subagent destroy a row with rowstatus

On Thu, 28 Oct 2010 20:43:21 +0200 Claus wrote: CK> I am working with net-snmp as master agent and a subagent which CK> register a private MIB with a table. CK> CK> First I create a row with set the RowStatus = createAndGo, set the CK> row object (in my example a DisplayStri

core dump while agentx subagent destroy a row with rowstatus

Hi, I am working with net-snmp as master agent and a subagent which register a private MIB with a table. First I create a row with set the RowStatus = createAndGo, set the row object (in my example a DisplayString). Than I destroy this row again. While de-register the row, while

Re: RowStatus for read only agent

On 12 April 2010 10:39, Robert Story wrote: > On Mon, 12 Apr 2010 09:04:31 +0100 Dave wrote: > DS> My take on this would be that if the table doesn't allow rows to be > DS> created or deleted dynamically via SNMP SET requests, then it should > DS> not contain a RowStatus

Re: RowStatus for read only agent

On Mon, 12 Apr 2010 09:04:31 +0100 Dave wrote: DS> My take on this would be that if the table doesn't allow rows to be DS> created or deleted dynamically via SNMP SET requests, then it should DS> not contain a RowStatus column in the first place. If there were a standard object

Re: RowStatus for read only agent

On 12 April 2010 02:36, Robert Story wrote: > On Sun, 11 Apr 2010 19:53:23 + Scott wrote: > GS> When I set the MAX-ACCESS for a RowStatus to read-only in the MIB then > smilint reports: > GS> "[4] {rowstatus-access} warning: illegal `RowStatus' access value&q

Re: RowStatus for read only agent

On Sun, 11 Apr 2010 19:53:23 + Scott wrote: GS> When I set the MAX-ACCESS for a RowStatus to read-only in the MIB then smilint reports: GS> "[4] {rowstatus-access} warning: illegal `RowStatus' access value" GS> GS> So I'm trying to figure out if the table is

RE: RowStatus for read only agent

When I set the MAX-ACCESS for a RowStatus to read-only in the MIB then smilint reports: "[4] {rowstatus-access} warning: illegal `RowStatus' access value" So I'm trying to figure out if the table is always going to be read only if I should include RowStatus or not and wha

Re: RowStatus for read only agent

On Fri, 9 Apr 2010 21:43:47 + Scott wrote: GS> The SNMP agent I work on is read only. Do the tables need a RowStatus GS> column or should they not have it since the row(s) can never be modified? That's a personal choice for the MIB author. If the table is defined with all colu

RowStatus for read only agent

The SNMP agent I work on is read only. Do the tables need a RowStatus column or should they not have it since the row(s) can never be modified? If the RowStatus column is used should it be set to "notInService(2)" since it's not available for use by a

Re: RowStatus type mib2c template problem

et Subject Re: RowStatus type mib2c template p

Re: RowStatus type mib2c template problem

are using 5.3.1. Then the reported EYC> RowStatus segmentation fault occurs. EYC> The same code didn't cause segmentation fault with 5.2.1. Ok... assuming you did at least recompile/relink the subagent against the 5.3 headers and libraries and it still crashes, there are 2 options: a) tr

Re: RowStatus type mib2c template problem

Hi Robert, The code was generated using 5.2.1 with mib2c.mfd.conf. I recently upgraded to Net-SNMP 5.3.1, although my subagent didn't change, the master agent and shared library are using 5.3.1. Then the reported RowStatus segmentation fault occurs. The same code didn't cause segmenta

Re: RowStatus type mib2c template problem

On Wed, 17 Jan 2007 10:03:56 -0600 [EMAIL PROTECTED] wrote: EYC> Dear net-snmp-coders, EYC> EYC> I found a problem in RowStatus type template generated by mib2c.mfd.conf or EYC> mib2c. container.conf. The current template will cause segmentation fault EYC> when getting a not ye

RowStatus type mib2c template problem

Dear net-snmp-coders, I found a problem in RowStatus type template generated by mib2c.mfd.conf or mib2c. container.conf. The current template will cause segmentation fault when getting a not yet created entry after _mfd_xxx_get_value and _mfd_xxx_get_column. It seems function

MFD RowStatus example

Hello coders, It's nice that I implemented RowStatus Table by using mfd.conf, on NET-SNMP v5.3.0.1 (v5.3.1 will ok). Scenario: A SNMP client will tell the sub-agent server_ip, server_port, game_ip and game_port, so the sub-agent could notify the correct server to deny that game&

Re: Dynamic Row Creation/Deletion using "RowStatus" Col

On Fri, 2005-10-14 at 21:27 +0530, [EMAIL PROTECTED] wrote: > Thank you very much for your great help/support. > I tried to correct the following methods: > > myTable_addEntry(...) > myTable_create_data_context(...) > etc. > > But the problem which I am facing that when I apply "snmpset" > the

Re: Dynamic Row Creation/Deletion using "RowStatus" Col

Hi Dave, Thank you very much for your great help/support. I tried to correct the following methods: myTable_addEntry(...) myTable_create_data_context(...) etc. But the problem which I am facing that when I apply "snmpset" the control never goes to the above specified methods. In normal case t

Re: Dynamic Row Creation/Deletion using "RowStatus" Col

On Wed, 2005-10-12 at 20:41 +0530, [EMAIL PROTECTED] wrote: > Kindly find attached file for the code reference. > struct spiConnEntry * > spiConnTable_addEntry(long atca910xSpiConnectionId ) > { > spiConnEntry *entry; > entry = (spiConnEntry *)malloc(sizeof(spiConnEntry)); [SNIP]

Re: Dynamic Row Creation/Deletion using "RowStatus" Col

using MGSOFT browser,It says no row creation. Steps which I followed: === 1. Select Rowstatus col as cretaeAndGo 2. Addrow 3. Commit Message : commit Failed. OID failed during set operation(No creation) During this operation control never goes to the respective

Re: Dynamic Row Creation/Deletion using "RowStatus" Col

On Wed, 2005-10-12 at 11:36 +0530, [EMAIL PROTECTED] wrote: > Please do help me if anyone has implemented "RowStatus" > for dynamic row creation/deletion. There are assorted examples of dynamic row creation/deletion in the source distribution, using a variety of MIB helpers. I&#x

Re: Dynamic Row Creation/Deletion using "RowStatus" Col

nnTable.c - spiConnTable_access.c etc. Please do help me if anyone has implemented "RowStatus" for dynamic row creation/deletion. Any help would be very greatly appreciated. Thank in advance. Regards/ Devendra The information contained in this electronic message and any attachm

Re: Dynamic Row Creation/Deletion using "RowStatus" Col

On Sat, 8 Oct 2005 12:12:35 +0530 [EMAIL PROTECTED] wrote: DCI> - To generate the code I have used - DCI> "mib2c.access_functions.conf" scripts. That script is not intended to be used directly - is it part of the mib2c.iterate_access.conf. -- NOTE: messages sent directly to m

Dynamic Row Creation/Deletion using "RowStatus" Col

response). */ int set_atca910xSpiRowStatus(void *data_context, long *val, size_t val_len) { return SNMP_ERR_NOERROR; /** XXX: change if an error occurs */ } QUES4: What about "RowStatus" col. How do I handle the following states? 1. Active 2. no

Re: setting RowStatus to NOSUCHOBJECT crashes agent?

On Wed, 31 Aug 2005 11:45:41 -0400 Philip W (Philip) wrote: GPW> Then we hit the SET button. We're trying to make sure bad GPW> values don't crash things. We found that the agent crashes (segmentation GPW> violation) before it calls our handler. What kind of handler is it? If you are having pr

setting RowStatus to NOSUCHOBJECT crashes agent?

Hello All. We're seeing the following problem. We use a mib browser that let us set variables, and it reads the current value first. We read a table row (that has RowStatus), and it does not exist, so RowStatus shows as NOSUCHOBJECT. Then we hit the SET button. We're trying to

Re: RowStatus =active Transition

On Thu, 2005-08-25 at 00:05 +0200, Anthony Novatsis wrote: > If the RowStatus=active occurs when there are still other columns > which are noSuchInstance (and these are not in the same PDU). In > other words, the RowStatus=active is premature. In this case, the > agent s

RowStatus =active Transition

Hello all, I am implementing the code for a table for the createAndWait method. The RowStatus is first set to createAndWait (which actually sets the value to notReady since other column values must be set). Afterward, other columns are set and then the RowStatus is set to active. If the

Re: rowstatus

>>>>> On Mon, 29 Nov 2004 12:26:52 -0500, "Gillis, Philip W (Philip)" <[EMAIL >>>>> PROTECTED]> said: Philip> I'm trying to understand row creation when I use mib2c's Philip> create-dataset.conf. I have a test table (below) with an P

rowstatus

I'm trying to understand row creation when I use mib2c's create-dataset.conf. I have a test table (below) with an index, a rowstatus, and a plain variable. If I set the plain variable with an index that does not exist yet, the row gets created. If I set the rowstatus to createAnd

Re: user-array: row deletion and RowStatus

the semantics of the TC completely. Using a RowStatus column to indicate the operational state of a row may well be frowned on, but does still correspond to the basic descriptions of these values. (Though I'll accept that specifying an infinite timeout is probably stretching the s

Re: user-array: row deletion and RowStatus

The argument that you don't want to create another column to handle state or operational status is a weak one. Considering how hard it is interpret the RowStatus TC as it is, do you really think overloading it for another use is wise? Woul

Re: user-array: row deletion and RowStatus

>>>>> On Wed, 24 Nov 2004 10:42:05 -0800 (PST), "David T. Perkins" <[EMAIL >>>>> PROTECTED]> said: David> Well, this discussion points out the problems with the David> RowStatus model, and is a demonstration why many MIB David> definitions a

Re: user-array: row deletion and RowStatus

make them available, regardless of their physical status, and thus the status should remain notInService. Actually, I'd probably even argue that they should remain active, since it is the 'RowStatus', not the 'ToasterStatus' object. WH> EG for Robert: consider the SPD M

Re: user-array: row deletion and RowStatus

HI, Well, this discussion points out the problems with the RowStatus model, and is a demonstration why many MIB definitions and agent designs support ONLY values createAndGo(4), active(1), and destroy(6). To support other values requires that the resource manager or most probably the agent to

Re: user-array: row deletion and RowStatus

On Wed, 24 Nov 2004 09:19:57 -0800 Wes wrote: WH> Dave> I would hope that such managers wouldn't misinterpret this WH> Dave> definition as saying that this *must* be 5 minutes. Definitely agree w/Dave here... -- Robert Story; NET-SNMP Junkie Support: Archive:

Re: user-array: row deletion and RowStatus

> On Wed, 24 Nov 2004 16:58:25 +, Dave Shield <[EMAIL PROTECTED]> said: >> The only issue would then be a manager that expects a certain >> behavior of the TC (which is what it has to go on). Dave> Including parsing the free text of the MIB description, I trust. No. Dave> I would hope t

Re: user-array: row deletion and RowStatus

> On Wed, 24 Nov 2004 15:32:31 +, Dave Shield <[EMAIL PROTECTED]> said: Robert> notReady is only used during row creation Dave> Where does it say that? My guess is that Dave is right, but it should rarely happen. You could put a row into notInService and then it could transition from th

Re: user-array: row deletion and RowStatus

Dave> I suggest you take a closer look at the DESCRIPTION field of Dave> such MIB objects as NET-SNMP-AGENT-MIB::nsDebugTokenStatus, Dave> nsLogStatus and NET-SNMP-EXTEND-MIB::nsExtendStatus Wes> Ahh... getting around TC definitions by changing it post-call. Chamging it? I'm just following the

Re: user-array: row deletion and RowStatus

> On Wed, 24 Nov 2004 15:55:02 +, Dave Shield <[EMAIL PROTECTED]> said: Dave> I suggest you take a closer look at the DESCRIPTION field of such Dave> MIB objects as NET-SNMP-AGENT-MIB::nsDebugTokenStatus, nsLogStatus Dave> and NET-SNMP-EXTEND-MIB::nsExtendStatus One last point: The IETF

Re: user-array: row deletion and RowStatus

> On Wed, 24 Nov 2004 15:55:02 +, Dave Shield <[EMAIL PROTECTED]> said: Dave> I suggest you take a closer look at the DESCRIPTION field of Dave> such MIB objects as NET-SNMP-AGENT-MIB::nsDebugTokenStatus, Dave> nsLogStatus and NET-SNMP-EXTEND-MIB::nsExtendStatus Ahh... getting around TC

Re: user-array: row deletion and RowStatus

Dave> Then a fuse blows, and all the toasters are knocked out. Dave> Fortunately the SNMP device is powered via a UPS, so can Dave> report the fact ('notReady'). Wes> FYI, the notReady state is not supposed to be used for not active Wes> conditions. Specifically, the r

Re: user-array: row deletion and RowStatus

Dave> Hmmm... I see what you mean, but I don't think it's as simple as that. Dave> The RowStatus TC feels to be somewhat ambiguous (if not inconsistent). Robert> Yep, I notices the sufficient wording too. I've been hoping that Robert> Mr. Perkins would jump in h

Re: user-array: row deletion and RowStatus

otReady state is not supposed to be used for not active conditions. Specifically, the rowstatus TC actually says that rows with a status of notReady are supposed to be automatically cleaned by the agent. You happen to be lucky that the time between automatic cleans in the Net-SNMP agent is infin

Re: user-array: row deletion and RowStatus

On Wed, 24 Nov 2004 10:45:03 + Dave wrote: DS> Dave> I can envisage situations where a table might well be missing two DS> Dave> or three "minor" column values, but still be ready to go live. DS> Robert> I think that the RowStatus TC doesn't allow that. DS&g

Re: user-array: row deletion and RowStatus

Dave> I can envisage situations where a table might well be missing two Dave> or three "minor" column values, but still be ready to go live. Robert> I think that the RowStatus TC doesn't allow that. Hmmm... I see what you mean, but I don't think it's as simp

Re: user-array: row deletion and RowStatus

On Tue, 23 Nov 2004 15:14:20 + Dave wrote: DS> > It wouldn't be too hard to add a flag which could be set during DS> > registration, and would signal the helper to not create the row. DS> DS> It wouldn't even have to change the API. DS> DS> The final parameter to 'netsnmp_table_container_regi

Re: user-array: row deletion and RowStatus

> It wouldn't be too hard to add a flag which could be set during > registration, and would signal the helper to not create the row. It wouldn't even have to change the API. The final parameter to 'netsnmp_table_container_register' is currently a boolean flag to control whether rows should be gr

Re: user-array: row deletion and RowStatus

a value specified Once all columns have values, the row DS> > transitions to notInService. DS> DS> That feels basically right, if a little simplistic. DS> I can envisage situations where a table might well be missing two DS> or three "minor" column values, but s

Re: user-array: row deletion and RowStatus

> The generated code could be tweaked to detect completely invalid RowStatus > creation attempts (eg no RowStatus varbind in the request) in reserve1 > fairly easily Hmmm... I suppose so. It feels a bit clunky, but should work. Things would get much more cumbersome if the "row

Re: user-array: row deletion and RowStatus

On Sun, 21 Nov 2004 22:06:56 + Dave wrote: DS> DS>The 'create_row' hook DS> DS> seems to activate the automatic creation of rows ... But this DS> DS> isn't what's needed for a pure RowStatus-controlled table. DS&g

Re: user-array: row deletion and RowStatus

s :-) DS>The 'create_row' hook DS> seems to activate the automatic creation of rows ... But this DS> isn't what's needed for a pure RowStatus-controlled table. RS> Hmm... ok, what is needed? Well, as I understand it, there a

Re: user-array: row deletion and RowStatus

seems to be some code within the helper handler DS> itself for deleting a row, but this seems to be linked with the DS> RowStatus checking, rather than anything more general. The array-user helper is pretty insistent about doing the insertion (other than at startup) and deletion for you.

user-array: row deletion and RowStatus

There seems to be some code within the helper handler itself for deleting a row, but this seems to be linked with the RowStatus checking, rather than anything more general. What's the approved way for removing a row using this helper? The other area that I'm not clear about yet is how

Re£º: Re: RowStatus does not transition to active from createAndGo

ot;kajtzu"."ABC" = STRING: > "212.226.226.1" > DISMAN-NSLOOKUP-MIB::lookupCtlOperStatus."kajtzu"."ABC" = INTEGER: > notStarted(2) > DISMAN-NSLOOKUP-MIB::lookupCtlTime."kajtzu"."ABC" = Gauge32: 0 milliseconds > DISMAN-NS