When we start radiusd with a thread pool configured, none of the requests from the pam-radius-auth proxy client are serviced/processed. The client never gets a reply from the server. From the server logs, the request is never seen. I noticed that when the server is started without the thread pool, the following logs are displayed (but they are not displayed when the thread pool is configured): Listening on authentication address * port 1812 Listening on accounting address * port 1813 Listening on proxy address * port 1814 Ready to process requests. Thanks, Keven -----Original Message----- From: freeradius-users-bounces+keven.smith-worthylake=genband.com@lists.freeradius.org [mailto:freeradius-users-bounces+keven.smith-worthylake=genband.com@lists.freeradius.org] On Behalf Of Alan DeKok Sent: Tuesday, December 07, 2010 3:42 PM To: FreeRadius users mailing list Subject: Re: thread pools in 2.1.10 Keven Smith-Worthylake wrote:
We just upgraded from freeRADIUS 1.1.7 to 2.1.10, and we're having issues getting freeRADIUS to work with a thread pool (see debug logs below). The thread pool config was working in version 1.1.7.
I don't see a problem with thread pools. And it would be *good* to describe the problem in a little more detail. "Something is wrong", followed by 100's of lines of debug output is unhelpful.
Were there major changes on how threads were implemented from 1.1.7 to 2.1.10? Why might we be having this issue?
No. What issue? Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html