Could not poll the database #8564
-
Support guidelines
I've found a bug and checked that ...
DescriptionI followed the instructions on installing firefly-iii with docker (im using podman actually), then I got error could not poll the database when it's started. Debug informationCould not poll the database: SQLSTATE[HY000] [2054] Server sent charset (0) unknown to the client. Please, report to the developers (Connection: mysql, SQL: select This error occured in file /var/www/html/app/Support/FireflyConfig.php on line 65 with code 0. Expected behaviourI can see the login page as shown by the demo Steps to reproduce
Additional infoNo response |
Beta Was this translation helpful? Give feedback.
Replies: 9 comments 13 replies
-
possible same issue: #1366 |
Beta Was this translation helpful? Give feedback.
-
I'm pretty sure the database container failed to start for some reason, check out the logs. |
Beta Was this translation helpful? Give feedback.
-
confirmed. marking this as an answer |
Beta Was this translation helpful? Give feedback.
-
It may be related to the recent update of the MariaDB image. See MariaDB/mariadb-docker#560 |
Beta Was this translation helpful? Give feedback.
-
I had the same error, during the night I updated mariadb and fireflyiii stopped connecting to the mariadb database, I thought that with a mysql client I can connect to the database without any problem, but after reverting to the previous version firefly is working correctly again. It would be interesting to know what was the problem with the connection between fireflyiii and the new version of mariadb. |
Beta Was this translation helpful? Give feedback.
-
when firefly_iii_core is in an unhealthy state like this cause here, I can not stop or remove the container, I have to do a complete reboot and catch it early to remove / stop. |
Beta Was this translation helpful? Give feedback.
-
Simply set Charest in docker compose will work. command: --character-set-server=utf8 |
Beta Was this translation helpful? Give feedback.
-
In the meantime, the mariadb containers have been updated as well, so the problem should be solved either way. Thanks everybody for your patience and feedback! |
Beta Was this translation helpful? Give feedback.
-
I'm having the exact same issue, but instead of MariaDB, I'm using MySQL, running on unraid using docker |
Beta Was this translation helpful? Give feedback.
Specifying an older build of mariadb (specifically 11.2) fixed the problem - seems like something's going on with the latest MariaDB Docker release.