I think the radius service is "radiusd" If it is, you can do a:

chkconfig radiusd on

The command is deprecated in favour of a systemd command using systemctl, but the terminal will tell you the more up to date command when it executes the chkconfig command.

Nick Howitt wrote:

I think the radius service is "radiusd" If it is, you can do a:

chkconfig radiusd on

The command is deprecated in favour of a systemd command using systemctl, but the terminal will tell you the more up to date command when it executes the chkconfig command.

Sorry no, it's still saying "Stopped" after a reboot. Very strange... it boots fine with the standard systemctl start radiusd however.

Can you look in the boot, messages and system logs to see if there are any failure messages? It could be that a service it depends on is not starting in time, or the service is just taking too long to start (it is allowed 90s and this has caused problems with the virus scanner on low powered systems)

Nick Howitt wrote:

Can you look in the boot, messages and system logs to see if there are any failure messages? It could be that a service it depends on is not starting in time, or the service is just taking too long to start (it is allowed 90s and this has caused problems with the virus scanner on low powered systems)

Dec 13 15:52:55 myclearosmachine systemd: radiusd.service: control process exited, code=exited status=1

Dec 13 15:52:55 myclearosmachine systemd: Unit radiusd.service entered failed state.

Dec 13 15:52:55 myclearosmachine systemd: radiusd.service failed.

That's all it say in the "messages" log.




systemctl status radiusd -l

[root@myclearosmachine ~]# systemctl status radiusd -l

● radiusd.service - FreeRADIUS high performance RADIUS server.

   Loaded: loaded (/usr/lib/systemd/system/radiusd.service; enabled; vendor preset: disabled)

   Active: failed (Result: exit-code) since Wed 2017-12-13 15:52:55 CET; 4min 12s ago

  Process: 1319 ExecStart=/usr/sbin/radiusd -d /etc/raddb (code=exited, status=1/FAILURE)

  Process: 1182 ExecStartPre=/usr/sbin/radiusd -C (code=exited, status=0/SUCCESS)

  Process: 1164 ExecStartPre=/bin/chown -R radiusd.radiusd /var/run/radiusd (code=exited, status=0/SUCCESS)



Dec 13 15:52:55 myclearosmachine.hiding.local systemd[1]: Starting FreeRADIUS high performance RADIUS server....

Dec 13 15:52:55 myclearosmachine.hiding.local systemd[1]: radiusd.service: control process exited, code=exited status=1

Dec 13 15:52:55 myclearosmachine.hiding.local systemd[1]: Failed to start FreeRADIUS high performance RADIUS server..

Dec 13 15:52:55 myclearosmachine.hiding.local systemd[1]: Unit radiusd.service entered failed state.

Dec 13 15:52:55 myclearosmachine.hiding.local systemd[1]: radiusd.service failed.

Only faliure at the boot seem to be that /usr/sbin/radiusd -d /etc/raddb
/etc/raddb is empty btw.

Those messages are not very helpful. Can you start it in debug mode. I believe it means adding a -X to the startup line. You may be able to do this if there is an /etc/sysconfig/radiusd file. If not, you may have to hack the start up script.

Nick Howitt wrote:

Those messages are not very helpful. Can you start it in debug mode. I believe it means adding a -X to the startup line. You may be able to do this if there is an /etc/sysconfig/radiusd file. If not, you may have to hack the start up script.

I think I found the problem. the file radiusd doesn't exist in /etc/sysconfig/
Do you maybe have one I can make a copy of?

I was not at home when I posted last. It does not look like there is a /etc/sysconfig/radiusd file used in the start up. The normal start up file is /usr/lib/systemd/system/radiusd.service, so perhaps try adding -X to the end of the ExecStart line then look at the logs when it fails.

No luck, but I did this in the rc.local

touch /var/lock/subsys/local

sleep 10

systemctl restart radiusd.service

sleep 10

systemctl restart syncthing@root.service

So everything starts up fine now.

That is only a 10ms delay for each module. It suggests it is trying to start just before a boot up dependency is matched, but it is not telling us which dependency. It would be great is we could make a change to the /usr/lib/systemd/system/radiusd.service file to tell it to wait until the dependency is reached, if only we could identify it.