Disparition de l'application Wallabag

Support
1

Mon serveur YunoHost

Matériel: Serveur Kimsufi KS-4C
Version de YunoHost: 4.4.2.1
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 ? : oui je pense que c’est lié suite à une mise à jour de l’application Wallabag qui a échoué. Surement similaire à ces posts :
Post 1
Post 2
Puis une mise à jour du serveur Yunohost.

Description du problème

Bonjour,

Je viens de remarquer que l’application Wallabag avait disparu de mon serveur. Je dirais le 3 août. Je pense que j’ai poussé une update par la Webadmin car dans les journaux je remarque l’erreur Une erreur s'est produite durant l'exécution du script de mise à niveau de l'application

Le log associé à cette erreur est celui-ci Log Yunopaste

Je viens de m’en apercevoir et j’étais dans surement dans une version inférieur de Yunohost a ce moment. Si j’essaye de restaurer l’application avec le backup pre-upgrade qui a été fait j’ai maintenant cette erreur
Cette sauvegarde ne peut pas être restaurée car elle provient d'une version YunoHost trop ancienne.

Je suppose donc que l’application à disparu quand j’ai fait la monté de version Yunohost… Je ne la vois plus dans le dossier /var/www.

J’ai remarqué que le backup wallabag2-pre-upgrade1.tar contenait un fichier /apps/wallabag2/backup/db.sql qui semble contenir mes données. J’ai donc tenté de réinstaller Wallabag en me disant que je remplacerais la base de donnée. Le Hic c’est que je ne trouve pas la bdd sur cette nouvelle installation. Sur une installation Wallabag classique elle devrait être dans /var/www/wallabag2/data/db mais j’ai l’impression que c’est différent sur Yunohost. Sauriez-vous me dire à quoi correspond le dossier /apps/wallabag2/backup/ dans mon backup ?

Merci d’avance a tout ceux qui auront pris la peine de s’intéresser à mon problème.

2

It looks like an epic catastrophy because the app change version. The bug was fixed in version 4.4.1

However there’s still a backup made prior to the upgrade but Yunohost complains that WARNING - Uhoh ... Yunohost failed to restore the app to the way it was before the failed upgrade :| … which may be another bug but it’s quite puzzling. The backup was by definition created on the same version Yunohost is on so …

I’ve seen some similar issue in the past tho because of complex technical reason. You may need to manually edit the .info.json file corresponding to your backup, located in /home/yunohost.backup/archives/ and fix what’s in front of yunohost_version inside that file

1 Like
3

Thanks Aleks,

It worked. I replaced

{"description": "", "created_at": 1659518908, "size": 128042312, "size_details": {"system": {}, "apps": {"wallabag2": 128041590}}, "apps": {"wallabag2": {"version": "2.3.8~ynh4", "name": "Wallabag", "description": "A self hostable read-it-later app"}}, "system": {}, "from_yunohost_version": "BASH_XTRACEFD:"}

By

{"description": "", "created_at": 1659518908, "size": 128042312, "size_details": {"system": {}, "apps": {"wallabag2": 128041590}}, "apps": {"wallabag2": {"version": "2.3.8~ynh4", "name": "Wallabag", "description": "A self hostable read-it-later app"}}, "system": {}, "from_yunohost_version": "4.4.2.1"}

And the restoration worked.

That’s great! Thanks again.

1 Like
4

Great to see it worked ! Thanks @Aleks

@ardnaxele : you tried to upgrade from 2.3.8. I think I recognize this issue :

DEBUG - Migration 20190601125843 failed during Execution. Error An exception occurred while executing 'ALTER TABLE entry ADD given_url LONGTEXT DEFAULT NULL, ADD hashed_given_url TINYTEXT DEFAULT NULL':
DEBUG - 
DEBUG - SQLSTATE[42000]: Syntax error or access violation: 1118 Row size too large. The maximum row size for the used table type, not counting BLOBs, is 8126. This includes storage overhead, check the manual. You have to change some columns to TEXT or BLOBs
WARNING - 09:29:38 ERROR     [console] Error thrown while running command "--no-interaction --env=prod doctrine:migrations:migrate". Message: "An exception occurred while executing 'ALTER TABLE entry ADD given_url LONGTEXT DEFAULT NULL, ADD hashed_given_url TINYTEXT DEFAULT NULL':
DEBUG - 
WARNING - SQLSTATE[42000]: Syntax error or access violation: 1118 Row size too large. The maximum row size for the used table type, not counting BLOBs, is 8126. This includes storage overhead, check the manual. You have to change some columns to TEXT or BLOBs" ["exception" => Doctrine\DBAL\Exception\DriverException { …},"command" => "--no-interaction --env=prod doctrine:migrations:migrate","message" => """  An exception occurred while executing 'ALTER TABLE entry ADD given_url LONGTEXT DEFAULT NULL, ADD hashed_given_url TINYTEXT DEFAULT NULL':\n  \n  SQLSTATE[42000]: Syntax error or access violation: 1118 Row size too large. The maximum row size for the used table type, not counting BLOBs, is 8126. This includes storage overhead, check the manual. You have to change some columns to TEXT or BLOBs  """]

but I can’t remember what was the source of this problem…

How old was your Wallabag installation ? Did you install it before 2018 ?

Let me know if the upgrade works now…

5

Hi @Lapineige

My installation seems to have been done on April 2, 2020. Yes I didn’t specify it but I did the update directly after restoring the application. I am in version 2.5.1~ynh2 and it works fine.

6

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.