# Oops...

Sometime the stack is stuck when we reset several instance due to rabbit mq process. The following screen is then obtain:
![oops_error](/img/known_errors/oops_error.png)

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:
![oops_error_2](/img/known_errors/oops_error_2.png)