[RADIATOR] Radiator keeps restarting

[Hugh Irvine]

Hello Dan -

You have two options - both will show you the Perl crash message(s).

1. run radiusd by hand from the command line:

	cd /your/Radiator/source/directory

	perl radiusd -foreground -log_stdout -trace 4 -config_file /your/Radiator/configuration/file

	…..

2. use restartWrapper - see section 16.1 in the Radiator 4.7 reference manual ("doc/ref.pdf").

regards

Hugh


On 17 Sep 2010, at 14:27, Dan Pike wrote:

> Hi,
> I've looked through the FAQ and the email archive and haven't stumbled on an answer to a problem that I'm having. 
> 
> I have radiator running on two servers.  Server #1 seems to be working without any problems.  However radiator on server #2 keeps rebooting when I try to have a device authenticate using that server.  I'm running a patched version of radiator 4.5.1.  Looking at the log files I see the server restart at the same point every time, right after it creates the accounting port.  Here's what I'm seeing in the logs:
> 
> 
> Fri Sep 17 12:06:00 2010: DEBUG: Handling with Radius::AuthGROUP: CheckLDAPServers_Network
> Fri Sep 17 12:06:00 2010: DEBUG: Handling with Radius::AuthLDAP2:
> Fri Sep 17 12:06:00 2010: INFO: Connecting to x.x.acme.com x.x.acme.com:636
> Fri Sep 17 12:06:01 2010: DEBUG: Creating StreamServer tcp port 0.0.0.0:9048
> Fri Sep 17 12:06:01 2010: DEBUG: Creating TACACSPLUS port 0.0.0.0:49
> Fri Sep 17 12:06:01 2010: DEBUG: Finished reading configuration file '/etc/radiator/radius.cfg'
> Fri Sep 17 12:06:01 2010: DEBUG: Reading dictionary file '/etc/radiator/dictionary'
> Fri Sep 17 12:06:01 2010: DEBUG: Reading dictionary file '/etc/radiator/configs/dictionary.own'
> Fri Sep 17 12:06:01 2010: DEBUG: Reading dictionary file '/etc/radiator/goodies/dictionary.cisco'
> Fri Sep 17 12:06:01 2010: DEBUG: Creating authentication port 0.0.0.0:1812
> Fri Sep 17 12:06:01 2010: DEBUG: Creating accounting port 0.0.0.0:1813
> Fri Sep 17 12:06:01 2010: NOTICE: Server started: Radiator 4.5.1 on server2.x.x.acme.com
> 
> 
> Any thoughts on what direction I should look to fix the problem?  My hunch is that one of the pre-requisites didn't install properly and radiator doesn't like something that it sees, but that's just a hunch.  I'm not sure how to determine what's making it want to restart.
> 
> Any help would be much appreciated!
> 
> Thanks,
> -Dan
> 
> 
> 
> 
> _______________________________________________
> radiator mailing list
> radiator at open.com.au
> http://www.open.com.au/mailman/listinfo/radiator



NB: 

Have you read the reference manual ("doc/ref.html")?
Have you searched the mailing list archive (www.open.com.au/archives/radiator)?
Have you had a quick look on Google (www.google.com)?
Have you included a copy of your configuration file (no secrets), 
together with a trace 4 debug showing what is happening?

-- 
Radiator: the most portable, flexible and configurable RADIUS server
anywhere. Available on *NIX, *BSD, Windows, MacOS X.
Includes support for reliable RADIUS transport (RadSec),
and DIAMETER translation agent.
-
Nets: internetwork inventory and management - graphical, extensible,
flexible with hardware, software, platform and database independence.
-
CATool: Private Certificate Authority for Unix and Unix-like systems.