(RADIATOR) Memory Leak problem

[PREVOSTO, Laurent]

> -----Message d'origine-----
> De : Olivier Macchioni 
> [mailto:olivier.macchioni at swisscom-eurospot.com] 
> Envoyé : vendredi 23 juin 2006 13:00
> À : PREVOSTO, Laurent
> Cc : radiator at open.com.au
> Objet : Re: (RADIATOR) Memory Leak problem
> 
> PREVOSTO, Laurent wrote:
> 
> >I've tracked the different arrays that belong to the 
> AuthRADIUS class during the last hours (%pendingRequests, 
> %sockets, %identifiers, %psIds) but the size is stable. 
> Anyway i'm quite sure the size of the process grows in 
> proportion with the number of packets treated.
> >Now i'm gonna try without syslog and maybe downgrade to 3.13 
> (or upgrade to 3.15), i hope it will make a difference.
> >
> >Is there any tool to monitor memory allocation a perl 
> process as you can find in C ?
> >  
> >
> 
> 
> Hi all, salut Laurent.
> 
> FYI, I've had problems with the <SYSLOG> clause as well - 
> exactly the same, memory leaks on version 3.14.
> 
> We fixed it by removing the <SYSLOG> clause :
> 
> #<Log SYSLOG>
> #        Trace           4
> #        LogSock         udp
> #        LogHost         172.16.4.241
> #        Facility        local0
> #       MaxMessageLength 1000
> #</Log>
> 
> We have numerous other servers running the same version of 
> RADIATOR, none of them shows the same behaviour.
> 
> Olivier
> 

I've upgraded Syslog.pm to the last version since the one provided with the perl package is pretty old.
We'll see if things get better this way.
By the way, did you try upgrading to 3.15 ? Did it solve the problem ?
Commenting out <Syslog> is a solution but i can't afford it : we do need logs for troubleshooting...

Regards,

Laurent

--
Archive at http://www.open.com.au/archives/radiator/
Announcements on radiator-announce at open.com.au
To unsubscribe, email 'majordomo at open.com.au' with
'unsubscribe radiator' in the body of the message.