Library share permission not found after recovey on a second server

Seafile Server
1

Hi,
After the crash of a seafile server I did the recovery on a second server but during the web connection in http when I try to open my library I get an error message Library share permission not found.

The .yml configuration file has been previously configured on server 2 and the seafile-backup folder as well on /opt. The installation of seafile was done via docker.

Voici la fichier de configuration
version: ‘2.0’
services:
db:
image: mariadb:10.11
container_name: seafile-mysql
environment:
- MYSQL_ROOT_PASSWORD=xxxxxxxx # Requested, set the root’s password of MySQL service.
- MYSQL_LOG_CONSOLE=true
volumes:
- /opt/seafile-mysql/db:/var/lib/mysql # Requested, specifies the path to MySQL data persistent store.
networks:
- seafile-net

memcached:
image: memcached:1.6.18
container_name: seafile-memcached
entrypoint: memcached -m 256
networks:
- seafile-net

seafile:
image: seafileltd/seafile-mc:latest
container_name: seafile
ports:
- “80:80”

- “443:443” # If https is enabled, cancel the comment.

volumes:
  - /opt/seafile-data:/shared   # Requested, specifies the path to Seafile data persistent store.
environment:
  - DB_HOST=db
  - DB_ROOT_PASSWD=xxxxxxxxxx # Requested, the value should be root's password of MySQL service.
  - TIME_ZONE=Etc/UTC  # Optional, default is UTC. Should be uncomment and set to your local time zone.
  - SEAFILE_ADMIN_EMAIL=contact@xxxxxxx # Specifies Seafile admin user, default is 'me@example.com'.
  - SEAFILE_ADMIN_PASSWORD=xxxxxxxxxx     # Specifies Seafile admin password, default is 'asecret'.
  - SEAFILE_SERVER_LETSENCRYPT=false   # Whether to use https or not.
  - SEAFILE_SERVER_HOSTNAME=xxxxxxxxxxxx # Specifies your host name if https is enabled.
depends_on:
  - db
  - memcached
networks:
  - seafile-net

networks:
seafile-net:
Here are the commands entered for the recovery
Docker compose up -d
docker cp /opt/seafile-backup/databases/ccnet_db-2023-11-08_15-38.sql seafile-mysql:/tmp/ccnet_db.sql
docker cp /opt/seafile-backup/databases/seafile_db-2023-11-08_15-38.sql seafile-mysql:/tmp/seafile_db.sql
docker cp /opt/seafile-backup/databases/seahub_db-2023-11-08_15-38.sql seafile-mysql:/tmp/seahub_db.sq
docker exec -it seafile-mysql /bin/sh -c “mysql -uroot -ponCP1eqGu45xd ccnet_db < /tmp/ccnet_db.sql”
docker exec -it seafile-mysql /bin/sh -c “mysql -uroot -ponCP1eqGu45xd seafile_db < /tmp/seafile_db.sql”
docker exec -it seafile-mysql /bin/sh -c “mysql -uroot -ponCP1eqGu45xd seahub_db < /tmp/seahub_db.sql”

cp -R /opt/seafile-backup/data/* /opt/seafile-data/seafile/
However when I use the seafile application everything seems ok

Thx for your help

2

FYI I got this, too, on first re-establishing the copied data files and database, and then connecting to it via a web page.

However, restarting the server & database, and then re-loading/relogging in to the web interface solved the problem.

My guess is, it has something to do with the way you have to install the server and get it running with no files and only the initial user. Then you stop it and sort of slip the correct data files and database in place.

That must leave the server in a place that is not quite right (some users or permissions or whatever held in memory or cached), but simply re-starting the server gets things all in order again.

3

I have the same issue. We used rsync to copy all files from HD to SSD drive. Plugged in the new drive. Server works but can’t access the files. Same Library share permission not found message. I restarted, logged out from the web page. Nothing.