<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
span.E-mailStijl17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 70.85pt 70.85pt 70.85pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=NL link="#0563C1" vlink="#954F72"><div class=WordSection1><p class=MsoNormal>Hi,<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span lang=EN-US>I upgraded my server from Debian Jessie (8) to Debian Stretch (9; the newest Stable release). With this upgrade OpenDNSSEC is upgraded from 1.4.6 to 2.0.3, while Mysql 5.5.58 is upgraded to MariaDB 10.1.26. My current OpenDNSSEC implementation uses a MySQL backend and follows the principle of ‘input and output files’.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US>During the upgrade I was made aware of the fact that the OpenDNSSEC upgrade to 2.0.3 requires two steps. Quote:<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US>******<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US>There are two steps in the database migration. If you are running OpenDNSSEC 1.4.6 from Debian stable, you need to apply the SQL statements from /usr/share/opendnssec/migrate_1_4_8.{mysql,sqlite3} against your existing database. <o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US>The enforcer does require a full migration, as the internal database has been completely revised. See the upstream documentation in the /usr/share/opendnssec/1.4-2.0_db_convert/README.md for a description. <o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US>You should also review the documentation on the OpenDNSSEC site. This can be updated in between releases to provide more help. Especially if you have tooling around OpenDNSSEC you should be aware that some command line utilities have changed. A fair amount of backward compatibility has been respected, but changes are present. <o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US>******<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='mso-fareast-language:NL'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US>In an attempt to migrate the database, I first ran the migrate_1_4_8.mysql. This threw the error that KEYDATA_VIEW already existed. As this table was empty, I removed it, and ran the remaining part of the SQL from migrate_1_4_8.mysql again. This resulted in a view with the name KEYDATA_VIEW. No further errors. <o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US>The next step (migrating to 2.0 db) involves running of convert_mysql in Bash. Initially this results in “error 1071 specified key was too long max key length is 767 bytes”. I tried to resolve this by setting the InnoDB variable innodb_file_format to ‘Barracuda’ and enabling innodb_large_prefix. This resulted in a new but similar error: “error 1709 index column size too large. The maximum column size is 767 bytes.”. And I’ve not been able to resolve this, which basically means that I’m stuck in the migration process towards OpenDNSSEC 2.0 and cannot start the relevant services on my server.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US>Any help is much appreciated.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US>--<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US>Dennis<o:p></o:p></span></p></div></body></html>