Unresponsive server when debugging
I'm running a 3.0.11 server with Firebird as the backend database. It works very well. I have an issue though when debugging (output to STDOUT): if an authentication query hangs or becomes very slow to respond, during that period of time, the server becomes unresponsive and it can be seen on the log of the nases "Radius server is not responding". Until this happens, it works just fine. If I launch the server without debug, it authorizes all users super fast (except the ones that are very slow), but it don't "hang" the server. It's like in debug mode threads are not used. Is that right? Thanks.
On Tue, Feb 14, 2017 at 11:39:11AM -0300, Lucas Diaz wrote:
If I launch the server without debug, it authorizes all users super fast (except the ones that are very slow), but it don't "hang" the server. It's like in debug mode threads are not used. Is that right?
Debug mode is single threaded. You can use `radiusd -fxxl stdout` to debug with threads enabled. Matthew -- Matthew Newton, Ph.D. <mcn4@leicester.ac.uk> Systems Specialist, Infrastructure Services, I.T. Services, University of Leicester, Leicester LE1 7RH, United Kingdom For IT help contact helpdesk extn. 2253, <ithelp@le.ac.uk>
Thanks! I'll try that. *LUCAS DIAZ | DPTO. REDES* _______________________________________________________ Istilart 255 | Tel.: 02983 513040 C.P. B7500EGE | Tres Arroyos | Bs As | Argentina * *www.eternet.cc <http://www.eternet.cc/> | *ETERNET SISTEMAS * On 02/14/2017 11:47 AM, Matthew Newton wrote:
On Tue, Feb 14, 2017 at 11:39:11AM -0300, Lucas Diaz wrote:
If I launch the server without debug, it authorizes all users super fast (except the ones that are very slow), but it don't "hang" the server. It's like in debug mode threads are not used. Is that right? Debug mode is single threaded.
You can use `radiusd -fxxl stdout` to debug with threads enabled.
Matthew
On Feb 14, 2017, at 9:39 AM, Lucas Diaz <lucasdiaz@eternet.cc> wrote:
I'm running a 3.0.11 server with Firebird as the backend database. It works very well.
That's good to hear.
I have an issue though when debugging (output to STDOUT): if an authentication query hangs or becomes very slow to respond, during that period of time, the server becomes unresponsive and it can be seen on the log of the nases "Radius server is not responding". Until this happens, it works just fine.
The only solution is to fix the DB. No amount of poking FreeRADIUS will make the DB run faster. I'm continually amazed at the number of databases which just don't work. How can you possibly rely on a DB when it takes seconds to respond to simple queries?
If I launch the server without debug, it authorizes all users super fast (except the ones that are very slow), but it don't "hang" the server. It's like in debug mode threads are not used. Is that right?
Yes. Alan DeKok.
participants (3)
-
Alan DeKok -
Lucas Diaz -
Matthew Newton