I recently upgraded to 2.0.4, and now I'm seeing the following error when I start FreeRADIUS: radiusd -X: /opt/freeradius-2.0.4/etc/raddb/radiusd.conf[210]: Error binding to port for 0.0.0.0 port 1812 radius.log: Sat May 3 20:21:39 2008 : Error: ERROR: Failed to open socket: Sat May 3 20:21:39 2008 : Error: /opt/freeradius-2.0.4/etc/raddb/radiusd.conf[210]: Error binding to port for 0.0.0.0 port 1812 Sun May 4 01:37:24 2008 : Info: Ready to process requests. I tried hardcoding the IP & Port in radiusd.conf, but it didn't make any difference. I reviewed posts to this list and found others have seen similar errors, but their fixes didn't apply to my situation. Any suggestinons? Thanks!
Lemaster, Rob wrote:
I recently upgraded to 2.0.4, and now I'm seeing the following error when I start FreeRADIUS: ... Sat May 3 20:21:39 2008 : Error: ERROR: Failed to open socket: Sat May 3 20:21:39 2008 : Error: /opt/freeradius-2.0.4/etc/raddb/radiusd.conf[210]: Error binding to port for 0.0.0.0 port 1812 Sun May 4 01:37:24 2008 : Info: Ready to process requests.
So it *does* eventually start. Do you change the configuration between the start attempts? If not, then it's difficult to say why it starts one time, and then not another. Maybe it's port re-use timers? Or something like the FreeBSD Jail issue? Is there a ktrace functionality on your system to see which system calls it's doing, and what the results are? Alan DeKok.
participants (2)
-
Alan DeKok -
Lemaster, Rob