control-socket bug in the last one v3.x updates?
ruyrybeyro at gmail.com
Tue Jul 29 07:34:26 CEST 2014
If it is of any use, I manage to track it down in git. I will follow the
instructions in doc/bugs later on during the day.
I only have the bug after applying
Author: Alan T. DeKok <aland at freeradius.org>
Date: Fri Jun 27 09:01:14 2014 -0400
Move checks for virtual_server to listen_parse()
Which is better than scattering them through the code.
> Message: 2
> Date: Mon, 28 Jul 2014 08:06:17 -0400
> From: Alan DeKok <aland at deployingradius.com>
> To: FreeRadius users mailing list
> <freeradius-users at lists.freeradius.org>
> Subject: Re: control-socket bug in the last one v3.x updates?
> Message-ID: <53D63CB9.20302 at deployingradius.com>
> Content-Type: text/plain; charset=UTF-8
> Rui Ribeiro wrote:
> > I have tried this with a copy of my configuration, and with a pristine
> > copy of freeradius, which only got inserted the link to activate control
> > socket into sites-enabled.
> Hmm... the default config works for me. Even with the control socket
> > /etc/freeradius/sites-enabled/control-socket: No such server "(null)"
> You should (a) have a default server, or (b) update the "listen"
> section to point to a server.
> And the libc printing code shouldn't crash when passed a NULL pointer.
> See doc/bugs for information about how to debug it some more. I can't
> reproduce it here, so that makes it difficult for me to help.
> Alan DeKok.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Freeradius-Users