Re: defunct mysql threads
I haven't examined the code of the client in detail, but it appears to disconnect where it should. The fact that I get a [mysqld defunct] proces even if I execute a query with the 'mysql' utility, I consider an implication of the server or the system. Am I correct in understanding that the binary distribution is a complete static binary that depends on no libraries installed on my system? And are there any tools I can use to find out what signals the mysqld processes are sending and receiving ? On Wed, Jul 02, 2003 at 08:38:42AM -0500, gerald_clark wrote: Does the client close the connection before exiting? Joshua Shapiro wrote: Hello, I am running the binary mysql 4.0.13 pclinux i686 with a linux 2.4.19 kernel. I have the problem that every time a client connects to the server and then exits, a defunct thread is left behind. Eventually the system prevents any further threads from being created. -- - - Service Observer * Canada-France-Hawaii Telescope - - -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: defunct mysql threads
Does the client close the connection before exiting? Joshua Shapiro wrote: Hello, I am running the binary mysql 4.0.13 pclinux i686 with a linux 2.4.19 kernel. I have the problem that every time a client connects to the server and then exits, a defunct thread is left behind. Eventually the system prevents any further threads from being created. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
defunct mysql threads
Hello, I am running the binary mysql 4.0.13 pclinux i686 with a linux 2.4.19 kernel. I have the problem that every time a client connects to the server and then exits, a defunct thread is left behind. Eventually the system prevents any further threads from being created. Even a simple command such as : bin/mysql mysql -e Select * from user will add the following to the log : 030701 13:11:28 16 Connect [EMAIL PROTECTED] on mysql 16 Query Select * from user 16 Quit and the error log remains unchanged, but there is another defunct mysqld process. The output of ps looks as follows UIDPID PPID C STIME TTY TIME CMD mysql 1650 1631 0 12:16 ttyp000:00:00 /usr/local/mysql/bin/mysqld --defaults-extra-file=/usr/local/mysql/data/my.cn mysql 1652 1650 0 12:16 ttyp000:00:00 /usr/local/mysql/bin/mysqld --defaults-extra-file=/usr/local/mysql/data/my.cn mysql 1653 1652 0 12:16 ttyp000:00:00 /usr/local/mysql/bin/mysqld --defaults-extra-file=/usr/local/mysql/data/my.cn mysql 1654 1652 0 12:16 ttyp000:00:00 /usr/local/mysql/bin/mysqld --defaults-extra-file=/usr/local/mysql/data/my.cn mysql 1655 1652 0 12:16 ttyp000:00:00 /usr/local/mysql/bin/mysqld --defaults-extra-file=/usr/local/mysql/data/my.cn mysql 1656 1652 0 12:16 ttyp000:00:00 /usr/local/mysql/bin/mysqld --defaults-extra-file=/usr/local/mysql/data/my.cn mysql 1657 1652 0 12:16 ttyp000:00:00 /usr/local/mysql/bin/mysqld --defaults-extra-file=/usr/local/mysql/data/my.cn mysql 1658 1652 0 12:16 ttyp000:00:00 /usr/local/mysql/bin/mysqld --defaults-extra-file=/usr/local/mysql/data/my.cn mysql 1659 1652 0 12:16 ttyp000:00:00 /usr/local/mysql/bin/mysqld --defaults-extra-file=/usr/local/mysql/data/my.cn mysql 1660 1652 0 12:16 ttyp000:00:00 /usr/local/mysql/bin/mysqld --defaults-extra-file=/usr/local/mysql/data/my.cn mysql 1664 1652 0 12:16 ttyp000:00:00 [mysqld defunct] mysql 1666 1652 0 12:17 ttyp000:00:00 [mysqld defunct] mysql 1718 1652 0 12:24 ttyp000:00:00 [mysqld defunct] mysql 1994 1652 0 13:11 ttyp000:00:00 [mysqld defunct] mysql 2005 1652 0 13:20 ttyp000:00:00 [mysqld defunct] Any help would be greatly appreciated, Joshua Shapiro -- - - Service Observer * Canada-France-Hawaii Telescope - - -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
