Docker problem Seafile server

Seafile Server
1

Hi,
I´m running the official Docker Server and I messed up, but don´t understand why?

I did some testing doing backup of the shared folder, and after changing user and group from root to “myuser” and then nothing works, even if I´m reverting to root again (this includes all sub folders).

Anyone that could explain why this is a problem?
What are the seafile docker username, not root?

Any help is much appreciated!
/tompa

2

Hey tompa,

can you post your docker logs? docker logs container_id

On my test machine the shared folder is owned by the user root with permissions 755. Except for the subfolder db this belongs to the user syslog and the group systemd-resolve

3

Hi D_FR,
thanks for your reply!

It looks like this after a restart;

*** Shutting down /scripts/start.py (PID 32)...
*** Shutting down runit daemon (PID 31)...
*** Running /etc/my_init.post_shutdown.d/10_syslog-ng.shutdown...
May 24 17:43:11 02df9021099d syslog-ng[24]: syslog-ng shutting down; version='3.5.6'
May 24 17:43:11 02df9021099d syslog-ng[24]: EOF on control channel, closing connection;
*** Init system aborted.
*** Killing all processes...
*** Running /etc/my_init.d/01_create_data_links.sh...
*** Running /etc/my_init.d/10_syslog-ng.init...
May 24 17:43:13 02df9021099d syslog-ng[24]: syslog-ng starting up; version='3.5.6'
May 24 17:43:14 02df9021099d syslog-ng[24]: EOF on control channel, closing connection;
*** Running /etc/my_init.d/99_mysql_setup.sh...
 
*** Running /etc/rc.local...
*** Booting runit daemon...
*** Runit started as PID 31
*** Running /scripts/start.py...
May 24 17:43:14 02df9021099d cron[38]: (CRON) INFO (pidfile fd = 3)
May 24 17:43:14 02df9021099d cron[38]: (CRON) INFO (Skipping @reboot jobs -- not system startup)
[2019-05-24 17:43:14] Preparing for letsencrypt ...
[2019-05-24 17:43:14] Found existing cert file /shared/ssl/mysite.com.crt
[2019-05-24 17:43:14] Skip letsencrypt verification since we have a valid certificate
4

Ok, I did a new install and there was a number of different owners and groups in sub folders, so I guess this was the problem(?)
I will not try to fix this, I just migrated data to new instance.