The third of our freeradius-0.5-servers behaves differently to the
others, when restarted remotely via ssh:
...
Starting Freeradius server: radwatch radiusd.
Starting Freeradius server: radwatch radiusd.
/etc/init.d/radius: start-stop-daemon: command not found
Starting Freeradius server: radwatch/etc/init.d/radius:
start-stop-daemon: command not found
radiusd.
...
The first two lines are from server1 and server2, the rest what server3
replies. The message "command not found" occurs only on restart
remotely. Local restart on the server shows what I expected:
# /etc/init.d/radius restart
Starting Freeradius server: radwatch radiusd.
The radius.log for remote and local restart looks different too:
remote:
...
Sun Jun 9 12:01:32 2002 : Info: MASTER: exit.
Sun Jun 9 12:01:32 2002 : Info: CHILD: exit.
Sun Jun 9 12:01:32 2002 : Error: MASTER: exit on signal (11)
...
local:
...
Sun Jun 9 12:03:13 2002 : Info: Listening on IP address *, ports
1812/udp and 1813/udp.
Sun Jun 9 12:03:13 2002 : Info: Ready to process requests.
...
The section for restart in the startscript is identical on all three
servers:
...
restart)
sh $0 stop quiet
sleep 3
sh $0 start
;;
...
Freeradius is running on Debian Woody with kernel 2.4.18.
Any hints or ideas?
Regards, Oliver
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html