At 05:53 PM 4/24/2002 +0300, Aleksandr Kuzminsky wrote:
>On Wed, 24 Apr 2002, Chris Parker wrote:
>
> > >Tue Apr 23 21:37:21 2002 : Error: rlm_sql: All sockets are being used!
> > >Please increase
> > > the maximum number of sockets!
> >
> > Well, that warning message should tell you something! Have you
> > done what it says in the error message?
>Yes, I have. But this is not solution for my question.
If this is happening then there is going to be a problem. If the server
can't access the database server, then it will only cause further problems
for you.
> > >The "stop" packet was not resent, despite NAS is configured to send
> > >accounting packet 3 times if no response from accounting server, so RADIUS
> > >sent accounting response acknowledgment to the NAS. Why it happens?
> > >--rfc2866--
> > > If the RADIUS accounting server is unable to successfully record the
> > > accounting packet it MUST NOT send an Accounting-Response
> > > acknowledgment to the client.
> > >--rfc2866--
> >
> > Hmmm, it *was* recorded in the 'detail' module, though, so it's not
> > fully incorrect.
>I agree, not fully incorrect, but _incorrect_.
No, not incorrect, just not what you want.
>Take a look to authorization. If I'll write to radiusd.conf something
>like this:
>authorize{
> files
> sql
> }
>then authorization will fail if fail any of "files" or sql.
>
> > What does the sql module return in that instance that there are not
> > enough sockets?
>As sources said, sql module return RLM_MODULE_NOOP in this case.
Ahhh. The default behaviour for NOOP is to treat it *not* as a failure.
SQL probably should not return NOOP if it is unable to obtain a socket.
It should be more appropriately FAIL.
> > you to control some of the different options. If SQL is the most
> > important logging method, you may want to put that before 'detail' in
> > the accounting section, so that it returns before calling 'detail'.
>Hmmm, its good idea. Although mail accounting module is sql for me, detail
>also needed. I will point it at the end of accounting group.
If SQL returns NOOP, then changing the order won't matter. The best
solution is to change the SQL code so that it returns FAIL when it can't
obtain a socket.
I'll take a look at doing this in the latest CVS.
-Chris
--
\\\|||/// \ StarNet Inc. \ Chris Parker
\ ~ ~ / \ WX *is* Wireless! \ Director, Engineering
| @ @ | \ http://www.starnetwx.net \ (847) 963-0116
oOo---(_)---oOo--\------------------------------------------------------
\ Wholesale Internet Services - http://www.megapop.net
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
