[10.x] Add new error messages for detecting lost connections #47398
Conversation
Ever since I moved from AWS Aurora to using AWS RDS Proxy, which (similar to pgbouncer) is essential to not overload the primary database with connection, I sporadically see these messages. This affects scheduled tasks, worker, HTTP requests; it's across the whole board. This happened across different PHP versions (7.4, 8.2) and different docker base OS images, as well as different Laravel version (8.x, 10.x).
| @@ -63,6 +63,8 @@ protected function causedByLostConnection(Throwable $e) | |||
| 'Reason: Server is in script upgrade mode. Only administrator can connect at this time.', | |||
| 'Unknown $curl_error_code: 77', | |||
| 'SSL: Handshake timed out', | |||
| 'SQLSTATE[08006] [7] SSL error: sslv3 alert unexpected message', | |||
There was a problem hiding this comment.
sslv3 😭 do we really want to support use of SSL v3? Do any modern databases actually still support this?
There was a problem hiding this comment.
AWS Aurora to using AWS RDS Proxy
Seems like a configuration error perhaps? Can you try setting the minimum TLS version to 1.2 in the parameter group?
There was a problem hiding this comment.
This is just the error message being received here; all connections are at minimum TLS 1.2 I can proof this with a query like this:
SELECT * FROM pg_stat_activity JOIN pg_stat_ssl USING(pid);
and the output of any Laravel initiated connection looks like this:
…
ssl | t
version | TLSv1.2
cipher | AES128-SHA256
bits | 128
…
We can change it to SQLSTATE[08006] [7] SSL error: if that makes more sense; I just never had any other message then the two I added in this PR.
Summary
Ever since I moved from AWS Aurora to using AWS RDS Proxy, which (similar to pgbouncer) is essential to not overload the primary database with connection, I sporadically see these messages. This affects scheduled tasks, worker, HTTP requests; it's across the whole board.
This happened across different PHP versions (7.4, 8.2) and different
docker base OS images, as well as different Laravel version (8.x, 10.x).
The message for
SQLSTATE[08006] [7] unrecognized SSL error code:is actually
SQLSTATE[08006] [7] unrecognized SSL error code: 6but I figured this minor error code shouldn't be relevant.
I also saw other messages starting with
SQLSTATE[08006] [7], so maybe there's a case for just adding this prefix, but I guess no one knows if this would really apply to all of such messages.