Skip to content
Snippets Groups Projects
Normal view Permalink
known_errors.md 579 B
Newer Older
  • Learn to ignore specific revisions
    • Hugo NOUTS's avatar
    mkdocs refacto  
    Hugo NOUTS committed
    1 
    ### :construction: Oops...
    Yoan VALLET's avatar
    update doc links and add easycozy known errors
    Yoan VALLET committed
    2
    Hugo NOUTS's avatar
    mkdocs refacto  
    Hugo NOUTS committed
    3 
    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:
    Yoan VALLET's avatar
    update doc links and add easycozy known errors
    Yoan VALLET committed
    4 5 
    ![oops_error](/img/known_errors/oops_error.png)
    Yoan VALLET's avatar
    update easy cozy known errors  
    Yoan VALLET committed
    6 
    On the server, we can see that the server is underwater by using "top" command:
    Yoan VALLET's avatar
    update doc links and add easycozy known errors
    Yoan VALLET committed
    7 8 
    ![oops_error_1](/img/known_errors/oops_error_1.png)
    Hugo NOUTS's avatar
    fix typos, added monitoring query build  
    Hugo NOUTS committed
    9 
    To fix this issue, just restart the service on the server with "docker-compose down / docker-compose up -d" in the easy-cozy folder:
    Yoan VALLET's avatar
    update doc links and add easycozy known errors
    Yoan VALLET committed
    10 
    ![oops_error_2](/img/known_errors/oops_error_2.png)