Hi List,

I am administering MySQL 4.0.13 on a Solaris 8 OS, and just this morning I encountered an error message like the one below. This is actually my first time to encounter such crash, I already tried searching for archives and the mysql doc to look for a solution but didn't find an exact answer. I am not sure also if I need to report a bug in Mysql website so I decided to report it first in the list. The way i understand it is that it already exceed the key_buffer_size of 16M which I stated in my .my.cnf, I tried to increase it to 30M but mysqld still doesn't start-up, it actually result in a segmentation fault error which has the same error message. For now, I do not know what to do but to upgrade if there's no way to resolve this problem.

I will really appreciate any help from the list....

I also include the settings for my .my.cnf for additional information. port = 3306 socket = /usr/local/mysql/var/mysql.sock #skip-locking set-variable = key_buffer=16M set-variable = max_allowed_packet=1M set-variable = table_cache=64 set-variable = sort_buffer=512K set-variable = net_buffer_length=8K set-variable = myisam_sort_buffer_size=8M log-bin server-id = 1

# Uncomment the following if you are using Innobase tables innodb_data_file_path = ibdata1:400M innodb_data_home_dir = /usr/local/mysql/var/ innodb_log_group_home_dir = /usr/local/mysql/var/ innodb_log_arch_dir = /usr/local/mysql/var/ set-variable = innodb_mirrored_log_groups=1 set-variable = innodb_log_files_in_group=3 set-variable = innodb_log_file_size=5M set-variable = innodb_log_buffer_size=8M innodb_flush_log_at_trx_commit=1 innodb_log_archive=0 set-variable = innodb_buffer_pool_size=16M set-variable = innodb_additional_mem_pool_size=2M set-variable = innodb_file_io_threads=4 set-variable = innodb_lock_wait_timeout=50

ERROR MESSAGES: 030922 10:32:37 mysqld started 030922 10:32:38 InnoDB: Started /usr/local/mysql/libexec/mysqld: ready for connections. Version: '4.0.13-log' socket: '/usr/local/mysql/var/mysql.sock' port: 3306 030923 7:30:06 Out of memory; Check if mysqld or some other process uses all available memory. If not you may have to use 'ulimit' to allow mysqld to use more memory or you can add more swap space 030923 7:30:06 Out of memory; Check if mysqld or some other process uses all available memory. If not you may have to use 'ulimit' to allow mysqld to use more memory or you can add more swap space 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=16777216 read_buffer_size=131072 sort_buffer_size=524280 max_used_connections=2 max_connections=100 threads_connected=1 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 80383 K bytes of memory Hope that's ok; if not, decrease some variables in the equation.

Thanks, Richard