Hello.
>/usr/local/mysql/libexec/mysqld: ready for connections. > Version: '4.0.23' socket: '/tmp/mysql.sock' port: 3306 Source > distribution > 050125 15:58:44 mysqld restarted The mysqld_safe script writes to error log that mysqld was restarted. So I don't see any useful in error log (InnoDB messages may say something to Heikki Tuuri, but I think that there is no information for us, because server works fine about several hour sometimes). So we should follow recomendations at: http://dev.mysql.com/doc/mysql/en/crashing.html If your server is not heavy-loaded - try to enable debugging. See: http://dev.mysql.com/doc/mysql/en/debugging-server.html Then make the trace and core files (--debug --core-file). Check that there are no memory leaks with top command. Can you switch to 4.1.9 and try to reproduce the problem? Try running the tests in the mysql-test directory and the MySQL benchmarks to find out on which test crashes mysqld. Do you use InnoDB tables? If so, disable InnoDB. Also run mysqld with --skip-networking option to reduce problems related to buggy gethostbyname() implementations. -- For technical support contracts, goto https://order.mysql.com/?ref=ensita This email is sponsored by Ensita.NET http://www.ensita.net/ __ ___ ___ ____ __ / |/ /_ __/ __/ __ \/ / Gleb Paharenko / /|_/ / // /\ \/ /_/ / /__ [EMAIL PROTECTED] /_/ /_/\_, /___/\___\_\___/ MySQL AB / Ensita.NET <___/ www.mysql.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
