Dear TS Wong, please send the whole .err log to me [EMAIL PROTECTED]
What MySQL versions and what Linux kernel version you are running? Thank you, Heikki ----- Original Message ----- From: ""ts.wong"" <[EMAIL PROTECTED]> Newsgroups: mailing.database.myodbc Sent: Thursday, October 30, 2003 5:25 AM Subject: mySQL crash > ------=_NextPart_000_007E_01C39ECE.F3C28910 > Content-Type: text/plain; > charset="us-ascii" > Content-Transfer-Encoding: 7bit > > Dear, > > We encountered mysql (innodb) crash, and we can't recover the database > after the crash. Could you please help use to investigate the problem. > > Thanks in advance for your help. > > The following is copied from the mysql error log: > > 031027 17:16:12 mysqld started > 031027 17:16:12 Warning: setrlimit couldn't increase number of open > files to more than 1024 (request: 5130) > 031027 17:16:12 Warning: Changed limits: max_connections: 1014 > table_cache: 64 > 031027 17:16:13 InnoDB: Database was not shut down normally. > InnoDB: Starting recovery from log files... > InnoDB: Starting log scan based on checkpoint at > InnoDB: log sequence number 30 3440731580 > InnoDB: Doing recovery: scanned up to log sequence number 30 3445974016 > InnoDB: Doing recovery: scanned up to log sequence number 30 3449948971 > 031027 17:16:13 InnoDB: Starting an apply batch of log records to the > database... > InnoDB: Progress in percents: 0 1 031027 17:16:14 InnoDB: Assertion > failure in thread 12292 in file page0page.c line 450 > InnoDB: Failing assertion: page_cur_rec_insert(&cur2, > page_cur_get_rec(&cur1), mtr) > InnoDB: We intentionally generate a memory trap. > InnoDB: Send a detailed bug report to [EMAIL PROTECTED] > 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=1044480 > 031027 17:16:14 mysqld ended > > > > Our my.cnf is as below: > # Example mysql config file for small systems. > # > # This is for a system with little memory (<= 64M) where MySQL is only > used > # from time to time and it's important that the mysqld deamon > # doesn't use much resources. > # > # You can copy this file to > # /etc/my.cnf to set global options, > # mysql-data-dir/my.cnf to set server-specific options (in this > # installation this directory is /var/lib/mysql) or > # ~/.my.cnf to set user-specific options. > # > # One can in this file use all long options that the program supports. > # If you want to know which options a program support, run the program > # with --help option. > > # The following options will be passed to all MySQL clients > [client] > #password = your_password > #port = 3306 > socket = /var/lib/mysql/mysql.sock > > # Here follows entries for some specific programs > > # The MySQL server > [mysqld] > port = 3306 > socket = /var/lib/mysql/mysql.sock > skip-locking > key_buffer = 64M > max_allowed_packet = 1M > table_cache = 512 > sort_buffer_size = 4M > net_buffer_length = 2K > thread_stack = 64K > read_buffer_size = 1M > datadir=/mysql_main/data/ > max_tmp_tables = 64 > thread_cache_size = 5 > max_connections = 1024 > query_cache_limit = 16M > query_cache_size = 8M > > > # Don't listen on a TCP/IP port at all. This can be a security > enhancement, > # if all processes that need to connect to mysqld run on the same host. > # All interaction with mysqld must be made via Unix sockets or named > pipes. > # Note that using this option without enabling named pipes on Windows > # (using the "enable-named-pipe" option) will render mysqld useless! > # > #skip-networking > server-id = 1 > > # Uncomment the following if you want to log updates > #log-bin > > # Uncomment the following if you are NOT using BDB tables > skip-bdb > > # Uncomment the following if you are using InnoDB tables > innodb_data_home_dir = > innodb_data_file_path = > /mdr_smpp/data/innodb/ibdata1:4G;/mdr_smpp/data/innodb/ibdata2:4G; > /mysql_main/data/innodb/ibdata3:10M:autoextend:max:4G > innodb_log_group_home_dir = /mdr_http/data/innodb/log1/ > innodb_log_arch_dir = /mdr_http/data/innodb/log1/ > # You can set .._buffer_pool_size up to 50 - 80 % > # of RAM but beware of setting memory usage too high > innodb_buffer_pool_size = 128M > innodb_log_files_in_group = 4 > innodb_additional_mem_pool_size = 4M > # Set .._log_file_size to 25 % of buffer pool size > innodb_log_file_size = 32M > innodb_log_buffer_size = 8M > innodb_flush_log_at_trx_commit = 2 > innodb_lock_wait_timeout = 80 > #innodb_force_recovery=4 > > [mysqldump] > quick > max_allowed_packet = 16M > > [mysql] > no-auto-rehash > # Remove the next comment character if you are not familiar with SQL > #safe-updates > > [isamchk] > key_buffer = 8M > sort_buffer_size = 8M > > [myisamchk] > key_buffer = 8M > sort_buffer_size = 8M > > [mysqlhotcopy] > interactive-timeout > > > Regards, > > > > TS Wong > > > Tong Seng, Wong > Senior Software Engineer > Radius-ED Sdn Bhd (Head Office - Asia ) > Suite 3B-20-3, Level 20, Block 3B, > Plaza Sentral, Jalan Stesen Sentral 5, > KL Sentral, 50470 Kuala Lumpur > Malaysia > > Tel : +603 2260 3700 > Fax : +603 2260 3708 > www.radius-ed.com <http://www.radius-ed.com/> > > This message is intended only for the use of the person(s) to whom it is > addressed and may contain information that is priviledged or otherwise > protected from disclosure. If you are not the intended recipient, you > must not view, disseminate, use or copy this email. Kindly notify the > sender immediately, and delete this email from your system. Thank you. > > > > > > ------=_NextPart_000_007E_01C39ECE.F3C28910-- > -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
