Troubleshooting Tip : FortiNAC Local Radius not starting with error 'Realm section is missing the realm name'
| Description | This article describes how how to solve one of the cases where local radius does not start in FortiNAC. |
| Scope | 8.8.x, 9.1.x, 9.2.x |
| Solution | In this case, indicators of this failure condition can be checked in the GUI status and on the local radius service logs
1) From FortiNAC GUI go in Network ->Radius -> Local Radius Status is : Enabled/Not Running.
2) Checking the Local Radius service logs on GUI go to Network -> Radius -> Local Service -> Service Status. It is possible to match these logs:
systemd[1]: radiusd.service: control process exited, code=exited status=1
3) Checking the Local Radius Systemd Journal logs from GUI Network -> Radius -> Local Service -> Systemd Journal. It is possible to match these logs:
radiusd[35249]: /etc/raddb/radiusd.conf[52]: Realm section is missing the realm name
This will happen if and is related to the Windbind service not being enabled and configured. By configuring the Winbind parameters will make the radiusd service to start.
Note. The troubleshooting steps above can be followed in GUI starting from 9.2 version. For prior versions, it will be necessary to enable local radius debugging from CLI.
Check the community articles below on how to enable debugging in GUI and CLI for local radius service.
Related articles.
|