[AGENT++] agent stopped after changing the snmpversion

Frank Fock fock at agentpp.com
Mon Apr 13 11:21:17 CEST 2009


Hi Venkataraman,

Sorry, I was mislead by the brace indenting. Jochen has found
the cause correctly.

You can modify the VACM at runtime. Getting a global lock
with mib_lock() is a good idea when doing so.
In any case, the VACM can be modified through SNMP
message from an authorized user at any time.

Best regards,
Frank

Ramasubramanian Venkataraman schrieb:
> Hi Frank and Jochen ,
>
> I will remove the LOG_BEGIN(ERROR_LOG | 0); Meanwhile, i dont see any problem with my code. The braces are correctly set.
>
> I have the agent which loads the USM users from a config file(say usm.conf) and Other configurations  in agent.conf, like
>
> agent_mode = can be secured(v3) or un-secured(v1)
> agent_logging = true/false // enable or disable the agent++ logging
> set/get community string for V1
>
> I read the community string and adding to the vacum only. i have created readview and writeview and creating the  addNewAccessEntry s also. 
> FYI, whenever i change the community string, agent works correctly with that community strings. 
>
> The agent was working fine when the agent_mode is set to V1. It accepts both v1,v3 requests and it was running quite a long time.
> When the agent mode is set to v3; it should accept only v3 requst. So,we are removing the v1 requests from the RequestList.
>
> My requirement is not to take V1 request when agent mode is secure(v3). So right now i m chking the request version and removing it from the requestList.
> I dont know whether it causing the problem.
>
> Please let me know if i can remove the vacum group for v1 when the agent mode is set to V3. So that agent itself will send an error.
> I can add the vacum group later if the agent mode is v1. Please let me know your comments.
>
> Thanks in Advance,
> Venkataraman
>
>
>
>
>
> ________________________________
> From: Jochen Katz <katz at agentpp.com>
> To: agentpp at agentpp.org
> Sent: Friday, 10 April, 2009 4:32:12 PM
> Subject: Re: [AGENT++] agent stopped after changing the snmpversion
>
> Hi,
>
>   
>> In the meantime if there is a V3 request comes, then agent process is
>> stopped with no cores. We dont have any clues in that case.
>>     
>
>   
>> LOG_BEGIN(ERROR_LOG | 0);
>>     
>
> an error log with level 0 will stop your agent. I have put the note
> about this from the LogEntry class constructor to the class description.
> And the log string will be extended by a "Exiting now".
>
> Remember that a client can also send SNMPv2c requests to the agent.
>
> Regards,
>   Jochen
> _______________________________________________
> AGENTPP mailing list
> AGENTPP at agentpp.org
> http://lists.agentpp.org/mailman/listinfo/agentpp
>
>
>
>       Add more friends to your messenger and enjoy! Go to http://messenger.yahoo.com/invite/
> _______________________________________________
> AGENTPP mailing list
> AGENTPP at agentpp.org
> http://lists.agentpp.org/mailman/listinfo/agentpp
>   





More information about the AGENTPP mailing list