rlm_sql_mysql on FreeBSD 5.4 - Segmentation fault at startup

[Dusty Doris]

I'm running it fine right now on freebsd 5.4.  I installed everything from 
ports.  I first installed mysql server from ports.

I'm runnning mysql-server-4.1.14

cd /usr/ports/databases/mysql41-server/
make install clean (I didn't specifiy any unique make options)_

cd /usr/ports/net/freeradius
make install clean (select mysql)

$uname -a
FreeBSD radsql1.soc.int 5.4-RELEASE-p7 FreeBSD 5.4-RELEASE-p7 #0: Tue Sep 
27 14:14:11 EDT 2005 
root at radacctm.lab.soc.int:/usr/obj/usr/src/sys/carp  i386


On Thu, 8 Dec 2005, Matthew Horoschun wrote:

> Hi All,
>
> I'm having trouble getting FreeRadius (CVS) working with MySQL 5.0.15 on 
> FreeBSD 5.4. I have been testing successfully with PostgreSQL up until now.
>
> Running under gdb:
>
> ...
> rlm_sql (sql): Attempting to connect rlm_sql_mysql #0
> rlm_sql_mysql: Starting connect to MySQL server for #0
> rlm_sql (sql): Connected new DB handle, #0
> rlm_sql (sql): failed after re-connect
> rlm_sql (sql): Error retrieving group list
> rlm_sql (sql): Error processing groups; rejecting user
> rlm_sql (sql): Released sql socket id: 0
>
> Program received signal SIGSEGV, Segmentation fault.
> [Switching to Thread 1 (LWP 100524)]
> 0x08059635 in safe_unlock (instance=0x0) at modcall.c:227
> 227             if (instance->mutex)
> (gdb) bt
> #0  0x08059635 in safe_unlock (instance=0x0) at modcall.c:227
> #1  0x0805971c in call_modsingle (component=1, sp=0x8139140, 
> request=0x806f800, default_result=6) at modcall.c:258
> #2  0x08059dc6 in modcall (component=1, c=0x8139140, request=0x806f800) at 
> modcall.c:590
> #3  0x0805979f in call_one (component=1, p=0x8139140, request=0x806f800, 
> priority=0xbfbfd1e0, result=0xbfbfd1e4) at modcall.c:287
> #4  0x08059896 in call_modgroup (component=1, g=0x8135ec0, request=0x806f800, 
> default_result=6) at modcall.c:342
> #5  0x08059d3b in modcall (component=1, c=0x8135ec0, request=0x806f800) at 
> modcall.c:575
> #6  0x0805876c in indexed_modcall (comp=1, idx=0, request=0x806f800) at 
> modules.c:428
> #7  0x08059271 in module_authorize (autz_type=0, request=0x806f800) at 
> modules.c:936
> #8  0x0804d412 in rad_authenticate (request=0x806f800) at auth.c:548
> #9  0x0805e00a in rad_respond (request=0x806f800, fun=0x804d25c 
> <rad_authenticate>) at request_process.c:451
> #10 0x0805fbad in thread_pool_addrequest (request=0x806f800, fun=0x804d25c 
> <rad_authenticate>) at threads.c:901
> #11 0x0805be34 in main (argc=2, argv=0xbfbfebfc) at radiusd.c:668
>
>
> I noticed that people have had somewhat similar problems 
> (http://lists.cistron.nl/pipermail/freeradius-users/2005-September/047030.html), 
> but I'm not sure that this is the same thing.
>
> Matthew.
> - List info/subscribe/unsubscribe? See 
> http://www.freeradius.org/list/users.html
>