Hardware: Kimsufi KS-3 YunoHost version: 4.3.6.2 I have access to my server : yes Are you in a special context or did you perform some particular tweaking on your YunoHost instance ? : no
Description of my issue
Hello !
I wanted to update mu Peertube, and an error occurred. Since then, my instance totally vanished…
I tried to restore the backup but :
“Cette sauvegarde ne peut pas être restaurée car elle provient d’une version YunoHost trop ancienne.”
“This backup cannot be restored because it is from an older YunoHost version.”
XXXX@xxxx:~$ sudo apt install --fix-broken
Reading package lists… Done
Building dependency tree
Reading state information… Done
0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
et
XXXX@xxxx:~$ sudo dpkg --configure -a
XXXX@xxxx:~$
Ainsi que
XXXX@xxxx:~$ sudo yunohost backup restore peertube-pre-upgrade2 --apps peertube --force --debug
469 DEBUG initializing base actions map parser for cli
475 DEBUG loading actions map namespace ‘yunohost’
482 DEBUG building parser…
502 DEBUG building parser took 0.020s
507 DEBUG acquiring lock…
551 DEBUG lock has been acquired
627 DEBUG loading python module yunohost.backup took 0.075s
627 DEBUG processing action [13865.1]: yunohost.backup.restore with args={‘name’: ‘peertube-pre-upgrade2’, ‘system’: None, ‘apps’: [‘peertube’], ‘force’: True}
629 DEBUG action [13865.1] executed in 0.001s
630 DEBUG lock has been released
630 ERROR This backup archive can not be restored because it comes from a too-old YunoHost version.
J’ai vérifié en SSH, tous les fichiers et répertoires sont bien présents.
J’ai un autre serveur avec une autre instance Peertube (surequel je n’ai eu aucun problème) et qui est chez Hetzner.
Je vois que l’app Prosody s’est installée.
Donc je l’installe sur le serveur KS. Puis je relance une install de Peertube (vu qu’il n’apparait plus dans mes app).
Cela a installé une instance vierge. Mais, quand je vais voir sur le serveur en SSH, les vidéos de l’ancienne instance sont toujours dans le dossier vidéos.
Existe-t-il un moyen de recréer le lien entre ces vidéos et la nouvelle instance ? Si non, je supprime ces vidéos via SSH ?
I am in the same boat, but only half. I had two Yunohosts with Peertube.
I think they got updated about two weeks ago. One still has Peertube, while the other has the same problem:
Peertube removed
unable to restore backup
unable to reinstall
On both servers @JohnLivingston’s Prosody-live-chat was installed (alongside Metronome). I noticed, on the broken server, that Prosody was listed as installed Yuno-app.
I removed it (Prosody) there and still was not able to reinstall Peertube. I just tried again now, it seems stuck on the old /home/yunohost.app/peertube/storage-directory: the installation is not able to change ownership of the files:
Warning: chown: changing ownership of '/home/yunohost.app/peertube/storage/videos/22eee980-5404-4980-a4d1-bad8e4a4aa4d-480.mp4': Permission denied
I recalled not storing the videos locally (it’s a small VPS), they are mounted over SSHFS:
That would explain the permissions problem. I umount /home/yunohost.app/peertube/storage/videos, and tried again while the old peertube-directory still existed. That also did not work.
I renamed the directory, sudo mv /home/yunohost.app/peertube/ /home/yunohost.app/peertube.bak, and this time tried restoring the backup, yunohost backup restore peertube-pre-upgrade1 --apps, and then… Success! Restoration completed
So far, so good. BUT: after remounting …storage/videos, the video’s are not available in Peertube. The meta-data is (the video’s are listed as local videos, but nothing can be played)
So, in short:
In case you altered the installation in any way (such as my SSHFS), undo it or make sure it is not in the way
Check existence of any /home/yunohost.app/peertube directory; move/rename if exists (don’t throw it away if your video’s are there)
N’étant pas utilisateur de Yunohost, je n’ai pas pu tester ce qui a été fait. Normalement, Prosody est en conflit avec le serveur XMPP Metronome, qui est utilisé par défaut par Yunohost. Peut être que c’est ça qui fait planter l’installation…
Bon je suis toujours dans l’impasse…je désinstalle je réeinstall mais rien le service ne démarre pas
> -- Logs begin at Tue 2022-03-22 08:32:01 UTC, end at Mon 2022-03-28 08:03:57 UTC. --
> mars 23 14:14:59 systemd[1]: peertube.service: Main process exited, code=exited, status=203/EXEC
> mars 23 14:14:59 systemd[1]: peertube.service: Failed with result 'exit-code'.
> mars 23 14:15:00 systemd[1]: peertube.service: Service RestartSec=100ms expired, scheduling restart.
> mars 23 14:15:00 systemd[1]: peertube.service: Scheduled restart job, restart counter is at 4.
> mars 23 14:15:00 systemd[1]: Stopped PeerTube daemon.
> mars 23 14:15:00 systemd[1]: Started PeerTube daemon.
> mars 23 14:15:00 systemd[1]: peertube.service: Main process exited, code=exited, status=203/EXEC
> mars 23 14:15:00 systemd[1]: peertube.service: Failed with result 'exit-code'.
> mars 23 14:15:00 systemd[1]: peertube.service: Service RestartSec=100ms expired, scheduling restart.
> mars 23 14:15:00 systemd[1]: peertube.service: Scheduled restart job, restart counter is at 5.
> mars 23 14:15:00 systemd[1]: Stopped PeerTube daemon.
> mars 23 14:15:00 systemd[1]: peertube.service: Start request repeated too quickly.
> mars 23 14:15:00 systemd[1]: peertube.service: Failed with result 'exit-code'.
> mars 23 14:15:00 systemd[1]: Failed to start PeerTube daemon.
> mars 28 07:53:02 systemd[1]: Started PeerTube daemon.
> mars 28 07:53:02 systemd[1]: peertube.service: Main process exited, code=exited, status=203/EXEC
> mars 28 07:53:02 systemd[1]: peertube.service: Failed with result 'exit-code'.
> mars 28 07:53:02 systemd[1]: peertube.service: Service RestartSec=100ms expired, scheduling restart.
> mars 28 07:53:02 systemd[1]: peertube.service: Scheduled restart job, restart counter is at 1.
> mars 28 07:53:02 systemd[1]: Stopped PeerTube daemon.
> mars 28 07:53:02 systemd[1]: Started PeerTube daemon.
> mars 28 07:53:02 systemd[1]: peertube.service: Main process exited, code=exited, status=203/EXEC
> mars 28 07:53:02 systemd[1]: peertube.service: Failed with result 'exit-code'.
> mars 28 07:53:02 systemd[1]: peertube.service: Service RestartSec=100ms expired, scheduling restart.
> mars 28 07:53:02 systemd[1]: peertube.service: Scheduled restart job, restart counter is at 2.
> mars 28 07:53:02 systemd[1]: Stopped PeerTube daemon.
> mars 28 07:53:02 systemd[1]: Started PeerTube daemon.
> mars 28 07:53:02 systemd[1]: peertube.service: Main process exited, code=exited, status=203/EXEC
> mars 28 07:53:02 systemd[1]: peertube.service: Failed with result 'exit-code'.
> mars 28 07:53:02 systemd[1]: peertube.service: Service RestartSec=100ms expired, scheduling restart.
> mars 28 07:53:02 systemd[1]: peertube.service: Scheduled restart job, restart counter is at 3.
> mars 28 07:53:02 systemd[1]: Stopped PeerTube daemon.
> mars 28 07:53:02 systemd[1]: Started PeerTube daemon.
> mars 28 07:53:02 systemd[1]: peertube.service: Main process exited, code=exited, status=203/EXEC
> mars 28 07:53:02 systemd[1]: peertube.service: Failed with result 'exit-code'.
> mars 28 07:53:03 systemd[1]: peertube.service: Service RestartSec=100ms expired, scheduling restart.
> mars 28 07:53:03 systemd[1]: peertube.service: Scheduled restart job, restart counter is at 4.
> mars 28 07:53:03 systemd[1]: Stopped PeerTube daemon.
> mars 28 07:53:03 systemd[1]: Started PeerTube daemon.
> mars 28 07:53:03 systemd[1]: peertube.service: Main process exited, code=exited, status=203/EXEC
> mars 28 07:53:03 systemd[1]: peertube.service: Failed with result 'exit-code'.
> mars 28 07:53:03 systemd[1]: peertube.service: Service RestartSec=100ms expired, scheduling restart.
> mars 28 07:53:03 systemd[1]: peertube.service: Scheduled restart job, restart counter is at 5.
> mars 28 07:53:03 systemd[1]: Stopped PeerTube daemon.
> mars 28 07:53:03 systemd[1]: peertube.service: Start request repeated too quickly.
> mars 28 07:53:03 systemd[1]: peertube.service: Failed with result 'exit-code'.
> mars 28 07:53:03 systemd[1]: Failed to start PeerTube daemon.
> mars 28 08:03:57 systemd[1]: Started PeerTube daemon.
> mars 28 08:03:57 systemd[1]: peertube.service: Main process exited, code=exited, status=203/EXEC
> mars 28 08:03:57 systemd[1]: peertube.service: Failed with result 'exit-code'.
> ```
Si un admin veut un coup de main pour debuguer, et est ok pour me donner un accès au serveur le temps d’une visio, je peux filer un coup de main.
Je ne connais pas trop le fonctionnement de yunohost, mais je connais bien celui de peertube, et je connais bien debian. Si l’admin en question sait un peu comment marche le packaging d’application yunohost, c’est un plus