Getting frequent error with Laravel Forge SQS connection

Question

Hi Guys, 
I am getting this error every day in my logs on night time, but the queue is working perfectly, I am using reset emails jobs on this queue and all good, but sometimes I am getting this error in my log..
Please help me.

Error executing "ReceiveMessage" on "https://sqs.us-east-1.amazonaws.com/600882XXXX98365/xxxx-pwd-reset-emails"; AWS HTTP error: cURL error 6: Could not resolve host: sqs.us-east-1.amazonaws.com (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for https://sqs.us-east-1.amazonaws.com/60088XXXX98365/xxxx-pwd-reset-emails
Level
ERROR
Exception
```{
   "class": "Aws\Sqs\Exception\SqsException",
   "message": "Error executing "ReceiveMessage" on "https://sqs.us-east-1.amazonaws.com/6008xxxx98365/xxxx-pwd-reset-emails"; AWS HTTP error: cURL error 6: Could not resolve host: sqs.us-east-1.amazonaws.com (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for https://sqs.us-east-1.amazonaws.com/60xxxx898365/xxxx-pwd-reset-emails",
   "code": 0,
   "file": "/home/forge/api.xxxx.com/vendor/aws/aws-sdk-php/src/WrappedHttpHandler.php:196",

Answer

Most likely this error was caused by a network connectivity issue preventing the request from reaching the SQS service. Failures are scenarios you have to expect in distributed systems and therefore must design to mitigate or withstand. By using SQS, you can depend on the high resiliency it provides for message queuing through its built-in redundancy and durability features. CloudWatch logs will show examples of issues that have occurred that SQS has mitigated or withstood. As long as upstream callers are using retry and backoff logic with SQS, the workload should continue operating as expected.

Getting frequent error with Laravel Forge SQS connection

Relevanter Inhalt