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

[Alan DeKok]

On Jan 21, 2015, at 1:20 PM, Noah Engelberth <nengelberth at team-meta.net> wrote:
> So, "in your existing configuration" means what I have with the virtual server not responding on an SQL "fail"?  Or to revert that change and then add that post-proxy handling?

  <sigh>  What I said was very clear.  I said to change ONE thing.  The PROXY.  I didn’t say to revert a change.

> My server configuration currently (with the virtual server not responding on SQL "fail") is:

  I didn’t ask for that.  I asked for the DEBUG OUTPUT.

  Paying attention would be nice.  Following instructions would be better.

> So, basically, the mikrotik_realm module looks at the realm name that came in from the client (which might be requesting hotspot.metalink.net or dhcp.metalink.net) and update the username to username at realm.  Suffix then proxies it off to the virtual server named platreg_<realm>

  NO.  I said that the suffix module DOES NOT DO PROXYING.

  Please pay attention.

> I can't easily run the live servers in debug mode -- they're under fairly heavy volume and it's hard to get useful information from them.  I have fairly high request logging turned up at the moment, and I can try to set up my debug environment with a test case that could replicate the issue if necessary.

  If only there was a free “radius client” tool which would let you send test packets.

  If only it was possible to create a test configuration *independent* of the live configuration, where test packets could be sent.

  Yes, I find this frustrating.  I’m trying to help you, and you’re making it as difficult as possible.

  Alan DeKok.