Hey Sven, thanks for the reply. My PowerDNS database and all tables are configured to use the latin1 character set. The only place I've configured UTF-8 is in the MySQL server-wide configuration (my.cnf). However, I was able to repro just now even without this MySQL configuration, so I don't think it's actually the cause.
I've been doing some more digging, and as far as I can tell, this error only happens after upgrading from MySQL 8.0.21 to 8.0.22. I upgraded the MySQL client, server and libraries on a server that was previously not experiencing this error, and the same error started happening. However, I'm unable to find anything in the MySQL changelogs ( https://dev.mysql.com/doc/relnotes/mysql/8.0/en/news-8-0-22.html) that would explain this. I opened a bug on GitHub: https://github.com/PowerDNS/pdns/issues/9777 Thanks, Daniel On Wed, Nov 25, 2020 at 1:44 AM Sven Kieske <s.kie...@mittwald.de> wrote: > On Di, 2020-11-24 at 20:07 -0800, Daniel Lo Nigro via Pdns-users wrote: > > > > If PowerDNS relies on the character set being explicitly set to latin1 > and > > breaks when other character sets (such as UTF-8) are set as the default > > collation on the server, it should explicitly set the character set used > by > > the connection to the MySQL server by executing SET NAMES 'latin1' after > > connecting but before executing any 'real' queries. This seems like a bug > > in PowerDNS. > > Hi, > > it's at least explicitly mentioned in the docs to create your database > with a latin1 character set: > > https://docs.powerdns.com/authoritative/guides/basic-database.html > > Engine=InnoDB CHARACTER SET 'latin1'; > > It's most of the time not a good idea to alter defaults if you do not now > the internal working of > the software very well, as can be seen in this example. > > It's up to debate if this is a bug of the software or if the documentation > should be more urgent about setting up > the database schema. The current wording is: > > "Example: configuring MySQL" > > This contains some ambiguity (an example is, most of the time, not the > only way to do something). > But the rest of the wording is imho relatively clear, that you should not > configure the database with a different schema. > > -- > Mit freundlichen Grüßen / Regards > > Sven Kieske > Systementwickler > > > Mittwald CM Service GmbH & Co. KG > Königsberger Straße 4-6 > 32339 Espelkamp > > Tel.: 05772 / 293-900 > Fax: 05772 / 293-333 > > https://www.mittwald.de > > Geschäftsführer: Robert Meyer, Florian Jürgens > > St.Nr.: 331/5721/1033, USt-IdNr.: DE814773217, HRA 6640, AG Bad Oeynhausen > Komplementärin: Robert Meyer Verwaltungs GmbH, HRB 13260, AG Bad Oeynhausen > > Informationen zur Datenverarbeitung im Rahmen unserer Geschäftstätigkeit > gemäß Art. 13-14 DSGVO sind unter www.mittwald.de/ds abrufbar. > >
_______________________________________________ Pdns-users mailing list Pdns-users@mailman.powerdns.com https://mailman.powerdns.com/mailman/listinfo/pdns-users
