Skip to content
Snippets Groups Projects
Commit 8921a26d authored by Yoan VALLET's avatar Yoan VALLET
Browse files

update easy cozy known errors

parent a7900bd0
No related branches found
No related tags found
No related merge requests found
# Oops...
Sometime the stack is stuck when we reset several instance due to rabbit mq process. The following screen is then obtain:
Sometime the stack is stuck when we reset several instances due to rabbit mq process. The following screen is then obtain when trying to access to an instance:
![oops_error](/img/known_errors/oops_error.png)
On the server we can see that the server is underwater by using "top" command:
On the server, we can see that the server is underwater by using "top" command:
![oops_error_1](/img/known_errors/oops_error_1.png)
To fix the issue you can just restart the service with "docker-compose down / docker-compose up -d" in the easy-cozy folder:
To fix the issue you can just restart the service on the server with "docker-compose down / docker-compose up -d" in the easy-cozy folder:
![oops_error_2](/img/known_errors/oops_error_2.png)
\ No newline at end of file
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment