Configure SQL to timeout requests rather than rejecting if no connections available

Alan DeKok aland at
Fri Jan 23 03:42:30 CET 2015

On Jan 21, 2015, at 2:14 PM, Noah Engelberth <nengelberth at> wrote:
> This made me think: "The previous change I made to make the virtual server not respond in the case of SQL failing is causing the virtual server not to respond the proxy, so I must need to revert that change.

  I didn’t say to revert that change.  So...

>  But I'm kind of confused on whether or not that's the correct course of action, so I'm going to request clarification before I make a change, since I don't have a working method of replicating this problem in my test environment right now because my test environment isn't set up to make 30+ RADIUS requests in a single second and resource exhaust my test RADIUS server.”

  You can use radclient to hammer the server.

> I then read back through my previous postings and realized I hadn't included the original configuration, so I posted it in hopes that maybe my confusion was stemming from a mis-communication between us caused by my failure to initially supply all information.

  Which is why we ask for all of the data.

> Ok, so it's apparent that I need to get an environment set up where I can get debug information for the situation.  The only reason for my previous comments was to exhaust all other options before I started doing that, because I expected it was going to take me a couple hours to either (1) set up my dev environment to generate a resource exhaustion scenario or (2) learn enough about how to use the radius client tool to simulate the same sort of setup.  

  It takes less time to set up a debug environment than to wait for responses on the list.

  I used to work with a guy whose attitude towards testing was “I don’t have time to write tests”.  For me, I don’t have time to *not* write tests.

> I do appreciate the effort you have put in and are continuing to put toward assisting me with my problem.  I'm disappointed by the nature of the response I got for trying to clarify things before I spent hours generating debug results, in case the confusion was stemming from something easily cleared up by me including information I originally left out.

  That’s why we ask for debug logs.  And why a good chunk of responses are questions like “What do you mean?” or “What are you really doing”?

  If you care about privacy, send the debug messages to me off-list. I’ll take a look.

  Alan DeKok.

More information about the Freeradius-Users mailing list