All, Our RADIUS server has been up and running fine for 127 days now. Suddenly today it no longer runs. I tried to put it into debug mode and got the following output: ---- [root@RAD01 ~]# /opt/freeradius/sbin/radiusd -X Starting - reading configuration files ... reread_config: reading radiusd.conf Config: including file: /opt/freeradius/etc/raddb/proxy.conf Config: including file: /opt/freeradius/etc/raddb/trs_proxy.conf Config: including file: /opt/freeradius/etc/raddb/clients.conf Config: including file: /opt/freeradius/etc/raddb/trs_clients.conf Config: including file: /opt/freeradius/etc/raddb/snmp.conf Config: including file: /opt/freeradius/etc/raddb/sqlcounter.conf Config: including file: /opt/freeradius/etc/raddb/eap.conf Config: including file: /opt/freeradius/etc/raddb/sql.conf main: prefix = "/opt/freeradius" main: localstatedir = "/opt/freeradius/var" main: logdir = "/opt/freeradius/var/log/radius" main: libdir = "/opt/freeradius/lib" main: radacctdir = "/opt/freeradius/var/log/radius/radacct" main: hostname_lookups = no main: max_request_time = 30 main: cleanup_delay = 5 main: max_requests = 1024 main: delete_blocked_requests = 0 main: port = 0 main: allow_core_dumps = no main: log_stripped_names = no main: log_file = "/opt/freeradius/var/log/radius/radius.log" main: log_auth = yes main: log_auth_badpass = yes main: log_auth_goodpass = no main: pidfile = "/opt/freeradius/var/run/radiusd/radiusd.pid" main: user = "trustive" main: group = "trustive" main: usercollide = no main: lower_user = "no" main: lower_pass = "no" main: nospace_user = "no" main: nospace_pass = "no" main: checkrad = "/opt/freeradius/sbin/checkrad" main: proxy_requests = yes proxy: retry_delay = 5 proxy: retry_count = 3 proxy: synchronous = no proxy: default_fallback = yes proxy: dead_time = 120 proxy: post_proxy_authorize = no proxy: wake_all_if_all_dead = no security: max_attributes = 200 security: reject_delay = 1 security: status_server = no main: debug_level = 0 read_config_files: reading dictionary read_config_files: reading naslist Using deprecated naslist file. Support for this will go away soon. read_config_files: reading clients /opt/freeradius/etc/raddb/radiusd.conf[751]: Missing client name ----- Can anyone shed any light on this? Unfortunately for me, one of our developers was working on our production server but *claims* not to have changed anything of any consequence... I'm really unsure of where this is coming from! Has anyone seen this error before or could anyone at least point me in the right direction? Best regards, -michelle.
Michelle Gates wrote:
Our RADIUS server has been up and running fine for 127 days now. Suddenly today it no longer runs. I tried to put it into debug mode and got the following output:
read_config_files: reading clients /opt/freeradius/etc/raddb/radiusd.conf[751]: Missing client name
Look at line 751 of clients.conf. It's not formatted correctly.
Can anyone shed any light on this? Unfortunately for me, one of our developers was working on our production server but *claims* not to have changed anything of any consequence...
The error message above would tend to disagree with him. Alan DeKok. -- http://deployingradius.com - The web site of the book http://deployingradius.com/blog/ - The blog
Thanks for your help Alan. I figured it out - someone had created a blank entry into our clients.conf file. *sigh* Thanks for your help!!! -michelle. -----Original Message----- From: freeradius-users-bounces+michelle=trustive.com@lists.freeradius.org [mailto:freeradius-users-bounces+michelle=trustive.com@lists.freeradius.org] On Behalf Of Alan DeKok Sent: 24-Jan-07 4:22 PM To: FreeRadius users mailing list Subject: Re: RADIUS will no longer start! Michelle Gates wrote:
Our RADIUS server has been up and running fine for 127 days now. Suddenly today it no longer runs. I tried to put it into debug mode and got the following output:
read_config_files: reading clients /opt/freeradius/etc/raddb/radiusd.conf[751]: Missing client name
Look at line 751 of clients.conf. It's not formatted correctly.
Can anyone shed any light on this? Unfortunately for me, one of our developers was working on our production server but *claims* not to have changed anything of any consequence...
The error message above would tend to disagree with him. Alan DeKok. -- http://deployingradius.com - The web site of the book http://deployingradius.com/blog/ - The blog - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html -- No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.5.432 / Virus Database: 268.17.8/649 - Release Date: 1/23/2007 8:40 PM
Hi,
read_config_files: reading clients /opt/freeradius/etc/raddb/radiusd.conf[751]: Missing client name
look at line 751 of the radiusd.conf file, or in clients.conf. Is the entry syntactically correct? If it is a DNS hostname, does it resolve to an IP address correctly? Greetings, Stefan Winter -- Stefan WINTER RESTENA Foundation - Réseau Téléinformatique de l'Education Nationale et de la Recherche R&D Engineer 6, rue Richard Coudenhove-Kalergi L-1359 Luxembourg email: stefan.winter@restena.lu Tel.: +352 424409-1 http://www.restena.lu Fax: +352 422473
Michelle Gates schrieb:
All,
Our RADIUS server has been up and running fine for 127 days now. Suddenly today it no longer runs. I tried to put it into debug mode and got the following output:
----
[root@RAD01 ~]# /opt/freeradius/sbin/radiusd -X Starting - reading configuration files ... reread_config: reading radiusd.conf Config: including file: /opt/freeradius/etc/raddb/proxy.conf Config: including file: /opt/freeradius/etc/raddb/trs_proxy.conf Config: including file: /opt/freeradius/etc/raddb/clients.conf Config: including file: /opt/freeradius/etc/raddb/trs_clients.conf Config: including file: /opt/freeradius/etc/raddb/snmp.conf Config: including file: /opt/freeradius/etc/raddb/sqlcounter.conf Config: including file: /opt/freeradius/etc/raddb/eap.conf Config: including file: /opt/freeradius/etc/raddb/sql.conf main: prefix = "/opt/freeradius" main: localstatedir = "/opt/freeradius/var" main: logdir = "/opt/freeradius/var/log/radius" main: libdir = "/opt/freeradius/lib" main: radacctdir = "/opt/freeradius/var/log/radius/radacct" main: hostname_lookups = no main: max_request_time = 30 main: cleanup_delay = 5 main: max_requests = 1024 main: delete_blocked_requests = 0 main: port = 0 main: allow_core_dumps = no main: log_stripped_names = no main: log_file = "/opt/freeradius/var/log/radius/radius.log" main: log_auth = yes main: log_auth_badpass = yes main: log_auth_goodpass = no main: pidfile = "/opt/freeradius/var/run/radiusd/radiusd.pid" main: user = "trustive" main: group = "trustive" main: usercollide = no main: lower_user = "no" main: lower_pass = "no" main: nospace_user = "no" main: nospace_pass = "no" main: checkrad = "/opt/freeradius/sbin/checkrad" main: proxy_requests = yes proxy: retry_delay = 5 proxy: retry_count = 3 proxy: synchronous = no proxy: default_fallback = yes proxy: dead_time = 120 proxy: post_proxy_authorize = no proxy: wake_all_if_all_dead = no security: max_attributes = 200 security: reject_delay = 1 security: status_server = no main: debug_level = 0 read_config_files: reading dictionary read_config_files: reading naslist Using deprecated naslist file. Support for this will go away soon. read_config_files: reading clients /opt/freeradius/etc/raddb/radiusd.conf[751]: Missing client name
The 751 maybe disleading, as you may not neccessarily find relevant information at line 751 in radiusd.conf. The server is reading clients and doing this, it complains about Missing client name You should have a look at clients.conf. Norbert Wegener
-----
Can anyone shed any light on this? Unfortunately for me, one of our developers was working on our production server but *claims* not to have changed anything of any consequence...
I'm really unsure of where this is coming from! Has anyone seen this error before or could anyone at least point me in the right direction?
Best regards,
-michelle.
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Michelle, Seems like someone took off your NASes either from your naslist or clients.conf files, in your raddb dir. In those files you need at least an entry like this (for clients.conf): client 10.10.10.1 { secret = secret123 } Where 10.10.10.1 would be your NAS address and secret123 your secret. By your debug, it seems that you're using the naslist file. As naslist in deprecated, please use the clients.conf instead. Hope this helps. Guilherme On 1/24/07, Michelle Gates <michelle@trustive.com> wrote:
All,
Our RADIUS server has been up and running fine for 127 days now. Suddenly today it no longer runs. I tried to put it into debug mode and got the following output:
----
[root@RAD01 ~]# /opt/freeradius/sbin/radiusd -X Starting - reading configuration files ... reread_config: reading radiusd.conf Config: including file: /opt/freeradius/etc/raddb/proxy.conf Config: including file: /opt/freeradius/etc/raddb/trs_proxy.conf Config: including file: /opt/freeradius/etc/raddb/clients.conf Config: including file: /opt/freeradius/etc/raddb/trs_clients.conf Config: including file: /opt/freeradius/etc/raddb/snmp.conf Config: including file: /opt/freeradius/etc/raddb/sqlcounter.conf Config: including file: /opt/freeradius/etc/raddb/eap.conf Config: including file: /opt/freeradius/etc/raddb/sql.conf main: prefix = "/opt/freeradius" main: localstatedir = "/opt/freeradius/var" main: logdir = "/opt/freeradius/var/log/radius" main: libdir = "/opt/freeradius/lib" main: radacctdir = "/opt/freeradius/var/log/radius/radacct" main: hostname_lookups = no main: max_request_time = 30 main: cleanup_delay = 5 main: max_requests = 1024 main: delete_blocked_requests = 0 main: port = 0 main: allow_core_dumps = no main: log_stripped_names = no main: log_file = "/opt/freeradius/var/log/radius/radius.log" main: log_auth = yes main: log_auth_badpass = yes main: log_auth_goodpass = no main: pidfile = "/opt/freeradius/var/run/radiusd/radiusd.pid" main: user = "trustive" main: group = "trustive" main: usercollide = no main: lower_user = "no" main: lower_pass = "no" main: nospace_user = "no" main: nospace_pass = "no" main: checkrad = "/opt/freeradius/sbin/checkrad" main: proxy_requests = yes proxy: retry_delay = 5 proxy: retry_count = 3 proxy: synchronous = no proxy: default_fallback = yes proxy: dead_time = 120 proxy: post_proxy_authorize = no proxy: wake_all_if_all_dead = no security: max_attributes = 200 security: reject_delay = 1 security: status_server = no main: debug_level = 0 read_config_files: reading dictionary read_config_files: reading naslist Using deprecated naslist file. Support for this will go away soon. read_config_files: reading clients /opt/freeradius/etc/raddb/radiusd.conf[751]: Missing client name
-----
Can anyone shed any light on this? Unfortunately for me, one of our developers was working on our production server but *claims* not to have changed anything of any consequence...
I'm really unsure of where this is coming from! Has anyone seen this error before or could anyone at least point me in the right direction?
Best regards,
-michelle.
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
On Wednesday 24 January 2007 10:02, Michelle Gates wrote:
read_config_files: reading clients /opt/freeradius/etc/raddb/radiusd.conf[751]: Missing client name
-----
Can anyone shed any light on this? Unfortunately for me, one of our developers was working on our production server but *claims* not to have changed anything of any consequence...
I'm really unsure of where this is coming from! Has anyone seen this error before or could anyone at least point me in the right direction?
Since you have multiple people poking around on a production config, you are using some sort of revision control... right? ;-) I tried to reproduce the error locally and here is what I've done to cause the same error message to show up. == clients.conf == client { secret = testing shortname = testing nastype = other } == clients.conf == [root@noctest raddb.dial]# /usr/sbin/radiusd -X ... read_config_files: reading clients /etc/raddb/radiusd.conf[327]: Missing client name To fix the issue, find the broken client entry and either comment it out or restore it with the correct client IP. Kevin Bonner
participants (7)
-
Alan DeKok -
Guilherme Franco -
Kevin Bonner -
Michelle Gates -
Norbert Wegener -
Stefan Winter -
Zoltan Ori