Synapse 1.94 fails to restore on a fresh installation

kr-cr commented 8 months ago

Context

Hardware: Raspberry 3B
YunoHost version: 11.2.5
Synapse version: 1.94
I have access to my server: : Through SSH and/or through the webadmin
Are you in a special context or did you perform some particular tweaking on your YunoHost instance?: yes
If yes, please explain: I try to restore my Yunohost instance to a new SD Card with a 64 bits OS (currently installed on a 32 bits one)

Steps to reproduce

I made a backup of Synapse 1.94 on my 32bits running instance.
I Installed Yunohost on the 64 bits, made upgrade and restored Yunohost successfully
I attempted to restore my Synapse backup on the new installation but it failed.

The 3 warnings I have in the logs are:

2023-10-21 16:28:45,946: WARNING - setfacl: Option -m: Invalid argument near character 3
2023-10-21 16:28:45,949: WARNING - setfacl: Option -m: Invalid argument near character 5

and I think the one that cause the script to fail:

2023-10-21 16:44:30,463: DEBUG - + pip3 install --upgrade setuptools wheel pip
2023-10-21 16:44:30,465: WARNING - ../settings/scripts/_common.sh: /opt/yunohost/matrix-synapse/bin/pip3: /opt/yunohost/matrix-synapse/bin/python3: bad interpreter: No such file or directory

Logs

Here is the my full log: https://paste.yunohost.org/raw/ofojaduqah

I also posted this on the Yunohost forum to get any help: https://forum.yunohost.org/t/synapse-fails-to-restore-on-a-fresh-installation/26859/

Thank you

kr-cr commented 8 months ago

Update : I seem to have finaly managed to restore it successfully!

I did 2 changes since the last try so I am not sure about which solved it. The 2 modifications are:

I stumbled upon this issue and more specifically this reply from Josue-T, that say that the architecture change needs a modification in the restoration script. I made the change in my backup.
I didn't specified it earlier but my backup was on an external HDD binded to the backup folder of Yunohost. This time I canceled the bind mount and move the backup archive to the card.

The issue can be tagged as resolved, but maybe the changes have to be documented somewhere.

Thank you

rosbeef commented 3 weeks ago

The bug persist on 1.107.0~ynh1

That resolve the bug (related to #242 ) : https://github.com/YunoHost-Apps/synapse_ynh/issues/242#issuecomment-822468973

Maybe this should help too : In https://github.com/YunoHost-Apps/synapse_ynh/blob/master/scripts/_common.sh local pip3="$code_dir"/bin/pip3 should better be local pip3="$code_dir"/bin/python3 -m pip

Situations like this are exactly why running "pip" or "pip3" directly is no longer recommended, in favor of: "python3 -m pip install ..."

source : https://stackoverflow.com/a/51373253

https://snarky.ca/why-you-should-use-python-m-pip/

Josue-T commented 1 week ago

Well closing because there was a lot of changes since this issue was created.

If the issue persist please create a new issue with the full log and details of the new issue.

YunoHost-Apps / synapse_ynh