Nextcloud can't create share

Bug
21

It’s also possible to create a new user domain and switch Nextcloud and Mail to the new user domain without deleting the old one.

No data is deleted. If you use the same usernames, mail data should just work. In Nextcloud, users get a new UID so data may need to be transferred from the old user folder to the new one. The UIDs are shown in the Accounts menu as Nextcloud admin.

Example of entering the Nextcloud container to check the folders:

[root@node1 ~]# runagent -m nextcloud1 podman exec -ti nextcloud-app sh

/var/www/html # ls data/
.htaccess                              5B98A16C-9EB7-4B22-BE22-B1DEAE03A24C/  f21f1e76-f45f-4703-a586-aa25c9124e61/
.ncdata                                D0C73181-DBCE-4D80-AD47-13C3A735DC66/  index.html
358144F9-0BA4-4516-8B55-8CFC4E39DAF7/  admin/
441E5AB4-BFC5-4D0C-AA64-9C4A0E24AA19/  appdata_ocbxeqyi7xce/

/var/www/html # ls data/D0C73181-DBCE-4D80-AD47-13C3A735DC66/files/
Documents                     Nextcloud.png                 Reasons to use Nextcloud.pdf  _Markus.md
Nextcloud Manual.pdf          Photos                        Templates
Nextcloud intro.mp4           Readme.md                     Templates credits.md

Yes, transfer is possible via NS8 cluster or backup/restore.

NS8 cluster: Add the new NS8 to the cluster and move the apps from old NS8 node to the new NS8 node, promote the new NS8 to the cluster leader and remove the old node, see also Cluster management — NS8 documentation

Backup/Restore: Backup the apps from the old NS8 and restore them on the new NS8, see also Backup and restore — NS8 documentation

You can find information about the apps on Github like for example GitHub - NethServer/ns8-openldap: NS8 OpenLDAP account provider module

Could you please give examples for good old tools? Maybe they’re already usable again.

22

good morning,

we tried this workaround. But all slap* commands are symlinks in container to slapd and they don’t work …
https://stackoverflow.com/questions/19537319/change-basedn-in-openldap

1 Like
23

I tried that approach but I didn’t find a way to stop the service as it is started with the container and if you kill slapd the container is restarted. I guess the container needs to be started without running slapd but I need to check…

Here is an example of running slapcat in the openldap container:

root@debianns8test:~# runagent -m openldap1
runagent: [INFO] starting bash -l
runagent: [INFO] working directory: /home/openldap1/.config/state

openldap1@debianns8test:~/.config/state$ podman ps
CONTAINER ID  IMAGE                                     COMMAND     CREATED             STATUS                 PORTS       NAMES
bf1421efb6e3  ghcr.io/nethserver/openldap-server:2.3.1              About a minute ago  Up About a minute ago              openldap

openldap1@debianns8test:~/.config/state$ podman exec -ti openldap sh

/var/lib/openldap $ ls
conf.d            dump-config.ldif  dump-mdb0.ldif    ldap.conf         openldap-data     run

/var/lib/openldap $ slapcat -v -l old_ldap.ldif
24

Thank you very much
… now we can see, there are two steps to enter a container.
Next question:
Now we try to move an container from node1(debian12) to node2(rocky linux), because of subscription support only for rocky basis…
Read there is a problem, if the basic OS’s are different…

1 Like
25

It’s not recommended to use different OS in a cluster in production because it’s hard to maintain and possible issues due to different package versions.
It’s possible to migrate apps to a new node using a different OS either by adding a new node and move the apps or via backup/restore.
I’d prefer the backup/restore method as it is more safe and clean.

1 Like
26

Hello Markus,
… since last nextcloud update the share problem is gone - partly !.
Users again can share documents with team members direct without needing email.
Sadly only possible, if this user had shared in the past something for the same team member.
… thanks for your help/time !

2 Likes