R500 Unleashed Log Filled With Errors - Normal?

[simple_user]

Hi, new Ruckus user here. Last night I got a notice that my two AP's joined the network and were previously disconnected due to heartbeat loss. I just installed them about 7 days ago and this is the first time this happened. Both still show up time of about 7 days. So I started poking around the logs and just from today the log is full of stuff like this:

Mar 13 00:42:34 Ruckus-Unleashed Eved: MLME-REPLAYFAILURE.indication(wlan1 AES-CCM keyid=37 unicast RA:addr=8c:fe:74:79:6d:a8 TA:addr=f8:0d:60:03:ff:c8) (pkt-rsc:1032 k->rsc[1]:1037
Mar 13 00:42:54 Ruckus-Unleashed ZD-APMgr: IPC_thread rcv ping from TACMON 
Mar 13 00:42:36 Ruckus-Unleashed meshd[30628]: send_controller_config line: 96 Controller connecting error, errno: 2 No such file or directory 
Mar 13 00:42:36 Ruckus-Unleashed meshd[30624]: send_controller_config line: 96 Controller connecting error, errno: 2 No such file or directory 
Mar 13 07:27:42 Ruckus-Unleashed syslog: pid=1065, _loadXmlStr():Unable to parse XML string (null) 
Mar 13 07:27:42 Ruckus-Unleashed syslog: upgrade_debug: pid=32375, get_ap_list(): ap-list found !! 


Is this normal?

[hayward_kong]

Also are the actually APs affected besides the logs?

[simple_user]

I don't think they were affected but I am not 100% sure because I was not on them when it happened. All I got was a push notification from the android app and an email that said they rejoined after heartbeat loss.

[hayward_kong]

since I know another forum user said was the heartbeat issue was happening.. but wasn't affecting users...... if you wanted to avoid the logs.. then go back to 200.6.x