[Pdns-users] Error after upgrade

[Daniel Lo Nigro]

I think this is happening because I set UTF-8 as the default collation on
my MySQL server, since most apps these days use UTF-8:

character-set-server  = utf8mb4
collation-server      = utf8mb4_general_ci

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.

On Tue, Nov 24, 2020 at 7:47 PM Daniel Lo Nigro <lists at d.sb> wrote:

> Hey Jorge, did you end up resolving this issue? I'm seeing the same error,
> but only on one of my five servers:
>
> pdns_server[599055]: Backend error: GSQLBackend unable to find
> before/after (after) for domain_id 8 and qname 'n7': Could not execute
> mysql statement: select ordername from records where ordername > ? and
> domain_id=? and disabled=0 and ordername is not null order by 1 asc limit
> 1: Illegal mix of collations (latin1_bin,IMPLICIT) and
> (utf8_general_ci,COERCIBLE) for operation '>'
>
> Collation on the ordername looks fine (CHARACTER SET latin1 COLLATE
> latin1_bin), and if I run the same query in the MySQL CLI it also works
> fine:
>
> mysql> select ordername from records where ordername > 'n7' and
> domain_id=8 and disabled=0 and ordername is not null order by 1 asc limit 1;
> +-----------+
> | ordername |
> +-----------+
> | ns1       |
> +-----------+
> 1 row in set (0.00 sec)
>
> The schema is identical across all replicas so I'm confused as to why only
> one of them is throwing these errors.
>
> Any ideas?
>
> Thanks,
> Daniel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.powerdns.com/pipermail/pdns-users/attachments/20201124/35fb5403/attachment.htm>