Sorry to reply to my own email, but I was correct. According to the
mysql docs, INT goes as big as 2147483647 for signed fields. BIGINT
goes a *LOT* bigger.
might be worth noting in the docs?
(not sure if others are pushing doing as many updates as me, but its
compounded by the fact that I do mysql replication between a few
servers, and have setup mysql autoincreament to go up by 5 as I'm
doing some master master replication between 3 Mysql Servers, hence
in my.cnf, I have setup "auto_increment_increment = 5"
Thanks
On 03 Apr 2007, at 7:55 PM, Justin Hammond wrote:
Hi,
I just finished diagnosing why all of a sudden my PDNS slave server
stoped doing zone transfers. Below I had the following error
message in the pdns logfile:
Apr 3 19:46:25 nurgle pdns[8104]: Communicator thread died because
of error: Failed to execute mysql_query, perhaps connection died?
Err=1: Duplicate entry '2147483647' for key 1
Apr 3 19:46:25 nurgle pdns[8104]: Communicator thread died because
of error: Failed to execute mysql_query, perhaps connection died?
Err=1: Duplicate entry '2147483647' for key 1
Unfortuantly, it seems that mysql isn't exactly descriptive enough.
I could not find that key in the ID file of any records. In fact,
there was no records that was "as big" as this entry at all. It
turned out to be that I guess we were hitting a overflow in the ID
field for records. Changing the ID field to "BIGINT" fixed the
problem. I'm not sure what the upper bounds of INT on mysql are but
you might want to update the SQL create table script?
(btw, this is PDNS 2.9.20)
Thanks
Justin
_______________________________________________
Pdns-users mailing list
[email protected]
http://mailman.powerdns.com/mailman/listinfo/pdns-users
_______________________________________________
Pdns-users mailing list
[email protected]
http://mailman.powerdns.com/mailman/listinfo/pdns-users
