Re: Start FreeRadius 4.0 with rlm_tacacs failed due to segV error

bryan xiang <[email protected]>
Newsgroups gmane.comp.freeradius.user
Message-ID <CAABO0yPyC=fiDqgNz5M_qFojeQo4VntV2aQJpNSeFtfAGwYBiQ@mail.gmail.com>
Thank you Alan for the quick response, glad to know you can reproduce it in
local
When the master branch will include your code?
after you fix it, you could see below log in your local?
Listening on auth address xx.xx.xx.xx port 1812
Listening on auth address 169.254.195.0 port 1812
Listening on auth address 127.0.0.1 port 1812
Listening on auth address ::1 port 1812
Listening on command file /var/opt/run/radiusd.sock
Ready to process requests

thanks,
Bryan

On Wed, Apr 23, 2025 at 11:47 PM Alan DeKok <[email protected]>
wrote:

> On Apr 23, 2025, at 10:34 AM, bryan xiang <[email protected]> wrote:
> > I use the latest FreeRadius 4.0 from github and I only use the rlm_tacacs
> > module build in FreeRadius
>
>   I don't think that module is included in the testing framework.  It
> hasn't really seen any code changes in a while.
>
> > When I try to start the radiusd daemon with -X, I encounter one segV
> error,
> > and start option with -XC has no problem for configuration
> > ...
> > Debug : Instantiating rlm_tacacs_tcp "tacacs.tcp"
> > CAUGHT SIGNAL: Segmentation fault
> > Backtrace of last 11 frames:
> > /opt/LU3P/lib64/libfreeradius-util.so(+0x32fc9)[0x7f2d3e4e3fc9]
> > /opt/LU3P/lib64/libfreeradius-util.so(fr_fault+0x75)[0x7f2d3e4e4465]
> > /lib64/libpthread.so.0(+0x12d10)[0x7f2d3c454d10]
> > /opt/LU3P/lib64/rlm_tacacs_tcp.so(+0x266f)[0x7f2d339f266f]
> >
> /opt/LU3P/lib64/libfreeradius-server.so(module_thread_instantiate+0xda)[0x7f2d3dff1e3a]
> >
> /opt/LU3P/lib64/libfreeradius-server.so(modules_thread_instantiate+0x65)[0x7f2d3dff2045]
> > /opt/LU3P/sbin/radiusd[0x4056d1]
> >
> /opt/LU3P/lib64/libfreeradius-io.so(fr_schedule_create+0x126)[0x7f2d3dae4d16]
> > /opt/LU3P/sbin/radiusd(main+0xdff)[0x404bcf]
> > /lib64/libc.so.6(__libc_start_main+0xe5)[0x7f2d3bd5a7e5]
> > /opt/LU3P/sbin/radiusd(_start+0x2e)[0x40533e]
> > No panic action set
>
>   Oops.  :(    When I try it locally, I see it crash, too.
>
>   I've pushed a patch which makes it not crash.  But I haven't tested the
> actual TACACS+ functionality.
>
>   Alan DeKok.
>
> -
> List info/subscribe/unsubscribe? See
> http://www.freeradius.org/list/users.html
>
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.