nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

R500 Unleashed and strange logs

unknown

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?

Find more posts tagged with

Accepted answers

All comments

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.

unknown

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?

beat_schilliger

The same here! Private unleashed network with two R310 APs no Mesh with system version 200.3.9.13.228!

The same with a one standalone R310 AP in another location:
Mar 14 08:24:18 WiFi meshd[6060]: No server running! Controller exiting.
Mar 14 08:24:18 WiFi meshd[6056]: No server running! Controller exiting.
Mar 14 08:23:58 WiFi ZD-APMgr: IPC_thread rcv ping from TACMON

Every 30 seconds...

unknown

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.

unknown

I just checked my logs and have the same thing. Unleashed R310 on 200.3.9.13.228. So far I haven't experienced any negative affects on my network.

Image_ images_messages_5f91c427135b77e24798c517_36b3f0100ff657bc4023caab5e4dea21_RackMultipart20170314129595g5y-74fc27d8-577d-46e4-9feb-572d1f07b38b-1333031019.png1489533732

Image_ images_messages_5f91c427135b77e24798c517_36b3f0100ff657bc4023caab5e4dea21_RackMultipart20170314129595g5y-74fc27d8-577d-46e4-9feb-572d1f07b38b-1333031019.png1489533732

unknown

As we can see the strange behavior took a place for many Unleashed installations with FW 200.3.9.13.228... I think that reboots of my AP is not related to this behavior and WiFi network is stable now. But all logs are filled by those messages. Thanks to all.

unknown

same here. 2 x R310 AP, same messages. 200.3.9.13.228 version. Roaming of Apple clients does not work. Not sure if that's related to the messages.

beat_schilliger

Unfortunately no news with two R310 no mesh and firmware 200.4.9.13.47:

Jun 1 09:01:18 RuckusAP-WZ meshd[3539]: No server running! Controller exiting.
Jun 1 09:01:06 RuckusAP-WZ ZD-APMgr: IPC_thread rcv ping from TACMON
Jun 1 09:00:56 RuckusAP-WZ meshd[3494]: No server running! Controller exiting.
Jun 1 09:00:48 RuckusAP-WZ meshd[3486]: No server running! Controller exiting.
Jun 1 09:00:36 RuckusAP-WZ ZD-APMgr: IPC_thread rcv ping from TACMON
Jun 1 09:00:26 RuckusAP-WZ meshd[3422]: No server running! Controller exiting.
Jun 1 09:00:18 RuckusAP-WZ meshd[3408]: No server running! Controller exiting.
Jun 1 09:00:06 RuckusAP-WZ ZD-APMgr: IPC_thread rcv ping from TACMON
Jun 1 08:59:55 RuckusAP-WZ meshd[3361]: No server running! Controller exiting.
Jun 1 08:59:48 RuckusAP-WZ meshd[3158]: No server running! Controller exiting.

unknown

Yes, the situation is the same with new firmware 200.4.9.13.47 on my R500. The answer from official support group is:
"Just got an update form the engineering team that these logs are
informational logs on the meshd status on the AP, and thus harmless and
would not impact the AP in any way, and can be ignored".

michael_brado

And Beat, someone from TME will contact you to be a beta tester of Unleashed Mobile App for 200.5 release.

unknown

Same here. 4xR600 with the 200.4.9.13.47 version:

Aug 3 14:10:42 CMD-Unleashed meshd[31648]: No server running! Controller exiting.
Aug 3 14:10:42 CMD-Unleashed syslog: pid=31656, main():FileCache synced
Aug 3 14:10:53 CMD-Unleashed meshd[31693]: No server running! Controller exiting.
Aug 3 14:10:57 CMD-Unleashed ZD-APMgr: IPC_thread rcv ping from TACMON
Aug 3 14:11:13 CMD-Unleashed meshd[31745]: No server running! Controller exiting.
Aug 3 14:11:18 CMD-Unleashed meshd[31756]: No server running! Controller exiting.
Aug 3 14:11:23 CMD-Unleashed meshd[31766]: No server running! Controller exiting.
Aug 3 14:11:27 CMD-Unleashed ZD-APMgr: IPC_thread rcv ping from TACMON
Aug 3 14:11:48 CMD-Unleashed meshd[31816]: No server running! Controller exiting.
Aug 3 14:11:53 CMD-Unleashed meshd[31824]: No server running! Controller exiting.
Aug 3 14:11:57 CMD-Unleashed ZD-APMgr: IPC_thread rcv ping from TACMON