3.0.11 - all threads blocked in "linelog"
nicolas.chaigneau at capgemini.com
Tue Jul 5 10:16:19 CEST 2016
> On Jun 23, 2016, at 9:42 AM, Chaigneau, Nicolas <nicolas.chaigneau at capgemini.com> wrote:
> > But my concern is that I'm unable to guarantee to our customer that the issue is fixed in 3.0.x, because I can't reproduce the issue in our test lab.
> > So I can't check that it does not happen anymore in 3.0.x...
> Well, that's the issue with open source software. There just isn't time / money to write test cases for everything.
> > Did you get feedback of people having experienced this issue previously, and reporting that it does not happen anymore ?
> > This would be reassuring :)
> That's what I recall.
> Alan DeKok.
Here's some feedback that may be useful (I could not find any in the mailing archives or on GitHub).
FreeRADIUS 3.0.11 got blocked three times (requiring a restart) with this issue within 24 hours (after that it was rolled back to 3.0.8).
After installing 3.0.x HEAD (18cc48e2d8fcd533e06eefaa5d81d4a96d01532e), it did not happen again. So I confirm that the issue is indeed fixed.
So, a word of advice, if you're using the linelog module and considering deploying FreeRADIUS 3.0.11 on production: *don't*. Upgrade to the 3.0.x HEAD.
This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message.
More information about the Freeradius-Users