CA
Crawlee & Apify•14mo ago
inland-turquoise

RequestQueue read/write is timing out constantly

We are receiving the following errors across 1000's of executions 
WARN  ApifyClient: API request failed 4 times. Max attempts: 9.
Cause:ApifyApiError: Unexpected error: "<html><body><h1>503 Service Unavailable</h1>\nNo server is available to handle this request.\n</body></html>\n"
  clientMethod: KeyValueStoreClient.get
  statusCode: 503
  type: undefined
  attempt: 4
  httpMethod: get
  path: /v2/key-value-stores/DWNfzdawBTwRFGVYS
  stack:
    at makeRequest (/home/myuser/node_modules/apify-client/dist/http_client.js:184:30)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at async KeyValueStoreClient._get (/home/myuser/node_modules/apify-client/dist/base/resource_client.js:25:30)
    at async StorageManager._getOrCreateStorage (/home/myuser/node_modules/@crawlee/core/storages/storage_manager.js:106:33)
    at async StorageManager.openStorage (/home/myuser/node_modules/@crawlee/core/storages/storage_manager.js:81:35)
    at async Actor.getValue (/home/myuser/node_modules/apify/actor.js:584:23)
    at async Actor.getInput (/home/myuser/node_modules/apify/actor.js:656:23)
    at async /home/myuser/main.js:11:19
    at async /home/myuser/node_modules/apify/actor.js:153:23
WARN  ApifyClient: API request failed 4 times. Max attempts: 9.
Cause:ApifyApiError: Unexpected error: "<html><body><h1>503 Service Unavailable</h1>\nNo server is available to handle this request.\n</body></html>\n"
  clientMethod: KeyValueStoreClient.get
  statusCode: 503
  type: undefined
  attempt: 4
  httpMethod: get
  path: /v2/key-value-stores/DWNfzdawBTwRFGVYS
  stack:
    at makeRequest (/home/myuser/node_modules/apify-client/dist/http_client.js:184:30)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at async KeyValueStoreClient._get (/home/myuser/node_modules/apify-client/dist/base/resource_client.js:25:30)
    at async StorageManager._getOrCreateStorage (/home/myuser/node_modules/@crawlee/core/storages/storage_manager.js:106:33)
    at async StorageManager.openStorage (/home/myuser/node_modules/@crawlee/core/storages/storage_manager.js:81:35)
    at async Actor.getValue (/home/myuser/node_modules/apify/actor.js:584:23)
    at async Actor.getInput (/home/myuser/node_modules/apify/actor.js:656:23)
    at async /home/myuser/main.js:11:19
    at async /home/myuser/node_modules/apify/actor.js:153:23
There is no mention of an outage of request queues on https://status.apify.com/ what is the issue?
Apify Status
Welcome to Apify's home for real-time and historical data on system performance.
2 Replies
inland-turquoise
inland-turquoiseOP•14mo ago
possibly KV Store related actually actually it's both. We also have across multiple runs 
WARN  PuppeteerCrawler: Setting status message timed out after 1s
WARN  ApifyClient: API request failed 4 times. Max attempts: 9.
Cause:ApifyApiError: Unexpected error: "<html><body><h1>503 Service Unavailable</h1>\nNo server is available to handle this request.\n</body></html>\n"
  clientMethod: RequestQueueClient.addRequest
  statusCode: 503
  type: undefined
  attempt: 4
  httpMethod: post
  path: /v2/request-queues/xThJzW8KHlheG71BW/requests
  stack:
WARN  PuppeteerCrawler: Setting status message timed out after 1s
WARN  ApifyClient: API request failed 4 times. Max attempts: 9.
Cause:ApifyApiError: Unexpected error: "<html><body><h1>503 Service Unavailable</h1>\nNo server is available to handle this request.\n</body></html>\n"
  clientMethod: RequestQueueClient.addRequest
  statusCode: 503
  type: undefined
  attempt: 4
  httpMethod: post
  path: /v2/request-queues/xThJzW8KHlheG71BW/requests
  stack:
evolutionary-blush
evolutionary-blush•14mo ago
Hi, we had a short incident on API, it should be resolved now

Did you find this page helpful?