I restarted and recreated the containers from the docker-compose, but without success. 01:23:54 http-server.c(869): DB error when check repo existence. 01:23:54 …/common/seaf-db.c(729): Failed to connect to MySQL: Can’t connect to MySQL server on ‘db’ (110) 01:23:47 http-server.c(869): DB error when check repo existence. 01:23:46 …/common/seaf-db.c(729): Failed to connect to MySQL: Can’t connect to MySQL server on ‘db’ (110) It seems, that since tonight at 01:30 am it stopped working. I see the database running in the mysql container and I see, that in the Seafile container, Seafile isn’t running. SEAFILE_SERVER_HOSTNAME=xx.xx.xx # Specifies your host name if https is enabled.Īll 3 containers are up and running and I can bash into them. SEAFILE_SERVER_LETSENCRYPT=false # Whether to use https or not. SEAFILE_ADMIN_EMAIL=$ # Specifies Seafile admin password, default is ‘asecret’. DB_ROOT_PASSWD=XXXX # Requested, the value shuold be root’s password of MySQL service. opt/seafile-data:/shared # Requested, specifies the path to Seafile data persistent store. #- “8482:8082” # If https is enabled, cancel the comment. opt/seafile-mysql/db:/var/lib/mysql # Requested, specifies the path to MySQL data persistent store. Should be uncomment and set to your local time zone. TIME_ZONE=Europe/Berlin # Optional, default is UTC. MYSQL_ROOT_PASSWORD=XXXX # Requested, set the root’s password of MySQL service. I used the docker-compose from the manual: I switched from “native” to docker for my Seafile installation.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |