Hardware: Dedicated old computer YunoHost version: 4.2.7 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
Hi all, after a system upgrade on June 30th, one of my Nextcloud installations has disappeared. Up to then, I was running three parallel Nextcloud installs with great success. The application system numbered them nextcloud, nextcloud__2 and nextcloud__3.
Since that update, nextcloud__3 is no longer listed in the installed apps, and is inaccessible at its urls. The data is still all there when I search for it via SSH, and a backup exists, but when I try to restore the data, I get an error linked to a missing directory for a specific user. Log is here: https://paste.yunohost.org/raw/ifumusezud
I then looked to see why the dir Multimedia was missing from this users directory to find that the entire /home/clare user dir is missing. Now, yunohost still thinks this user exists, when I sudo yunohost user list that user is active and visible, and the listing is the same via the web admin.
Iâm not sure what the best procedure is here, shall I recreate a âhomeâ dir for that user manually (what folders should I recreate?) or should I try to restore an older system backup? If I did the former, should I then try to re-run the ânextcloud__3â restore and hope for the best?
Restored all User data from a system backup (the option to restore only some portions of the backup is suuper nice) that restore was successful
Listed the content of the home dirs via SSH: the missing users folder was not restored. Upon further inspection, that users home folder was not part of the backup, so it has been missing since early May. Meanwhile, this ynh user has been using various services while signed in, namely that Nextcloud instance, without any issues, not sure how useful that info is.
Manually created that users home folder, then ran the restore, the restoration got a few steps further before failing again on a chown issue I do not understand.
Question: why would the nextcloud restore try to chown to a user that is not a unix user? My understanding is that ynh users are not created as unix users?
Thanks again for any help / ideas you can provide.
Ok, not too sure how this related to the update, but after a long session with @Aleks here is what solved the issue:
The resolve
the restore operation was failing because of a chown command. It was impossible to give ownership to the LDAP user, the command returned chown: invalid user: 'user'