Technical Tip: How to restart the wireless controller daemon
Description
This may provide a solution where FortiAPs are having difficulty connecting to the wireless controller.
Scope
FortiGate.
Solution
FGT (root) # execute wireless-controller restart-acd
command parse error before 'restart-acd'
Command fail. Return code -61
Exit from the management VDOM and enter the global context as shown:
FGT (root) # end
FGT # config global
The command will then work:
FGT (global) # execute wireless-controller restart-acd
This operation will reboot wireless controller daemon!
Do you want to continue? (y/n)
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>
Or the next command can restart the process without knowing the process ID:
fnsysctl killall cw_acd
Note:
Super Admin privilege is required to run the 'fnsysctl' command. Otherwise, FortiGate will return an error, as explained in Troubleshooting Tip: fnsysctl command returns Unknown action 0