Closed nemesifier closed 3 years ago
jpereira
commented
3 years ago @nemesisdesign if you don't mind, please install the gdb in your system and enable the panic_action=... in the radiusd.conf. it would be useful to help us to figure out where is the error.
nemesifier
commented
3 years ago @jpereira sure, I tried panic_action = "gdb -silent -x ${raddbdir}/panic.gdb %e %p 2>&1 | tee ${logdir}/gdb-${name}-%p.log"" here's what I get:
CAUGHT SIGNAL: Segmentation fault
Calling: gdb -silent -x /etc/freeradius/panic.gdb freeradius 1773268 2>&1 | tee /var/log/freeradius/gdb-freeradius-1773268.log
Temporarily setting PR_DUMPABLE to 1
Reading symbols from freeradius...
(No debugging symbols found in freeradius)
Attaching to program: /usr/sbin/freeradius, process 1773268
Could not attach to process. If your uid matches the uid of the target
process, check the setting of /proc/sys/kernel/yama/ptrace_scope, or try
again as the root user. For more details, see /etc/sysctl.d/10-ptrace.conf
ptrace: Operation not permitted.
/etc/freeradius/1773268: No such file or directory.
/etc/freeradius/panic.gdb:1: Error in sourced command file:
No frame selected.The file /etc/sysctl.d/10-ptrace.conf contains:
kernel.yama.ptrace_scope = 1/proc/sys/kernel/yama/ptrace_scope is 1.
What more can I do?
jpereira
commented
3 years ago @nemesisdesign please, try it:
# gdb /usr/sbin/freeradiusOnce in the gdb> prompt, please execute run. as you get the error, then execute bt and copy/paste here the entire stacktrace.
jpereira
commented
3 years ago @nemesisdesign btw, ensure to have installed the freeradius-dbg packages needed to show the functions/line/source information.
nemesifier
commented
3 years ago Before trying your suggestion, it occurred to me that since I migrated from the official ubuntu packages to the networkradius packages, it may have happened that some packages were mixed which is of course undesirable so I started clean again (uninstalled the freeradius packages, reinstalled and reconfigured them) and the error went away, everything is working and HTTP2 is enabled in nginx, so if anyone gets the same error I would suggest to try this before opening an issue here, I guess this can be safely closed.
Anyway, learning to debug these cases can be helpful though, is there any page which concentrates all the tips you're giving me here?
jpereira
commented
3 years ago @nemesisdesign https://wiki.freeradius.org/project/bug-reports
What type of defect/bug is this?
Crash or memory corruption (segv, abort, etc...)
How can the issue be reproduced?
I had a working deployment using the rest module on version 3.20, the full setup is documented at https://openwisp-radius.readthedocs.io/en/latest/developer/freeradius.html, but since HTTP2 is not usable with that version I upgraded to 3.23 using the networkradius deb packages on Ubuntu 20.
After upgrading I only had to move the config files from /etc/freeradius/3.0 to /etc/freeradius.
With this version I get a segmentation fault on attempting an authorization.
I am using sql module, sqlcounter and rest. I am including the full debug output which should clarify also the configuration.
If you could suggest further steps I can take to get more detail about what exactly is going wrong I will be grateful
Log output from the FreeRADIUS daemon
Relevant log output from client utilities
No response
Backtrace from LLDB or GDB
No response