Bug #8685 Server crash caused by 'show status where variable_name like "%database%"'
Submitted: 22 Feb 2005 13:42 Modified: 24 Feb 2005 16:45
Reporter: Joerg Bruehe Email Updates:
Status: Closed Impact on me:
Category:MySQL Server Severity:S1 (Critical)
Version:5.0.3-pre OS:Some Unix, 64 bit only
Assigned to: Jani Tolonen CPU Architecture:Any

[22 Feb 2005 13:42] Joerg Bruehe
Test 'information_schema' fails due to a server crash:

information_schema             [ fail ]

Errors are (from /export/spare/mysqldev/sunfire100c-64bit/test/mysql-debug-5.0.3-alpha-sun-solaris2.8-sparc-64bit/mysql-test/var/log/mysqltest-time) :
/export/spare/mysqldev/sunfire100c-64bit/test/mysql-debug-5.0.3-alpha-sun-solaris2.8-sparc-64bit/bin/mysqltest: At line 347: query 'show status where variable_name like "%database%"' failed: 2013: Lost connection to MySQL server during query
(the last lines may be the most important ones)

Ending Tests
Shutting-down MySQL daemon

master not cooperating with mysqladmin, will try manual kill
./mysql-test-run: kill: no such process
master refused to die. Sending SIGKILL
./mysql-test-run: kill: no such process
Master shutdown finished
Slave shutdown finished
information_schema_inno        [ pass ]

This occurred (until now) on hpita2-64bit (HP-UX), octane2-64bit (IRIX), and sunfire100c-64bit (Solaris) only. As this 'debug' build failed on some other platforms, more might show up in future runs.

How to repeat:
Build + test.
[24 Feb 2005 16:45] Jani Tolonen
Thank you for your bug report. This issue has been committed to our
source repository of that product and will be incorporated into the
next release.

If necessary, you can access the source repository and build the latest
available version, including the bugfix, yourself. More information 
about accessing the source trees is available at