Bug 1394787 - undefined symbol: get_vtable in /usr/lib64/libtdsodbc.so.0 with freeradius-unixODBC
Summary: undefined symbol: get_vtable in /usr/lib64/libtdsodbc.so.0 with freeradius-un...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: freeradius
Version: 7.2
Hardware: x86_64
OS: Linux
high
medium
Target Milestone: rc
: ---
Assignee: Nikolai Kondrashov
QA Contact: Jaroslav Aster
URL:
Whiteboard:
Depends On: 1391960
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-14 13:08 UTC by Marcel Kolaja
Modified: 2020-03-11 15:22 UTC (History)
17 users (show)

Fixed In Version: freeradius-3.0.4-7.el7_3
Doc Type: Bug Fix
Doc Text:
Previously, the FreeRADIUS server exported symbols that were conflicting with symbols defined in the libltdl library. When the FreeRADIUS server tried to open a connection to the MSSQL server using the rlm_sql_odbc interface and UnixODBC was configured to use the FreeTDS library, the connection failed with the following error message: "undefined symbol: get_vtable" This update renames the conflicting symbols. As a result, connections to MSSQL servers no longer fail in the described situation.
Clone Of: 1391960
Environment:
Last Closed: 2017-01-17 18:08:39 UTC
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2017:0072 0 normal SHIPPED_LIVE freeradius bug fix update 2017-01-17 22:50:30 UTC

Description Marcel Kolaja 2016-11-14 13:08:23 UTC
This bug has been copied from bug #1391960 and has been proposed
to be backported to 7.3 z-stream (EUS).

Comment 6 errata-xmlrpc 2017-01-17 18:08:39 UTC
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://rhn.redhat.com/errata/RHBA-2017-0072.html


Note You need to log in before you can comment on or make changes to this bug.