Hide Forgot
Description of problem: freeradius-python fix libpython2.7.so dependency at compile time Version-Release number of selected component (if applicable): freeradius-python-3.0.4-6.el7 How reproducible: Always Steps to Reproduce: 1] install freeradius-python 2] Enable python module: $ ln -s /etc/raddb/mods-available/python /etc/raddb/mods-enabled/ 3] Run radiusd in debug mode:- $ radiusd -X Actual results: Fails loading python module Expected results: Load python module without error Additional info: https://github.com/FreeRADIUS/freeradius-server/blob/f4f26418724ee68e7bda8dbea989bc35479c4029/src/modules/rlm_python/rlm_python.c#L771 As per below code it seems it is expecting library version name should be in this format (libpythonpy_major.py_minor.so) but by default library available on system after install python library as a name "libpython2.7.so.1.0" so after install the Freeradius it needs to create symlink of libpython as freeradius code expects. python_dlhandle = dlopen("libpython" STRINGIFY(PY_MAJOR_VERSION) "." STRINGIFY(PY_MINOR_VERSION) ".so", RTLD_NOW | RTLD_GLOBAL); freeradius installation code needs to create symlink from libpython as below ln -sf /usr/lib64/libpython2.7.so.1.0 /usr/lib64/libpython2.7.so
Thank you for the report, Nilesh. This is indeed is a problem. However, adding such a symlink in the freeradius-python package is the wrong solution. This symlink belongs to the python-devel package, and the actual workaround would be installing that package. Meanwhile I submitted a patch upstream fixing this issue another way: https://github.com/FreeRADIUS/freeradius-server/pull/1592 Let's see what upstream replies.
Sorry, reset the qa_ack accidentally (not sure how that happened). Patrik, could you please restore it? Thank you.
Upstream wasn't interested in taking the fix. If we are to fix this, we'll need to carry a patch to generated configure files ourselves, which is far from optimal. Provided there is a workaround of installing the python-devel package, I suggest we close this as WONTFIX. Anyone against?
Going to try to convince upstream again after consulting with others. Perhaps we can still get this in.
Hi Nikolai, yes, this workaround works, I have tested it, but I think it is not correct that base package depends on devel package. Convince upstream is better way :-). I suggest keep this bug open for now.
Upstream has accepted my fix. Jaroslav, Patrik, please consider ACK'ing. The test would be trivial: 1. Make sure python-devel package is not installed and/or there is no "/usr/lib64/libpython2.7.so" file, or similar unversioned library. 2. Start FreeRADIUS. 3. Test passes if python modules work and/or the log doesn't contain the following or similar message: Failed loading libpython symbols into global symbol table: libpython2.7.so: cannot open shared object file: No such file or directory
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2017:1954