Vincent-TP wrote

Hi  @luca22 

 

Thanks for posting here.

When did you first notice this issue? Did it occur on a previous software version, such as 6.2.0.17?

Will the clienthistory file finally generate?

  @Vincent-TP 

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.

Vincent-TP wrote

Hi  @luca22 

Thanks for the reply.

Are these logs still being generated currently? If not, how long are they typically generated for?

luca22 wrote

Vincent-TP wrote

Hi  @luca22 

 

Thanks for posting here.

When did you first notice this issue? Did it occur on a previous software version, such as 6.2.0.17?

Will the clienthistory file finally generate?

  @Vincent-TP 

 

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.

 

@Vincent-TP 

I have not checked every single daily log, but of the ones I checked, it does occurs every day.  In today's log, it started trying around 2:30:00 AM, and finally gave up around 2:42:09 AM - highlighted is the error in creating the clienthistory file:

06-03-2026 02:40:37.846 INFO [anomaly-storage-pool-0] [] c.t.s.o.a.c.p.c.m(): save device health score to manager , site device health list size : 1 use : 2 ms 
06-03-2026 02:41:13.082 INFO [temp-disk-file-pool-0] [] c.t.s.o.c.c.n.b.a(): start to check clear expired diskMultipartFile
06-03-2026 02:41:34.133 INFO [client-inform-work-group-7] [] c.t.s.o.c.u.s.b(): list local interface macs: [BC-24-11-09-03-DF]
06-03-2026 02:42:00.032 INFO [monitor-schedule-statistic-pool-1] [] c.t.s.o.m.s.p.s.a(): done device:statistic:5min:0 1780479600
06-03-2026 02:42:09.014 ERROR [client-schedule-statistic-clean-task-1] [] c.t.s.o.c.m.r.r(): Failed to create index: Index: Document{{site=1, type=1, last_seen=-1, associated=-1, port=1, guest=1, mac=1, radio_Id=1, multi_radio_Id=1}} - Options: Document{{background=true}} on collection: clienthistory_2026m06_t1s1, db: omada_data
org.springframework.dao.DataIntegrityViolationException: 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)' on server 127.0.0.1:27217. The full response is {"ok": 0.0, "errmsg": "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)", "code": 67, "codeName": "CannotCreateIndex"}

 

Vincent-TP wrote

  @luca22 

Thank you so much for taking the time to post the issue on the TP-Link community!
To better assist you, I've created a support ticket via your registered email address and escalated it to our support engineer to look into the issue. The ticket ID is TKID260607799. Please check your inbox and confirm that the support email was received. Thanks!
Once the issue is resolved, please update this thread with your solution to help others who may encounter the same problem.
Many thanks for your excellent cooperation and patience!

Hi  @Vincent-TP 

Once I have collected it, where am I supposed to send the exported log file?  Is "us" this thread?  Do you have a ticket portal (none is mentioned in the email I received)?  These are the instructions I received: