Hi,
just performed a successful upgrade from bullseye to bookworm using the congenial upgrade script.
Thank you for this well crafted piece of code!
All the services are up and running again, only php-fpm didn’t grew up completely.
Browsing my Nextcloud gives me a ‘502- bad gateway’.
Inspecting Nginx error.log:
2024/03/07 07:27:21 [crit] 11860#11860: *955 connect() to unix:/run/php/php7.4-fpm.sock failed (2: No such file or directory) while connecting to upstream, client: 2a0a:2782:3f9:7c00:2d83:4b23:700:cb96, server: ***.***.org, request: "GET /nextcloud/index.php/204 HTTP/1.1", upstream: "fastcgi://unix:/run/php/php7.4-fpm.sock:", host: "***.***.org"
So let’s peek inside /etc/nginx/nginx.conf. Nginx is stuck with PHP 7.4, while the machine now is on PHP 8.2.7
# Upstream to abstract back-end connection(s) for PHP
upstream php {
server unix:/run/php/php7.4-fpm.sock;
}
php --version
PHP 8.2.7 (cli) (built: Jun 9 2023 19:37:27) (NTS)
The only ‘php’ in /run is php_sessions, so let’s locate it
locate fpm.sock
/etc/alternatives/php-fpm.sock
/mnt/dietpi-backup/data/etc/alternatives/php-fpm.sock
/mnt/dietpi-backup/data/var/lib/dpkg/alternatives/php-fpm.sock
/var/lib/dpkg/alternatives/php-fpm.sock
What is it in ‘alternatives’?
lrwxrwxrwx 1 root root 15 Mar 6 19:39 php -> /usr/bin/php8.2
lrwxrwxrwx 1 root root 24 Mar 6 09:42 php-fpm.sock -> /run/php/php7.4-fpm.sock
At least, is php-fpm running?
ps aux | grep php
root 11955 0.0 0.1 3560 1920 pts/0 S+ 07:29 0:00 grep php
ps aux | grep php-fpm
root 11975 0.0 0.1 3560 1920 pts/0 S+ 07:30 0:00 grep php-fpm
Is there anybody who already fixed this and linked the new php-fpm with Nginx?
Thanks for help
Frans
I have searched the existing open and closed issues
Required Information
G_DIETPI_VERSION_CORE=9
G_DIETPI_VERSION_SUB=1
G_DIETPI_VERSION_RC=1
G_GITBRANCH=‘master’
G_GITOWNER=‘MichaIng’
G_LIVE_PATCH_STATUS[0]=‘not applicable’
bookworm
Linux ..org 6.6.16-current-meson64 #1 SMP PREEMPT Fri Feb 23 08:25:28 UTC 2024 aarch64 GNU/Linux
arm64
Odroid C2 (aarch64)