We have two 4.0.15 mysql servers set up as master and slave for each other on HP-UX PA-RISC and Itanium. A<->B
When using the "HP-UX PA-RISC 2.0, 64-bit only" release, we have problems with replication. Even though it should have (and "SHOW SLAVE STATUS" reports) the other server as master, the indexes reported in "SHOW SLAVE STATUS" is the same as the ones in "SHOW MASTER STATUS" on the same server. No errors are reported in the error files. The same problem exists using the "HP-UX 11.22 (IA64, 64bit)" release on Itanium. When the "HP-UX 11.11 (PA-RISC 1.1 and 2.0)" release is used, with the same configuration, on the same servers, everything works perfectly. We can not use this workaround on Itanium though, since there only exists one binary (64 bit) for Itanium. Values extracted on the hosts: A: bash-2.04# netstat -n -i Name Mtu Network Address Ipkts Ierrs Opkts Oerrs Coll lan0 1500 192.168.1.0 192.168.1.163 2922857 0 2532087 0 0 my.cnf: [mysqld] server-id=1 log-bin=/usr/local/mysql/data/query-bin master-port=3306 master-host=192.168.1.164 master-user=repluser master-password=repluser master-connect-retry=30 master.info: query-bin.001 1499005 192.168.1.164 repluser repluser 3306 30 SHOW SLAVE STATUS: | 192.168.1.164 | repluser | 3306 | 30 | query-bin.001 | 1499339 | A-relay-bin.001 | 1499379 | | Yes | Yes | | | 0 | | 0 | 1499339 | 1499379 | SHOW MASTER STATUS: | query-bin.001 | 1499339 | | | B: bash-2.04# netstat -n -i Name Mtu Network Address Ipkts Ierrs Opkts Oerrs Coll lan0 1500 192.168.1.0 192.168.1.164 2388705 0 2092210 0 0 lo0 4136 127.0.0.0 127.0.0.1 26767 0 26767 0 0 my.cnf: server-id=2 log-bin=/usr/local/mysql/data/query-bin master-port=3306 master-host=192.168.1.163 master-user=repluser master-password=repluser master-connect-retry=30 master.info: query-bin.001 681 192.168.1.163 repluser repluser 3306 30 SHOW SLAVE STATUS: | 192.168.1.163 | repluser | 3306 | 30 | query-bin.001 | 681 | B-relay-bin.001 | 1801 | | Yes | Yes | | | 0 | | 0 | 681 | 1801 | SHOW MASTER STATUS: | query-bin.001 | 681 | | | Running a simple master - slave replication (log-bin on A and master-host and so on on B), the slave on B will fail with the following reason, even if server A is shut down: 030919 16:11:37 Slave I/O thread: connected to master '[EMAIL PROTECTED]:3306', replication started in log 'FIRST' at position 4 030919 16:11:37 Error reading packet from server: Binary log is not open (server_errno=1236) 030919 16:11:37 Got fatal error 1236: 'Binary log is not open' from master when reading data from binary log There shouldn't be anything wrong with the configuration, since the same configuration works with the other binary. Has anyone else had the same problem? Is it a bug? Regards, Lars-Göran Forsberg ________________________________________________________________________ > lars-göran forsberg > software engineer > incomit ab > p.o. box 83 > se-651 03 karlstad > sweden > phone +46 54 17 67 36 > fax + 46 54 17 67 99 > [EMAIL PROTECTED] > www.incomit.com ________________________________________________________________________ -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
