Enabling ldap causes freeradius server to not start up.
Alan DeKok
aland at deployingradius.com
Sat Oct 10 09:07:23 CEST 2009
Jesper Klit Jensen wrote:
> Freeradius: 2.1.6 OS: Open Suse 11.0 LDAP 2.4.9
>
> Problem is when running radiusd in forground with logging:
> Thread spawned new child 1. Total threads in pool: 1
> Thread 1 waiting to be assigned a request
> Thread pool initialized
> radiusd: #### Opening IP addresses and Ports ####
> listen {
> type = "auth"
> ipaddr = x.x.x.x
> port = 0
> }
> listen {
> type = "acct"
> ipaddr = x.x.x.x
> port = 0
>
> No more after that. It will only startup if ldap is total disabled.
What does that mean? You turn off the LDAP server? Or you delete
LDAP from the FreeRADIUS configuration?
> LDAP user account works.
>
> Please help me with some hints for finding this problem.
Use strace to see what it's doing, and where it's blocking.
Odds are that FreeRADIUS is doing a system call, and the OS is never
returning. Fix the OS, and FreeRADIUS will work.
Alan DeKok.
More information about the Freeradius-Users
mailing list