Ok, I ran the server in debugging mode (radiusd -X) with the assumption that this would be single threaded.
It appeared to function correctly. I ran it for about 5 minutes. I was getting some timeouts from my NAS talking to the radius server. I assume this is because a single thread could not handle the load of around 500 clients? I also complied 1.0.4 on one of the newer servers, it appeared to run without any difficulties as well. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of King, Michael Sent: Wednesday, October 18, 2006 5:47 PM To: FreeRadius users mailing list Subject: RE: SSL_read failed in a system call Just so I don't do something stupid. The easiest way to do this is run the server in debugging mode. /path/to/radiusd -X Correct? Mike -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Alan DeKok Sent: Wednesday, October 18, 2006 5:14 PM To: FreeRadius users mailing list Subject: Re: SSL_read failed in a system call "King, Michael" <[EMAIL PROTECTED]> wrote: > I've still got the server locked up in a state where it throws this > error message at will. The issues is "bad record mac", not "failed in system call". The second error message is a result of the first. I suspect threading issues. Try running the server in non-threaded mode. If that works, then the SSL locking code should be back-ported from the CVS head (src/main/threads.c) Alan DeKok. -- http://deployingradius.com - The web site of the book http://deployingradius.com/blog/ - The blog - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html