[RADIATOR] Radiator Crash. SQL Timeout.
    David Zych 
    dmrz at illinois.edu
       
    Fri Dec 21 15:20:19 CST 2012
    
    
  
> Hello Heikki.
> I ran Radiator as you mention
> 
> ./radiusd -config_file radius_siptrunk_edge.cfg -foreground -log_stdout
> 
> The process crashed again,  unfortunately the only error is a "killed"
> message in the console
I log my accounting info to an Oracle DB, and I had a similar-looking
problem to this when I first upgraded my Radius servers to RHEL6 (and
thus newer versions of various dependencies); my Radiator process that
handles accounting would sometimes die completely after a SQL Timeout
error (though in my case it was for an INSERT instead of a SELECT).
What ultimately solved the problem for me was to disable the ADR feature
of Oracle client; apparently it "has been known to resolve issues with
OCI clients in 11.2", and it certainly did in my case.  Here's what I
put in sqlnet.ora:
DIAG_ADR_ENABLED=OFF
DIAG_SIGHANDLER_ENABLED=FALSE
DIAG_DDE_ENABLED=FALSE
I didn't see any more crashes after that.  Of course, YMMV and I am by
no means anything resembling an Oracle expert.
David
    
    
More information about the radiator
mailing list