Update and backup of YH Hubzilla 8.6 package did not work

Hardware: VPS online

YunoHost version: 11.2.3

I have access to my server : Through SSH | through the webadmin | direct access via keyboard / screen |

Are you in a special context or did you perform some particular tweaking on your YunoHost instance ? : no

Description of my issue

After a not correct working update from YH Hubzilla 8.4.1 to YH Hubzilla 8.6 and deleting of the HZ App - the resorting of the backup did not work

First the installation seamed fine but the HZ queueworker was not doing anything so that no posts could be sent.

After the support of a HZ DEV we found out that the HZ Composer which needs PHP version >= 8.1.0 gets on my YH server just php 7.4.33 provided.

root@admin:~# cd /var/www/hubzilla
root@admin:/var/www/hubzilla# util/config system php_path                                                                                
Composer detected issues in your platform:                                                                                               

Your Composer dependencies require a PHP version ">= 8.1.0". You are running 7.4.33.                                                     

PHP Fatal error:  Composer detected issues in your platform: Your Composer dependencies require a PHP version ">= 8.1.0". You are running
 7.4.33. in /var/www/hubzilla/vendor/composer/platform_check.php on line 24                                           

than i tried to restore the hub installation to the last working installation with the automatic made backup by YH but also that was not working. I got this warning

WARNING - /var/cache/yunohost/app_tmp_work_dirs/app_mvszbjej/restore: line 30: db_user: unbound variable

and here is the full log:


I hope very strongly the backup can be still used an be reinstalled and my hub is not lost. Please tell me what i your try.

Thank your very much for any help in this topic. I really appreciate all your great work you do for YH

the backup could be restored now

Took me a while to understand how to do it but now i found a fix.

During the YNH backup process somehow the variable “db_user” was not stored - it is missing in the file “settings.yml” where all the variables are stored in for restoring a YNH app backup file

So here is what i did and what you can try if you came in to a similar situation:

YNH App backup archives are stored in /home/yunohost.backup/archives/

With your SFTP client make a save copy of your not working backup archive to your local hard drive - just in case…

Rename the backup archive on the server from “hubzilla-pre-upgrade2.tar” to something like “hubzilla-save.tar” so that YNH will not overwrite this archive by any other backup operation.

Go by ssh to /home/yunohost.backup

$ cd /home/yunohost.backup/

extract the file “settings.yml” from the backup .tar archive

$ tar -xf archives/hubzilla-save.tar apps/hubzilla/settings/settings.yml

(all this tar commands will take a while, depending how large your archive is, so be patient till the operation is done)

You find the extracted file under /home/yunohost.backup/apps/hubzilla/settings/settings.yml

Edit the extracted file “settings.yml” by adding the line “db_user: hubzilla” and save the file.
My SFTP client can do this within the app. If your SFTP Client can’t do this you have to first download the file, use a text editor for editing, and upload it again by SFTP.

Delete the original file “settings.yml” whin the .tar achieve

$ tar --delete -f archives/hubzilla-save.tar apps/hubzilla/settings/settings.yml

add the new edited file “settings.yml” to the .tar achiv

$ tar -uf archives/hubzilla-save.tar apps/hubzilla/settings/settings.yml

Now the YNH restore script can find the variable “$db_user” the and the restoring of the backup archive will work. Just select the renamed archive in the YNH webAdmin interface

or do in this case (archivename = hubzilla-save ) by command line

$ yunohost backup restore hubzilla-save --apps hubzilla --debug

1 Like

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