R500 Unleashed and strange logs

[dmitry_ivanov_e]

There is something strange in the logs of my R500 Unleshed 200.39.13.228, every minute repeats this:

Mar 13 23:04:09 Ruckus meshd[9415]: No server running!  Controller exiting.
Mar 13 23:04:05 Ruckus ZD-APMgr: IPC_thread rcv ping from TACMON
Mar 13 23:03:39 Ruckus meshd[9267]: No server running!  Controller exiting.
Mar 13 23:03:39 Ruckus meshd[9262]: No server running!  Controller exiting.
Mar 13 23:03:35 Ruckus ZD-APMgr: IPC_thread rcv ping from TACMON
Mar 13 23:03:09 Ruckus meshd[9102]: No server running!  Controller exiting.
Mar 13 23:03:08 Ruckus meshd[9098]: No server running!  Controller exiting.
Mar 13 23:03:05 Ruckus ZD-APMgr: IPC_thread rcv ping from TACMON
Mar 13 23:02:38 Ruckus meshd[8946]: No server running!  Controller exiting.
Mar 13 23:02:38 Ruckus meshd[8942]: No server running!  Controller exiting.
Mar 13 23:02:35 Ruckus ZD-APMgr: IPC_thread rcv ping from TACMON
Mar 13 23:02:08 Ruckus meshd[8809]: No server running!  Controller exiting.
Mar 13 23:02:08 Ruckus meshd[8805]: No server running!  Controller exiting.

All log is fulling by this messages.... I dont use Mesh in my installation. Could somebody explain what does it mean?

[michael_brado]

Please open a ticket with Tech Support and provide Logs from your Master AP. 
(Admin&Services, Diagnostics, Logs, and both System and AP logs)
https://support.ruckuswireless.com/contact-us

I see one UN-767 bug on Unleashed for Google social media authentication failed, but STA is authorized,
but the output is not exactly like yours, but contains the No server running! Controller exiting statements.

[dmitry_ivanov_e]

Sorry, but my Tech support subscription is not covers Unleshed. It's my own home AP. But I will try 🙂

[michael_brado]

How many APs do you have?  Are you on the latest 200.4.9.13.228 version?
Are you having any problems, or just seeing these unusual log messages?

[dmitry_ivanov_e]

Just only one AP. FW is 200.3.9.13.228 and it is latest for my AP. AP self reboots every 2-3 days. I dont know why, only uptime parameter show me that AP reboots and new empty logs starts again. I suggest a log file is overloading or something like that.