-
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]: rlm_python: Fatal Python error: drop_gil: drop_gil: GIL is not locked #5111
Comments
tested on
with same result |
Please submit a PR with a testcase which reproduces this and we'll try to develop a fix. I'd also be interested to see if you still get the crash with master (v4) as that code is substantially different. |
do not know how to create PR, could you please provide me with an example? Steps to reproduce: Build:
Configure:
Also I tried to build v4 but configuration is different and I still working on making simple working configuration (will update if I will be able to run rlm_python on v4) |
... Limiting to have more than one instance
@sirmax123 Could you please perform your tests against the branch |
... Limiting to have more than one instance
Just built and tested, looks good to me:
(tested with So, I think this issue can be marked as fixed when your patch is merged. Thank you! |
Thank you @sirmax123 for the feedback.
|
... Limiting to have more than one instance
main_interprerter is checked, but there are code paths by which the variable is used without being initialized.
Any chance that this fix will come to the upcoming release? ---EDIT--- We are running a simple python script in docker based on freeradius/freeradius-server:3.2.6, and everything seems works fine except the radius shutdown process. When we stop it it complains about: `Fatal Python error: drop_gil: drop_gil: GIL is not locked Current thread 0x00007f13307c5080 (most recent call first): Extension modules: radiusd (total: 1) I presume it is related to the issue mentioned above. |
What type of defect/bug is this?
Crash or memory corruption (segv, abort, etc...)
How can the issue be reproduced?
I'd like to have 2 instances of Python code (using rlm_python) in order to split my code into 2 scripts
e.g smx like this
ipaddr.py
:service.py
:and the second script returns something like
The idia is to handle in different scripts for different
kinds
of usernames,I need it for Cisco ISG, where I have
users
withUser-Name
= IP ADDRESS andService
whereUser-Name
is name of serviceSo I'm trying to do it in the following way:
There is no real code in scripts, just 2 copies of example.py from distribution.
And I got:
One script works OK, so as workaround I can put all code into one file, it possible.
Log output from the FreeRADIUS daemon
Relevant log output from client utilities
rlm_python
Backtrace from LLDB or GDB
The text was updated successfully, but these errors were encountered: