On Oct 27, 2015, at 6:50 PM, Oscar Jofre <oscar@jofre.com> wrote:
I have configuring a new FreeRadius 3.0.6 on Centos7 and MariaDB.
I would suggest 3.0.10. It has a lot of bugs fixed over 3.0.6.
Also I have all this warnings/errors on log. What is really important to fix and how ???
If they're warning messages, fix them. Error messages will cause the server to not start.
1) START RADIUS
Tue Oct 27 22:36:17 2015 : Warning: No 'ipaddr' or 'ipv4addr' or 'ipv6addr' field found in client 0.0.0.0/0. Please fix your configuration
What part of that message is unclear?
2)
Tue Oct 27 22:36:17 2015 : Warning: rlm_sql (sql): 1 of 1 connections in use. You probably need to increase "spare"
What part of that message us unclear?
3)
Tue Oct 27 22:36:51 2015 : ERROR: (4217) ERROR: sql : Received conflicting packet from client 0.0.0.0/0 port 39418 - ID: 59 due to unfinished request.
This happens because your database is slow. Fix it. It's not a FreeRADIUS problem.
4)
Tue Oct 27 22:36:54 2015 : Warning: No such configuration item .type..query
What part of that message is unclear? Find the configuration which has ".type.query", and fix it. Note that the default configuration does *not* have these errors. This problem is because of something you changed on your local system.\
5)
Tue Oct 27 22:37:04 2015 : Error: (7162) Ignoring duplicate packet from client 0.0.0.0/0 port 47432 - ID: 116 due to unfinished request in component <core> module <queue>
This is the same problem as #3.
6)
Tue Oct 27 22:37:09 2015 : Error: rlm_sql (sql): Duplicate entry '30a1ada7fbf7328ec740200d6042f02b' for key 'acctuniqueid' Tue Oct 27 22:37:09 2015 : Error: rlm_sql_mysql: Cannot store result Tue Oct 27 22:37:09 2015 : Error: rlm_sql_mysql: MySQL error 'Duplicate entry '30a1ada7fbf7328ec740200d6042f02b' for key 'acctuniqueid''
3.0.10 has updates to the queries which work around this issue.
7)
Tue Oct 27 22:38:36 2015 : Error: Unresponsive child for request 11202, in component <core> module Tue Oct 27 22:38:36 2015 : Error: Unresponsive child for request 11201, in component <core> module
This is probably the same issue as #3. Alan DeKok.