rlm_python3 behavior with multi-worker threads

[Erdal Emlik]


Hi FreeRADIUS team,



I’m using FreeRADIUS (version 3.2.4) with rlm_python3 for authentication.



I have the following question:



- Does FreeRADIUS’ thread pool affect rlm_python3 requests?

- Specifically, does each RADIUS worker call the same Python interpreter instance, or does each worker get its own Python context?( i mean 28 workers uses trying to use single instance at the same time right as doc says “item is GLOBAL TO THE SERVER.  That is, you cannot have two instances of the python module”)



Additionally, within the Python module, I log requests and sometimes see “queue full” messages. 



However, even when these messages appear, I observe that the Python module still returns a response to FreeRADIUS. 

Within Python, I perform some comparisons and assign IPs accordingly, and even if a "queue full" exception occurs, FreeRADIUS still receives the IP assignment and returns a response without any issue.

- Is this “queue full” behavior related to the Python module itself, or is it due to FreeRADIUS threading/queue management?



I hope i made it clear. 



Thanks for your guidance.



Best regards


Sent from my iPhone