Bug #15456 No error messages or warnings when trying to connect to a
Submitted: 3 Dec 2005 11:03 Modified: 3 Feb 2006 14:29
Reporter: Hartmut Holzgraefe Email Updates:
Status: Can't repeat Impact on me:
None 
Category:MySQL Cluster: Cluster (NDB) storage engine Severity:S3 (Non-critical)
Version:5.0.16 OS:Linux (Linux/x86, MacOS X)
Assigned to: CPU Architecture:Any

[3 Dec 2005 11:03] Hartmut Holzgraefe
Description:
I tried to connect a MySQL server running on a Linux/x86 box to a PowerPC MAC.

This can't work due to the different byte order, but it doesn't give an error message either
(at least we couldn't see any in the mysqld error log or the cluster log). 

In this case (Linux->Mac) it was pretty obvious whats wrong but in a mixed architecture
Linux setup it might happen that one actually doesn't really know (or care) about the
architecture of a given box, so it would be nice to get some sort of message to get
on the right track.

How to repeat:
Set up a cluster on PowerPC or Sparc machines and try to connect an intel based MySQL server to it or vice versa.

Suggested fix:
Give an error message about incompatible byte order in either the mysql error log, the cluster log, or both
[8 Jan 2006 20:34] Hartmut Holzgraefe
can't reproduce with latest 5.0bk source, 
using a linux/x86 cluster and a linux/ppc mysqld

the pcc mysqld logs this in its error log just fine:

Configuration error: Could not alloc node id at 192.168.1.5 port 1186: Node does not have the same endianness as the management server.

have to re-test this with a MacOS/X box ...
[12 Jan 2006 4:25] Stewart Smith
This error message was introduced about a year ago. It should be the same for any platform. I don't see how OSX could be suppressing it (and yet letting other things into the mysql error log).