MySQL Bugs: #28790: Error in my_thread_global

Bug #28790	Error in my_thread_global_end(): 1 threads didn't exit
Submitted:	30 May 2007 20:18	Modified:	30 May 2007 20:35
Reporter:	GIovanni M	Email Updates:
Status:	Duplicate	Impact on me:	None
Category:	MySQL Server: Installing	Severity:	S1 (Critical)
Version:	5.0.41	OS:	Linux
Assigned to:		CPU Architecture:	Any
Tags:	mysql_install_db

Description:
NOTE: I'm using Linux Debian etch 4.0 (last version with all patches and updates)

I can configure,make and install mysql 5.0.41 but When i run mysql_install_db --user=mysql the next error appears:

ws:~# /usr/local/mysql/bin/mysql_install_db --user=mysql
Installing MySQL system tables...
Error in my_thread_global_end(): 1 threads didn't exit
OK
Filling help tables...
Error in my_thread_global_end(): 1 threads didn't exit
OK

To start mysqld at boot time you have to copy
support-files/mysql.server to the right place for your system

PLEASE REMEMBER TO SET A PASSWORD FOR THE MySQL root USER !
To do so, start the server, then issue the following commands:
/usr/local/mysql/bin/mysqladmin -u root password 'new-password'
/usr/local/mysql/bin/mysqladmin -u root -h 127.0.1.1 password 'new-password'
See the manual for more instructions.
You can start the MySQL daemon with:
cd /usr/local/mysql ; /usr/local/mysql/bin/mysqld_safe &

You can test the MySQL daemon with mysql-test-run.pl
cd mysql-test ; perl mysql-test-run.pl

Please report any problems with the /usr/local/mysql/bin/mysqlbug script!

The latest information about MySQL is available on the web at
http://www.mysql.com
Support MySQL by buying support/licenses at http://shop.mysql.com

How to repeat:

4)# /usr/local/mysql/bin/mysql_install_db --user=mysql

Please do not submit the same bug more than once. An existing bug report already describes this very problem. Even if you feel that your issue is somewhat different, the resolution is likely
to be the same. Because of this, we hope you add your comments to the original bug instead.

Thank you for your interest in MySQL.

Duplicate of bug #27970