Unable to index all documents. Response: {"took":1,"errors":true,"items":[]}
cesarferreira opened this issue · 7 comments
Keep getting this errors on our app, it's been working fine for like a year
2020-10-01 16:14:09.937 D/Logsene: Worker started, message queue size = 4
2020-10-01 16:14:09.938 D/Logsene: Attempting to send bulk request
2020-10-01 16:14:10.090 E/Logsene: Unable to index all documents. Response: {"took":1,"errors":true,"items":[]}
Request:
2020-10-01 16:14:10.094 D/Logsene: Worker succeeded in sending logs, message queue size = 4
2020-10-01 16:14:10.097 I/WM-WorkerWrapper: Worker result SUCCESS for Work [ id=1bceb32c-2217-4fe4-9b17-720440bffbeb, tags={ com.sematext.logseneandroid.LogWorker, com.sematext.android.LogWorker.interval } ]
2020-10-01 16:29:22.161 D/Logsene: Worker started, message queue size = 4
2020-10-01 16:29:22.162 D/Logsene: Attempting to send bulk request
2020-10-01 16:29:22.293 E/Logsene: Unable to index all documents. Response: {"took":1,"errors":true,"items":[]}
Request:
2020-10-01 16:29:22.297 D/Logsene: Worker succeeded in sending logs, message queue size = 4
2020-10-01 16:29:22.300 I/WM-WorkerWrapper: Worker result SUCCESS for Work [ id=1bceb32c-2217-4fe4-9b17-720440bffbeb, tags={ com.sematext.logseneandroid.LogWorker, com.sematext.android.LogWorker.interval } ]
2020-10-01 16:44:09.930 D/Logsene: Worker started, message queue size = 4
2020-10-01 16:44:09.931 D/Logsene: Attempting to send bulk request
2020-10-01 16:44:10.088 E/Logsene: Unable to index all documents. Response: {"took":1,"errors":true,"items":[]}
Request:
2020-10-01 16:44:10.092 D/Logsene: Worker succeeded in sending logs, message queue size = 4
Which version of the Logsene Android library are you using, and would it be possible for you to try the latest version?
Thank you for the quick reply!
I'm on 2.4.1 since 19 Aug 2020 (so, latest)
This just started happening today or when did it start?
I assume you are sending logs to Sematext? If so, mind checking the usage/stats for the Logs App where these logs are being sent to and make sure you didn't reach some sort of a limit?
@cesarferreira are you still experiencing this issue?
I've seen it a few more times yes @gr0
Can you share your application token or identifier to my mail? It is rafal.kuc@sematext.com, so I can check out what we see on the backend and verify.
I'm closing this one. @cesarferreira if you see any of this behavior again, please let us know your application details at the mail I pasted in the above comment.