[RADIATOR] SNMPAgent and high peak in cacti graph at logrotate

[Hugh Irvine]

Hello Dennis -

As Barry notes (thanks Barry), it is much preferable to use the  
Radiator special characters to generate log files.

Barry's example willl generate a new file every night at midnight  
with filenames of the form:

	/var/log/radiator/20081003.log

See section 5.2 in the Radiator reference manual ("doc/ref.pdf").

hope that helps

regards

Hugh


On 3 Oct 2008, at 01:07, Barry Ard wrote:

> Dennis Ortsen wrote:
>> Hello all,
>>
>> we have 2 radiator 4.3.1-1 (RPM) instances running on 2 RHEL5.2  
>> server. On both we have enabled the SNMPAgent to monitor  
>> Challenges, Requests, Accepts in Authentication and we monitor  
>> Authentication errors in cacti (rrdtool). The SNMPAgent works  
>> fine, monitoring in cacti also works fine, but every night at  
>> 04:00 all graphs in cacti show a huge peak. This is exactly the  
>> same time that the servers rotate their logfiles. When radiator  
>> gets its logfile rotated, a SIGHUP signal is sent to the radiuspid  
>> to force radiator to use the new logfile. My guess is that this  
>> SIGHUP signal is causing the SNMPAgent to "reset" itself too,  
>> which results in the huge peak in the cacti graphs. This behaviour  
>> renders the cacti graphs unusable, while it is actually a nice  
>> collection of statistics we can use to better understand  
>> authentication errors in our wireless network.
>>
>> Is there a way to get rid of that peak, in other words, make sure  
>> that the SNMPAgent doesn't get "reset" or skips the result of the  
>> peak?
>>
>> SNMPAgent config section:
>> ==========================================
>> <SNMPAgent>
>>         ROCommunity some_string
>> </SNMPAgent>
>> ==========================================
>>
>> current logrotate script for radiator:
>> ==========================================
>> /var/log/radius/logfile {
>>     rotate 2
>>     size 50M
>>     daily
>>     postrotate
>>         /bin/kill -HUP `cat /var/log/radius/radiusd.pid 2> /dev/ 
>> null` 2> /dev/null || true
>>     endscript
>> }
>> ==========================================
>>
>> Thanks in advance,
>>
>> with kind regards,
>>
>> Dennis Ortsen
>> HAN University
>>
>>
>>
>>
>> _______________________________________________
>> radiator mailing list
>> radiator at open.com.au
>> http://www.open.com.au/mailman/listinfo/radiator
>>
> Why bother using logrotate but use the radiator defined "Special  
> Characters" to specify the logfile, like:
> LogFile /var/log/radiator/%Y%m%d.log
>
> Barry
>
> _______________________________________________
> radiator mailing list
> radiator at open.com.au
> http://www.open.com.au/mailman/listinfo/radiator



NB:

Have you read the reference manual ("doc/ref.html")?
Have you searched the mailing list archive (www.open.com.au/archives/ 
radiator)?
Have you had a quick look on Google (www.google.com)?
Have you included a copy of your configuration file (no secrets),
together with a trace 4 debug showing what is happening?
Have you checked the RadiusExpert wiki:
http://www.open.com.au/wiki/index.php/Main_Page

-- 
Radiator: the most portable, flexible and configurable RADIUS server
anywhere. Available on *NIX, *BSD, Windows, MacOS X.
Includes support for reliable RADIUS transport (RadSec),
and DIAMETER translation agent.
-
Nets: internetwork inventory and management - graphical, extensible,
flexible with hardware, software, platform and database independence.
-
CATool: Private Certificate Authority for Unix and Unix-like systems.