### :construction: Oops...

Sometime the stack get stuck when we reset several instances, overflowing our message broker rabbitmq. The following screen is then obtained when trying to access 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:
![oops_error_1](/img/known_errors/oops_error_1.png)

To fix this issue, 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)