Feeding accounting logs into mysql

2004-07-09 Thread Stephan von Krawczynski 
Hello all,

has anybody a script at hand for feeding some (old) freeradius accounting log
files into a mySQL db?
I know I read somewhere about such a script...

Thanks for any hints
Stephan


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

Re: Feeding accounting logs into mysql

2004-07-09 Thread Stephan von Krawczynski 
On Fri, 9 Jul 2004 16:19:30 +0300 (EEST)
Kostas Kalevras [EMAIL PROTECTED] wrote:

 On Fri, 9 Jul 2004, Stephan von Krawczynski wrote:
 
  Hello all,
 
  has anybody a script at hand for feeding some (old) freeradius accounting
  log files into a mySQL db?
  I know I read somewhere about such a script...
 
 I would suggest just using radrelay with a properly configured radius server.

Yes, that would be handy indeed. The only thing I don't get about this is why
there is no mode for radrelay to feed the given detail file and then just exit.
At least the man-page and doc files tell that the thing truncs the detail file
and stays online for feeding further data being added to the detail file
later on.
How do you prevent this? Or is this only a lack of documentation?
The situation is having around 150 old detail files that should be fed into the
new mysql-accounting freeradius.

Thanks for your help
Stephan

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

Re: How to auth_log via sql ?

2004-06-20 Thread Stephan von Krawczynski 
On Sun, 20 Jun 2004 23:25:01 +1000
[EMAIL PROTECTED] (Paul Hampson) wrote:

 On Sun, Jun 20, 2004 at 02:42:52PM +0200, Stephan von Krawczynski wrote:
  this is possibly a very simple question, but browsing through the list and
  FAQs I could not find any hints.
  How can you write the information auth_log produces in a logfile to sql
  instead_without_ doing authentication via sql?
  You can't simply write sql into the authorize section, because it will
  try to authorize, right?
 
 You're after the post-auth SQL query. Edit it and the table to record
 what you want to see, and then put sql in your post-auth section, in the
 appropriate Post-Auth-Type section if relevant.
 
 You'll have to be using 1.0 or 1.1 series FreeRADIUS to have this.

Hello Paul,

Thanks for this hint.
The problem with this solution is (as far as I can see):

#  Post-Authentication
#  Once we KNOW that the user has been authenticated, there are
#  additional steps we can take.
post-auth {

This means it does not get called if authentication failed, correct?

Contrary auth_log gets called for every authentication-request, no matter if
failing or succeeding later on. This may be important while debugging user
login problems. It would not help a lot if you could only see the working
cases...

Any additional thoughts?
Stephan




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