Reclaiming failed request back to the list or queue
Hello. I am facing this issue regularly.
I am using Crawlee with Cheerio.
How can I resolve this?
WARN CheerioCrawler: Reclaiming failed request back to the list or queue. Client network socket disconnected before secure TLS connection was established
{"id":"MrkS5lrulGSjDt4","url":"https://XXX.net","retryCount":1}
DEBUG RequestQueue2(a1eb453f-c08b-4f09-b21a-90faacd2dbdd, default): Failed to delete request lock for request MrkS5lrulGSjDt4 {"err":{"name":"Error","message":"Request with ID MrkS5lrulGSjDt4 is not locked in queue default","stack":"Error: Request with ID MrkS5lrulGSjDt4 is not locked in queue default\n at RequestQueueClient.deleteRequestLock (F:\GitHub\Swim\X_Crawlee_Nitter\app\node_modules\@crawlee\src\resource-clients\request-queue.ts:361:19)\n at async RequestQueue.reclaimRequest (F:\GitHub\Swim\X_Crawlee_Nitter\app\node_modules\@crawlee\src\storages\request_queue_v2.ts:177:17)\n at async CheerioCrawler._requestFunctionErrorHandler (F:\GitHub\Swim\X_Crawlee_Nitter\app\node_modules\@crawlee\src\internals\basic-crawler.ts:1482:17)\n at async wrap (F:\GitHub\Swim\X_Crawlee_Nitter\app\node_modules\@apify\src\index.ts:77:27)"}}
2 Replies
Someone will reply to you shortly. In the meantime, this might help:
passive-yellow•3mo ago
Hello! Can you share some code, for instance how you instantiate your crawler? I'm wandering what could cause the "Request with ID MrkS5lrulGSjDt4 is not locked in queue default" error.
Regarding the TLS error: are you using proxies?