-
Notifications
You must be signed in to change notification settings - Fork 223
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
StuckThreadDetectionValve at setup/setupembeddeddb-default.action #53
Comments
After several refreshes in the browser I got (note, the CPU usage was very high for a while and then went back to zero - I used the trial install):
|
Hmm.. it seems after further experimentation that if I leave the container started for a while (after setting the database) it crashes with a 137 error (out of memory). I don't know which part of it crashes or if this is another problem. Also tried with latest version of confluence (6.4.0). |
When I choose the production database and connect to the standard postgre:9.6 container i see the following in the log output:
|
It does not really leave me with details I can debug from, the Out of memory issue might be that you're container is limited to less than the host machines. I think it was only in Java 9 the JVM is able to know the memory limitation when running in a container. Please provide details about the host machine, CPU, RAM. |
Sorry for not being specific enough and thank you for the quick reply. I tested it with: The OOM issue was related to the docker configuration on my MacOSX (2,7Ghz i5, 16GB RAM but only 1GB Assigned to Docker). The OOM issue is resolved and the container gets unstuck after a while. I can go beyond the database install and use confluence. However, it takes a very long time to get unstuck. After receiving the SQL error messages (above) I receive the following:
At the same time with the unstucking i receive another round of SQL error messages (below). I am not sure if I can ignore them and safely use Confluence or future data might get corrupted.
|
I'm seeing the same error when running a new container with a demo license. It gets the license, but after applying it it always fails. This is using latest container version on ubuntu 18 with
|
Hello
I have successfully used the image in April for creating and running a confluence install. Last month I wanted to upgrade the installation and tested the new image after building it. I could not make it run again and started seeing this WARN + exception:
This seems to have happend about 2 months ago, was not able to use the image afterwards. Any ideas?
Even new installs (different server, fresh image, recreate container, removed volumes) fail with the same problem.
Running Docker 17.06.1-ce on Mac OSX and Docker 17.06.1-ce on Ubuntu 16.04.
The text was updated successfully, but these errors were encountered: