Heikki, Yes, I'm running MySQL on 32-bit Linux.
I think maybe something had just gotten corrupted. MySQL restarted itself yesterday, with the following in the error log: 050407 16:24:49 [ERROR] 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=536870912 read_buffer_size=2093056 max_used_connections=201 max_connections=200 threads_connected=49 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 1342686 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. thd=0x59d064a0 Attempting backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong... frame pointer (ebp) is NULL, did you compile with -fomit-frame-pointer? Aborting backtrace! Trying to get some variables. Some pointers may be invalid and cause the dump to abort... thd->query at 0x59f907f8 is invalid pointer thd->thread_id=68571 The manual page at http://www.mysql.com/doc/en/Crashing.html contains information that should help you find out what is causing the crash. 050407 16:24:51 InnoDB: Database was not shut down normally! Unless you tell me different, I'll just plan on upgrading to 4.1.11 (I'm still running 4.1.8) -----Original Message----- From: Heikki Tuuri [mailto:[EMAIL PROTECTED] Sent: Friday, April 08, 2005 12:24 AM To: mysql@lists.mysql.com Subject: Re: Out of memory, but plenty of swap space left John, are you running on a 32-bit computer? Then, normally, the process size is limited to 2 GB. Best regards, Heikki Tuuri Innobase Oy Foreign keys, transactions, and row level locking for MySQL InnoDB Hot Backup - a hot backup tool for InnoDB which also backs up MyISAM tables http://www.innodb.com/order.php ----- Original Message ----- From: ""Jon Wagoner"" <[EMAIL PROTECTED]> Newsgroups: mailing.database.myodbc Sent: Thursday, April 07, 2005 7:31 PM Subject: Out of memory, but plenty of swap space left > Recently I've been getting error 1041 at times, which gives the message > to update the ulimit or add swap space. =20 > > This is a dedicated MySQL server, so I have no ulimit set for MySQL. > According to /proc/meminfo I have over 1GB of swap free. > Mem: 2118533120 2067628032 50905088 0 19677184 1659768832 > Swap: 1998733312 686882816 1311850496 > MemTotal: 2068880 kB > MemFree: 49712 kB > MemShared: 0 kB > Buffers: 19216 kB > Cached: 1320684 kB > SwapCached: 300184 kB > Active: 943996 kB > Inactive: 1008424 kB > HighTotal: 1179484 kB > HighFree: 2044 kB > LowTotal: 889396 kB > LowFree: 47668 kB > SwapTotal: 1951888 kB > SwapFree: 1281104 kB > > The mysqld section of my.cnf contains the following: > > log-bin > server-id =3D 106 > basedir =3D /usr > datadir =3D /var/lib/mysql > tmpdir =3D /tmp > language =3D /usr/share/mysql/english > skip-locking > set-variable =3D key_buffer=3D512M > set-variable =3D max_allowed_packet=3D1G > set-variable =3D table_cache=3D3072 > set-variable =3D sort_buffer=3D2M > set-variable =3D record_buffer=3D2M > set-variable =3D thread_cache=3D8 > set-variable =3D thread_concurrency=3D8 > set-variable =3D myisam_sort_buffer_size=3D64M > set-variable =3D thread_stack=3D128K > set-variable =3D open_files_limit=3D8192 > set-variable =3D tmp_table_size=3D50M > max_tmp_tables =3D 100 > innodb_data_home_dir =3D /var/lib/mysql/ > innodb_data_file_path =3D ibdata1:10M:autoextend > innodb_log_group_home_dir =3D /var/lib/mysql/ > innodb_log_arch_dir =3D /var/lib/mysql/ > set-variable =3D innodb_buffer_pool_size=3D384M > set-variable =3D innodb_additional_mem_pool_size=3D20M > set-variable =3D innodb_log_file_size=3D5M > set-variable =3D innodb_log_buffer_size=3D8M > innodb_flush_log_at_trx_commit=3D1 > set-variable =3D innodb_lock_wait_timeout=3D50 > > long_query_time=3D30 > query_cache_limit=3D1M > query_cache_size=3D64M > query_cache_type=3D1 > max_connections=3D200 > > Does anyone have any suggestions as to why I'm getting out of memory > errors? Do I have some of the settings wrong? > If it matters, I have about 50GB worth of data, split between InnoDB and > MyISAM tables. I last got the error updating records in one of the > MyISAM tables which was about 1MB in size. > > -- > MySQL General Mailing List > For list archives: http://lists.mysql.com/mysql > To unsubscribe: > http://lists.mysql.com/[EMAIL PROTECTED] > -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
