Can't migrate or update - php7.0 error

,

I’ve been trying to find a solution for weeks when I have time (I’m just an amateur) and tried many forum topics before deciding to post my support request.

yr YunoHost

Matériel: VPS Hosted by Greenhost
Version de YunoHost: 4.4.2.14 (stable)
J’ai accès à mon serveur : En SSH | Par la webadmin

Êtes-vous dans un contexte particulier ou avez-vous effectué des modificiations particulières sur votre instance ? : non

Description du problème

When I try update (under system update)

There are some pending migrations waiting to be ran. Please go to the [Tools > Migrations] view to run them.

I tick the box and click run to

  1. Upgrade the system to Debian Bullseye and YunoHost 11.x

The errors I get:

  • Setting up php7.0-fpm (7.0.33-63+0~20220929.70+debian11~1.gbp80dc38) …

Job for php7.0-fpm.service failed because the control process exited with error code.

See “systemctl status php7.0-fpm.service” and “journalctl -xe” for details.

invoke-rc.d: initscript php7.0-fpm, action “restart” failed.

    • php7.0-fpm.service - The PHP 7.0 FastCGI Process Manager
  • Loaded: loaded (/lib/systemd/system/php7.0-fpm.service; disabled; vendor preset: enabled)

  • Active: failed (Result: exit-code) since Sat 2022-11-12 09:23:36 GMT; 12ms ago

  • Docs: man:php-fpm7.0(8)

  • Process: 12331 ExecStart=/usr/sbin/php-fpm7.0 --nodaemonize --fpm-config /etc/php/7.0/fpm/php-fpm.conf (code=exited, status=78)

  • Process: 12332 ExecStopPost=/usr/lib/php/php-fpm-socket-helper remove /run/php/php-fpm.sock /etc/php/7.0/fpm/pool.d/www.conf 70 (code=exited, status=0/SUCCESS)

  • Main PID: 12331 (code=exited, status=78)

  • CPU: 73ms

  • Nov 12 09:23:35 MYDOMAIN systemd[1]: Starting The PHP 7.0 FastCGI Process Manager…

  • Nov 12 09:23:35 MYDOMAIN php-fpm7.0[12331]: [12-Nov-2022 09:23:35] WARNING: Nothing matches the include pattern ‘/etc/php/7.0/fpm/pool.d/*.conf’ from /etc/php/7.0/fpm/php-fpm.conf at line 125.

  • Nov 12 09:23:35MYDOMAIN php-fpm7.0[12331]: [12-Nov-2022 09:23:35] ERROR: No pool defined. at least one pool section must be specified in config file

  • Nov 12 09:23:35 MYDOMAIN php-fpm7.0[12331]: [12-Nov-2022 09:23:35] ERROR: failed to post process the configuration

  • Nov 12 09:23:35 vMYDOMAIN php-fpm7.0[12331]: [12-Nov-2022 09:23:35] ERROR: FPM initialization failed

  • Nov 12 09:23:35 MYDOMAIN systemd[1]: php7.0-fpm.service: Main process exited, code=exited, status=78/CONFIG

  • Nov 12 09:23:36 MYDOMAIN systemd[1]: php7.0-fpm.service: Failed with result ‘exit-code’.

  • Nov 12 09:23:36 MYDOMAIN systemd[1]: Failed to start The PHP 7.0 FastCGI Process Manager.

dpkg: error processing package php7.0-fpm (–configure):

installed php7.0-fpm package post-installation script subprocess returned error exit status 1

dpkg: dependency problems prevent configuration of php7.0:

php7.0 depends on libapache2-mod-php7.0 | php7.0-fpm | php7.0-cgi; however:

Package libapache2-mod-php7.0 is not installed.

Package php7.0-fpm is not configured yet.

Package php7.0-cgi is not installed.

dpkg: error processing package php7.0 (–configure):

dependency problems - leaving unconfigured

  • Processing triggers for mariadb-server-10.5 (1:10.5.15-0+deb11u1) …

Errors were encountered while processing:

php7.0-fpm

php7.0

E: Sub-process /usr/bin/dpkg returned an error code (1)

Migration 0021_migrate_to_bullseye did not complete, aborting. Error: Failed to reinstall mariadb-common ?

When I try to update in SSH

sudo apt install --fix-broken

Nov 12 09:30:15 MYDOMAIN systemd[1]: Starting The PHP 7.0 FastCGI Process Manager…
Nov 12 09:30:15 MYDOMAIN php-fpm7.0[14144]: [12-Nov-2022 09:30:15] WARNING: Nothing matches the include pattern '/etc/php/7.0/fpm/pool.d/.conf’ from /etc/php/7.0/fpm/php-fpm.conf at line 125.
Nov 12 09:30:15
MYDOMAIN* php-fpm7.0[14144]: [12-Nov-2022 09:30:15] ERROR: No pool defined. at least one pool section must be specified in config file
Nov 12 09:30:15 MYDOMAIN php-fpm7.0[14144]: [12-Nov-2022 09:30:15] ERROR: failed to post process the configuration
Nov 12 09:30:15 MYDOMAIN php-fpm7.0[14144]: [12-Nov-2022 09:30:15] ERROR: FPM initialization failed
Nov 12 09:30:15MYDOMAIN systemd[1]: php7.0-fpm.service: Main process exited, code=exited, status=78/CONFIG
Nov 12 09:30:15 MYDOMAIN systemd[1]: php7.0-fpm.service: Failed with result ‘exit-code’.
Nov 12 09:30:15 MYDOMAIN systemd[1]: Failed to start The PHP 7.0 FastCGI Process Manager.
dpkg: error processing package php7.0-fpm (–configure):
installed php7.0-fpm package post-installation script subprocess returned error exit status 1
dpkg: dependency problems prevent configuration of php7.0:
php7.0 depends on libapache2-mod-php7.0 | php7.0-fpm | php7.0-cgi; however:
Package libapache2-mod-php7.0 is not installed.
Package php7.0-fpm is not configured yet.
Package php7.0-cgi is not installed.

dpkg: error processing package php7.0 (–configure):
dependency problems - leaving unconfigured
Errors were encountered while processing:
php7.0-fpm
php7.0
E: Sub-process /usr/bin/dpkg returned an error code (1)

Based on another topic, I tried

yunohost service status nginx

root@vps:/home/admin# yunohost service status nginx
configuration: valid
description: Serves or provides access to all the websites hosted on your server
last_state_change: 2022-11-12 09:03:38
start_on_boot: enabled
status: running

And

yunohost service status php7.0-fpm

I get

Error: Unknown service ‘php7.0-fpm’

Under /yunohost/admin/#/services for php
I only have php7.3-fpm nd php8.0-fpm

Now keep in mind I’m not sure what I’m doing…

I thought about trying

sudo apt install php7.0 php7.0-cli php7.0-common php7.0-curl php7.0-mbstring php7.0-mysql php7.0-xml

Seen on another topic but I get this

Reading package lists… Done
Building dependency tree… Done
Reading state information… Done
php7.0 is already the newest version (7.0.33-63+0~20220929.70+debian11~1.gbp80dc38).
php7.0-cli is already the newest version (7.0.33-63+0~20220929.70+debian11~1.gbp80dc38).
php7.0-common is already the newest version (7.0.33-63+0~20220929.70+debian11~1.gbp80dc38).
php7.0-curl is already the newest version (7.0.33-63+0~20220929.70+debian11~1.gbp80dc38).
php7.0-mbstring is already the newest version (7.0.33-63+0~20220929.70+debian11~1.gbp80dc38).
php7.0-mysql is already the newest version (7.0.33-63+0~20220929.70+debian11~1.gbp80dc38).
php7.0-xml is already the newest version (7.0.33-63+0~20220929.70+debian11~1.gbp80dc38).
0 upgraded, 0 newly installed, 0 to remove and 29 not upgraded.
2 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n]

I don’t know if clicking Y will help or if this is another problem.

Can someone help me please?

i suggest you try to remove php7 and reinstall it

  1. sudo apt-get remove php7.0

  2. sudo apt-get purge php7.0

  3. sudo dpkg --configure -a

  4. sudo apt-get install php7.0

  5. sudo apt-get install -f

  6. sudo apt-get clean

  7. sudo apt-get update --fix-missing

now to to check if fpm service is healthy
yunohost service status php7.0-fpm

if so try to upgrade

(Or not even reinstalling php7.0 : just uninstall it … it’s weird that you still have php7.0 being on Buster … )

Thanks but unfortunately that didn’t work.

I tried all 6 instructions

1st one

Do you want to continue? [Y/n] Y
(Reading database … 103753 files and directories currently installed.)
Removing php7.0 (7.0.33-63+0~20220929.70+debian11~1.gbp80dc38) …
Setting up php7.0-fpm (7.0.33-63+0~20220929.70+debian11~1.gbp80dc38) …
Job for php7.0-fpm.service failed because the control process exited with error code.
See “systemctl status php7.0-fpm.service” and “journalctl -xe” for details.
invoke-rc.d: initscript php7.0-fpm, action “restart” failed.
● php7.0-fpm.service - The PHP 7.0 FastCGI Process Manager
Loaded: loaded (/lib/systemd/system/php7.0-fpm.service; disabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Sat 2022-11-12 14:42:22 GMT; 23ms ago
Docs: man:php-fpm7.0(8)
Process: 35271 ExecStart=/usr/sbin/php-fpm7.0 --nodaemonize --fpm-config /etc/php/7.0/fpm/php-fpm.conf (code=exited, status=78)
Process: 35272 ExecStopPost=/usr/lib/php/php-fpm-socket-helper remove /run/php/php-fpm.sock /etc/php/7.0/fpm/pool.d/www.conf 70 (code=exited, status=0/SUCCESS)
Main PID: 35271 (code=exited, status=78)
CPU: 66ms

For all instructions I get a similar error message

Nov 12 14:47:39 Domain php-fpm7.0[42974]: [12-Nov-2022 14:47:39] WARNING: Nothing matches the include pattern ‘/etc/php/7.0/fpm/pool.d/*.conf’ from /etc/php/7.0/fpm/php-fpm.conf at line 125.
Nov 12 14:47:39 Domain php-fpm7.0[42974]: [12-Nov-2022 14:47:39] ERROR: No pool defined. at least one pool section must be specified in config file
Nov 12 14:47:39 Domain php-fpm7.0[42974]: [12-Nov-2022 14:47:39] ERROR: failed to post process the configuration
Nov 12 14:47:39 Domain php-fpm7.0[42974]: [12-Nov-2022 14:47:39] ERROR: FPM initialization failed
Nov 12 14:47:39 Domain systemd[1]: php7.0-fpm.service: Main process exited, code=exited, status=78/CONFIG
Nov 12 14:47:39 Domain systemd[1]: php7.0-fpm.service: Failed with result ‘exit-code’.
Nov 12 14:47:39 Domain systemd[1]: Failed to start The PHP 7.0 FastCGI Process Manager

And yes @Aleks I don’t get why I have php7.0
On my VPS I have:

  • Matomo
  • phpmyadmin
  • 6 x Custom Web app (all with Wordpress installed manually)
  • 1 x Wordpress
  • 5 x Redirect
  • Yunohost backup

None are using php 7.0

Then lets try sudo apt remove php7.0* (and review carefully what apt will tell you, it may want to remove important packages because of this)

did you try just to remove it as aleks suggested ?

Yes I tried. I always try what @Aleks suggest!!!

root@vps:/etc/php/7.0/fpm/pool.d# sudo apt remove php7.0
Reading package lists… Done
Building dependency tree… Done
Reading state information… Done
The following packages will be REMOVED:
php7.0
0 upgraded, 0 newly installed, 1 to remove and 30 not upgraded.
2 not fully installed or removed.
After this operation, 88.1 kB disk space will be freed.
Do you want to continue? [Y/n] Y
(Reading database … 103749 files and directories currently installed.)
Removing php7.0 (7.0.33-63+0~20220929.70+debian11~1.gbp80dc38) …
Setting up php7.0-fpm (7.0.33-63+0~20220929.70+debian11~1.gbp80dc38) …
Job for php7.0-fpm.service failed because the control process exited with error code.
See “systemctl status php7.0-fpm.service” and “journalctl -xe” for details.
invoke-rc.d: initscript php7.0-fpm, action “restart” failed.
● php7.0-fpm.service - The PHP 7.0 FastCGI Process Manager
Loaded: loaded (/lib/systemd/system/php7.0-fpm.service; disabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Sat 2022-11-12 15:36:14 GMT; 10ms ago
Docs: man:php-fpm7.0(8)
Process: 66293 ExecStart=/usr/sbin/php-fpm7.0 --nodaemonize --fpm-config /etc/php/7.0/fpm/php-fpm.conf (code=exited, status=78)
Process: 66294 ExecStopPost=/usr/lib/php/php-fpm-socket-helper remove /run/php/php-fpm.sock /etc/php/7.0/fpm/pool.d/www.conf 70 (code=exited, status=0/SUCCESS)
Main PID: 66293 (code=exited, status=78)
CPU: 56ms

Nov 12 15:36:14 vps.domain systemd[1]: Starting The PHP 7.0 FastCGI Process Manager…
Nov 12 15:36:14 vps.domain php-fpm7.0[66293]: [12-Nov-2022 15:36:14] WARNING: Nothing matches the include pattern ‘/etc/php/7.0/fpm/pool.d/*.conf’ from /etc/php/7.0/fpm/php-fpm.conf at line 125.
Nov 12 15:36:14 vps.domain php-fpm7.0[66293]: [12-Nov-2022 15:36:14] ERROR: No pool defined. at least one pool section must be specified in config file
Nov 12 15:36:14 vps.domain php-fpm7.0[66293]: [12-Nov-2022 15:36:14] ERROR: failed to post process the configuration
Nov 12 15:36:14 vps.domain php-fpm7.0[66293]: [12-Nov-2022 15:36:14] ERROR: FPM initialization failed
Nov 12 15:36:14 vps.domain systemd[1]: php7.0-fpm.service: Main process exited, code=exited, status=78/CONFIG
Nov 12 15:36:14 vps.domain systemd[1]: php7.0-fpm.service: Failed with result ‘exit-code’.
Nov 12 15:36:14 vps.domain systemd[1]: Failed to start The PHP 7.0 FastCGI Process Manager.
dpkg: error processing package php7.0-fpm (–configure):
installed php7.0-fpm package post-installation script subprocess returned error exit status 1
Errors were encountered while processing:
php7.0-fpm
E: Sub-process /usr/bin/dpkg returned an error code (1)
root@vps:/etc/php/7.0/fpm/pool.d#

I also tried See “systemctl status php7.0-fpm.service” it’s about the same error

root@vps:/etc/php/7.0/fpm/pool.d# systemctl status php7.0-fpm.service
● php7.0-fpm.service - The PHP 7.0 FastCGI Process Manager
Loaded: loaded (/lib/systemd/system/php7.0-fpm.service; disabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Sat 2022-11-12 15:36:14 GMT; 3min 13s ago
Docs: man:php-fpm7.0(8)
Process: 66293 ExecStart=/usr/sbin/php-fpm7.0 --nodaemonize --fpm-config /etc/php/7.0/fpm/php-fpm.conf (code=exited, status=78)
Process: 66294 ExecStopPost=/usr/lib/php/php-fpm-socket-helper remove /run/php/php-fpm.sock /etc/php/7.0/fpm/pool.d/www.conf 70 (code=exited, status=0/SUCCE>
Main PID: 66293 (code=exited, status=78)
CPU: 56ms

Nov 12 15:36:14 vps.domain systemd[1]: Starting The PHP 7.0 FastCGI Process Manager…
Nov 12 15:36:14 vps.domain php-fpm7.0[66293]: [12-Nov-2022 15:36:14] WARNING: Nothing matches the include pattern ‘/etc/php/7.0/fpm/pool.d/*.conf’ from /etc/>
Nov 12 15:36:14 vps.domain php-fpm7.0[66293]: [12-Nov-2022 15:36:14] ERROR: No pool defined. at least one pool section must be specified in config file
Nov 12 15:36:14 vps.domain php-fpm7.0[66293]: [12-Nov-2022 15:36:14] ERROR: failed to post process the configuration
Nov 12 15:36:14 vps.domain php-fpm7.0[66293]: [12-Nov-2022 15:36:14] ERROR: FPM initialization failed
Nov 12 15:36:14 vps.domain systemd[1]: php7.0-fpm.service: Main process exited, code=exited, status=78/CONFIG
Nov 12 15:36:14 vps.domain systemd[1]: php7.0-fpm.service: Failed with result ‘exit-code’.
Nov 12 15:36:14 vps.domain systemd[1]: Failed to start The PHP 7.0 FastCGI Process Manager.
root@vps:/etc/php/7.0/fpm/pool.d#

Ok now trying with *

=====> All system packages are up to date!

THANK YOU

(And I see "The current Debian distribution is not Buster! " so I will ask Greenhost to upgrade my VPS).

Eeeeh I’m not sure your VPS provider is supposed to upgrade your VPS, they only provide the “hardware” layer, they usually don’t handle the software layer …

Ok, I’ll find a way to do it.