-
-
Notifications
You must be signed in to change notification settings - Fork 272
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
Dispatcher unable to connect to DB after initially working #108
Comments
Just a note, that deleting the db mapped volume fixes the problem but I would prefer to not do that. |
So after deleting the db everything works fine now? Even after restarting your stack? |
I can confirm that after deleting db and restarting multiple times, it continues to work. |
@ZummiGummi Ok looks like the same issue as #80 (comment). Come back to me if this issue occurs again. |
Very inconsistent behavior trying to pinpoint the cause, but I think this link fixed the problem. |
Behaviour
Steps to reproduce this issue
docker-compose pull
to update from 1.64 to latest (1.66)docker-compose up
docker-compose up
Expected behaviour
Actual behaviour
Configuration
docker --version
) : Docker version 19.03.11, build 42e35e61f3docker-compose --version
) : docker-compose version 1.24.1, build 4667896buname -a
) : Linux 4.19.0-9-amd64 can not connect to librenms gui - 404 page not found #1 SMP Debian 4.19.118-2+deb10u1 (2020-06-07) x86_64 GNU/Linuxdocker-compose.yml
,.env
, ...docker-compose.yml
.env
librenms.env
Docker info
Logs
logs.txt
The text was updated successfully, but these errors were encountered: