Ruckus R720 Errors

[peter_cox_je3b6]

Running a Ruckus R720 (106.0.0.99.1363) as a standalone unit and everything seems to be running fine from a WiFi perspective. That being said every 5 seconds or so I am seeing the following in the log:

Oct  3 21:17:28 AUS-AP-EAST daemon.err wsgclient[493]: communicatorInit:290 Call 'getWSGServerUrl()' failed, ret:8/url not found
Oct  3 21:17:28 AUS-AP-EAST daemon.err wsgclient[493]: registration:708 Failed to init socket! ret:8 url:
Oct  3 21:17:33 AUS-AP-EAST daemon.err wsgclient[493]: communicatorInit:290 Call 'getWSGServerUrl()' failed, ret:8/url not found
Oct  3 21:17:33 AUS-AP-EAST daemon.err wsgclient[493]: registration:708 Failed to init socket! ret:8 url:
Oct  3 21:17:38 AUS-AP-EAST daemon.err wsgclient[493]: communicatorInit:290 Call 'getWSGServerUrl()' failed, ret:8/url not found
Oct  3 21:17:38 AUS-AP-EAST daemon.err wsgclient[493]: registration:708 Failed to init socket! ret:8 url:
Oct  3 21:17:43 AUS-AP-EAST daemon.err wsgclient[493]: communicatorInit:290 Call 'getWSGServerUrl()' failed, ret:8/url not found
Oct  3 21:17:43 AUS-AP-EAST daemon.err wsgclient[493]: registration:708 Failed to init socket! ret:8 url:
Oct  3 21:17:48 AUS-AP-EAST daemon.err wsgclient[493]: communicatorInit:290 Call 'getWSGServerUrl()' failed, ret:8/url not found
Oct  3 21:17:48 AUS-AP-EAST daemon.err wsgclient[493]: registration:708 Failed to init socket! ret:8 url:

Does anyone have any idea on how to remedy this?

thanks,

Peter

[michael_brado]

Are you playing with IPv6?  I see one bug that says some of these are 'wsgclient' unable to find server IP. [scg-73562]

[peter_cox_je3b6]

The IPv6 settings are all defaults, haven't changed any of them.

Connection Type = Auto Configuration
DNS servers are empty under IPv6. 

[michael_brado]

I don't see anything else, not enough log details.  I suggest open a ticket with support if this is client affecting.
https://support.ruckuswireless.com/contact-us

[peng_xia]

this error was caused by the SmartcellGateway Agent feature enabled, if you are sure it's not in your required list, just disable it and the error msg will fly away.
I used the standalone ap for verifying this.