(RADIATOR) Oracle SQL timeout causing crash

[Viraj Alankar]

Hello,

Awhile ago I posted the message below regarding Radiator dying on a SQL
timeout.

I received some suggestions to update the DBI/DBD modules, which I did and am
also running v2.18.2 of Radiator. I see the same thing in the log, and
restart_wrapper reports:

Your program

   /usr/bin/radiusd -config /disk/store0/radius/raddb/radiusd.cfg

exited unexpectedly with exit status 0,
signal number 0 and dump indication 0.

The STDERR output was .

The program will be restarted again by /disk/store0/radius/bin/restartWrapper
in 10 seconds.

My current versions:

DBI v1.19
DBD::Oracle v1.08
Oracle v8.0.5 x86 client libraries
The Oracle server being queried is v8.1.7 on Sun
PERL v5.005_03 (came with Redhat 6.2)

It is strange because sometimes, Radiator processes the error normally and
backs off from querying the database. However at other times it just dies as
above. I'm using 'Timeout 10' for these SQL AuthBy's. The reason for the SQL
timeout is that the database is overloaded during these times.

Any help appreciated.

Viraj.

On Thu, Jun 28, 2001 at 09:46:53AM -0400, Viraj Alankar wrote:
> 
> Hello,
> 
> 	We are using v2.18.1 on Linux x86. Whenever there is a SQL
> timeout, the Radiator process just exits.
> 
> Thu Jun 28 08:57:40 2001: ERR: Execute failed for 'select ...': SQL Timeout
> 
> It then exits with error code 0. We have the restart_wrapper in place
> which restarts it, but is there a reason why it would die? I have not
> placed it in a higher trace level yet because it is in production, getting
> a large # of requests (about 20-40/sec), and this happens rarely. Though
> if needed I can do this. Thanks for any help.
> 
> Viraj.
===
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.