Can't performe a full index with occ fulltextsearch:index

[GekoCH]

I'm running Nextcloud: 28.0.2.5 elasticsearch: 8.8.2

I tried to do a full index with occ fulltextsearch:index but I get this error at file 123911 of 184926.

I can open the particular file without any problem so it0s not corrupt. Can someone help me to get this working? Thx

Memory: 607 MB                                                                                                                                                ┌─ Indexing  ────                                                                                                                                             │ Action: indexDocument                                                                                                                                       │ Provider: Files                Account: admin                                                                                                               │ Document: 335204                                                                                                                                            │ Info: application/vnd.openxmlformats-officedocument.spreadsheetml.sheet                                                                                     │ Title: xxx/yyy/test.xlsx
│ Content size: 11952924
│ Chunk:     48/1685
│ Progress: 123911/184926
└──
┌─ Results ────
│ Result: 124110/124110
│ Index: files:335196
│ Status: ok
│ Message: {"_index":"my_index","_id":"files:335196","_version":1,"result":"cr
│ eated","_shards":{"total":2,"successful":1,"failed":0},"_seq_no":123795,"_pri
│ mary_term":1}
└──
┌─ Errors ────
│ Error:    630/630
│ Index: files:335228
│ Exception: Elastic\Elasticsearch\Exception\ClientResponseException
│ Message: unknown error
│
│
└──
## x:first result ## c/v:prec/next result ## b:last result
## f:first error ## h/j:prec/next error ## d:delete error ## l:last error
## q:quit ## p:pause

In ElasticSearchPlatform.php line 202:

  [OCA\FullTextSearch\Exceptions\PlatformTemporaryException]

[gianlucagilardi]

same issue here. Following.