2.8.4. Troubleshooting Windows service Previous topic Parent topic Child topic Next topic

Windows service does not start

When Windows service does not start at all, the problem can be caused by a missing Perl module. The exact error can be usually found from the Radiator log file, search a line with ERR information or line specifying missing Perl module, for example Can't locate Win32/NetAdmin.pm in @INC (you may need to install the Win32::NetAdmin module).

Windows service does not stay up

When Windows service does start but stops after a while, the problem might also be a missing Perl module. In this case the module is loaded only when it is tried to be used instead of loading the module during startup. Radiator log file can contain information why the service stopped, but this situation can also be troubleshooted with command line.
  • Stop Radiator Windows service if it is running.
  • Start Radiator manually from command line window. Use the shortcut for elevated command line window \Program Files\Radiator\Perl command line Elevated to get Perl environment and have Radiator log file permissions. Radiator log file permissions are needed because debug information is both logged to file and printed to command line window.
  • To start radiusd type for example: perl C:\Radiator\Radiator\radiusd -log_stdout -foreground -trace 4 -config_file "C:\Program Files\Radiator\radiator.conf" The default configuration from the command can be changed to suit the troubleshooting needs.
This will start radiusd and print all the debug information to the command line window and to Radiator log file. Once the request that caused Radiator Windows service to stop is sent to the server again, it is likely that the command line window will show the exact problem.

SE_TCB_PRIVILEGE errors when using command line

When Radiator is run from command line in Windows and <AuthBy LSA> is used, following error might appear: ERR: Could not AdjustPrivilege SE_TCB_PRIVILEGE: A required privilege is not held by the client. on the command line. This means that Radiator must be run on Windows as a user that has the ‘Act as part of the operating system's security policy' (SE_TCB_PRIVILEGE) enabled. The 'Local System' account that the Radiator Windows service runs as has this privilege by default. If all the other errors have been cleared by troubleshooting with command line and only this error is left, Radiator Windows service will work.