From: Paul Schilling Date: March 17 1999 7:49pm Subject: MySQL 3.22.19b locking on Solaris 2.6 List-Archive: http://lists.mysql.com/mysql/444 Message-Id: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Between Feb 8th and last night we have experienced 4 lockups by the mysql server. Once locked up the safe_mysql and 1 mysqld process are still running but you can not connect to the server. A ps shows this: USER PID %CPU %MEM SZ RSS TT S START TIME COMMAND 17001 0.0 0.2 868 240 ? S Mar 09 0:00 /bin/sh /.../mysql/bin/safe_mysqld --log=/.../MYSQL/query.log 17012 0.0 9.31925617712 ? S Mar 09 45:12 /.../mysql-3.22.19b/libexec/mysqld --basedir=/.../mysql-3.22.19b --datadir=/.../mysql-3.22.19b/var --log=/.../MYSQL/query.log Each of the lockups occurred at about 1:20am after at least a week of mysql uptime. Nothing is croned for that time. It also happened on a different weekday each time. Other server information did not show anything out of the ordinary at this time. 3 of the 4 lockups were while running the prebuilt 3.21.33b Solaris 2.6 binary. The 4th was a mysql 3.22.19b I build w/ --with-debug and -ggdb. A gcore followed by gdb didn't show anything useful. The machine is a SPARC 20. If any more information is needed please contact me. Thanks in advanced for any help with this. -- Paul Schilling Biomedical Computing Group University of Wisconsin-Madison pschill@stripped Phone: (608) 265-3712