I'd like to know how common this problem is.
>
> Thanks,
> Heikki
>
>
>> Regards,
>> Ricardo.-
>>
>> -Mensaje original-
>> De: Ricardo Martinez [mailto:rmarti...@redvoiss.net]
>> Enviado el: lunes, 19 de noviembre de 2012 18:50
&
kki Vatiainen'; 'radiator@open.com.au'
> Asunto: RE: [RADIATOR] SQL Timeout
>
> There is also other post about the same issue :
>
> http://www.open.com.au/pipermail/radiator/2011-April/017237.html
>
>
>
> -Mensaje original-
> De: Ricardo Martinez
ainen'; 'radiator@open.com.au'
Asunto: RE: [RADIATOR] SQL Timeout
There is also other post about the same issue :
http://www.open.com.au/pipermail/radiator/2011-April/017237.html
-Mensaje original-
De: Ricardo Martinez [mailto:rmarti...@redvoiss.net] Enviado el: lunes, 19
de nov
tor@open.com.au'
Asunto: RE: [RADIATOR] SQL Timeout
Is there another more safe way to do the BackOff. What I'm trying to do
is when a SQLquery is Timeout by Radiator mark the server as "down" and do
the next AuthBy Clause.
I saw a pair of question about the same issue near 2002
en
Enviado el: lunes, 19 de noviembre de 2012 18:21
Para: radiator@open.com.au
Asunto: Re: [RADIATOR] SQL Timeout
On 11/19/2012 10:47 PM, Ricardo Martinez wrote:
> Question : When it says ".Radiator will wait for when trying to
> contact the SQL server." this means that a */sel
On 11/19/2012 10:47 PM, Ricardo Martinez wrote:
> Question : When it says “…Radiator will wait for when trying to contact
> the SQL server…” this means that a */select/* is a CONTACT???
Hello Ricardo,
there is a contact before the select. The contact succeeds but the
subsequent query (DELYREQ) t
I’m doing 3 or even 4 querys for each one and keeps connecting to the mySQL
server and not doing the BackOff.
The Timeout parameter seems to be very clear about the behavior :
*5.31.4 Timeout*
This optional parameter specifies a timeout interval in seconds that
Radiator will wait
for when try
81>;<242>-<251><184><200>q<174>`<239><24>k
Attributes:
SIP-AVP = "tranum:sip:0212345678@10.0.0.82
<mailto:tranum%3Asip%3A0212345678@10.0.0.82>"
SIP-AVP = "channels:1"
Thanks,
Ricardo.-
*De:*Michael [mailto:ri...@
I miss the change : ContinueWhileIgnore for ContinueWhileReject
*De:* Michael [mailto:ri...@vianet.ca]
*Enviado el:* lunes, 19 de noviembre de 2012 16:28
*Para:* Ricardo Martinez
*CC:* radiator@open.com.au
*Asunto:* Re: [RADIATOR] SQL Timeout
looks like your first AuthBy SQL is answering
ss-Accept
Identifier: 112
Authentic: @<165><188><181>;<242>-<251><184><200>q<174>`<239><24>k
Attributes:
SIP-AVP = "tranum:sip:0212345678@10.0.0.82"
SIP-AVP = "channels:1"
Thanks,
Ricardo.-
*De:*
looks like your first AuthBy SQL is answering accept. is this maybe
because you don't have any 'check' options at all? Then if accept,
never process the AuthBy FILE because of ContunueWhileIgnore.
For example, maybe you need at least one check option:
AuthColumnDef 1, Encrypted-Password, ch
Hello Griff -
The first thing to check is the MySQL logs to see what is happening
with the database.
Then you should probably turn on LogMicroseconds (requires Time-HiRes
from CPAN) to see how long the queries are taking and what is happening
when the problem occurs. It sounds like there i
ore.
Thanks
Chris
-Original Message-
From: Hugh Irvine [mailto:hugh@;open.com.au]
Sent: 21 October 2002 02:51
To: Chris Cronje
Cc: [EMAIL PROTECTED]
Subject: Re: (RADIATOR) SQL Timeout vs SQL "Could not Connect"
Hello Chris -
Could you please clarify what you mean by "s
s is a lot easier to check: use
"top" on Unix or else Task Manager in NT.
Dave
> -Original Message-
> From: Janet N. del Mundo [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, March 13, 2001 5:16 PM
> To: [EMAIL PROTECTED]
> Cc: [EMAIL PROTECTED]
> Subject: Re: (RADIATO
Hello Janet -
On Wednesday 14 March 2001 09:15, Janet N. del Mundo wrote:
> Hi Hugh,
>
> The missedaccounting file contained just the accounting stop records.
> Yes, I waited for about 30 mins. and authentication requests started to
> be rejected. That's when I had to restart Radiator. What ca
Hi Hugh,
The missedaccounting file contained just the accounting stop records.
Yes, I waited for about 30 mins. and authentication requests started to
be rejected. That's when I had to restart Radiator. What can I do to
not interrupt the users authentication? Would it make any difference if
I
Hello Janet -
What data is contained in the AcctFailedLogFileName file? Did it actually
catch the accounting data? Notice that this will only catch accounting stops
as sessions end, and as the debug shows, Radiator will not retry the
connection for 10 minutes (600 seconds) - did you wait that
Hello Faez -
On Fri, 24 Nov 2000, Faez Itrat wrote:
> Hi,
> I have just started evaluating radiator and am using its demo version
> at the mement and my users database is created on Remote Oracle
> database...am facing two problems..firstly i'm getting sql timeout and
> secondly the radius pro
Hello Alexey -
On Sat, 23 Sep 2000, Alexey A. Shavaldin wrote:
> Hello !
>
> On Sat, 23 Sep 2000, Hugh Irvine wrote:
>
> > Could you send us a bit more detail on your hardware and software plaforms and
> > the Radiator and database setups (in terms of what software is running on what
> > host)
Hello !
On Sat, 23 Sep 2000, Hugh Irvine wrote:
> Could you send us a bit more detail on your hardware and software plaforms and
> the Radiator and database setups (in terms of what software is running on what
> host)? Also, have you tried altering the Timeout and FailureBackoffTime
> parameters
Hello Alexey -
Could you send us a bit more detail on your hardware and software plaforms and
the Radiator and database setups (in terms of what software is running on what
host)? Also, have you tried altering the Timeout and FailureBackoffTime
parameters in the AuthBy SQL clause? Normally, Radi
Hello Emin -
On Thu, 29 Jun 2000, Emin TAHRALI wrote:
>
> Hello Hugh,
>
> Many thanks for the given information...
>
>
> The questions below can be useful to go a bit further and solve this
> Problem:
>
> What are the exact conditions, when the Radioator sends TimeOut Error
> Message?
When
Title: RE: (RADIATOR) SQL Timeout
Hello Hugh,
Many thanks for the given information...
The questions below can be useful to go a bit further and solve this Problem:
What are the exact conditions, when the Radioator sends TimeOut Error Message?
How does the Radioator communicate with
Hello Emin -
On Wed, 28 Jun 2000, Emin TAHRALI wrote:
>
> Hi,
>
> We are using two radiators working simultaneously, and AuthBy SQL
> authentication.
> We have some troubles with SQL Timeout Problem.
>
> The Error Logs are as below:
>
> 1. Error Log of 1st Radiator
> Sun Jun 25 13:31:13 2000
Hello Beth -
On Tue, 02 May 2000, Beth Morgan wrote:
> Hi all,
>
> We are running Radiator 2.15, using mysqld Ver 3.22.29 for
> freebsdelf3.3. Every week or so I am having to reboot the machine when
> it stops wanting to authenticate because of a SQL timeout. Here's what
> the log says:
>
>
Beth,
Check out Netsaint at www.netsaint.org. I have it running here monitoring
quite an array of items from individual services to disk space. If something
goes down, it pages me via an alpha-numberic pager with a text description
of what is not responding as expected.
-Danny
-Original Me
Hello Andrew -
On Wed, 29 Dec 1999, Andrew Kaplan wrote:
> I am still plagued with Radiator failing to authenticate. We had problems
> today. The log shows a bunch of SQL timeout errors at the same time. Any
> idea as to what is the problem.
>
If you are trying to authenticate from SQL and th
You could add a backup sql server and then specify another DBSource,
DBUsername, & DBAuth in your AuthBy. Then if your sql server timesout
Radiator would switch to your backup and your users would still be able to
authenticate.
-Original Message-
From: Andrew Kaplan <[EMAIL PROTECTED]>
T
On Tue, Dec 28, 1999 at 05:50:44PM -0500, Andrew Kaplan wrote:
> I am still plagued with Radiator failing to authenticate. We had problems
> today. The log shows a bunch of SQL timeout errors at the same time. Any
> idea as to what is the problem.
>
If it's a regular problem, perhaps leave Radi
29 matches
Mail list logo
