Bug 691023
| Summary: | master sends wrong serial to slave | ||
|---|---|---|---|
| Product: | [Fedora] Fedora EPEL | Reporter: | Vasiliy G Tolstov <v.tolstov> |
| Component: | pdns | Assignee: | Morten Stevens <mstevens> |
| Status: | CLOSED NEXTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | el5 | CC: | mstevens, ruben |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2012-10-26 17:45:42 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Vasiliy G Tolstov
2011-03-26 08:50:15 UTC
What is the column type of the serial in your database schema? Making it an unsigned int should help. on master:
Table: domains
Create Table: CREATE TABLE `domains` (
`id` int(11) NOT NULL AUTO_INCREMENT,
`name` varchar(255) NOT NULL,
`master` varchar(128) DEFAULT NULL,
`last_check` int(11) DEFAULT NULL,
`type` varchar(6) NOT NULL,
`notified_serial` int(11) DEFAULT NULL,
`account` varchar(40) DEFAULT NULL,
PRIMARY KEY (`id`),
UNIQUE KEY `name_index` (`name`)
) ENGINE=MyISAM AUTO_INCREMENT=41342 DEFAULT CHARSET=latin1
on slave:
CREATE TABLE domains (
id INTEGER PRIMARY KEY,
name VARCHAR(255) NOT NULL COLLATE NOCASE,
master VARCHAR(128) DEFAULT NULL,
last_check INTEGER DEFAULT NULL,
type VARCHAR(6) NOT NULL,
notified_serial INTEGER DEFAULT NULL,
account VARCHAR(40) DEFAULT NULL
);
Ok, you might want to change the notified_serial column to unsigned integer, since the integer can overflow when it gets too big. In master and slave? Yes, both. (In reply to comment #5) > Yes, both. Chage for both servers - this not close the problem. After changing schema and setting new serial of SOA record slave recieves wrong serial from master Mar 28 10:34:04 monitoring pdns[15311]: Received NOTIFY for 238.127.188.in-addr.arpa from 188.127.236.4, we are up to date: 2147483647<=3534744394 (master SOA 238.127.188.in-addr.arpa. 86400 IN SOA ns1.clodo.ru. clodo.clodo.ru. 3534744395 3600 600 86400 3600 ) (slave SOA 238.127.188.in-addr.arpa. 86400 IN SOA ns1.clodo.ru. clodo.clodo.ru. 3534744394 3600 600 86400 3600) Is the change_date column for the SOA record higher on the master then it is on the slave? Master and slave has 0 on this. After change in master to 1, nothing changed Mar 28 11:32:13 monitoring pdns[15311]: Received NOTIFY for 238.127.188.in-addr.arpa from 188.127.236.4, we are up to date: 2147483647<=3534744394 Ok, then I have no idea what's wrong. Would you mind posting your issue on the powerdns mailing list? I'm already do this see link http://wiki.powerdns.com/trac/ticket/96#comment:2 Ah, I didn't know that was you :) I'll see if I can backport this change to 2.9.22 (In reply to comment #11) > Ah, I didn't know that was you :) > > I'll see if I can backport this change to 2.9.22 Sorry, but when You can try to backport this? I'm pretty busy atm, but somewhere this week. I've been thinking about this some more, and something doesn't make sense. If you've converted the column on your slave the serial on your slave should be lower than the master. What's the serial in the slave db? Have you tried restarting the slave, maybe it's caching the SOA records. I'm try to completely destroy slave db and says master to notify slave about all zones - problem stays... Fixed in: pdns-3.1-1.el6 https://admin.fedoraproject.org/updates/pdns-3.1-1.el6 |