MongoDB CannotCreateIndex error — namespace name too long in 6.2.10.17
Hi,
I'm running Omada Software Controller 6.2.10.17 on Windows Server 2025 and seeing the following error repeating in the server.log at the start of each month:
Command failed with error 67 (CannotCreateIndex): 'namespace name generated from index name "omada_data.clienthistory_2026m06_t1s1.$site_1_type_1_last_seen_-1_associated_-1_port_1_guest_1_mac_1_radio_Id_1_multi_radio_Id_1" is too long (127 byte max)'
The error occurs when the controller tries to create its monthly clienthistory collection index. The auto-generated index name exceeds MongoDB's 127 byte namespace limit.
This might be a bug introduced in 6.2.10.17 as the index name is too long by design. The error repeats every second and fills the log.
Has anyone else encountered this and found a fix or workaround? Is there a planned fix from TP-Link?
Running:
- Omada Controller 6.2.10.17 on Windows Server 2025
- 2x EAP660HD APs ver. 1.1.5
- 1x EAP773 AP ve. 1.4.3
Thanks
I went back to the logs, looks like this started on 6.2.0.17. The clienthistory file does not exist anywhere in the controller data folder. The first instance of this problem that I could find was:
04-09-2026 10:08:19.154 INFO [main] [] c.t.s.o.s.OmadaMain(): Starting OmadaMain v6.2.0.17 using Java 17.0.11 with PID 10024
This warning appears multiple time a day since then. Attached a more extensive log.
