Re: mysqldump different on 32bit vs. 64bit?

Posted by TrevorH on 2012/1/24 12:00:54
It just means that you have binary logging turned on on one server and not on the other

mysqldump different on 32bit vs. 64bit?

Posted by knebb on 2012/1/24 11:46:10
Hi all,

I'm having a strange issue with mysqldump.

I've two MySQL servers running independend from each other. One is CentOS 5.7 32bit and the other is CentOS 5.7 64bit. RPM command shows both are same versions:
[root@mysqla ~]# rpm -qa|grep mysql
mysql-5.0.77-4.el5_6.6
php-mysql-5.1.6-27.el5_7.4
mysql-server-5.0.77-4.el5_6.6

And:
[root@mysqlb ~]# rpm -qa|grep mysql
perl-DBD-mysql-4.012-1.el5.rf
mysql-server-5.0.77-4.el5_6.6
mysql-5.0.77-4.el5_6.6

My script looks like this:
[root@mysqla ~]# cat backup_mysql.sh
#!/bin/bash
mysqldump -v --opt --master-data --lock-all-tables --triggers --routines --flush-logs --delete-master-logs  -u root -pxXxXx --all-databases > mysql.dump


On host a this runs fine, host b it connects but does not dump anything.

Being in mysql it shows different versions:
Welcome to the MySQL monitor.  Commands end with ; or \g.
Your MySQL connection id is 933651
Server version: 5.0.77 Source distribution

Type 'help;' or '\h' for help. Type '\c' to clear the buffer.

mysql> select @@version;
+-----------+
| @@version |
+-----------+
| 5.0.77    |
+-----------+
1 row in set (0.00 sec)
mysql> select @@version;
+------------+
| @@version  |
+------------+
| 5.0.77-log |
+------------+
1 row in set (0.00 sec)


The only difference I see is the "-log" appendix to the server version.

So could someone explain what the "-log" means and why the identical mysqldump commands are NOT doing the same?

And, there is no major difference in /etc/my.cnf nor in ~/.my.cnf.

This Post was from: https://www.centos.org/newbb/viewtopic.php?forum=41&topic_id=35458