I got my answer when I unziped the file. The image is a Yunohost Bookworm 12.0.7 .
Hi,
I installed Bookworm from the Rpi imager then followed the curl installation to install Yunohost, a few days ago.
Should I use your Yunohost image instead and perform a new install?
Thank you.
no thereâs no reason to switch to the Yunohost image instead
Does it work with armbian too?
Hi all,
I followed the steps to upgrade to Bookworm, I then looked through this long thread and followed everything I could come across to solve this issue, but it persists.
root@matemates:/etc/php# apt full-upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
The following packages have been kept back:
moulinette ssowat yunohost yunohost-admin
0 upgraded, 0 newly installed, 0 to remove and 4 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n]
Setting up php7.3-fpm (7.3.33-22+0~20241124.122+debian12~1.gbpb244f0) ...
Not replacing deleted config file /etc/php/7.3/fpm/php.ini
Job for php7.3-fpm.service failed because the control process exited with error code.
See "systemctl status php7.3-fpm.service" and "journalctl -xeu php7.3-fpm.service" for details.
invoke-rc.d: initscript php7.3-fpm, action "restart" failed.
â php7.3-fpm.service - The PHP 7.3 FastCGI Process Manager
Loaded: loaded (/lib/systemd/system/php7.3-fpm.service; disabled; preset: enabled)
Active: activating (auto-restart) (Result: exit-code) since Thu 2024-11-28 11:35:48 CET; 8ms ago
Docs: man:php-fpm7.3(8)
Process: 3368144 ExecStart=/usr/sbin/php-fpm7.3 --nodaemonize --fpm-config /etc/php/7.3/fpm/php-fpm.conf (code=exite
d, status=78)
Process: 3368145 ExecStopPost=/usr/lib/php/php-fpm-socket-helper remove /run/php/php-fpm.sock /etc/php/7.3/fpm/pool.
d/www.conf 73 (code=exited, status=0/SUCCESS)
Main PID: 3368144 (code=exited, status=78)
CPU: 13ms
dpkg: error processing package php7.3-fpm (--configure):
installed php7.3-fpm package post-installation script subprocess returned error exit status 1
Errors were encountered while processing:
php7.3-fpm
Updating coolwsd systemplate
E: Sub-process /usr/bin/dpkg returned an error code (1)
I really donât know what else to do, and donât want to do too much in case I break something, if I didnât already.
Any suggestions?
I upgrade those and it all worked fine. But I canât install applications via the webadmin. Iâve tried to install webmin.
I tried to upgrade php7.3-fpm and I get this same error and I donât know where to go from here.
root@matemates:~# apt install php7.3-fpm
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
php7.3-fpm is already the newest version (7.3.33-22+0~20241124.122+debian12~1.gbpb244f0).
php7.3-fpm set to manually installed.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n]
Setting up php7.3-fpm (7.3.33-22+0~20241124.122+debian12~1.gbpb244f0) ...
Job for php7.3-fpm.service failed because the control process exited with error code.
See "systemctl status php7.3-fpm.service" and "journalctl -xeu php7.3-fpm.service" for details.
invoke-rc.d: initscript php7.3-fpm, action "restart" failed.
â php7.3-fpm.service - The PHP 7.3 FastCGI Process Manager
Loaded: loaded (/lib/systemd/system/php7.3-fpm.service; disabled; preset: enabled)
Active: activating (auto-restart) (Result: exit-code) since Thu 2024-11-28 12:05:48 CET; 11ms ago
Docs: man:php-fpm7.3(8)
Process: 10334 ExecStart=/usr/sbin/php-fpm7.3 --nodaemonize --fpm-config /etc/php/7.3/fpm/php-fpm.conf (code=exited,
status=78)
Process: 10336 ExecStopPost=/usr/lib/php/php-fpm-socket-helper remove /run/php/php-fpm.sock /etc/php/7.3/fpm/pool.d/
www.conf 73 (code=exited, status=0/SUCCESS)
Main PID: 10334 (code=exited, status=78)
CPU: 54ms
dpkg: error processing package php7.3-fpm (--configure):
installed php7.3-fpm package post-installation script subprocess returned error exit status 1
Errors were encountered while processing:
php7.3-fpm
Updating coolwsd systemplate
E: Sub-process /usr/bin/dpkg returned an error code (1)
So I found out that there were some old .conf files for apps which had long been removed. I renamed those to âfilename.conf.oldâ and the issue was gone.
I was able to install Webmin but now Iâm getting this error on the url page.
502 Bad Gateway
If you see this page, your connection with the server is working but the internal service providing this path is not responding.
Administrator, make sure that the service is running, and check its logs if it is not. The Services page is in your webadmin, under
Tools > Services
.Thank you for using YunoHost.
Similar issue here. In /etc/apt/source.list.d/yunohost.list
, I had:
deb https://forge.yunohost.org/debian/ bookworm stable #testing
This sed
operation failed on it because of # testing
comment I still had. In the end, this line should be in the file:
deb [signed-by=/usr/share/keyrings/yunohost-bookworm.gpg] http://forge.yunohost.org/debian/ bookworm stable
I also had a non-problematic issue at the end, because I have fish shell set as default shell.
Info: [####################] > 100.0% Done
Warning: WARNING To run the migration 0031_terms_of_services, your must accept the following disclaimer:
Warning: ---
Warning: This migration is purely an informational message about the fact that the YunoHost project now publishes Terms of Services related to the technical and community services.
Warning:
Warning: The YunoHost project is a team of volunteers who have made common cause to create a free operating system for servers, called YunoHost. The YunoHost software is published under the AGPLv3 license (<https://www.gnu.org/licenses/agpl-3.0.txt>). In connection with this software, the project administers and makes available several technical and community services for various purposes. By using these services, you agree to be bound by the following Terms of Services: <https://yunohost.org/terms_of_services>.
Warning: ---
Warning: If you accept to run the migration, please re-run the command with the option '--accept-disclaimer'.
Success! Migration 0027_migrate_to_bookworm completed
/usr/share/fish/functions/prompt_pwd.fish (line 41): Invalid index value
set full $all[2..]
^
in function 'prompt_pwd'
called on line 1 of file /usr/share/fish/functions/fish_prompt.fish
in command substitution
called on line 33 of file /usr/share/fish/functions/fish_prompt.fish
in function 'fish_prompt'
in command substitution
/usr/share/fish/functions/fish_git_prompt.fish (line 173): $(...) is not supported. In fish, please use '(uname)'.
if string match -q Darwin -- "$(uname)" && string match -q /usr/bin/git -- "$(command -s git)" && type -q xcode-select && type -q xcrun
^
from sourcing file /usr/share/fish/functions/fish_git_prompt.fish
called on line 1 of file /usr/share/fish/functions/fish_vcs_prompt.fish
in command substitution
called on line 4 of file /usr/share/fish/functions/fish_vcs_prompt.fish
in function 'fish_vcs_prompt'
called on line 1 of file /usr/share/fish/functions/fish_prompt.fish
in command substitution
called on line 33 of file /usr/share/fish/functions/fish_prompt.fish
in function 'fish_prompt'
in command substitution
source: Error while reading file â/usr/share/fish/functions/fish_git_prompt.fishâ
/usr/share/fish/functions/prompt_pwd.fish (line 41): Invalid index value
set full $all[2..]
^
in function 'prompt_pwd' with arguments '-d 1 -D 1'
called on line 1 of file /usr/share/fish/functions/fish_title.fish
in command substitution
called on line 18 of file /usr/share/fish/functions/fish_title.fish
in function 'fish_title'
in command substitution
I simply rerun following command with bash:
sudo yunohost tools migrations run
Other issues I had:
- Deleted
/etc/apt/source.list.d/nodejs.list
for v0.10 - had to restart
nginx
as mentioned here - started Mariadb/mysql for Freshrss to work
- had an issue with Pluxml displaying
message : session_start(): Failed to read session data: files (path: /var/lib/php/sessions)
on the blog. It fixed it-self.
I installed rspamd
and metronome
apps, and it seems to work!
Thanks for this great upgrade!
The service is running fine.
This is the output for systemctl status webmin
â webmin.service - Webmin server daemon
Loaded: loaded (/lib/systemd/system/webmin.service; enabled; preset: enabled)
Active: active (running) since Thu 2024-11-28 13:31:35 CET; 13min ago
Process: 15775 ExecStart=/usr/share/webmin/miniserv.pl /etc/webmin/miniserv.conf (code=exited, status=0/SUCCESS)
Main PID: 15777 (miniserv.pl)
Tasks: 1 (limit: 19146)
Memory: 27.5M
CPU: 600ms
CGroup: /system.slice/webmin.service
ââ15777 /usr/bin/perl /usr/share/webmin/miniserv.pl /etc/webmin/miniserv.conf
Nov 28 13:31:32 matemates.com systemd[1]: Starting webmin.service - Webmin server daemon...
Nov 28 13:31:32 matemates.com perl[15775]: pam_unix(webmin:auth): authentication failure; logname= uid=0 euid=0 tty= ruser= rhost= user=root
Nov 28 13:31:34 matemates.com webmin[15775]: Webmin starting
Nov 28 13:31:35 matemates.com systemd[1]: Started webmin.service - Webmin server daemon.
And journalctl -u webmin.service
see logs here
I move this post to the Webmin app thread.
Did the upgrade today. There was a major error, probably not related to ynh itself:
Warning: E: Failed to fetch http://debian.proxad.net/debian/pool/main/l/live-tools/live-tools_20190831.1_all.deb: Error reading from server - read (104: Connection reset by peer) [IP: 2a01:e0c:1:1598::2 80]
Warning: E: Unable to fetch some packages; try '-o APT::Get::Fix-Missing=true' to continue with missing packages
Error: Migration 0027_migrate_to_bookworm did not complete, aborting. Error: Failed to run command 'aptitude full-upgrade --show-why -o Dpkg::Options::='--force-confold''
I guess I was just unlucky there.
Tthe result was that the migration failed and yunohost itself wasnât working (because some python packages were left completely broken). So it was impossible to restart the migration or even display the logs
I just relaunched an âapt dist-upgradeâ, and chose to keep my config files each time the process asked me. I did replace the dnsmasq.conf
, which turned out to be a mistake. I had to use regen-conf
to get the correct version and get internet back.
After that, yunohost
was working again so I could relaunch the migration, which seems to have run correctly. So far everything seems to be ok
Thanks for this!
An app that had a strange behaviour after the migration was Automad. I had two Automad instances installed and they got their data deleted, meaning they looked like freshly installed.
I havenât looked into the backup yet. Though I restored them from the backup, but same thing. Iâll look into the files and see if anythingâs there.
Comparing my ynh two servers running on a rpi4(after migrating to debian 12 with default ynh migration tool), with another server I fresh installed RasiOS12 I noticed one difference, they were running different kernel version, both yunhost were stuck in an old 6.1 version.
What I did to fix it:
sudo apt install sudo apt install linux-image-rpi-2712 linux-image-rpi-v8
then:
- sudo umount /boot
- sudo mkdir /boot/firmware
- sudo nano /etc/fstab and changed /boot to /boot/firmware
- reboot
Now I have kernel 6.6.62 on all of them as expected, but still the fresh one with raspiOS the /boot/firmware folder has 446MB, on those two running ynh same folder has 191MB, not sure how to fix that and if it can be a problem in the future.
Jâai fais la mise Ă jour de deux serveurs avec des applications multiples. Aucun soucis pour cette montĂ©e de version !
Franchement je suis déçu, câest un peu trop simple !
Câest vraiment un bonheur dâutilisation, merci Ă toute lâĂ©quipe !
Bonjour Ă tous,
Je rencontre un petit souci lors de ma migration
Info : [###################.] > 99.1% Processing libc-bin
Attention : E: Sub-process /usr/bin/dpkg returned an error code (1)
Attention : Job for php7.3-fpm.service failed because the control process exited with error code.
Attention : See âsystemctl status php7.3-fpm.serviceâ and âjournalctl -xeâ for details.
Attention : invoke-rc.d: initscript php7.3-fpm, action ârestartâ failed.
Attention : dpkg: error processing package php7.3-fpm (âconfigure):
Attention : installed php7.3-fpm package post-installation script subprocess returned error exit status 1
Attention : Errors were encountered while processing:
Attention : php7.3-fpm
Erreur : La migration 0027_migrate_to_bookworm a Ă©chouĂ©, abandon. Erreur : Failed to run command âaptitude full-upgrade cron rspamd- luajit- libluajit-5.1-2- --show-why -o APT::Force-LoopBreak=1 -o Dpkg::Options::=ââforce-confoldââ
Le journal de migration complet est ici https://paste.yunohost.org/raw/wupepejoqa
En lancant la commande en question à la main voici le résultat
sudo aptitude full-upgrade cron rspamd- luajit- libluajit-5.1-2- --show-why -o APT::Force-LoopBreak=1 -o Dpkg::Options::=ââforce-confoldâ
[sudo] Mot de passe de XXXX :
cron is already installed at the latest version (3.0pl1-162), so it will not be upgraded
Le paquet rspamd nâest pas installĂ©, il ne sera donc pas enlevĂ©.
Le paquet luajit nâest pas installĂ©, il ne sera donc pas enlevĂ©.
Le paquet libluajit-5.1-2 nâest pas installĂ©, il ne sera donc pas enlevĂ©.
cron is already installed at the latest version (3.0pl1-162), so it will not be upgraded
Le paquet rspamd nâest pas installĂ©, il ne sera donc pas enlevĂ©.
Le paquet luajit nâest pas installĂ©, il ne sera donc pas enlevĂ©.
Le paquet libluajit-5.1-2 nâest pas installĂ©, il ne sera donc pas enlevĂ©.
Aucun paquet ne va ĂȘtre installĂ©, mis Ă jour ou enlevĂ©.
0 paquets mis à jour, 0 nouvellement installés, 0 à enlever et 954 non mis à jour.
Il est nĂ©cessaire de tĂ©lĂ©charger 0 o dâarchives. AprĂšs dĂ©paquetage, 0 o seront utilisĂ©s.
ParamĂ©trage de php7.3-fpm (7.3.33-22+0~20241124.122+debian11~1.gbpb244f0) âŠ
Job for php7.3-fpm.service failed because the control process exited with error code.
See âsystemctl status php7.3-fpm.serviceâ and âjournalctl -xeâ for details.
invoke-rc.d: initscript php7.3-fpm, action ârestartâ failed.
â php7.3-fpm.service - The PHP 7.3 FastCGI Process Manager
Loaded: loaded (/lib/systemd/system/php7.3-fpm.service; disabled; vendor preset: enabled)
Active: activating (auto-restart) (Result: exit-code) since Tue 2024-12-03 19:56:38 CET; 16ms ago
Docs: man:php-fpm7.3(8)
Process: 596276 ExecStart=/usr/sbin/php-fpm7.3 --nodaemonize --fpm-config /etc/php/7.3/fpm/php-fpm.conf (code=exited, status=78)
Process: 596277 ExecStopPost=/usr/lib/php/php-fpm-socket-helper remove /run/php/php-fpm.sock /etc/php/7.3/fpm/pool.d/www.conf 73 (code=exited, status=0/SUCCESS)
Main PID: 596276 (code=exited, status=78)
CPU: 75ms
dpkg: erreur de traitement du paquet php7.3-fpm (âconfigure) :
installed php7.3-fpm package post-installation script subprocess returned error exit status 1
Des erreurs ont Ă©tĂ© rencontrĂ©es pendant lâexĂ©cution :
php7.3-fpm
E: Sub-process /usr/bin/dpkg returned an error code (1)
ParamĂ©trage de php7.3-fpm (7.3.33-22+0~20241124.122+debian11~1.gbpb244f0) âŠ
Job for php7.3-fpm.service failed because the control process exited with error code.
See âsystemctl status php7.3-fpm.serviceâ and âjournalctl -xeâ for details.
invoke-rc.d: initscript php7.3-fpm, action ârestartâ failed.
â php7.3-fpm.service - The PHP 7.3 FastCGI Process Manager
Loaded: loaded (/lib/systemd/system/php7.3-fpm.service; disabled; vendor preset: enabled)
Active: activating (auto-restart) (Result: exit-code) since Tue 2024-12-03 19:56:43 CET; 14ms ago
Docs: man:php-fpm7.3(8)
Process: 597695 ExecStart=/usr/sbin/php-fpm7.3 --nodaemonize --fpm-config /etc/php/7.3/fpm/php-fpm.conf (code=exited, status=78)
Process: 597696 ExecStopPost=/usr/lib/php/php-fpm-socket-helper remove /run/php/php-fpm.sock /etc/php/7.3/fpm/pool.d/www.conf 73 (code=exited, status=0/SUCCESS)
Main PID: 597695 (code=exited, status=78)
CPU: 71ms
dpkg: erreur de traitement du paquet php7.3-fpm (âconfigure) :
installed php7.3-fpm package post-installation script subprocess returned error exit status 1
Des erreurs ont Ă©tĂ© rencontrĂ©es pendant lâexĂ©cution :
php7.3-fpm
et si je tente de lancer php 7.3 Ă la main
systemctl start php7.3-fpm.service
==== AUTHENTICATING FOR org.freedesktop.systemd1.manage-units ===
Authentification requise pour démarrer « php7.3-fpm.service ».
Authenticating as: root
Password:
==== AUTHENTICATION COMPLETE ===
Job for php7.3-fpm.service failed because the control process exited with error code.
See âsystemctl status php7.3-fpm.serviceâ and âjournalctl -xeâ for details.
avez-vous une idée de vers ou commencer à creuser ?
Est-ce que tu peux partager le retour de :
sudo journalctl -u php7.3-fpm -n 100 --no-pager --no-hostname
Le voici
déc. 03 20:07:44 systemd[1]: Stopped The PHP 7.3 FastCGI Process Manager.
déc. 03 20:07:44 systemd[1]: php7.3-fpm.service: Start request repeated too quickly.
dĂ©c. 03 20:07:44 systemd[1]: php7.3-fpm.service: Failed with result âexit-codeâ.
déc. 03 20:07:44 systemd[1]: Failed to start The PHP 7.3 FastCGI Process Manager.
dĂ©c. 03 20:14:50 systemd[1]: Starting The PHP 7.3 FastCGI Process ManagerâŠ
dĂ©c. 03 20:14:50 php-fpm7.3[608666]: [03-Dec-2024 20:14:50] ERROR: [pool dokuwiki__2] the chdir path â/var/www/dokuwiki__2â does not exist or is not a directory
déc. 03 20:14:50 php-fpm7.3[608666]: [03-Dec-2024 20:14:50] ERROR: failed to post process the configuration
déc. 03 20:14:50 php-fpm7.3[608666]: [03-Dec-2024 20:14:50] ERROR: FPM initialization failed
déc. 03 20:14:50 systemd[1]: php7.3-fpm.service: Main process exited, code=exited, status=78/CONFIG
dĂ©c. 03 20:14:50 systemd[1]: php7.3-fpm.service: Failed with result âexit-codeâ.
déc. 03 20:14:50 systemd[1]: Failed to start The PHP 7.3 FastCGI Process Manager.
déc. 03 20:14:50 systemd[1]: php7.3-fpm.service: Scheduled restart job, restart counter is at 1.
déc. 03 20:14:50 systemd[1]: Stopped The PHP 7.3 FastCGI Process Manager.
dĂ©c. 03 20:14:50 systemd[1]: Starting The PHP 7.3 FastCGI Process ManagerâŠ
dĂ©c. 03 20:14:50 php-fpm7.3[608673]: [03-Dec-2024 20:14:50] ERROR: [pool dokuwiki__2] the chdir path â/var/www/dokuwiki__2â does not exist or is not a directory
déc. 03 20:14:50 php-fpm7.3[608673]: [03-Dec-2024 20:14:50] ERROR: failed to post process the configuration
déc. 03 20:14:50 php-fpm7.3[608673]: [03-Dec-2024 20:14:50] ERROR: FPM initialization failed
déc. 03 20:14:50 systemd[1]: php7.3-fpm.service: Main process exited, code=exited, status=78/CONFIG
dĂ©c. 03 20:14:50 systemd[1]: php7.3-fpm.service: Failed with result âexit-codeâ.
déc. 03 20:14:50 systemd[1]: Failed to start The PHP 7.3 FastCGI Process Manager.
déc. 03 20:14:50 systemd[1]: php7.3-fpm.service: Scheduled restart job, restart counter is at 2.
déc. 03 20:14:50 systemd[1]: Stopped The PHP 7.3 FastCGI Process Manager.
dĂ©c. 03 20:14:50 systemd[1]: Starting The PHP 7.3 FastCGI Process ManagerâŠ
dĂ©c. 03 20:14:50 php-fpm7.3[608682]: [03-Dec-2024 20:14:50] ERROR: [pool dokuwiki__2] the chdir path â/var/www/dokuwiki__2â does not exist or is not a directory
déc. 03 20:14:50 php-fpm7.3[608682]: [03-Dec-2024 20:14:50] ERROR: failed to post process the configuration
déc. 03 20:14:50 php-fpm7.3[608682]: [03-Dec-2024 20:14:50] ERROR: FPM initialization failed
déc. 03 20:14:50 systemd[1]: php7.3-fpm.service: Main process exited, code=exited, status=78/CONFIG
dĂ©c. 03 20:14:50 systemd[1]: php7.3-fpm.service: Failed with result âexit-codeâ.
déc. 03 20:14:50 systemd[1]: Failed to start The PHP 7.3 FastCGI Process Manager.
déc. 03 20:14:50 systemd[1]: php7.3-fpm.service: Scheduled restart job, restart counter is at 3.
déc. 03 20:14:50 systemd[1]: Stopped The PHP 7.3 FastCGI Process Manager.
dĂ©c. 03 20:14:50 systemd[1]: Starting The PHP 7.3 FastCGI Process ManagerâŠ
dĂ©c. 03 20:14:50 php-fpm7.3[608718]: [03-Dec-2024 20:14:50] ERROR: [pool dokuwiki__2] the chdir path â/var/www/dokuwiki__2â does not exist or is not a directory
déc. 03 20:14:50 php-fpm7.3[608718]: [03-Dec-2024 20:14:50] ERROR: failed to post process the configuration
déc. 03 20:14:50 php-fpm7.3[608718]: [03-Dec-2024 20:14:50] ERROR: FPM initialization failed
déc. 03 20:14:50 systemd[1]: php7.3-fpm.service: Main process exited, code=exited, status=78/CONFIG
dĂ©c. 03 20:14:50 systemd[1]: php7.3-fpm.service: Failed with result âexit-codeâ.
déc. 03 20:14:50 systemd[1]: Failed to start The PHP 7.3 FastCGI Process Manager.
déc. 03 20:14:51 systemd[1]: php7.3-fpm.service: Scheduled restart job, restart counter is at 4.
déc. 03 20:14:51 systemd[1]: Stopped The PHP 7.3 FastCGI Process Manager.
dĂ©c. 03 20:14:51 systemd[1]: Starting The PHP 7.3 FastCGI Process ManagerâŠ
dĂ©c. 03 20:14:51 php-fpm7.3[608757]: [03-Dec-2024 20:14:51] ERROR: [pool dokuwiki__2] the chdir path â/var/www/dokuwiki__2â does not exist or is not a directory
déc. 03 20:14:51 php-fpm7.3[608757]: [03-Dec-2024 20:14:51] ERROR: failed to post process the configuration
déc. 03 20:14:51 php-fpm7.3[608757]: [03-Dec-2024 20:14:51] ERROR: FPM initialization failed
déc. 03 20:14:51 systemd[1]: php7.3-fpm.service: Main process exited, code=exited, status=78/CONFIG
dĂ©c. 03 20:14:51 systemd[1]: php7.3-fpm.service: Failed with result âexit-codeâ.
déc. 03 20:14:51 systemd[1]: Failed to start The PHP 7.3 FastCGI Process Manager.
déc. 03 20:14:51 systemd[1]: php7.3-fpm.service: Scheduled restart job, restart counter is at 5.
déc. 03 20:14:51 systemd[1]: Stopped The PHP 7.3 FastCGI Process Manager.
déc. 03 20:14:51 systemd[1]: php7.3-fpm.service: Start request repeated too quickly.
dĂ©c. 03 20:14:51 systemd[1]: php7.3-fpm.service: Failed with result âexit-codeâ.
déc. 03 20:14:51 systemd[1]: Failed to start The PHP 7.3 FastCGI Process Manager.
dĂ©c. 03 20:14:55 systemd[1]: Starting The PHP 7.3 FastCGI Process ManagerâŠ
dĂ©c. 03 20:14:55 php-fpm7.3[610087]: [03-Dec-2024 20:14:55] ERROR: [pool dokuwiki__2] the chdir path â/var/www/dokuwiki__2â does not exist or is not a directory
déc. 03 20:14:55 php-fpm7.3[610087]: [03-Dec-2024 20:14:55] ERROR: failed to post process the configuration
déc. 03 20:14:55 php-fpm7.3[610087]: [03-Dec-2024 20:14:55] ERROR: FPM initialization failed
déc. 03 20:14:55 systemd[1]: php7.3-fpm.service: Main process exited, code=exited, status=78/CONFIG
dĂ©c. 03 20:14:55 systemd[1]: php7.3-fpm.service: Failed with result âexit-codeâ.
déc. 03 20:14:55 systemd[1]: Failed to start The PHP 7.3 FastCGI Process Manager.
déc. 03 20:14:55 systemd[1]: php7.3-fpm.service: Scheduled restart job, restart counter is at 1.
déc. 03 20:14:55 systemd[1]: Stopped The PHP 7.3 FastCGI Process Manager.
dĂ©c. 03 20:14:55 systemd[1]: Starting The PHP 7.3 FastCGI Process ManagerâŠ
dĂ©c. 03 20:14:55 php-fpm7.3[610092]: [03-Dec-2024 20:14:55] ERROR: [pool dokuwiki__2] the chdir path â/var/www/dokuwiki__2â does not exist or is not a directory
déc. 03 20:14:55 php-fpm7.3[610092]: [03-Dec-2024 20:14:55] ERROR: failed to post process the configuration
déc. 03 20:14:55 php-fpm7.3[610092]: [03-Dec-2024 20:14:55] ERROR: FPM initialization failed
déc. 03 20:14:55 systemd[1]: php7.3-fpm.service: Main process exited, code=exited, status=78/CONFIG
dĂ©c. 03 20:14:55 systemd[1]: php7.3-fpm.service: Failed with result âexit-codeâ.
déc. 03 20:14:55 systemd[1]: Failed to start The PHP 7.3 FastCGI Process Manager.
déc. 03 20:14:55 systemd[1]: php7.3-fpm.service: Scheduled restart job, restart counter is at 2.
déc. 03 20:14:55 systemd[1]: Stopped The PHP 7.3 FastCGI Process Manager.
dĂ©c. 03 20:14:55 systemd[1]: Starting The PHP 7.3 FastCGI Process ManagerâŠ
dĂ©c. 03 20:14:55 php-fpm7.3[610101]: [03-Dec-2024 20:14:55] ERROR: [pool dokuwiki__2] the chdir path â/var/www/dokuwiki__2â does not exist or is not a directory
déc. 03 20:14:55 php-fpm7.3[610101]: [03-Dec-2024 20:14:55] ERROR: failed to post process the configuration
déc. 03 20:14:55 php-fpm7.3[610101]: [03-Dec-2024 20:14:55] ERROR: FPM initialization failed
déc. 03 20:14:55 systemd[1]: php7.3-fpm.service: Main process exited, code=exited, status=78/CONFIG
dĂ©c. 03 20:14:55 systemd[1]: php7.3-fpm.service: Failed with result âexit-codeâ.
déc. 03 20:14:55 systemd[1]: Failed to start The PHP 7.3 FastCGI Process Manager.
déc. 03 20:14:55 systemd[1]: php7.3-fpm.service: Scheduled restart job, restart counter is at 3.
déc. 03 20:14:55 systemd[1]: Stopped The PHP 7.3 FastCGI Process Manager.
dĂ©c. 03 20:14:55 systemd[1]: Starting The PHP 7.3 FastCGI Process ManagerâŠ
dĂ©c. 03 20:14:55 php-fpm7.3[610104]: [03-Dec-2024 20:14:55] ERROR: [pool dokuwiki__2] the chdir path â/var/www/dokuwiki__2â does not exist or is not a directory
déc. 03 20:14:55 php-fpm7.3[610104]: [03-Dec-2024 20:14:55] ERROR: failed to post process the configuration
déc. 03 20:14:55 php-fpm7.3[610104]: [03-Dec-2024 20:14:55] ERROR: FPM initialization failed
déc. 03 20:14:55 systemd[1]: php7.3-fpm.service: Main process exited, code=exited, status=78/CONFIG
dĂ©c. 03 20:14:55 systemd[1]: php7.3-fpm.service: Failed with result âexit-codeâ.
déc. 03 20:14:55 systemd[1]: Failed to start The PHP 7.3 FastCGI Process Manager.
déc. 03 20:14:56 systemd[1]: php7.3-fpm.service: Scheduled restart job, restart counter is at 4.
déc. 03 20:14:56 systemd[1]: Stopped The PHP 7.3 FastCGI Process Manager.
dĂ©c. 03 20:14:56 systemd[1]: Starting The PHP 7.3 FastCGI Process ManagerâŠ
dĂ©c. 03 20:14:56 php-fpm7.3[610108]: [03-Dec-2024 20:14:56] ERROR: [pool dokuwiki__2] the chdir path â/var/www/dokuwiki__2â does not exist or is not a directory
déc. 03 20:14:56 php-fpm7.3[610108]: [03-Dec-2024 20:14:56] ERROR: failed to post process the configuration
déc. 03 20:14:56 php-fpm7.3[610108]: [03-Dec-2024 20:14:56] ERROR: FPM initialization failed
déc. 03 20:14:56 systemd[1]: php7.3-fpm.service: Main process exited, code=exited, status=78/CONFIG
dĂ©c. 03 20:14:56 systemd[1]: php7.3-fpm.service: Failed with result âexit-codeâ.
déc. 03 20:14:56 systemd[1]: Failed to start The PHP 7.3 FastCGI Process Manager.
déc. 03 20:14:56 systemd[1]: php7.3-fpm.service: Scheduled restart job, restart counter is at 5.
déc. 03 20:14:56 systemd[1]: Stopped The PHP 7.3 FastCGI Process Manager.
déc. 03 20:14:56 systemd[1]: php7.3-fpm.service: Start request repeated too quickly.
dĂ©c. 03 20:14:56 systemd[1]: php7.3-fpm.service: Failed with result âexit-codeâ.
déc. 03 20:14:56 systemd[1]: Failed to start The PHP 7.3 FastCGI Process Manager.
Je suis assez curieux de savoir ou il va chercher cette reference a Dokuwiki, qui a été désinstallé il y a bien 2 ans de mon serveur
Bon jâai trouvĂ© la source de mon erreur.
dans /etc/php/7.3/fpm/pool.d jâavais des references a des anciennes applications .
Jâai renommĂ© les fichiers .conf qui posaient un souci et relancĂ© la mise Ă jour.
La migration de php7.3-fpm est passé.
Wait and see
Merci pour lâaiguillage @Aleks
Edit : le reste de la migration câest dĂ©roulĂ© sans souci
Bonjour, de mon cĂŽtĂ©, pour effectuer la migration, il a fallu que je dĂ©sistalle wireguard_client qui empĂȘchait de poursuivre le process.
A la fin de la migration qui sâest bien passĂ©, le dnsmasq a plantĂ© (ça arrivait souvent dâailleurs ces derniers temps), et cette fois-ci, impossible de le redĂ©marrer. Voici le lien YunoPaste :
https://paste.yunohost.org/hojuhusane
En gros, il nâarrive pas Ă mettre en place une socket dâĂ©coute pour 10.10.10.0
.
Jâaimerais rĂ©initialiser complĂštement dnsmasq Ă son Ă©tat dâorigine car je ne compte plus utiliser wireguard_client de toute façon pour le moment, câĂ©tait peut-ĂȘtre ça qui faisait planter mon dnsmasq.
Il y a une commande il me semble le faire (un truc comme regen-conf
?) mais je ne mâen souviens plus du tout, est-ce que vous pourriez mâaider svp ? Merci
Informations complémentaires :
Contenu de /etc/dnsmasq.conf
:
domain-needed
expand-hosts
localise-queries
interface=lo
resolv-file=/etc/resolv.dnsmasq.conf
cache-size=256
Contenu de /etc/resolv.dnsmasq.conf
: beaucoup dâadresses IPv4 et IPv6 sous la forme dâune liste nameserver ADRESSE_IP
mais rien ne contenant 10.10.10.0
Bon, jâai utilisĂ© chatGPT et voici une solution que jâespĂšre pĂ©renne :
En root, jâai procĂ©dĂ© Ă un yunohost tools regen-conf dnsmasq --force
.
Ensuite, le problĂšme dâadresse persistait donc jâai cherchĂ© cette adresse dns /etc
avec grep -rnw '/etc/' -e '10.10.10.0'
, jâai obtenu 2 rĂ©sultats dont /etc/dnsmasq.d/vpn:2:listen-address=10.10.10.0
.
Enfin, jâai donc lancĂ© nano /etc/dnsmasq.d/vpn
et commenté listen 10.10.10.0
, puis jâai lancĂ© un systemctl restart dnsmasq
et confirmé que le systÚme fonctionnait avec systemctl status dnsmasq
.
Jâai eu un second problĂšme avec lâapplication LSTU, qui malheureusement, nâa pas la petite Ă©toile (application officiellement supportĂ©e). Jâai donc dĂ©sinstallĂ© et jâutilise YOURLS avec son inerface un peu datĂ© mais au moins supportĂ© par Yunohost.