Hi, We have major problems with one of our database machines the past few weeks. We've replaced the complete machine about 3 times now, with different memory... no luck. So I doubt it's hardware. It's a SuperMicro SuperServer 6014H-82 ... dual Xeon 3.0, 8GB DDR2-RAM, 4x73GB Maxtor SCSI (RAID10)
The symptoms are that MySQL is constantly (eg. within every 30 minutes) getting signal 11's according to the logfile, and is restarting. 060613 08:47:25 mysqld started 060613 8:47:26 InnoDB: Started; log sequence number 0 144990980 060613 8:47:26 [Note] /usr/libexec/mysqld: ready for connections. Version: '5.0.21-debug' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution mysqld got signal 11; This could be because you hit a bug. It is also possible that this binary or one of the libraries it was linked against is corrupt, improperly built, or misconfigured. This error can also be caused by malfunctioning hardware. We will try our best to scrape up some info that will hopefully help diagnose the problem, but since we have already crashed, something is definitely wrong and this may fail. key_buffer_size=67108864 read_buffer_size=6287360 max_used_connections=22 max_connections=750 threads_connected=19 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 6206509 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Writing a core file The memory is OK, it's a machine dedicated to MySQL with 8GB of RAM. We're now running on Fedora Core 5 on x86_64 platform. We were running the latest Fedora 5 RPM's (mysql-5.0.21-2.FC5.1), but since they are compiled with --without-debug I've rebuild it from the SRPM with --with-debug=full When running this, I got no crash... but couldn't run it too long, since the machine became very slow and a lot of clients could no longer connect after sometime due to timeout. When running with --skip-safemalloc I got the crashes as well. I'm running with --core-file and it states 'Writing a core file' in the logs... but it doesn't write it anywhere ! I've also added --core-file-size=1000000 and even changed system-ulimit for corefiles to unlimited. It just never writes a core file :(( Also tried starting mysqld directly under user mysql, to bypass any possible problem with setuid and not being able to dump core files... no success. If someone could help me with this .... maybe I'm missing a step :) Thanks in advance ! Regards, -- WideXS http://www.widexs.nl Wouter de Jong System-Administrator Tel +31 (0)23 5698070 Fax +31 (0)23 5698099 Bijlmermeerstraat 62, 2131 HG HOOFDDORP, NL -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
