-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[defect]: FreeRADIUS 3.2.3 container crashes after sending status-server messages #5326
Comments
can you run it under gdb that will let us know exactly which function and variable had the issue. |
|
FreeRADIUS logs leading up to crash
|
Here is another gdb output I get. But this time, I received a segmentation fault. I also ran with gdb --args /usr/sbin/freeradius -fl stdout (no debug).
|
Thanks for the report (and helpful docker environment) - fixed in 05a4bfc |
Thanks for quickly fixing this! I see this issue in 3.0.26 as well. Should I open another defect? Or did your fix cover 3.0.26 as well? |
We'll push a fix for 3.0, too. |
@rtblossom 3.0.x fix added as well. Was giving it a while to test. |
What type of defect/bug is this?
Crash or memory corruption (segv, abort, etc...)
How can the issue be reproduced?
I created a repository to help in reproducing the issue. It contains a docker-compose file that builds a set of containers and then runs the test. The crash will then be easy to replicate.
https://github.com/rtblossom/fr-status-server-issue
Just clone the repository and run "docker-compose up --build".
The scenario is FreeRADIUS timing out proxied authentication messages over RadSec and then sending status-server messages to the RadSec server. FreeRADIUS eventually exits after TLS and talloc errors.
Log output from the FreeRADIUS daemon
Relevant log output from client utilities
No response
Backtrace from LLDB or GDB
No response
The text was updated successfully, but these errors were encountered: