Bug #25731 Error in failure report
Submitted: 20 Jan 2007 12:38 Modified: 22 Jan 2007 12:38
Reporter: Mikael Ronström Email Updates:
Status: Duplicate Impact on me:
Category:MySQL Cluster: Cluster (NDB) storage engine Severity:S3 (Non-critical)
Version:5.1.14 OS:Any
Assigned to: CPU Architecture:Any

[20 Jan 2007 12:38] Mikael Ronström
When using a MySQL Server where either one hasn't done
mysql_install_db or the mysql database for some reason has
been corrupted, then the MySQL Server reports the error code
perror 157
says Illegal error code
When looking at the code one finds that 157 is HA_ERR_NO_CONNECTION
which is used by NDB handler mostly to report that it couldn't connect
to the cluster.
But it is also used for a number of other cases

How to repeat:
Start MySQL Server with running cluster but where
mysql_install_db hasn't been performed of MySQL Server datadir

Suggested fix:
Document the error code 157 (in perror and docs)
Fix a new error code for this error and document it (in perror and docs)
[21 Jan 2007 11:24] Valeriy Kravchuk
Thank you for a problem report. Please, specify the exact MySQL server versions affected (just for completeness).
[22 Jan 2007 12:38] Hartmut Holzgraefe
duplicate of the more general bug #25177