Replies: 2 comments
-
same issue any solution for that to debug @mnapoli |
Beta Was this translation helpful? Give feedback.
0 replies
-
Your code is timing out, it's likely an issue related to your app or 3rd party APIs you are calling, not Bref. Are you calling an API that sometimes takes a long time to respond? |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Description:
I encountered an issue where the PHP script times out, and Bref restarts PHP-FPM to start from a clean slate, flushing the PHP logs. The specific error is as follows:
"The request d03b92ac-6c3c-4887-b60a-11d986913817 timed out after 5000 ms. Note: the duration may be lower than the Lambda timeout, which is intentional. Bref stops the PHP-FPM request before a hard Lambda timeout, because a hard timeout prevents logs from being written to CloudWatch."
Timeouts like this can occur when trying to connect to a remote API or database. If this happens continuously, it’s recommended to verify those connections.
I have already followed the Bref RDS documentation. My Lambda function is running inside a VPC in a private subnet and has internet connectivity through a NAT gateway. and RDS is also running in same vpc
### Issue Details:
Environment: Lambda running Bref inside a private VPC with NAT gateway.
Problem: The script times out after 5000 ms, leading to a PHP-FPM restart. (This is happening randomly once or twice in a week)
Observation: No additional debugging information is available beyond the script timeout error.
I am trying to identify the root cause of the issue, but the lack of detailed logs or error information makes it difficult to debug.
### Request:
@mnapoli
Could you provide guidance or suggestions for debugging this issue further?
Are there additional tools, logs, or methods that can help pinpoint the root cause of the script timeout?
Beta Was this translation helpful? Give feedback.
All reactions