Re: 1.1.6 with rlm_sqlippool: ip=[] len=0

To: "FreeRadius users mailing list" <freeradius-users@lists.freeradius.org>
Subject: Re: 1.1.6 with rlm_sqlippool: ip=[] len=0
From: "Guilherme Franco" <guilhermefranco@gmail.com>
Date: Wed, 9 May 2007 19:17:59 -0300
In-reply-to: <5e239f520705091514i59b0de4arc8d0bbd8d3d01a0d@mail.gmail.com>
References: <5e239f520705091514i59b0de4arc8d0bbd8d3d01a0d@mail.gmail.com>
Reply-to: FreeRadius users mailing list <freeradius-users@lists.freeradius.org>

Hello,

Using Freeradius 1.1.6 on latest RHEL AS4 x64 with rlm_sqlippool, using PostgreSQL
8.2.1.

After some hours operating, freeradius start to log lots of "Info:
rlm_sqlippool: ip=[] len=0". Running the allocate-find query directly under
psql shows no problem.

Issuing "service radiusd restart" solves the problem. I did a
cron.hourly job with this then.

This was happening with 1.1.4 and I thought that 1.1.6 would correct this.

Wasn't 1.1.6 supposed to work this out?

Thanks.

Follow-Ups:
- Re: 1.1.6 with rlm_sqlippool: ip=[] len=0
  - From: Alan DeKok <aland@deployingradius.com>

Previous by Date: RE: freeradius & redback sms
Next by Date: RE: FR with MySQL - Stored Procedures
Previous by Thread: Re:
Next by Thread: Re: 1.1.6 with rlm_sqlippool: ip=[] len=0
Freeradius-Users May 2007 archives indexes sorted by: [ thread ] [ subject ] [ author ] [ date ]
Freeradius-Users list archive Table of Contents
More information about the Freeradius-Users mailing list

This archive was generated by a fusion of Pipermail (Mailman edition) and MHonArc.