11-05-2022 04:03 AM
i have ruckus r300
Nov 5 10:18:11 RuckusAP daemon.err wsgclient[441]: crResloveAddrInfo:152 getaddrinfo failed, ret:-2/Name or service not known
Nov 5 10:18:11 RuckusAP daemon.err wsgclient[441]: cmrInit:138 Call 'crDefSocketInit()' failed, ip: port:443, ret:124/CR initial socket failed
Nov 5 10:18:11 RuckusAP daemon.err wsgclient[441]: communicatorInit:364 Init connection failed, ret:124, connectRetry:13477
Nov 5 10:18:11 RuckusAP daemon.err wsgclient[441]: registration:594 Failed to init socket! ret:124 url:https://RuckusController/wsg/ap
Nov 5 10:18:16 RuckusAP daemon.err wsgclient[441]: crResloveAddrInfo:152 getaddrinfo failed, ret:-2/Name or service not known
Nov 5 10:18:16 RuckusAP daemon.err wsgclient[441]: cmrInit:138 Call 'crDefSocketInit()' failed, ip: port:443, ret:124/CR initial socket failed
Nov 5 10:18:16 RuckusAP daemon.err wsgclient[441]: communicatorInit:364 Init connection failed, ret:124, connectRetry:13478
11-07-2022 11:51 AM
If it runs on standalone mode, I don't think you need to worry about those AP syslogs.
May I know what exact problem you are facing and what is the impact of it?
11-15-2022 09:01 AM
Hi Nirben,
As I have explained before, you can ignore those event logs, AP should work just fine.
May I know what is the actual service impact?