Hi everyone
I wanted to upgrade Nextcloud but since it doesn’t support 32bit (for now) the upgrade doesn’t work
I just want to upgrade the app to the old version I was using (20.0.7)
It’s seems pretty simple but I couldn’t find the write syntax for
sudo yunohost app upgrade nextcloud -v 20.0.7
?
And how to look for the proper syntax like in this case ?
(So that I can do it by myself next time)
You would need to upgrade to a special branch (yunohost app upgrade nextcloud -u https//github.com/TheBranchURL) that contains this version.
Unfortunately it’s not possible, and such a branch no longer exist.
Someone would have to recreate it, based on the state of the app when it was using Nextcloud 24.
I’s relatively “easy” if you are used to github, you need to check the last Nextcloud 24 version in the repository and revert to/copy that commit repository state in a new branch/fork. Or rather take the current state, fork it, and revent the “Nextcloud 25” commit (if you do it manually : the have to change the source URL, sha256sum, and php version back to 7.4 I think).
Maybe someone with write rights on the Nextcloud_ynh repository can do it ? 
PS : for clarity, could you rewrite the topic title in something more explicit, such as “Choose Nextcloud version during upgrad” ? Thanks ! 
Hello,
I am confused.
The package should prevent upgrades to incompatible versions.
If “the upgrade doesn’t work”, then the old version should have been restored.
Can you clarify this, and what is your current app version?
App downgrading is not supported on YunoHost. Even more so with such an old version.
Deleting then restoring backups is the way to go.
yunohost app install --help
yunohost app upgrade --help
In there:
yunohost app upgrade --help
usage: yunohost app upgrade [app ...] [-h] [-u URL] [-f FILE] [-F] [-b]
Upgrade app
positional arguments:
app App(s) to upgrade (default all)
optional arguments:
-h, --help show this help message and exit
-u URL, --url URL Git url to fetch for upgrade
-f FILE, --file FILE Folder or tarball for upgrade
-F, --force Force the update, even though the app is up to date
-b, --no-safety-backup
Disable the safety backup during upgrade
If you want to install or upgrade to a specific version of a Nextcloud, then the commands would be:
yunohost app install $URL
yunohost app upgrade nextcloud -u $URL
where
URL=https://github.com/YunoHost-Apps/nextcloud_ynh if you want to use the latest version or
URL=https://github.com/YunoHost-Apps/nextcloud_ynh/tree/testing to use the testing branch.
@Lapineige is slightly wrong (sorry 
), since any Github repo url is valid. So you can directly put a commit instead of the branch name. You can browse Commits · YunoHost-Apps/nextcloud_ynh · GitHub to find out your commit:
URL=https://github.com/YunoHost-Apps/nextcloud_ynh/tree/fc3f68340414be4a7f3d9ff81affa93bc236602d for v23.0.0.
That’s tricky here : the package will upgrade.
But then some part of the app fill eventually fails (there is a bug with 32 bits versions that as to be resolved upstream, not on Yunohost side).
We disabled by error the upgrade to Nextcloud 25 for 32 bits system because in the confusion we thought 32 bits was no longer supported. It still is, at least for Nextcloud 25.
And the bug is not fully solved in the lastest version (in testing branch) so it wasn’t merged yet.
Oh I didn’t understand it was a downgrade, and not an upgrade to Nextcloud 24 from 20.
That’s great !
Thanks
I tried with
sudo yunohost app upgrade nextcloud -u GitHub - YunoHost-Apps/nextcloud_ynh at fc3f68340414be4a7f3d9ff81affa93bc236602d
but it I had
Warning: E: Packages need to be removed but remove is disabled.
Warning: The following packages have unmet dependencies:
Warning: php7.3-apcu : Breaks: php-apcu (< 5.1.22+4.0.11-2+0~20221209.34+debian11~1.gbp2b07cb~)
Warning: php7.3-igbinary : Breaks: php-igbinary (< 3.2.12+2.0.8-2+0~20221210.36+debian11~1.gbp293257~)
Warning: php7.3-imagick : Breaks: php-imagick (< 3.7.0-3+0~20221209.38+debian11~1.gbp8a8977~)
Warning: php7.3-redis : Breaks: php-redis (< 5.3.7+4.3.0-2+0~20221210.45+debian11~1.gbp99917f~)
Warning: php7.4-bcmath : Depends: php7.4-common (= 7.4.33-1+deb11u1) but 1:7.4.33-2+0~20230107.75+debian11~1.gbp33ea31 is to be installed
Warning: php7.4-bz2 : Depends: php7.4-common (= 7.4.33-1+deb11u1) but 1:7.4.33-2+0~20230107.75+debian11~1.gbp33ea31 is to be installed
Warning: php7.4-gmp : Depends: php7.4-common (= 7.4.33-1+deb11u1) but 1:7.4.33-2+0~20230107.75+debian11~1.gbp33ea31 is to be installed
Warning: php7.4-imap : Depends: php7.4-common (= 7.4.33-1+deb11u1) but 1:7.4.33-2+0~20230107.75+debian11~1.gbp33ea31 is to be installed
Warning: php7.4-zip : Depends: php7.4-common (= 7.4.33-1+deb11u1) but 1:7.4.33-2+0~20230107.75+debian11~1.gbp33ea31 is to be installed
Warning: Unable to install dependencies
As suggested I
sudo apt install --fix-broken
Reading package lists… Done
Building dependency tree… Done
Reading state information… Done
0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Setting up php7.3-fpm (7.3.33-9+0~20230106.102+debian11~1.gbpc4e85f) …
insserv: warning: current start runlevel(s) (empty) of scriptphp7.3-fpm' overrides LSB defaults (2 3 4 5). insserv: warning: current stop runlevel(s) (0 1 2 3 4 5 6) of scriptphp7.3-fpm’ overrides LSB defaults (0 1 6).
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: failed (Result: exit-code) since Thu 2023-01-19 11:47:36 GMT; 34ms ago
Docs: man:php-fpm7.3(8)
Process: 23329 ExecStart=/usr/sbin/php-fpm7.3 --nodaemonize --fpm-config /etc/php/7.3/fpm/php-fpm.conf (code=exited, status=78)
Process: 23330 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: 23329 (code=exited, status=78)
CPU: 139ms
Jan 19 11:47:35 ludivine.nohost.me systemd[1]: Starting The PHP 7.3 FastCGI Process Manager…
Jan 19 11:47:36 ludivine.nohost.me php-fpm7.3[23329]: [19-Jan-2023 11:47:36] ERROR: [pool nextcloud] the chdir path ‘/var/www/nextcloud’ does not exist or is not a directory
Jan 19 11:47:36 ludivine.nohost.me php-fpm7.3[23329]: [19-Jan-2023 11:47:36] ERROR: failed to post process the configuration
Jan 19 11:47:36 ludivine.nohost.me php-fpm7.3[23329]: [19-Jan-2023 11:47:36] ERROR: FPM initialization failed
Jan 19 11:47:36 ludivine.nohost.me systemd[1]: php7.3-fpm.service: Main process exited, code=exited, status=78/CONFIG
Jan 19 11:47:36 ludivine.nohost.me systemd[1]: php7.3-fpm.service: Failed with result ‘exit-code’.
Jan 19 11:47:36 ludivine.nohost.me systemd[1]: Failed to start The PHP 7.3 FastCGI Process Manager.
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
E: Sub-process /usr/bin/dpkg returned an error code (1)
admin@ludivine:~ $ sudo dpkg --configure -a
Setting up php7.3-fpm (7.3.33-9+0~20230106.102+debian11~1.gbpc4e85f) …
insserv: warning: current start runlevel(s) (empty) of scriptphp7.3-fpm' overrides LSB defaults (2 3 4 5). insserv: warning: current stop runlevel(s) (0 1 2 3 4 5 6) of scriptphp7.3-fpm’ overrides LSB defaults (0 1 6).
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: failed (Result: exit-code) since Thu 2023-01-19 11:48:31 GMT; 35ms ago
Docs: man:php-fpm7.3(8)
Process: 24430 ExecStart=/usr/sbin/php-fpm7.3 --nodaemonize --fpm-config /etc/php/7.3/fpm/php-fpm.conf (code=exited, status=78)
Process: 24431 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: 24430 (code=exited, status=78)
CPU: 139ms
Jan 19 11:48:31 ludivine.nohost.me systemd[1]: Starting The PHP 7.3 FastCGI Process Manager…
Jan 19 11:48:31 ludivine.nohost.me php-fpm7.3[24430]: [19-Jan-2023 11:48:31] ERROR: [pool nextcloud] the chdir path ‘/var/www/nextcloud’ does not exist or is not a directory
Jan 19 11:48:31 ludivine.nohost.me php-fpm7.3[24430]: [19-Jan-2023 11:48:31] ERROR: failed to post process the configuration
Jan 19 11:48:31 ludivine.nohost.me php-fpm7.3[24430]: [19-Jan-2023 11:48:31] ERROR: FPM initialization failed
Jan 19 11:48:31 ludivine.nohost.me systemd[1]: php7.3-fpm.service: Main process exited, code=exited, status=78/CONFIG
Jan 19 11:48:31 ludivine.nohost.me systemd[1]: php7.3-fpm.service: Failed with result ‘exit-code’.
Jan 19 11:48:31 ludivine.nohost.me systemd[1]: Failed to start The PHP 7.3 FastCGI Process Manager.
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
After that I couldn’t see yunohost in my apps so I tried to restore the app (like @tituspijean suggest) with the back up than I had this
It seems to have an issues with php … But php service is running
systemctl status php7.4-fpm
● php7.4-fpm.service - The PHP 7.4 FastCGI Process Manager
Loaded: loaded (/lib/systemd/system/php7.4-fpm.service; enabled; vendor preset: enabled)
Active: active (running) since Mon 2023-01-16 21:14:44 GMT; 2 days ago
Docs: man:php-fpm7.4(8)
Process: 29316 ExecReload=/bin/kill -USR2 $MAINPID (code=exited, status=0/SUCCESS)
Main PID: 22484
Status: “Processes active: 0, idle: 2, Requests: 0, slow: 0, Traffic: 0req/sec”
Tasks: 3 (limit: 2058)
CPU: 2min 14.449s
CGroup: /system.slice/php7.4-fpm.service
├─22484 php-fpm: master process (/etc/php/7.4/fpm/php-fpm.conf)
├─29418 php-fpm: pool www
└─29420 php-fpm: pool www
Is this because the app is searching php7.3-fpm and I have php 7.4-fpm ?
These were not optional questions, assessing the situation is important before jumping into the CLI.
2023-01-19 12:19:29,809: DEBUG - Jan 19 12:19:28 maindomain.tld php-fpm7.3[27259]: [19-Jan-2023 12:19:28] ERROR: Another FPM instance seems to already listen on /var/run/php/php7.4-fpm-rss-bridge.sock
So, PHP7.3-FPM complains about RSS-Bridge app’s PHP7.4 socket? Looks like a bad cleanup from that app.
After answering to the first questions above, share the outputs of:
ls -la /etc/php/7.3/fpm/pool.d
ls -la /etc/php/7.4/fpm/pool.d
I’m sorry, it was the 20.0.7 and I wanted to find an earlier version that supported 32bit architecture
Ohh I didn’t saw the error with rss bridge
ls -la /etc/php/7.3/fpm/pool.d
total 40
drwxr-xr-x 2 root root 4096 Jan 13 14:26 .
drwxr-xr-x 4 root root 4096 Jan 11 21:30 …
-rw-r----- 1 my_webapp my_webapp 296 Jan 13 12:33 my_webapp.conf
-rw-r----- 1 root root 1051 Dec 30 2021 nextcloud.conf
-rw-r----- 1 rss-bridge rss-bridge 301 Jan 13 14:26 rss-bridge.conf
-rw-r–r-- 1 root root 19703 May 15 2020 www.conf
admin@ludivine:~ $ ls -la /etc/php/7.4/fpm/pool.d
total 36
drwxr-xr-x 2 root root 4096 Jan 19 11:09 .
drwxr-xr-x 4 root root 4096 Jan 13 10:48 …
-rw-r----- 1 root root 377 Jan 16 21:14 my_webapp.conf
-rw-r----- 1 root root 382 Jan 16 21:14 rss-bridge.conf
-rw-r–r-- 1 root root 19683 Jan 7 08:34 www.conf
Mmmh the app is supposed to use PHP7.3. Weird.
Let’s check: sudo yunohost app setting rss-bridge phpversion
It’s the 7.4 version
Then let’s clean it up and try again:
sudo systemctl stop php7.3-fpm
sudo rm /etc/php/7.3/fpm/pool.d/rss-bridge.conf
sudo systemctl start php7.3-fpm
then restore the app. 
admin@ludivine:~ $ sudo systemctl stop php7.3-fpm
admin@ludivine:~ $ sudo rm /etc/php/7.3/fpm/pool.d/rss-bridge.conf
admin@ludivine:~ $ sudo systemctl start php7.3-fpm
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.
systemctl status php7.3-fpm.service
● 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: failed (Result: exit-code) since Thu 2023-01-19 16:18:28 GMT; 1min 7s ago
Docs: man:php-fpm7.3(8)
Process: 31978 ExecStart=/usr/sbin/php-fpm7.3 --nodaemonize --fpm-config /etc/php/7.3/fpm/php-fpm.conf (code=exited, status=78)
Process: 31979 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: 31978 (code=exited, status=78)
CPU: 139ms
admin@ludivine:~ $ journalctl -xe
Hint: You are currently not seeing messages from other users and the system.
Users in groups ‘adm’, ‘systemd-journal’ can see all messages.
Pass -q to turn off this notice.
Jan 19 11:47:17 ludivine.nohost.me sudo[22275]: admin : TTY=pts/0 ; PWD=/home/admin ; USER=root ; COMMAND=/usr/bin/apt install --fix-broken
Jan 19 11:47:17 ludivine.nohost.me sudo[22275]: pam_unix(sudo:session): session opened for user root(uid=0) by admin(uid=1007)
Jan 19 11:47:37 ludivine.nohost.me sudo[22275]: pam_unix(sudo:session): session closed for user root
Jan 19 11:48:23 ludivine.nohost.me sudo[23392]: admin : TTY=pts/0 ; PWD=/home/admin ; USER=root ; COMMAND=/usr/bin/dpkg --configure -a
Jan 19 11:48:23 ludivine.nohost.me sudo[23392]: pam_unix(sudo:session): session opened for user root(uid=0) by admin(uid=1007)
Jan 19 11:48:31 ludivine.nohost.me sudo[23392]: pam_unix(sudo:session): session closed for user root
Jan 19 11:49:46 ludivine.nohost.me polkit-agent-helper-1[24456]: pam_unix(polkit-1:auth): authentication failure; logname= uid=1007 euid=0 tty= ruser=le_roi rhost= user=le_roi
Jan 19 12:34:58 ludivine.nohost.me sudo[29979]: admin : TTY=pts/0 ; PWD=/home/admin ; USER=root ; COMMAND=/usr/bin/apt-get clean
Jan 19 12:34:58 ludivine.nohost.me sudo[29979]: pam_unix(sudo:session): session opened for user root(uid=0) by admin(uid=1007)
Jan 19 12:34:58 ludivine.nohost.me sudo[29979]: pam_unix(sudo:session): session closed for user root
Jan 19 12:35:20 ludivine.nohost.me sudo[29991]: admin : TTY=pts/0 ; PWD=/home/admin ; USER=root ; COMMAND=/usr/bin/apt-get update --fix-missing
Jan 19 12:35:20 ludivine.nohost.me sudo[29991]: pam_unix(sudo:session): session opened for user root(uid=0) by admin(uid=1007)
Jan 19 12:35:27 ludivine.nohost.me sudo[29991]: pam_unix(sudo:session): session closed for user root
Jan 19 16:15:01 ludivine.nohost.me sudo[31938]: admin : TTY=pts/0 ; PWD=/home/admin ; USER=root ; COMMAND=/usr/bin/yunohost app setting rss-bridge phpversion
Jan 19 16:15:01 ludivine.nohost.me sudo[31938]: pam_unix(sudo:session): session opened for user root(uid=0) by admin(uid=1007)
Jan 19 16:15:02 ludivine.nohost.me sudo[31938]: pam_unix(sudo:session): session closed for user root
Jan 19 16:18:10 ludivine.nohost.me sudo[31969]: admin : TTY=pts/0 ; PWD=/home/admin ; USER=root ; COMMAND=/bin/systemctl stop php7.3-fpm
Jan 19 16:18:10 ludivine.nohost.me sudo[31969]: pam_unix(sudo:session): session opened for user root(uid=0) by admin(uid=1007)
Jan 19 16:18:10 ludivine.nohost.me sudo[31969]: pam_unix(sudo:session): session closed for user root
Jan 19 16:18:21 ludivine.nohost.me sudo[31973]: admin : TTY=pts/0 ; PWD=/home/admin ; USER=root ; COMMAND=/bin/rm /etc/php/7.3/fpm/pool.d/rss-bridge.conf
Jan 19 16:18:21 ludivine.nohost.me sudo[31973]: pam_unix(sudo:session): session opened for user root(uid=0) by admin(uid=1007)
Jan 19 16:18:21 ludivine.nohost.me sudo[31973]: pam_unix(sudo:session): session closed for user root
Jan 19 16:18:28 ludivine.nohost.me sudo[31975]: admin : TTY=pts/0 ; PWD=/home/admin ; USER=root ; COMMAND=/bin/systemctl start php7.3-fpm
Jan 19 16:18:28 ludivine.nohost.me sudo[31975]: pam_unix(sudo:session): session opened for user root(uid=0) by admin(uid=1007)
Jan 19 16:18:28 ludivine.nohost.me sudo[31975]: pam_unix(sudo:session): session closed for user root
Use sudo 
Ohh yes 
░░ The process’ exit code is ‘exited’ and its exit status is 78.
Jan 19 16:18:28 ludivine.nohost.me systemd[1]: php7.3-fpm.service: Failed with result ‘exit-code’.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: Debian -- User Support
░░
░░ The unit php7.3-fpm.service has entered the ‘failed’ state with result ‘exit-code’.
Jan 19 16:18:28 ludivine.nohost.me systemd[1]: Failed to start The PHP 7.3 FastCGI Process Manager.
░░ Subject: A start job for unit php7.3-fpm.service has failed
░░ Defined-By: systemd
░░ Support: Debian -- User Support
░░
░░ A start job for unit php7.3-fpm.service has finished with a failure.
░░
░░ The job identifier is 24934 and the job result is failed.
Jan 19 16:18:28 ludivine.nohost.me sudo[31975]: pam_unix(sudo:session): session closed for user root
Jan 19 16:20:01 ludivine.nohost.me CRON[31993]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Jan 19 16:20:01 ludivine.nohost.me CRON[31994]: (root) CMD (: YunoHost DynDNS update; sleep $((RANDOM%60)); ! ping -q -W5 -c1 ip.yunohost.org >/dev/null 2>&1 || test -e /var/run/moulinette_yunohost.lock || yunoh>
Jan 19 16:20:05 ludivine.nohost.me CRON[31993]: pam_unix(cron:session): session closed for user root
Jan 19 16:22:08 ludivine.nohost.me writefreely[22081]: 2023/01/19 16:22:08 “GET /robots.txt” 200 907.287µs “Mozilla/5.0 (X11; Linux x86_64; rv:108.0) Gecko/20100101 Firefox/108.0”
Jan 19 16:22:08 ludivine.nohost.me writefreely[22081]: 2023/01/19 16:22:08 “GET /adalesia/” 200 46.262262ms “Mozilla/5.0 (X11; Linux x86_64; rv:108.0) Gecko/20100101 Firefox/108.0”
Jan 19 16:23:23 ludivine.nohost.me slapd[1111]: slap_global_control: unrecognized control: 1.3.6.1.4.1.4203.666.5.16
Jan 19 16:23:23 ludivine.nohost.me slapd[1111]: slap_global_control: unrecognized control: 1.3.6.1.4.1.4203.666.5.16
Jan 19 16:23:23 ludivine.nohost.me sudo[32014]: admin : TTY=pts/0 ; PWD=/home/admin ; USER=root ; COMMAND=/bin/journalctl -xe
Jan 19 16:23:23 ludivine.nohost.me sudo[32014]: pam_unix(sudo:session): session opened for user root(uid=0) by admin(uid=1007)
I just saw I can upgrade sudo-ldap maybe it can help.
So I tried to install it but got an 400 error and suggest me to
sudo apt install --fix-broken
et/ousudo dpkg --configure -a’
So I made it but I still had an error with php7.3
The error is weirdly not displayed here. Try triggering the error again and share sudo tail -n 30 /var/log/php7.3-fpm.log
It respond :
[16-Jan-2023 21:14:38] NOTICE: Terminating …
[16-Jan-2023 21:14:38] NOTICE: exiting, bye-bye!
[19-Jan-2023 11:08:54] ERROR: Another FPM instance seems to already listen on /var/run/php/php7.4-fpm-rss-bridge.sock
[19-Jan-2023 11:08:54] ERROR: FPM initialization failed
[19-Jan-2023 11:23:57] ERROR: Another FPM instance seems to already listen on /var/run/php/php7.4-fpm-rss-bridge.sock
[19-Jan-2023 11:23:57] ERROR: FPM initialization failed
[19-Jan-2023 11:24:21] ERROR: Another FPM instance seems to already listen on /var/run/php/php7.4-fpm-rss-bridge.sock
[19-Jan-2023 11:24:21] ERROR: FPM initialization failed
[19-Jan-2023 11:47:36] ERROR: [pool nextcloud] the chdir path ‘/var/www/nextcloud’ does not exist or is not a directory
[19-Jan-2023 11:47:36] ERROR: failed to post process the configuration
[19-Jan-2023 11:47:36] ERROR: FPM initialization failed
[19-Jan-2023 11:48:31] ERROR: [pool nextcloud] the chdir path ‘/var/www/nextcloud’ does not exist or is not a directory
[19-Jan-2023 11:48:31] ERROR: failed to post process the configuration
[19-Jan-2023 11:48:31] ERROR: FPM initialization failed
[19-Jan-2023 11:49:46] ERROR: [pool nextcloud] the chdir path ‘/var/www/nextcloud’ does not exist or is not a directory
[19-Jan-2023 11:49:46] ERROR: failed to post process the configuration
[19-Jan-2023 11:49:46] ERROR: FPM initialization failed
[19-Jan-2023 12:19:28] ERROR: Another FPM instance seems to already listen on /var/run/php/php7.4-fpm-rss-bridge.sock
[19-Jan-2023 12:19:28] ERROR: FPM initialization failed
[19-Jan-2023 12:19:56] ERROR: Another FPM instance seems to already listen on /var/run/php/php7.4-fpm-rss-bridge.sock
[19-Jan-2023 12:19:56] ERROR: FPM initialization failed
[19-Jan-2023 16:18:28] ERROR: [pool nextcloud] the chdir path ‘/var/www/nextcloud’ does not exist or is not a directory
[19-Jan-2023 16:18:28] ERROR: failed to post process the configuration
[19-Jan-2023 16:18:28] ERROR: FPM initialization failed
[19-Jan-2023 16:27:04] ERROR: [pool nextcloud] the chdir path ‘/var/www/nextcloud’ does not exist or is not a directory
[19-Jan-2023 16:27:04] ERROR: failed to post process the configuration
[19-Jan-2023 16:27:04] ERROR: FPM initialization failed
[19-Jan-2023 16:27:30] ERROR: [pool nextcloud] the chdir path ‘/var/www/nextcloud’ does not exist or is not a directory
[19-Jan-2023 16:27:30] ERROR: failed to post process the configuration
[19-Jan-2023 16:27:30] ERROR: FPM initialization failed
Ah yes indeed, there is a leftover file.
sudo rm /etc/php/7.3/fpm/pool.d/nextcloud.conf
then restore again
There is this PR that adresses upgrade from old Nextcloud to version 25
And we need testing for merge!
I’m sorry but I don’t understand
Nextcloud isn’t install anymore and I need to back up the data
I looked at the link again and from what I understand the person had a problem with the version of php when upgrading so he made a commit version with the possibility to use 7.4 version when someone upgrade
But when I was trying to upgrade to this the nextcloud app was deleted
So now I’m trying to back up the app when it was running (before the migration 21-24 if I remember well) but I had an error with it
Maybe there is something I don’t understand but i try to learn to use git and yunohost