Could not poll the database

[vader-pepe]

Support guidelines

• I've read the support guidelines

I've found a bug and checked that ...

• ... the documentation does not mention anything about my problem
• ... there are no open or closed issues that are related to my problem
• ... it's definitely a Firefly III issue, not me

Description

I 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 information

Could not poll the database: SQLSTATE[HY000] [2054] Server sent charset (0) unknown to the client. Please, report to the developers (Connection: mysql, SQL: select id, name, data from configuration where name = is_demo_site and configuration.deleted_at is null limit 1)

This error occured in file /var/www/html/app/Support/FireflyConfig.php on line 65 with code 0.

Expected behaviour

I can see the login page as shown by the demo

Steps to reproduce

1. clone the repo
2. create docker-compose.yml
3. change the port to 3000 (80 doesn't work for me. does't have to be 3000. can be anything)
4. add 'docker.io/' prefix for image if you using podman
5. run podman-compose up -f docker-compose.yml -d
6. open localhost:3000

Additional info

No response

[vader-pepe]

possible same issue: #1366

[JC5]

I'm pretty sure the database container failed to start for some reason, check out the logs.

[JC5]

Sorry, then I don't know what it could be.

[vader-pepe]

Could it be WSL problem?

[Still34]

I just got hit with the same problem about an hour ago. It was working perfectly fine before then.

[Still34]

Specifying an older build of mariadb (specifically 11.2) fixed the problem - seems like something's going on with the latest MariaDB Docker release.

[vader-pepe]

Specifying an older build of mariadb (specifically 11.2) fixed the problem - seems like something's going on with the latest MariaDB Docker release.

confirmed. marking this as an answer

[JC5]

Thanks for the feedback, I'll check it out for sure. Perhaps I'll have to pin the previous release in the Docker file to be safe.

[t-hamano]

It may be related to the recent update of the MariaDB image. See MariaDB/mariadb-docker#560

[JC5]

Indeed, the error message is the same.

[DarkWayC0de]

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.

[ahmaddxb]

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.

[dmarguerat]

Simply set Charest in docker compose will work.

command: --character-set-server=utf8

[xavasp]

Thanks, now it works.

[czwama]

Thanks, this fixed it for me as well

[Leah96xxx]

@dmarguerat which service do we need to add this command to? Firefly core or firefly db?

[dmarguerat]

@Leah96xxx Firefly db which is the MariaDB container.

[Leah96xxx]

Thanks. Confirmed that's fixed it for me too using mariadb:latest

[JC5]

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!

[DanielvdSpoel]

I'm having the exact same issue, but instead of MariaDB, I'm using MySQL, running on unraid using docker