<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On 2015/07/22 06:48 PM, Mark Moseley wrote:<br>
</span><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">
On Tue, Jul 21, 2015 at 5:00 PM, Gabriel Marais<br></span><span class="">
<<a href="mailto:gabriel.j.marais@gmail.com" target="_blank">gabriel.j.marais@gmail.com</a> <mailto:<a href="mailto:gabriel.j.marais@gmail.com" target="_blank">gabriel.j.marais@gmail.com</a>>> wrote:<br>
<br>
Hi Guys<br>
<br>
Seems like I have hit a brick wall. I have PowerDNS 2.9.x running as<br>
master and 2 slaves. I am busy moving over to Ubuntu 14.x on newly<br>
installed servers and as such I ended up with PowerDNS 3.x which is<br>
not compatible with the older 2.9 schema on MySQL.<br>
<br>
I have read in a thread that one could use custom queries to<br>
overcome the immediate issue of moving a complete DNS implementation<br>
over to the version 3.x schema but I cannot seem to find the custom<br>
queries to overcome the issue from my log :-<br>
<br>
Jul 22 01:17:46 hubble pdns[2006]: Backend error: Failed to execute<br>
mysql_query, perhaps connection died? Err=1: Unknown column 'auth'<br>
in 'field list'<br>
<br>
Ultimately, I would like to move over to PowerDNS 3.x but right now<br>
I need to get another 'slave' working which is sitting on PowerDNS<br>
3.x to work with my 2.9 master and database schema.<br>
<br>
Can anyone perhaps point me in the right direction with the custom<br>
queries to accommodate the missing "auth" column in the new DB schema?<br>
<br>
<br>
<br>
</span></blockquote>
Hi Mark<br>
<br>
Thanks for the reply. This is what I was looking for..<span class=""><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I limped by for a little while with these queries, in the middle of a<br>
2.9.x->3.x upgrade. It's been long enough now that I couldn't tell you<br>
what negative side effects it had, but I do remember that AXFR's did<br>
*NOT* work with the below queries. IIRC with this setup, AXFRs will<br>
actually cause a restart of pdns, so you'd want to get off of it pretty<br>
quick.<br>
<br>
</blockquote></span>
I added the queries to my config file, pdns.local.gmysql.conf<br>
But I'm still getting the error on the "auth" field :-<span class="im HOEnZb"><br>
Backend error: Failed to execute mysql_query, perhaps connection died? Err=1: Unknown column 'auth' in 'field list'<br>
<br>
</span><div class="HOEnZb"><div class="h5"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
# Use old queries till we get schema updated<br>
gmysql-basic-query=SELECT content,ttl,prio,type,domain_id,name FROM<br>
records WHERE type='%s' and name='%s'<br>
gmysql-any-id-query=SELECT content,ttl,prio,type,domain_id,name FROM<br>
records WHERE name='%s' and domain_id=%d<br>
gmysql-list-query=SELECT content,ttl,prio,type,domain_id,name FROM<br>
records WHERE 0=%d and domain_id='%d' order by name, type<br>
<br>
<br>
At the same time, the 2.9.x boxes might work just fine (but you'd<br>
obviously want to test first) with the 3.x schema, though I'm assuming<br>
you're doing mysql replication.<br></blockquote></div></div></blockquote><div><br></div><div><br></div><div><br></div><div>Must be a different query. You could tcpdump the query and match it up to the list of queries in the pdns docs and adapt it accordingly perhaps. </div></div><br></div></div>