aland at deployingradius.com
Tue Sep 22 02:46:34 CEST 2015
On Sep 21, 2015, at 7:06 PM, Andrew Parisio <parisioa at gmail.com> wrote:
> Like I said in my original email we are aware of the problems caused by the
> lack of a timeout and are actively working to fix that, so you don't need
> to be condescending and rude about the lack of a timeout.
His message was neither condescending nor rude. It simply points out that you're blaming FreeRADIUS, when the real blame lies elsewhere. I suggest learning how to take feedback without getting offended.
After all, *you* are the one who asked for help. You should have entertained the idea that perhaps the problem wasn't FreeRADIUS.
I *hate* it when people ask questions and get offended at the answers. It's anti-social, and has no place in polite society.
suggest dropping the idea that you've been offended, and keeping the conversation technical. The alternative is for you to keep complaining, which will result in you getting unsubscribed and permanently banned from the list.
> My question was that even after dynamo recovered FreeRADIUS continued to
> fail to call python, and I wanted to make sure that even after we fix the
> timeout issue that there isn't another problem that could be triggered.
> Are you suggesting the only possible explanation for what we saw was that
> all of the worker threads were still waiting for a response from dynamo 2
> days later, and that there is no point in debugging why FreeRADIUS was
> unable to execute rlm_python?
That is what Arran said.
FreeRADIUS calls Python, which calls your software. If your software doesn't return execution to FreeRADIUS for 2 days, it's the fault of *your software*. Go fix it.
> I suppose that's possible but it seems
> unlikely that that many sockets were hung open for that long. Is there any
> way to see what the worker threads were doing?
Do python / C debuggers exist? If so, use them. Use "strace". These are all tools which are available to you as an administrator. There is nothing FreeRADIUS-specific about debugging a program.
I'll bet dollars to donuts that if you run your Python programs from the shell (not using FreeRADIUS), they'll block for 2 days, too. Which would indicate that the problem isn't FreeRADIUS.
More information about the Freeradius-Users