radiusd exited on signal 10 when used with sql authorization

Christian Kujau <[email protected]>
Newsgroups gmane.os.freebsd.bugbusters
Message-ID <[email protected]>
Please see attached send-pre file.

Thanks,
Christian.
-- 
BOFH excuse #308:

CD-ROM server needs recalibration

_______________________________________________
[email protected] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-bugbusters
To unsubscribe, send any mail to "[email protected]"
send-pr.txt (text/plain, 3.6 KB)
SEND-PR: -*- send-pr -*-
SEND-PR: Lines starting with `SEND-PR' will be removed automatically, as
SEND-PR: will all comments (text enclosed in `<' and `>').
SEND-PR:
SEND-PR: Please consult the following URL if you are not sure how to
SEND-PR: fill out a problem report:
SEND-PR: http://www.freebsd.org/doc/en/articles/problem-reports/
SEND-PR:
SEND-PR: Note that the Synopsis field is mandatory.
SEND-PR:
SEND-PR: Please note that (unless you state otherwise) if your report 
SEND-PR: includes a patch then it will be taken under the same license as 
SEND-PR: the one on the file(s) you want to change.
SEND-PR:
SEND-PR: BE ADVISED THAT FREEBSD PROBLEM REPORTS ARE PUBLIC INFORMATION AND
SEND-PR: WILL BE PUBLISHED AS-IS ON THE PROJECT'S MAILING LISTS AND WEB SITES.
SEND-PR: DO NOT SUBMIT ANY INFORMATION YOU DO NOT WANT MADE PUBLIC.
SEND-PR:
SEND-PR: If you wish to submit a problem report confidentially, then contact
SEND-PR: the FreeBSD bugmaster ([email protected]) to arrange for a
SEND-PR: relevant developer to be contacted.
SEND-PR:
SEND-PR: For sensitive security issues, consider contacting the FreeBSD
SEND-PR: security officer team ([email protected]) directly.
SEND-PR:
SEND-PR: Choose from the following categories:
SEND-PR:
SEND-PR: advocacy  alpha     amd64     bin       conf      docs      
SEND-PR: gnu       i386      ia64      java      kern      misc      
SEND-PR: ports     powerpc   sparc64   standards threads   usb       
SEND-PR: www       
SEND-PR:
To: [email protected]
From: Charlie & <root>
Reply-To: Charlie & <root>
Cc: 
X-send-pr-version: 3.113
X-GNATS-Notify: 


>Submitter-Id:	current-users
>Originator:	Charlie &
>Organization:	
>Confidential:	no
>Synopsis:	radiusd exited on signal 10 when used with sql authorization
>Severity:	serious
>Priority:	low
>Category:	kern
>Class:		sw-bug
>Release:	FreeBSD 6.1-STABLE amd64
>Environment:
System: FreeBSD bsd7 6.1-STABLE FreeBSD 6.1-STABLE #4: Thu May 11 17:48:43 CEST 2006 root@bsd7:/usr/obj/usr/src/sys/bsd6-7 amd64


>Description:

(this is my first PR for FreeBSD, so please bear with me if I missed something)

I've set up a FreeRadius server on this amd64 machine wich is running just 
fine using flat files ("users") to do the authorization. Now I wanted to switch
to a mysql backend (I've chosen "ldap" and "mysql" when I did "make" in the portsdir). 

Radiusd starts just fine:

Info: rlm_eap_tls: Loading the certificate file as a chain
Info: rlm_sql (sql): Driver rlm_sql_mysql (module rlm_sql_mysql) loaded and linked
Info: rlm_sql (sql): Attempting to connect to root@localhost:/conusrdb
Info: rlm_sql_mysql: Starting connect to MySQL server for #0
Info: rlm_sql_mysql: Starting connect to MySQL server for #1
Info: rlm_sql_mysql: Starting connect to MySQL server for #2
Info: rlm_sql_mysql: Starting connect to MySQL server for #3
Info: rlm_sql_mysql: Starting connect to MySQL server for #4
Info: Ready to process requests.

But when it receives an auth-request id dies with:

kernel: pid 48382 (radiusd), uid 30323: exited on signal 10

(that's why I've chosen "kern" for "Category" of this PR)

	
>How-To-Repeat:

enable "sql" in radiusd.conf:

authorize {
   ...
   sql
}

Have the NAS (Network Access Server, in my case a Netgear Wireless AP) send 
an Auth-Request to the AAA (radius server) and watch it die with:

kernel: pid 48382 (radiusd), uid 30323: exited on signal 10

Please see more details (incl. ktrace) here: http://nerdbynature.de/bits/radiusd/


Thank you for your time,
Christian.

>Fix:
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.