fail to send close messages to the radius server

Nikos Mavrogiannopoulos n.mavrogiannopoulos at
Wed Jan 6 14:38:19 PST 2016

On Wed, 2016-01-06 at 19:23 +0800, Yick Xie wrote:
> Hi Nikos,
> Speaking of the devil, it comes. I just rechecked the server and 
> found
> the problem I mentioned in the first thread. The situation is far too
> complicated than I imagined. This user got 2 stall session in this
> ocserv instance, but only today's one was not set acct-stop-time in
> the radius SQL. So I only had the today's log, sorry. As for the
> record, the radius server only got messages until today 14:20, yet
> actually the session was still active before 16:04:17, then again
> nothing changed in the radius server. The radius server and ocserv
> were deployed in one server.

Thanks. It seems that the worker is blocked on recv(). I suppose that
is Linux which  its select() manpage says:

"Under Linux, select() may report a socket file descriptor as "ready
for reading", while nevertheless  a  subsequent  read  blocks.  This
could for example happen when data has arrived but upon examination has
wrong checksum and is discarded.  There may be other  circumstances  in
which a file descriptor is spuriously reported as ready.  Thus it may
be safer to use O_NON‐BLOCK on sockets that should not block."

I think it is safer to use SO_RCVTIMEO for that case. I'll commit a
patch soon.


More information about the openconnect-devel mailing list