Description
This article describes the process for restarting the wireless controller daemon on the FortiGate. Restarting the wireless controller daemon is usually preferred to rebooting the FortiGate device when troubleshooting wireless connectivity issues.
This may provide a solution where FortiAPs are having difficulty connecting to the wireless controller.
Scope
FortiGate.
Solution
The command to restart the wireless controller daemon is:
execute wireless-controller restart-acd
To verify the results, run the command diagnose debug crashlog read on the FortiGate and check for a line stating 'the killed daemon is /bin/cw_acd: status=0x0' (which signifies the daemon was successfully restarted).
Alternatively, run the command diagnose sys process pidof cw_acd before and after running execute wireless-controller restart-acd to validate that the process restarted successfully (the process-id will change after the process is restarted):
FortiGate # diagnose sys process pidof cw_acd
2258
FortiGate # execute wireless-controller restart-acd
This operation will reboot wireless controller daemon!
Do you want to continue? (y/n)y
FortiGate # diagnose sys process pidof cw_acd
2379
In some cases where the process is not restarting when executing execute wireless-controller restart-acd, try restarting the process with this command instead:
diagnose sys kill 11 <process_id>
