Just upgraded to FreeBSD 15.0 overnight
and noticed only one failure - Serendipity using MYSQL
is giving my an error. Using Nginx-devel, mariadb118, php84 .
This was working in Freebsd 14.3 .
Eror logs
from php-fpm
[29-Nov-2025 14:30:03.152289] DEBUG: pid 71140, fpm_got_signal(), line 81: received SIGCHLD
[29-Nov-2025 14:30:03.152363] DEBUG: pid 71140, fpm_event_loop(), line 426: event module triggered 1 events
[29-Nov-2025 14:30:03.152431] NOTICE: pid 71140, fpm_children_bury(), line 300: [pool www] child 71150 exited with code 0 after 12103.741743 seconds from start
[29-Nov-2025 14:30:03.152449] DEBUG: pid 71140, fpm_children_make(), line 449: blocking signals before child birth
[29-Nov-2025 14:30:03.154962] DEBUG: pid 71140, fpm_children_make(), line 473: unblocking signals, child born
[29-Nov-2025 14:30:03.154997] NOTICE: pid 71140, fpm_children_make(), line 479: [pool www] child 82633 started
From nginx
[error] 76006#100398: *9047 upstream prematurely closed connection while reading response header from upstream, client: 162.157.247.67, server: www.nk.ca, request: "POST /~doctor/blog/serendipity/serendipity_admin.php? HTTP/3.0", upstream: "fastcgi://unix:/var/run/php-fpm.sock:", referrer: "https://www.nk.ca/~doctor/blog/serendipity/serendipity_admin.php?serendipity[adminModule]=entries&serendipity[adminAction]=new"
Now can you go from no issue to error in an
OS upgrade?
On 29/11/2025 22.55, The Doctor wrote:
Just upgraded to FreeBSD 15.0 overnight81: received SIGCHLD
and noticed only one failure - Serendipity using MYSQL
is giving my an error. Using Nginx-devel, mariadb118, php84 .
This was working in Freebsd 14.3 .
Eror logs
from php-fpm
[29-Nov-2025 14:30:03.152289] DEBUG: pid 71140, fpm_got_signal(), line
[29-Nov-2025 14:30:03.152363] DEBUG: pid 71140, fpm_event_loop(), line426: event module triggered 1 events
[29-Nov-2025 14:30:03.152431] NOTICE: pid 71140, fpm_children_bury(),line 300: [pool www] child 71150 exited with code 0 after 12103.741743 >seconds from start
[29-Nov-2025 14:30:03.152449] DEBUG: pid 71140, fpm_children_make(),line 449: blocking signals before child birth
[29-Nov-2025 14:30:03.154962] DEBUG: pid 71140, fpm_children_make(),line 473: unblocking signals, child born
[29-Nov-2025 14:30:03.154997] NOTICE: pid 71140, fpm_children_make(),line 479: [pool www] child 82633 started
while reading response header from upstream, client: 162.157.247.67,
From nginx
[error] 76006#100398: *9047 upstream prematurely closed connection
server: www.nk.ca, request: "POST >/~doctor/blog/serendipity/serendipity_admin.php? HTTP/3.0", upstream: >"fastcgi://unix:/var/run/php-fpm.sock:", referrer: >"https://www.nk.ca/~doctor/blog/serendipity/serendipity_admin.php?serendipity[adminModule]=entries&serendipity[adminAction]=new"
Now can you go from no issue to error in an
OS upgrade?
Could be a change in default php settings, for example the >max_execution_time for fpm-php could have changed either by a decision
by freebsd or zend. You could try to extend the time and see if it helps
you (don't forget to restart fpm-php after change of value).
----
//Aho
| Sysop: | Amessyroom |
|---|---|
| Location: | Fayetteville, NC |
| Users: | 54 |
| Nodes: | 6 (0 / 6) |
| Uptime: | 19:20:27 |
| Calls: | 742 |
| Files: | 1,218 |
| D/L today: |
5 files (8,203K bytes) |
| Messages: | 184,913 |
| Posted today: | 1 |