What's new

wlceventd: _add_wlc_event_tbl client table was full ?

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

John_

Occasional Visitor
I noticed this in my system log after wlcenvend events (deauth, auth, assoc).
wlceventd: _add_wlc_event_tbl(737): client table was full

Not a big deal but I am curious as to what could be causing it.

GT-AX6000 388.1 uptime 17 days

Memory
Total 994.97 MB
Free 423.62 MB
Buffers 7.09 MB
Cache 42.49 MB
Swap No swap configured

Internal Storage
NVRAM usage 72345 / 196608 bytes
JFFS 2.32 / 44.46 MB
 
Im also getting this to my system log. Anyone know what this is?

Oct 18 12:39:43 RT-AX56U wlceventd: _add_wlc_event_tbl(765): client table was full
Oct 18 12:39:43 RT-AX56U hostapd: eth5: STA xx:xx:xx:xx:xx:xx IEEE 802.11: disassociated
Oct 18 12:39:43 RT-AX56U wlceventd: _add_wlc_event_tbl(765): client table was full
Oct 18 12:39:43 RT-AX56U hostapd: eth5: STA xx:xx:xx:xx:xx:xx IEEE 802.11: disassociated
Oct 18 12:39:44 RT-AX56U wlceventd: _add_wlc_event_tbl(765): client table was full
Oct 18 12:39:44 RT-AX56U hostapd: eth5: STA xx:xx:xx:xx:xx:xx IEEE 802.11: disassociated
Oct 18 12:40:20 RT-AX56U wlceventd: _add_wlc_event_tbl(765): client table was full
 
Would like to know as well
 
What is too many clients? How can that happen? I only have 10-15 wireless client on 3 mesh nodes.
 
My xt8 also reports this message (at ~ 2:00am) were after the wireless backhaul fails and drops to 2,4GHz. I need to reboot the node to solve this issue for another 24 hours.
 

Similar threads

Latest threads

Support SNBForums w/ Amazon

If you'd like to support SNBForums, just use this link and buy anything on Amazon. Thanks!

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top