Re : 2.0.0-pre : Failed to open socket.
ERROR: Failed to open socket: check the port 1812 if it is being used. Or you can also run radius on the old school port 1645 for testing. ================================================== Benjamin K. Eshun ----- Message d'origine ---- De : Debashis Prusty <dprusty@systemsfusion.com> À : FreeRadius users mailing list <freeradius-users@lists.freeradius.org> Envoyé le : Mercredi, 20 Juin 2007, 18h02mn 39s Objet : 2.0.0-pre : Failed to open socket. I am trying to rum Freeradius on Solaris with MySQL. Logs are pasted below. Its working fine for earlier versions of Freeradius. Do any one have the solution? Thanks in advance, Debashis ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ freeradius/sbin # ./radiusd -X Config: including file: /opt/sf/freeradius/etc/raddb/radiusd.conf Config: including file: /opt/sf/freeradius/etc/raddb/proxy.conf Config: including file: /opt/sf/freeradius/etc/raddb/clients.conf Config: including file: /opt/sf/freeradius/etc/raddb/snmp.conf Config: including file: /opt/sf/freeradius/etc/raddb/eap.conf Config: including file: /opt/sf/freeradius/etc/raddb/sql.conf Config: including file: /opt/sf/freeradius/etc/raddb/sql/mysql-dialup.conf FreeRADIUS Version 2.0.0-pre1, for host i386-pc-solaris2.10, built on Jun 19 2007 at 10:29:22 Starting - reading configuration files ... read_config_files: reading dictionary main { prefix = "/opt/sf/freeradius" localstatedir = "/opt/sf/freeradius/var" logdir = "/opt/sf/freeradius/var/log/radius" libdir = "/opt/sf/freeradius/lib" radacctdir = "/opt/sf/freeradius/var/log/radius/radacct" hostname_lookups = no max_request_time = 30 cleanup_delay = 5 max_requests = 1024 allow_core_dumps = no log_stripped_names = no log_file = "/opt/sf/freeradius/var/log/radius/radius.log" log_auth = no log_auth_badpass = no log_auth_goodpass = no pidfile = "/opt/sf/freeradius/var/run/radiusd/radiusd.pid" checkrad = "/opt/sf/freeradius/sbin/checkrad" debug_level = 0 proxy_requests = yes log { syslog_facility = "daemon" } proxy server { retry_delay = 5 retry_count = 3 default_fallback = no dead_time = 120 wake_all_if_all_dead = no } security { max_attributes = 200 reject_delay = 1 status_server = yes } } home_server localhost { ipaddr = 127.0.0.1 IP address [127.0.0.1] port = 1812 type = "auth" secret = "testing123" response_window = 20 max_outstanding = 65536 zombie_period = 40 status_check = "status-server" ping_check = "none" ping_interval = 30 check_interval = 30 num_answers_to_alive = 3 num_pings_to_alive = 3 revive_interval = 120 status_check_timeout = 4 } server_pool my_auth_failover { type = my_auth_failover home_server = localhost } realm example.com { auth_pool = my_auth_failover } realm LOCAL { ldflag = fail_over } port = 1812 listen { type = "auth" ipaddr = * port = 0 ERROR: Failed to open socket: /opt/sf/freeradius/etc/raddb/radiusd.conf[195]: Error binding to port for 0.0.0.0 port 1812 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html _____________________________________________________________________________ Ne gardez plus qu'une seule adresse mail ! Copiez vos mails vers Yahoo! Mail
No. I have tried this. As I have mentioned earlier versions like 1.1.4 & 1.1.6 are working fine. Problem is with version 2.0.0, where the listen part is not comented. Lets think of something else. ERROR: Failed to open socket: check the port 1812 if it is being used. Or you can also run radius on the old school port 1645 for testing. ================================================== Benjamin K. Eshun ----- Message d'origine ---- De : Debashis Prusty <dprusty@systemsfusion.com> À : FreeRadius users mailing list <freeradius-users@lists.freeradius.org> Envoyé le : Mercredi, 20 Juin 2007, 18h02mn 39s Objet : 2.0.0-pre : Failed to open socket. I am trying to rum Freeradius on Solaris with MySQL. Logs are pasted below. Its working fine for earlier versions of Freeradius. Do any one have the solution? Thanks in advance, Debashis ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ freeradius/sbin # ./radiusd -X Config: including file: /opt/sf/freeradius/etc/raddb/radiusd.conf Config: including file: /opt/sf/freeradius/etc/raddb/proxy.conf Config: including file: /opt/sf/freeradius/etc/raddb/clients.conf Config: including file: /opt/sf/freeradius/etc/raddb/snmp.conf Config: including file: /opt/sf/freeradius/etc/raddb/eap.conf Config: including file: /opt/sf/freeradius/etc/raddb/sql.conf Config: including file: /opt/sf/freeradius/etc/raddb/sql/mysql-dialup.conf FreeRADIUS Version 2.0.0-pre1, for host i386-pc-solaris2.10, built on Jun 19 2007 at 10:29:22 Starting - reading configuration files ... read_config_files: reading dictionary main { prefix = "/opt/sf/freeradius" localstatedir = "/opt/sf/freeradius/var" logdir = "/opt/sf/freeradius/var/log/radius" libdir = "/opt/sf/freeradius/lib" radacctdir = "/opt/sf/freeradius/var/log/radius/radacct" hostname_lookups = no max_request_time = 30 cleanup_delay = 5 max_requests = 1024 allow_core_dumps = no log_stripped_names = no log_file = "/opt/sf/freeradius/var/log/radius/radius.log" log_auth = no log_auth_badpass = no log_auth_goodpass = no pidfile = "/opt/sf/freeradius/var/run/radiusd/radiusd.pid" checkrad = "/opt/sf/freeradius/sbin/checkrad" debug_level = 0 proxy_requests = yes log { syslog_facility = "daemon" } proxy server { retry_delay = 5 retry_count = 3 default_fallback = no dead_time = 120 wake_all_if_all_dead = no } security { max_attributes = 200 reject_delay = 1 status_server = yes } } home_server localhost { ipaddr = 127.0.0.1 IP address [127.0.0.1] port = 1812 type = "auth" secret = "testing123" response_window = 20 max_outstanding = 65536 zombie_period = 40 status_check = "status-server" ping_check = "none" ping_interval = 30 check_interval = 30 num_answers_to_alive = 3 num_pings_to_alive = 3 revive_interval = 120 status_check_timeout = 4 } server_pool my_auth_failover { type = my_auth_failover home_server = localhost } realm example.com { auth_pool = my_auth_failover } realm LOCAL { ldflag = fail_over } port = 1812 listen { type = "auth" ipaddr = * port = 0 ERROR: Failed to open socket: /opt/sf/freeradius/etc/raddb/radiusd.conf[195]: Error binding to port for 0.0.0.0 port 1812 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html ________________________________ Ne gardez plus qu'une seule adresse mail ! Copiez vos mails <http://www.trueswitch.com/yahoo-fr/> vers Yahoo! Mail
Debashis Prusty wrote:
No. I have tried this. As I have mentioned earlier versions like 1.1.4 & 1.1.6 are working fine. Problem is with version 2.0.0, where the listen part is not comented. Lets think of something else.
As I said earlier , but will say again for clarity. It *is* a bug in pre1, Alan was trying something out that broke binding in some BSD based operating systems and looks like Solaris too ... The code has been taken out in the CVS head... if you want to use the new features of 2** (of which there are many) use the CVS head not pre1. In my opinion the biggest advantage of 2.*.* is the FreeRADIUS unlang (see man unlang) which wasn't included in pre1 anyway. -- Arran Cudbard-Bell (A.Cudbard-Bell@sussex.ac.uk) Authentication, Authorisation and Accounting Officer Infrastructure Services | ENG1 E1-1-08 University Of Sussex, Brighton EXT:01273 873900 | INT: 3900
Hi Arran and all, In message <467978FF.4010403@sussex.ac.uk>, Arran Cudbard-Bell <A.Cudbard-Bell@sussex.ac.uk> writes
Debashis Prusty wrote:
No. I have tried this. As I have mentioned earlier versions like 1.1.4 & 1.1.6 are working fine. Problem is with version 2.0.0, where the listen part is not comented. Lets think of something else.
As I said earlier , but will say again for clarity.
It *is* a bug in pre1, Alan was trying something out that broke binding in some BSD based operating systems and looks like Solaris too ...
Following a little bit of detective work with gdb, I realised that the problem is with the udpfromto code in -pre1, at least on FreeBSD. Passing --without-udpfromto to configure on FreeBSD means 2.0.0-pre1 works on FreeBSD 6.2-RELEASE. Supposedly udpfromto works on BSD like operating systems, but I've never got it to work on FreeBSD, even in 1.1.x.
The code has been taken out in the CVS head... if you want to use the new features of 2** (of which there are many) use the CVS head not pre1.
Has the faulty code really been taken out or fixed, or is the resolution of this situation a side-effect of udpfromto being disabled in HEAD at the moment?
In my opinion the biggest advantage of 2.*.* is the FreeRADIUS unlang (see man unlang) which wasn't included in pre1 anyway.
I have a working FreeBSD port for 2.0.0-pre1 on my system, but I'm loath to ask for it to be committed. I have to patch for bugs #452, 453 and 454 (thanks to Nicolas for committing my enhanced patch for #454 to HEAD and the 1.1 branch), and pass --without-udpfromto to get the thing to work at all - though it is now working on my live system. Further, pre1 has features missing compared to HEAD (not least the sites-available / sites-enabled stuff in raddb, which leads to quite a few changes in the configuration file), the PGP signature for the pre1 .tar.gz doesn't verify and the .tar.bz2 isn't PGP signed, also raddb/certs/bootstrap doesn't work for me in pre1. I haven't bothered to try to debug raddb/certs/bootstrap yet; I have my own way of building the necessary certificates. Nevertheless, if any FreeBSD users want a tarball of my 2.0.0-pre1 port, please email me. At the moment, it couldn't be committed to the ports tree because the patches are organised incorrectly, but it does work on my machine. I had a relatively painless migration to a version 2 configuration - svn_load_dirs to update the configuration vendor branch in my private Subversion repository, svn copy to tag that vendor drop, svn merge the vendor branch changes to my live configuration, a bit of manual conflict resolution followed svn resolved (though less than I'd feared - Subversion got most things right by itself), then svn ci when I'd done. That said, all I've done this far is port my version 1.1.6 configuration to version 2 configuration files; I've not taken advantage of anything new, nor will I do so without sites-available / sites-enabled and some other things that not in pre1. Is there any hope of a 2.0.0-pre2 release any time soon? I realise that version 2 is still under active development, that HEAD has just gone through a period of being uninstallable for a while so it may be wise to let things settle a while longer, and that the priority is on development rather than release of even a "pre" version. That said, I feel that there may be sufficient broken or missing in 2.0.0-pre1 to discourage further testing now, which I understood to be the whole point of shipping 2.0.0-pre1. Whilst "it's fixed in HEAD" is fine for those who hang out here, FreeBSD ports are not really supposed to depend on a CVS or Subversion checkout for their main tarball. Recent discussion on freebsd-ports has suggested that, at most, using a checkout should be a non-default option. As development on 2.x continues, the FreeBSD package list is changing, so that really leaves my only options at the moment as patching 2.0.0-pre1 or creating an unofficial 2.0.0-pre2 based on a tarball I'd have to host myself. On that note, whilst I know this isn't the best place to report it (what is - bug database?), there's a typo in HEAD. raddb/Makefile version 1.26 has a typo in the second line of the install target - it should be sites-available not sites-evailable. Best wishes to you all, David -- David Wood david@wood2.org.uk
As I said earlier , but will say again for clarity.
It *is* a bug in pre1, Alan was trying something out that broke binding in some BSD based operating systems and looks like Solaris too ...
Following a little bit of detective work with gdb, I realised that the problem is with the udpfromto code in -pre1, at least on FreeBSD. Passing --without-udpfromto to configure on FreeBSD means 2.0.0-pre1 works on FreeBSD 6.2-RELEASE. Supposedly udpfromto works on BSD like operating systems, but I've never got it to work on FreeBSD, even in 1.1.x.
Thats the one !
The code has been taken out in the CVS head... if you want to use the new features of 2** (of which there are many) use the CVS head not pre1.
Has the faulty code really been taken out or fixed, or is the resolution of this situation a side-effect of udpfromto being disabled in HEAD at the moment?
Taken out as far as I know, but you'd have to ask Alan for that one.
Is there any hope of a 2.0.0-pre2 release any time soon? I realise that version 2 is still under active development,
Very active, though I did hear a mention of pre2 coming out soonish :) Currently trying to help fix/diagnose a very weird bug that breaks FR on 64 bit PPC based OSX boxes ... Ah do you run a 64bit BSD machine ? If so would really appreciate feedback on whether FR can do EAP without bombing out (though the issue isn't actually with the EAP module) ...
that HEAD has just gone through a period of being uninstallable for a while so it may be wise to let things settle a while longer Really ? It's been building fine for me ? What error do you get ?
Hi,
The code has been taken out in the CVS head... if you want to use the new features of 2** (of which there are many) use the CVS head not pre1.
Has the faulty code really been taken out or fixed, or is the resolution of this situation a side-effect of udpfromto being disabled in HEAD at the moment?
from what I recall the code is disabled (and was wrong anyway - cant dig out the post from Alan but it was near beginning of this month)
Further, pre1 has features missing compared to HEAD (not least the sites-available / sites-enabled stuff in raddb, which leads to quite a few changes in the configuration file), the PGP signature for the pre1 .tar.gz doesn't verify and the .tar.bz2 isn't PGP signed, also raddb/certs/bootstrap doesn't work for me in pre1. I haven't bothered to try to debug raddb/certs/bootstrap yet; I have my own way of building the necessary certificates.
Nevertheless, if any FreeBSD users want a tarball of my 2.0.0-pre1 port, please email me. At the moment, it couldn't be committed to the ports tree because the patches are organised incorrectly, but it does work on my machine.
ignore pre1. work with pre2 (aka current HEAD). alan
David Wood wrote:
Following a little bit of detective work with gdb, I realised that the problem is with the udpfromto code in -pre1, at least on FreeBSD.
Yes.... that's been known for a while, and has been mentioned on this list. There was no need to investigate, just upgrade to CVS head, which people have said works.
Passing --without-udpfromto to configure on FreeBSD means 2.0.0-pre1 works on FreeBSD 6.2-RELEASE. Supposedly udpfromto works on BSD like operating systems, but I've never got it to work on FreeBSD, even in 1.1.x.
That's news to me.
Has the faulty code really been taken out or fixed, or is the resolution of this situation a side-effect of udpfromto being disabled in HEAD at the moment?
I don't have access to a current BSD box, so I have no idea if it's fixed. I do know that the udpfromto code works for me on Linux.
I have a working FreeBSD port for 2.0.0-pre1 on my system, but I'm loath to ask for it to be committed. I have to patch for bugs #452, 453 and 454 (thanks to Nicolas for committing my enhanced patch for #454 to HEAD and the 1.1 branch), and pass --without-udpfromto to get the thing to work at all - though it is now working on my live system.
Bugs #452 and 453 have fixed in CVS head for almost a month.
Further, pre1 has features missing compared to HEAD (not least the sites-available / sites-enabled stuff in raddb, which leads to quite a few changes in the configuration file),
It's not *necessary* to use it, but it is *extremely* useful. It will be more useful in the future, for a number of reasons.
the PGP signature for the pre1 .tar.gz doesn't verify
It does on my system. What's the error?
and the .tar.bz2 isn't PGP signed, also raddb/certs/bootstrap doesn't work for me in pre1.
What is the error? I think it's likely using the wrong "make" program. That can be fixed by turning the Makefile from a GNU make file into a more standard Make file.
Is there any hope of a 2.0.0-pre2 release any time soon?
Yes. Hopefully this week, or next week.
Whilst "it's fixed in HEAD" is fine for those who hang out here, FreeBSD ports are not really supposed to depend on a CVS or Subversion checkout for their main tarball. Recent discussion on freebsd-ports has suggested that, at most, using a checkout should be a non-default option. As development on 2.x continues, the FreeBSD package list is changing, so that really leaves my only options at the moment as patching 2.0.0-pre1 or creating an unofficial 2.0.0-pre2 based on a tarball I'd have to host myself.
I would suggest *not* creating an official port of 2.0.0 until it has been officially released. That is, you can try creating a local port, but *please* don't commit it to the FreeBSD "ports" tree. It's not stable, it's not meant to be stable, it's not meant to be used in any production environment.
On that note, whilst I know this isn't the best place to report it (what is - bug database?), there's a typo in HEAD. raddb/Makefile version 1.26 has a typo in the second line of the install target - it should be sites-available not sites-evailable.
Fixed, thanks. Alan DeKok.
participants (6)
-
A.L.M.Buxey＠lboro.ac.uk -
Alan DeKok -
Arran Cudbard-Bell -
David Wood -
Debashis Prusty -
Eshun Benjamin