|->>I have a problem where I upgraded v1 to v2 of freeradius and now I can only |->start it with mode radius -X , if I try use script is simply does following. |-> |-> |-> |->>/usr/local/etc/rc.d]# ./rc.radiusd start |->>Starting FreeRADIUS:radiusd: Error: No log destination specified. |->>Radius |-> |-> |->>Any advise? |-> |->FYI - I have now made a startup script to the following. |-> |->/usr/local/sbin/radiusd -X & > /dev/null 2>&1 |-> |->To Run Freeradius as this is a production machine.
It is complaining that you have not specified a place to write a log file.
====== logdir = /var/log # # The logging messages for the server are appended to the # tail of this file. # log_file = ${logdir}/radius.log ======
This is from my radiusd.conf file. Radius writes log file messages (few and far between) to /var/log/radius.log
Fix that and you wont have to use the redirect to /dev/null, which I would not use anyway as you want log files to know if something is going wrong.
This is the beginning of my radius.conf, it seems the entry is indeed there and valid as it's same as old installation. prefix = /usr/local exec_prefix = ${prefix} sysconfdir = ${prefix}/etc localstatedir = /var sbindir = ${exec_prefix}/sbin logdir = /var/log raddbdir = ${sysconfdir}/raddb radacctdir = ${logdir}/radacct # Location of config and logfiles. confdir = ${raddbdir} run_dir = ${localstatedir}/run/radiusd # # The logging messages for the server are appended to the # tail of this file. # log_file = ${logdir}/radius.log
HTH, Keith
Have you checked permissions of the file / dir? Marcel Grandemange wrote:
|->>I have a problem where I upgraded v1 to v2 of freeradius and now I can only |->start it with mode radius -X , if I try use script is simply does following. |-> |-> |-> |->>/usr/local/etc/rc.d]# ./rc.radiusd start |->>Starting FreeRADIUS:radiusd: Error: No log destination specified. |->>Radius |-> |-> |->>Any advise? |-> |->FYI - I have now made a startup script to the following. |-> |->/usr/local/sbin/radiusd -X & > /dev/null 2>&1 |-> |->To Run Freeradius as this is a production machine.
It is complaining that you have not specified a place to write a log file.
====== logdir = /var/log # # The logging messages for the server are appended to the # tail of this file. # log_file = ${logdir}/radius.log ======
This is from my radiusd.conf file. Radius writes log file messages (few and far between) to /var/log/radius.log
Fix that and you wont have to use the redirect to /dev/null, which I would not use anyway as you want log files to know if something is going wrong.
This is the beginning of my radius.conf, it seems the entry is indeed there and valid as it's same as old installation.
prefix = /usr/local exec_prefix = ${prefix} sysconfdir = ${prefix}/etc localstatedir = /var sbindir = ${exec_prefix}/sbin logdir = /var/log raddbdir = ${sysconfdir}/raddb radacctdir = ${logdir}/radacct
# Location of config and logfiles. confdir = ${raddbdir} run_dir = ${localstatedir}/run/radiusd
# # The logging messages for the server are appended to the # tail of this file. # log_file = ${logdir}/radius.log
HTH, Keith
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
On Wed, 10 Dec 2008, Marcel Grandemange wrote: |-> |->|->>I have a problem where I upgraded v1 to v2 of freeradius and now I can |->only |->|->start it with mode radius -X , if I try use script is simply does |->following. |->|-> |->|->>/usr/local/etc/rc.d]# ./rc.radiusd start |->|->>Starting FreeRADIUS:radiusd: Error: No log destination specified. |->|->>Radius |->>====== |->>logdir = /var/log |->># |->># The logging messages for the server are appended to the |->># tail of this file. |->># |->>log_file = ${logdir}/radius.log |->>====== I am still running 1.1.7. We only have about 200 dialup users left, so I have never upgraded beyond that version as I don't feel the need and dialup is the only thing we use Radius for. Two things, one, have the config options between the 1.x and 2.x changed for logging? I have not looked at v2 so I don't know. The other is possibly permissions on the file or directory. But I don't think that is it as you would probably get a different error.
participants (3)
-
Keith -
Marcel Grandemange -
Marco C. Coelho