Closed stefblokdijk closed 3 months ago
this is most likely a temporary hiccup.
Hi @driesvints, i'm actually still experiencing this. The thumbs up on my post makes it seem like i'm not the only one having this problem.
I've done some more research and found that the temporary solution is to uninstall swoole which worked on 2 projects that connect to AWS Redshift.
I use php 8.3, so these were the required steps:
sail root-shell
apt remove php8.3-swoole
Here's the information I found:
The swoole fix was released in version v6.0.0-alpha but I wasn't able to install that via apt
. I think this should eventually be addressed in sail itself since php8.3-swoole is being installed when setting up sail.
I've solved this issue here
Ondřej updated the php-swoole extension package to the 5.1.4 swoole src release that contains the fix php8.1-swoole/now 6.0.0+really+5.1.4-1+ubuntu22.04.1+deb.sury.org+1 amd64
so everyone can rebuild their sail container image and the SSL issue is no more without force removing the extension
https://github.com/oerdnj/deb.sury.org/issues/2205 https://github.com/swoole/swoole-src/releases/tag/v5.1.4
Sail Version
1.30.2
Laravel Version
11.16.0
PHP Version
8.3.9
Operating System
macOS
OS Version
14.5
Description
I haven't touched this project in a while, so when I installed everything again I was met with the following error when trying to execute a Redshift query from Sail (locally):
SQLSTATE[08006] [7] could not send SSL negotiation packet: Resource temporarily unavailable
. No changes have been made to the project, database or AWS security settings.However it does work when executing the any query using
php artisan serve
instead ofsail up
.The following Github issue might be related to this: https://github.com/php/php-src/issues/14665
Steps To Reproduce
docker-compose.yml
config/database.php connection
Example query