[AGENT++] agent stopped after changing the snmpversion

[Frank Fock]

Hi Venkataraman,

You do not need to change these log levels,
as these occur on severe misconfigurations
of the agent only. In those cases, the agent
cannot proceed running (otherwise a seg.fault
would occur).

Best regards,
Frank

Ramasubramanian Venkataraman wrote:
> Hi Frank and Jochen,
> 
> Thanks a lot for your solution. Now i changed the error_log level and its working well. But in agent++ api, i found in few places the ERROR_LOG is set to 0.
> Please let me know if we need to change that aswell.
> 
> We are using AGENT++ API Version 3.5.27b
> 
> 
> mib_proxy.cpp:400:              LOG_BEGIN(ERROR_LOG | 0);
> notification_originator.cpp:175:                        LOG_BEGIN(ERROR_LOG | 0);
> notification_originator.cpp:299:                LOG_BEGIN(ERROR_LOG | 0);
> proxy_forwarder.cpp:134:                LOG_BEGIN(ERROR_LOG | 0);
> request.cpp:1191:               LOG_BEGIN(ERROR_LOG | 0);
> request.cpp:1197:               LOG_BEGIN(ERROR_LOG | 0);
> snmp_community_mib.cpp:201:       LOG_BEGIN(ERROR_LOG | 0);
> snmp_community_mib.cpp:506:       LOG_BEGIN(ERROR_LOG | 0);
> snmp_request.cpp:602:           LOG_BEGIN(ERROR_LOG | 0);
> threads.cpp:212:                LOG_BEGIN(ERROR_LOG | 0);
> threads.cpp:221:                LOG_BEGIN(ERROR_LOG | 0);
> v3_mib.cpp:192:   LOG_BEGIN(ERROR_LOG | 0);
> v3_mib.cpp:392:    LOG_BEGIN(ERROR_LOG | 0);
> v3_mib.cpp:889:    LOG_BEGIN(ERROR_LOG | 0);
> v3_mib.cpp:1554:    LOG_BEGIN(ERROR_LOG | 0);
> v3_mib.cpp:1607:    LOG_BEGIN(ERROR_LOG | 0);
> 
> 
> 
> 
> 
> ________________________________
> From: Frank Fock <fock at agentpp.com>
> To: Ramasubramanian Venkataraman <venkiram_be at yahoo.co.in>
> Cc: Jochen Katz <katz at agentpp.com>; agentpp at agentpp.org
> Sent: Monday, 13 April, 2009 2:51:17 PM
> Subject: Re: [AGENT++] agent stopped after changing the snmpversion
> 
> 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
>>  
> 
> 
>       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

-- 
AGENT++
http://www.agentpp.com
http://www.snmp4j.com
http://www.mibexplorer.com
http://www.mibdesigner.com