Re: detail sql logging problem

[Alan DeKok]

[EMAIL PROTECTED] wrote:
 a further question on this one - as the detail relay virtual
 server buffered-sql is only supposed to run when the main thread
 isnt busy...and is only supposed to read detail file, log to SQL
 then 'be quiet' why, when it encounters such an issue does the
 main authentication/accounting etc thread not process anything?

  I'm not sure  I haven't been able to test it myself, so I don't
really know what's going on in that situation.

 I'd have thought that the virtual server would be moaning and
 complaining as much as it wants, but the main core functionality
 would just keep on going...

  I would think so, too.

  Maybe the detail file reader is re-queuing failed requests too
quickly, and starving other threads from CPU...

  Alan DeKok.
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html

Re: detail sql logging problem

[Alan DeKok]

[EMAIL PROTECTED] wrote:
 further to last email, heres example packet:

...
 Acct-Session-Time = 0

  unlang. :)

accounting {
...
if (Acct-Sesion-Time != 0) {
sql
}
else {
ok
}
...
}

  i.e. bypass the module that gets upset over 0 session time.

  Alan DeKok.
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html

Re: detail sql logging problem

[A . L . M . Buxey]

Hi,

   unlang. :)

yes - i was pondering that one.  okay.
and even better, use eg sql_log for the
ones that are session-time = 0 so that i can
capture them, know them, and see when the 
issue is fixed etc...

alan
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html