[Pdns-users] Error after upgrade

[Jorge Arenas]

Thanks Marcus
I did the updates of the database schemas (With some warnings on charset modifications, but apparently the changes were made)

make the modifications from 3.4.0 to 4.1.0, 4.1.0 to 4.2.0 and 4.2.0 to 4.3.0 

 but I keep getting the same error

reading some post in internet ( I am not an expert on MySQL) they mention that this error: "Is generally caused by comparing two strings of incompatible collations or by attempting to select data of different collations into a combined column"
But I do not know how correct this

Jorge Arenas Quezada 
Aguascalientes, Ags Mexico 
jorgeaaq at yahoo.com 

    On Monday, October 19, 2020, 1:04:07 AM CDT, Markus Ehrlicher <markus.ehrlicher at komsa.de> wrote:  
 
  <!--#yiv5784906753 _filtered {} _filtered {} _filtered {}#yiv5784906753 #yiv5784906753 p.yiv5784906753MsoNormal, #yiv5784906753 li.yiv5784906753MsoNormal, #yiv5784906753 div.yiv5784906753MsoNormal {margin:0cm;margin-bottom:.0001pt;font-size:12.0pt;font-family:"Times New Roman", serif;}#yiv5784906753 a:link, #yiv5784906753 span.yiv5784906753MsoHyperlink {color:#0563C1;text-decoration:underline;}#yiv5784906753 a:visited, #yiv5784906753 span.yiv5784906753MsoHyperlinkFollowed {color:#954F72;text-decoration:underline;}#yiv5784906753 p.yiv5784906753msonormal0, #yiv5784906753 li.yiv5784906753msonormal0, #yiv5784906753 div.yiv5784906753msonormal0 {margin-right:0cm;margin-left:0cm;font-size:12.0pt;font-family:"Times New Roman", serif;}#yiv5784906753 span.yiv5784906753E-MailFormatvorlage18 {font-family:"Calibri", sans-serif;color:#1F497D;}#yiv5784906753 span.yiv5784906753E-MailFormatvorlage19 {font-family:"Calibri", sans-serif;color:windowtext;}#yiv5784906753 .yiv5784906753MsoChpDefault {font-size:10.0pt;} _filtered {}#yiv5784906753 div.yiv5784906753WordSection1 {}-->
Hello Jorge,
 
  
 
I stumbled upon the same problem a few months ago. Here you can find the schema-updates:
 
https://github.com/PowerDNS/pdns/tree/master/modules/gmysqlbackend
 
  
 
best regards,
 
Markus
 
  
 
Von: Pdns-users <pdns-users-bounces at mailman.powerdns.com>Im Auftrag von Jorge Arenas via Pdns-users
Gesendet: Montag, 19. Oktober 2020 05:42
An: pdns-users at mailman.powerdns.com
Betreff: [Pdns-users] Error after upgrade
 
  
 
I have a Centos 7 running PowerDNS
 
  
 
after a update to
 
  
 
 mysql-community-server-8.0.22-1.el7.x86_64
 
 mysql-community-devel-8.0.22-1.el7.x86_64
 
 pdns-4.3.1-1pdns.el7.x86_64
 
 pdns-backend-mysql-4.3.1-1pdns.el7.x86_64
 pdns-tools-4.3.1-1pdns.el7.x86_64
 
  
 
I am receiving this messages
 
  
 
  
 
ct 18 22:38:14 pdns_server: Backend error: GSQLBackend unable to find before/after (after) for domain_id 48 and qname 'xxxx': 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 '>'
 
  
 
Oct 18 22:38:16 pdns_server: Backend reported permanent error which prevented lookup (GSQLBackend unable to find before/after (after) for domain_id 48 and qname 'xxxx': 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 '>'), aborting
 
  
 
Oct 18 22:38:16 pdns_server: Backend error: GSQLBackend unable to find before/after (after) for domain_id 48 and qname 'xxxxxx': 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 '>'
 
  
 
  
 
I do not know if there some bug or requirement of the updated software
 
  
 
I had and old version of pdns and I do not know if i need to update my database schema
 
  
 
Can someone help me or point me in the right direction?
 
  
 
thanks in advance
 
  
 
Jorge Arenas
 
  
 
  
 
  
 
  
 
  
 
  
 
  
 
  
   
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.powerdns.com/pipermail/pdns-users/attachments/20201019/f732612b/attachment.htm>