[7.x] Add SSL SYSCALL EOF as a lost connection message #32696
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As Laravel get's deployed everywhere and to Clever Cloud, we started to get errors from long running workers trying to execute jobs having DB queries.
When a worker has not executed anything in a while, the first job fails with this error while the next ones runs fine.
SQLSTATE[HY000]: General error: 7 SSL SYSCALL error: EOF detected (SQL: select * from "an_example_table")
Our investigation shows that the connection is closed by the server because it was not used and we fixed it by adding these calls inspired by Heroku's recommandations:
But we tought that Laravel might consider this as a try again message.
PS: Maybe the message is too specific and should be more generic:
SSL SYSCALL error: EOF detected
and I think it should be backported to 6.x.Regards