[RADIATOR] Possible execution issue

Heikki Vatiainen hvn at open.com.au
Tue Mar 12 13:45:21 UTC 2019

On 11/03/2019 12.13, Dubravko Penezic wrote:

> I am in process of migrating some instance of RADIUS to RADIATOR and
> found strange behaver :
> If you miss spell <Client ... like <client ... Radiator will crash with
> follow error :

This is on purpose. If a <clause ...> fails to load, the rest of the 
configuration will not be loaded either and the process exits.

>   Mon Mar 11 10:58:47 2019: DEBUG: include /etc/radiator/conf.d/config.conf
> 00000000 Mon Mar 11 10:58:47 2019 297110: ERR: Could not load client
> module Radius::client: Can't locate Radius/client.pm in @INC (@INC
> contains: /opt/radiator/radiator /usr/local/lib64/perl5
> /usr/local/share/perl5 /usr/lib64/perl5/vendor_perl
> /usr/share/perl5/vendor_perl /usr/lib64/perl5 /usr/share/perl5 .) at
> /opt/radiator/radiator/Radius/Configurable.pm line 565, <> line 6.
> 00000000
> Error is correct because /opt/radiator/radiator/Radius/Client.pm only
> exist, but it is configuration error not execution error so it need to
> be handled on that way.

The main purpose for the above is preventing unexpected configuration. 
For example, if a configuration is moved to a different server that does 
not have all required modules, it can cause an AuthBy not to load. If 
this is not noticed from logs, it can cause the configuration to become 
badly broken. In other words, this is for safety and being clear that 
there is a serious problem.

For the above reason I'd say the current behaviour is better than 
handling it with some other way.


Heikki Vatiainen <hvn at open.com.au>

Radiator: the most portable, flexible and configurable RADIUS server
anywhere. SQL, proxy, DBM, files, LDAP, TACACS+, PAM, Active Directory,
DIAMETER etc. Full source on Unix, Windows, MacOSX, Solaris, VMS, etc.

More information about the radiator mailing list