Closed jwhips closed 3 months ago
I can confirm the fix was to login to the running container (that fails to launch LibreNMS), change the database password to not have a "\" (backslash) and then update the env file with that new password and then I was able to update to the latest version of LibreNMS.
I'd advise that a new instance should avoid a backslash in the database password.
Support guidelines
I've found a bug and checked that ...
Description
I have been running 23.11 for a few months without issue.
I did a docker compose down / pull / up and librenms failed to start. Reverting back to 23.11 causes the issue to go away.
Expected behaviour
I was expecting the new version of librenms to launch without issue.
Actual behaviour
I am getting two consistent errors in my docker compose logs ; this is one of them. Unsure if the two are related.
Steps to reproduce
Docker info
Docker Compose config
Logs
Additional info
This appears to be the problem.
Changing the compose file to image: librenms/librenms:23.11.0 fixes the issue.
I also see other errors in the logs, unsure what they are or if they should be a concern. Thank you for all you do.