extra warning messages for "SSL: Connection timed out"

[rbro]

Description

I am running PHP 8.3.16 on Linux, and I run PHP with "error_log = /var/log/phplog".

At times, I believe after long running processes have finished, I will see warnings like this logged:

[26-Feb-2025 00:10:35 America/New_York] PHP Warning:  PHP Request Shutdown: SSL: Connection timed out in Unknown on line 0

I'm trying to figure out where they are coming from and how to suppress them. My code is connecting to a MySQL database over SSL, so one possibility could be from this line, but I don't know for sure:

https://github.com/php/php-src/blob/master/ext/openssl/xp_ssl.c#L271

My questions are:

• is there something I can do to definitely find out where this error is coming from?
• could it be suppressed?

Thanks for your help.

PHP Version

8.3.16

Operating System

Linux

[iluuu1994]

Maybe @bukka can help.

[bukka]

Yeah that's the right place where it's triggered most likely.

I think it might come from mysqlnd trying to finalize connection in request shutdown (assuming you don't use persistent connections). As it's using tls stream, it will fail on io for some reason and shows this message. If it happens on long running request, maybe MySQL server closes that connection due to some limits. Could be even the stream timout (like https://www.php.net/manual/en/mysqlnd.config.php#ini.mysqlnd.net-read-timeout ) but that's already quite hight by default.

I would probably look to the MySQL stats to see if there is anything close to limits and if there are any forced closures (there might be stat for it but not sure). You could even try to trace conncecttion (e.g. get traffic dump using tcpdump or other tools - if you use aws, then vpc logs might help) and see if there's anything there. There are tools to do that. Basically you will need to somehow figure it out and if you see something suspicious on PHP side, you can let us know. Otherwise there's unfortunately not much we can do about this.

There is no way to suppress it as far as I'm aware because it is an issue that should be reported. Well you can of course filter it from logs yourself if you don't mind that error (it might not be really a problem but it really depends what the cause is).