-
Notifications
You must be signed in to change notification settings - Fork 187
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Race condition between Seahub and MySQL #408
Comments
We are re-designing the docker image for version 12.0. We will keep the issue in mind during the process. If you still have the problem at that time, just let me know. |
To troubleshoot the problem, when seahub.sh failed to start, please send the seahub.log at that moment. By the way, please make sure the docker is the latest version. |
Unfortunately, there's not much going on there. I just checked to make sure Docker and my Docker images are up to date and restarted the service a few times until this happened, and this is all that's in
Meanwhile, much like the Docker log above, the Docker logs for this are showing that it can't connect to the DB:
|
I just updated to the 12.0.4 container, and this is still sometimes happening. This time, the Docker logs show this:
|
I got the same problem when upgrading from latest version to 12.0.4. My installation is broken since then. One of the visible errors is this line when starting the container:
I looked into it for a bit and I am not sure why the bootstrap script tries to change something in another static container file? |
I get the same error, but there is more information when running the container with the This is a completely fresh install of 12.0.4 and it worked fine at first, but after a couple of reboots it now fails.
|
I use the following (redacted) Docker compose file for my Seafile installation. It's very similar to the official one:
I also have
systemd
set up to launch it:However, about half the time when I start the service, Seahub fails to start because MySQL isn't quite ready by the time it checks. It doesn't seem to retry, either. The specific error I see is:
In those cases, I either need to stop the service and start it again, or run
seahub.sh
within the container manually in order to successfully start Seahub.The text was updated successfully, but these errors were encountered: