FR3 Debugging Switches

Adam Bishop Adam.Bishop at ja.net
Wed Oct 9 16:22:10 CEST 2013


It appears the debugging switches don't work quite as I'd expect in FreeRADIUS 3 when RadSec is configured.

  # radiusd -fxx -l stdout

Works as expected (threaded debugging with no timestamps), however:

  # radiusd -fXx -l stdout
  <snip>
  Wed Oct  9 14:44:18 2013 : Error: /opt/freeradiuss/etc/raddb/sites-enabled/tls[7]: Threading must be enabled for TLS sockets to function properly.
  Wed Oct  9 14:44:18 2013 : Error: /opt/freeradiuss/etc/raddb/sites-enabled/tls[7]: You probably need to do 'radiusd -fxx -l stdout' for debugging

'-fXxx -l stdout' reacts in the same way, but '-fxxx -l stdout' does run and produce timestamps, so I think this one is just a documentation issue - I can't find anything doc/ that says xxx is a valid combination.  radiusd --help also indicates that -fXx should still be valid.

Similarly, when doing a config check:

  # ./sbin/radiusd -Cfxx -l stdout
  <snip>
  /opt/freeradiuss/etc/raddb/sites-enabled/tls[7]: Threading must be enabled for TLS sockets to function properly.
  /opt/freeradiuss/etc/raddb/sites-enabled/tls[7]: You probably need to do 'radiusd -fxx -l stdout' for debugging

The init scripts for debian (possibly RHEL too) trigger the latter one, as it runs a config check on restart (which bails out due to the error above).

Regards,

Adam Bishop

 gpg: 0x6609D460

Janet, the UK's research and education network.


Janet(UK) is a trading name of Jisc Collections and Janet Limited, a 
not-for-profit company which is registered in England under No. 2881024 
and whose Registered Office is at Lumen House, Library Avenue,
Harwell Oxford, Didcot, Oxfordshire. OX11 0SG. VAT No. 614944238



More information about the Freeradius-Users mailing list