Re: 1.1.6 with rlm_sqlippool: ip=[] len=0
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.
Guilherme Franco wrote:
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?
Which part of the ChangeLog said that? Alan DeKok. -- http://deployingradius.com - The web site of the book http://deployingradius.com/blog/ - The blog
Hello Mr. DeKok, On my earlier posts (months ago, with 1.1.4), it has been told that the latest CVS would solve the problem. I thought that 1.1.6 would include the fix from the CVS head. 1.1.6 Changelog: *Fixed bug in PostgreSQL module that caused server crash. I thought that this would correct the behaviour as well, because the server did crash sometimes (I've sent some valgrind outputs to you in previous posts). Using the latest CVS will fix the problem? Thank you very much. On 5/10/07, Alan DeKok <aland@deployingradius.com> wrote:
Guilherme Franco wrote:
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?
Which part of the ChangeLog said that?
Alan DeKok. -- http://deployingradius.com - The web site of the book http://deployingradius.com/blog/ - The blog - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Guilherme Franco wrote:
On my earlier posts (months ago, with 1.1.4), it has been told that the latest CVS would solve the problem. I thought that 1.1.6 would include the fix from the CVS head.
1.1.6 Changelog: *Fixed bug in PostgreSQL module that caused server crash.
The error you posted is not a server crash.
I thought that this would correct the behaviour as well, because the server did crash sometimes (I've sent some valgrind outputs to you in previous posts).
Perhaps there are two unrelated bugs. One got fixed. I have no idea what the other bug is.
Using the latest CVS will fix the problem?
No. Alan DeKok. -- http://deployingradius.com - The web site of the book http://deployingradius.com/blog/ - The blog
Ok, But a lot of times, on the process of server restart (every hour on cron.hourly), freeradius hangs and "Error: There appears to be another RADIUS server running on the authentication port 1812" messages appears. I have to manually "kill -9 radiusd" and start it again. Version 1.1.6 hangs more in this matter than 1.1.4 do. Also, I've tried to update to the latest CVS (freeradius-server-snapshot-20070511.tar.bz2) just to check out (because Mr. Nixon have told earlier that the postgresql driver was fixed in CVS), but "Floating point Exception" occurred. That's it. Thanks. On 5/10/07, Alan DeKok <aland@deployingradius.com> wrote:
Guilherme Franco wrote:
On my earlier posts (months ago, with 1.1.4), it has been told that the latest CVS would solve the problem. I thought that 1.1.6 would include the fix from the CVS head.
1.1.6 Changelog: *Fixed bug in PostgreSQL module that caused server crash.
The error you posted is not a server crash.
I thought that this would correct the behaviour as well, because the server did crash sometimes (I've sent some valgrind outputs to you in previous posts).
Perhaps there are two unrelated bugs. One got fixed. I have no idea what the other bug is.
Using the latest CVS will fix the problem?
No.
Alan DeKok. -- http://deployingradius.com - The web site of the book http://deployingradius.com/blog/ - The blog - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Guilherme Franco wrote:
I have to manually "kill -9 radiusd" and start it again. Version 1.1.6 hangs more in this matter than 1.1.4 do.
Then something else is going seriously wrong. Are you sure the postgres libraries on your system are OK?
Also, I've tried to update to the latest CVS (freeradius-server-snapshot-20070511.tar.bz2) just to check out (because Mr. Nixon have told earlier that the postgresql driver was fixed in CVS), but "Floating point Exception" occurred.
There is floating point code in the server? Not that I'm aware of. And if you see an error, is it so hard to give us *more* information than "something went wrong"? It's impossible to fix a problem that only you see if you say little more than "it doesn't work". Alan DeKok. -- http://deployingradius.com - The web site of the book http://deployingradius.com/blog/ - The blog
On Sat 12 May 2007, Guilherme Franco wrote:
Ok,
But a lot of times, on the process of server restart (every hour on cron.hourly), freeradius hangs and "Error: There appears to be another RADIUS server running on the authentication port 1812" messages appears.
I have to manually "kill -9 radiusd" and start it again. Version 1.1.6 hangs more in this matter than 1.1.4 do.
Also, I've tried to update to the latest CVS (freeradius-server-snapshot-20070511.tar.bz2) just to check out (because Mr. Nixon have told earlier that the postgresql driver was fixed in CVS), but "Floating point Exception" occurred.
OK. Well, please give us more information about this problem (Back trace etc) so that we can try to fix it. -- Peter Nixon http://www.peternixon.net/ PGP Key: http://www.peternixon.net/public.asc
Mr. Alan and Mr. Peter, Sorry for the lack of information. I'll give more details about the problem on Monday. Thank you very much. On 5/12/07, Peter Nixon <listuser@peternixon.net> wrote:
On Sat 12 May 2007, Guilherme Franco wrote:
Ok,
But a lot of times, on the process of server restart (every hour on cron.hourly), freeradius hangs and "Error: There appears to be another RADIUS server running on the authentication port 1812" messages appears.
I have to manually "kill -9 radiusd" and start it again. Version 1.1.6 hangs more in this matter than 1.1.4 do.
Also, I've tried to update to the latest CVS (freeradius-server-snapshot-20070511.tar.bz2) just to check out (because Mr. Nixon have told earlier that the postgresql driver was fixed in CVS), but "Floating point Exception" occurred.
OK. Well, please give us more information about this problem (Back trace etc) so that we can try to fix it.
--
Peter Nixon http://www.peternixon.net/ PGP Key: http://www.peternixon.net/public.asc - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
participants (3)
-
Alan DeKok -
Guilherme Franco -
Peter Nixon