MySQL Bugs: #637: failure to create master.pid

Bug #637	failure to create master.pid
Submitted:	11 Jun 2003 11:18	Modified:	4 Jul 2003 7:56
Reporter:	David Lovering	Email Updates:
Status:	Not a Bug	Impact on me:	None
Category:	MySQL Server: Installing	Severity:	S2 (Serious)
Version:	4.0.13	OS:	Linux (RedHat Linux 9.0)
Assigned to:	Bugs System	CPU Architecture:	Any

Description:
During the 'make test' sequence, all the tests successfully completed -- until immediately following the 'create' test.  At this point the following message appeared --

ERROR: /opt/src/mysql-4.0.13/mysql-test/var/run/master.pid was not created in 30 seconds;  Aborting

Since this was done through a carefully edited install script (based upon MySQL recommendations), I do not think that a 'fat-finger' issue is involved -- particularly as all previous steps/compile elements concluded properly.

I am concerned, as this install script is being prepared for possible use in other machines, and I don't want to have odd failures appearing elsewhere.  Moreover, an inability to spawn a mysqld process would be lethal to the server environment in which this is to operate.

How to repeat:
Using the 4.0.13 tar.gz file
/usr/sbin/useradd mysql
/usr/sbin/groupadd mysql
mkdir /var/lib/mysql
chown -R mysql /var/lib/mysql
chgrp -R mysql /var/lib/mysql
./configure \
--prefix=/usr/local/mysql \
--with-unix-socket-path=/var/lib/mysql/mysql.sock \
--localstatedir=/var/lib/mysql
make
make test
... generates error message noted above, and then aborts

Suggested fix:
Either (a) augment your instructions as how how to prepare the socket file and its parent directory(ies), (b) modify the make script(s), or (c) provide follow-up hints as to what sort of remedial action should be pursued if this error appears.

Thank you for taking the time to report a problem.  Unfortunately
you are not using a current version of the product your reported a
problem with -- the problem might already be fixed. Please download
a new version from http://www.mysql.com/downloads/

If you are able to reproduce the bug with one of the latest versions,
please change the version on this bug report to the version you
tested and change the status back to "Open".  Again, thank you for
your continued support of MySQL.

We don't plan to fix this bug in mysql-4.0.
It is already fixed in newer version mysql-4.1.

To launch 'make test' you have to add option --with-extra-charset=complex to configure.. We will add this note to manual soon..

In fact, you only need -with-extra-charset=complex for ctype_xxx tests to work.
Unfortunately in MySQL 4.0 there is no easy way to determine what charsets are available from the test - to skip tests intelligently (like InnoDB or BDB tests are skipped).
It's done (for a long time already) in 4.1

As for 4.0 - you can simply remove - or rename ctype_xxx tests (to e.g. *.test-disabled)