Re: MySql - crashes daily
Hi. Can you show me some of your critical system logs? David Yeung, In China, Beijing. My First Blog:http://yueliangdao0608.cublog.cn My Second Blog:http://yueliangdao0608.blog.51cto.com My Msn: yueliangdao0...@gmail.com 2010/12/7 Raj Shekhar rajl...@rajshekhar.net In infinite wisdom Basil Daoust bdao...@lemonfree.com wrote: Any help greatly appreciated. Our mysql is restarting a LOT! Here is what is in the log, it doesn't seem to give much help. Do you have the coredump from this crash? If yes, can you load the core dump into gdb and run bt (backtrace) and see what it produces? Check this link to see what steps are required http://ronaldbradford.com/blog/how-to-crash-mysqld-intentionally-2010-03-05/ -- Raj Shekhar - If there's anything more important than my ego around, I want it caught and shot now. - Read the latest at my blog: Humor in the bookstore http://rajshekhar.net/blog/archives/391-Humor-in-the-bookstore.html -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/mysql?unsub=yueliangdao0...@gmail.com
Re: MySql - crashes daily
In infinite wisdom Basil Daoust bdao...@lemonfree.com wrote: Any help greatly appreciated. Our mysql is restarting a LOT! Here is what is in the log, it doesn't seem to give much help. Do you have the coredump from this crash? If yes, can you load the core dump into gdb and run bt (backtrace) and see what it produces? Check this link to see what steps are required http://ronaldbradford.com/blog/how-to-crash-mysqld-intentionally-2010-03-05/ -- Raj Shekhar - If there's anything more important than my ego around, I want it caught and shot now. - Read the latest at my blog: Humor in the bookstore http://rajshekhar.net/blog/archives/391-Humor-in-the-bookstore.html -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
MySql - crashes daily
Any help greatly appreciated. Our mysql is restarting a LOT! Here is what is in the log, it doesn't seem to give much help. --start of log-- InnoDB: Warning: a long semaphore wait: 101203 15:12:40 - 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=1073741824 read_buffer_size=16773120 max_used_connections=601 max_connections=600 threads_connected=27 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 20706971 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. thd=(nil) 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 is NULL, did you compile with -fomit-frame-pointer? Aborting backtrace! 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. --end of log-- So before you ask if we have 20G of memory we are running this on amazons : High-Memory Quadruple Extra Large Instance 68.4 GB of memory, 26 EC2 Compute Units (8 virtual cores with 3.25 EC2 Compute Units each), 1690 GB of local instance storage, 64-bit platform We are using Fedora Core 8, with MySQL 5.0.45. these mysql packages are installed. mysql.x86_64 5.0.45-6.fc8 installed mysql-libs.x86_64 5.0.45-6.fc8 installed mysql-server.x86_64 5.0.45-6.fc8 installed It seems odd to me that we get a InnoDB error when this server doesn't have a single InnoDB table. I also did notice the max_used_connections but from the last 20 or so restarts only 2 hit 601, others where as low as approx 150. I'm hopeful that someone has a idea or two. Basil -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
Re: MySql - crashes daily
On Fri, December 3, 2010 14:11, Basil Daoust wrote: Any help greatly appreciated. Our mysql is restarting a LOT! Here is what is in the log, it doesn't seem to give much help. --start of log-- InnoDB: Warning: a long semaphore wait: 101203 15:12:40 - 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=1073741824 read_buffer_size=16773120 max_used_connections=601 max_connections=600 threads_connected=27 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 20706971 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. thd=(nil) 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 is NULL, did you compile with -fomit-frame-pointer? Aborting backtrace! 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. --end of log-- So before you ask if we have 20G of memory we are running this on amazons : High-Memory Quadruple Extra Large Instance 68.4 GB of memory, 26 EC2 Compute Units (8 virtual cores with 3.25 EC2 Compute Units each), 1690 GB of local instance storage, 64-bit platform We are using Fedora Core 8, with MySQL 5.0.45. these mysql packages are installed. mysql.x86_64 5.0.45-6.fc8 installed mysql-libs.x86_64 5.0.45-6.fc8 installed mysql-server.x86_64 5.0.45-6.fc8 installed It seems odd to me that we get a InnoDB error when this server doesn't have a single InnoDB table. I also did notice the max_used_connections but from the last 20 or so restarts only 2 hit 601, others where as low as approx 150. I'm hopeful that someone has a idea or two. Basil You might check your my.cnf file to see if InnoDB engine is enabled. SOURCE IP FROM HEADER: *Please block this account's access to the * *internet until its cleaned up. We are basing * *this on an analysis of the header NOT the FROM* *address. * -- William R. Mussatto Systems Engineer http://www.csz.com 909-920-9154
MySQL crashes
Anybody have any idea why MySQL would start to have this error message every 4 or so days at midnight: Connection error: Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2) This just started happening a little more than 2 weeks ago. The server has been running fine for almost two years. MySQL is on a Linux system. There are about 750 dbs and accessed by approximately half that number websites (375). Half of the websites are on a different server than the MySQL server. Charlene -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
Re: MySQL crashes
Charlene, You should check the mysql error log and if there isn't a message about the cause there you may want to check /var/log/syslog for mysql being killed by oomkiller. Tyler On 6/21/10 11:11 AM, Charlene wrote: Anybody have any idea why MySQL would start to have this error message every 4 or so days at midnight: Connection error: Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2) This just started happening a little more than 2 weeks ago. The server has been running fine for almost two years. MySQL is on a Linux system. There are about 750 dbs and accessed by approximately half that number websites (375). Half of the websites are on a different server than the MySQL server. Charlene -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
Re: MySQL crashes
Charlene wrote: Anybody have any idea why MySQL would start to have this error message every 4 or so days at midnight: Do look at the logs, but if the error always occurs at midnight, you might look for a disk backup or compression program that's scheduled to run than and accesses the database files incompatibly. Cheers, Ann -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
Re: MySQL crashes
you can stop your Mysql server (the program) and delete the file mysql.sock and the try to start. 2010/6/21 Tyler Poland tpol...@engineyard.com Charlene, You should check the mysql error log and if there isn't a message about the cause there you may want to check /var/log/syslog for mysql being killed by oomkiller. Tyler On 6/21/10 11:11 AM, Charlene wrote: Anybody have any idea why MySQL would start to have this error message every 4 or so days at midnight: Connection error: Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2) This just started happening a little more than 2 weeks ago. The server has been running fine for almost two years. MySQL is on a Linux system. There are about 750 dbs and accessed by approximately half that number websites (375). Half of the websites are on a different server than the MySQL server. Charlene -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/mysql?unsub=guifre.bo...@gmail.com -- Guifre Bosch Fabregas Tlf.: 687911075
Mysql crashes, do not understand backtrace
On one of the servers we maintain mysql recently crashed. In safe mode (innodb_force_recovery = 4) it runs but then you can't do any mutations to the databases. When we try to start it in normal mode it crashes and we do not really understand the backtrace. We eventually ended up in flushing all the databases and start adding, backups of, them one-by-one except for one (used by openX 2.4.4). It now runs normally with the backups, but could someone give us more insight in what has happend and what could be the cause of it? The server is a: Intel(R) Xeon(R) CPU 3060 @ 2.40GHz with 4 GB RAM running: Linux 2.6.15-1.2054_FC5smp #1 SMP Tue Mar 14 16:05:46 EST 2006 i686 i686 i386 GNU/Linux mysql version: mysql Ver 14.12 Distrib 5.0.27, for redhat-linux-gnu (i686) using readline 5.0 mysqld log: Number of processes running now: 0 100211 11:55:23 mysqld restarted 100211 11:55:23 InnoDB: Database was not shut down normally! InnoDB: Starting crash recovery. InnoDB: Reading tablespace information from the .ibd files... InnoDB: Restoring possible half-written data pages from the doublewrite InnoDB: buffer... 100211 11:55:23 InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 3 319452546. InnoDB: Doing recovery: scanned up to log sequence number 3 320533610 InnoDB: 1 transaction(s) which must be rolled back or cleaned up InnoDB: in total 159 row operations to undo InnoDB: Trx id counter is 0 25336832 100211 11:55:23 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 InnoDB: Apply batch completed InnoDB: Starting in background the rollback of uncommitted transactions 100211 11:55:23 InnoDB: Rolling back trx with id 0 25327402, 159 rows to undo 100211 11:55:23 InnoDB: Started; log sequence number 3 320533610 InnoDB: Dump of the tablespace extent descriptor: len 40; hex 639114ee23260004febfafbeaafffbef; asc c #; InnoDB: Serious error! InnoDB is trying to free page 17905 InnoDB: though it is already marked as free in the tablespace! InnoDB: The tablespace free space info is corrupt. InnoDB: You may need to dump your InnoDB tables and recreate the whole InnoDB: database! InnoDB: Please refer to InnoDB: http://dev.mysql.com/doc/refman/5.0/en/forcing-recovery.html InnoDB: about forcing recovery. 100211 11:55:23InnoDB: Assertion failure in thread 2960472992 in file fsp0fsp.c line 2980 InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to http://bugs.mysql.com. InnoDB: If you get repeated assertion failures or crashes, even InnoDB: immediately after the mysqld startup, there may be InnoDB: corruption in the InnoDB tablespace. Please refer to InnoDB: http://dev.mysql.com/doc/refman/5.0/en/forcing-recovery.html InnoDB: about forcing recovery. 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=134217728 read_buffer_size=131072 max_used_connections=0 max_connections=100 threads_connected=0 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 348671 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. thd=(nil) 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... Cannot determine thread, fp=0xb0752308, backtrace may not be correct. Stack range sanity check OK, backtrace follows: 0x8178043 0x83cf830 0x8381ad3 0x8387768 0x836739d 0x83682be 0x8360c19 0x833c928 0x839edab 0x4073b6 0x35333e New value of fp=(nil) failed sanity check, terminating stack trace! Please read http://dev.mysql.com/doc/mysql/en/Using_stack_trace.html and follow instructions on how to resolve the stack trace. Resolved stack trace is much more helpful in diagnosing the problem, so please do resolve it 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. 100211 11:55:23 mysqld ended When running resolve_stack_dump -s /tmp/mysqld.sym -n mysqld.stack we get: 0x8178043 handle_segfault + 643 0x83cf830 fsp_header_init + 9408 0x8381ad3 btr_free_externally_stored_field + 995 0x8387768
RE: Mysql crashes, do not understand backtrace
When running with force-recovery, the database will indeed be read-only. This is on purpose. When you have an error of this nature, the procedure is to find a force-recovery level which allows you to start mysql, then export all the data. Then you can shut down mysql, wipe your innodb tablespace and log file, restart mysql in a clean state, then re-import your data. Please proceede with caution though; if possible make a backup of the mysql data directory in its current corrupted state before you delete anything. Regards Gavin Towey -Original Message- From: Wesley Wajon [mailto:wes...@oktober.nl] Sent: Monday, February 15, 2010 6:30 AM To: mysql@lists.mysql.com Subject: Mysql crashes, do not understand backtrace On one of the servers we maintain mysql recently crashed. In safe mode (innodb_force_recovery = 4) it runs but then you can't do any mutations to the databases. When we try to start it in normal mode it crashes and we do not really understand the backtrace. We eventually ended up in flushing all the databases and start adding, backups of, them one-by-one except for one (used by openX 2.4.4). It now runs normally with the backups, but could someone give us more insight in what has happend and what could be the cause of it? The server is a: Intel(R) Xeon(R) CPU 3060 @ 2.40GHz with 4 GB RAM running: Linux 2.6.15-1.2054_FC5smp #1 SMP Tue Mar 14 16:05:46 EST 2006 i686 i686 i386 GNU/Linux mysql version: mysql Ver 14.12 Distrib 5.0.27, for redhat-linux-gnu (i686) using readline 5.0 mysqld log: Number of processes running now: 0 100211 11:55:23 mysqld restarted 100211 11:55:23 InnoDB: Database was not shut down normally! InnoDB: Starting crash recovery. InnoDB: Reading tablespace information from the .ibd files... InnoDB: Restoring possible half-written data pages from the doublewrite InnoDB: buffer... 100211 11:55:23 InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 3 319452546. InnoDB: Doing recovery: scanned up to log sequence number 3 320533610 InnoDB: 1 transaction(s) which must be rolled back or cleaned up InnoDB: in total 159 row operations to undo InnoDB: Trx id counter is 0 25336832 100211 11:55:23 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 InnoDB: Apply batch completed InnoDB: Starting in background the rollback of uncommitted transactions 100211 11:55:23 InnoDB: Rolling back trx with id 0 25327402, 159 rows to undo 100211 11:55:23 InnoDB: Started; log sequence number 3 320533610 InnoDB: Dump of the tablespace extent descriptor: len 40; hex 639114ee23260004febfafbeaafffbef; asc c #; InnoDB: Serious error! InnoDB is trying to free page 17905 InnoDB: though it is already marked as free in the tablespace! InnoDB: The tablespace free space info is corrupt. InnoDB: You may need to dump your InnoDB tables and recreate the whole InnoDB: database! InnoDB: Please refer to InnoDB: http://dev.mysql.com/doc/refman/5.0/en/forcing-recovery.html InnoDB: about forcing recovery. 100211 11:55:23InnoDB: Assertion failure in thread 2960472992 in file fsp0fsp.c line 2980 InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to http://bugs.mysql.com. InnoDB: If you get repeated assertion failures or crashes, even InnoDB: immediately after the mysqld startup, there may be InnoDB: corruption in the InnoDB tablespace. Please refer to InnoDB: http://dev.mysql.com/doc/refman/5.0/en/forcing-recovery.html InnoDB: about forcing recovery. 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=134217728 read_buffer_size=131072 max_used_connections=0 max_connections=100 threads_connected=0 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 348671 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. thd=(nil) 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... Cannot determine thread, fp=0xb0752308, backtrace may not be correct. Stack range sanity check OK, backtrace follows: 0x8178043 0x83cf830 0x8381ad3 0x8387768 0x836739d 0x83682be
Re: Mysql Crashes I/O error...
This was a faulty disk after all. I just did not see any errors, when running smartd. However, they showed up when looking on the system log. I am currently replacing the disk. Thank you, George Crewe On 8/3/07, George F. Crewe [EMAIL PROTECTED] wrote: Hello everybody, I am looking for some help on my mysql server crashes. I run version 5.0.27 on Fedora 6. However, suddenly mysql server starting crashing. I revised the log and it is telling me that is having a input/output operating system error on a read operation. The error shows up like this on the log: 070803 00:29:12 mysqld started 070803 0:29:12 InnoDB: Started; log sequence number 0 210331564 070803 0:29:12 [Note] /usr/libexec/mysqld: ready for connections. Version: '5.0.27' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution InnoDB: Error: tried to read 16384 bytes at offset 0 29802496. InnoDB: Was only able to read -1. 070803 0:29:43 InnoDB: Operating system error number 5 in a file operation. InnoDB: Error number 5 means 'Input/output error'. InnoDB: Some operating system error numbers are described at InnoDB: http://dev.mysql.com/doc/refman/5.0/en/operating-system-error-codes.html InnoDB: File operation call: 'read'. InnoDB: Cannot continue operation. I check my disk with smartd utility and it passes the test. I do not know where to look. Any help will be greatly appreciated. George Crewe -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Mysql Crashes I/O error...
Hello everybody, I am looking for some help on my mysql server crashes. I run version 5.0.27 on Fedora 6. However, suddenly mysql server starting crashing. I revised the log and it is telling me that is having a input/output operating system error on a read operation. The error shows up like this on the log: 070803 00:29:12 mysqld started 070803 0:29:12 InnoDB: Started; log sequence number 0 210331564 070803 0:29:12 [Note] /usr/libexec/mysqld: ready for connections. Version: '5.0.27' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution InnoDB: Error: tried to read 16384 bytes at offset 0 29802496. InnoDB: Was only able to read -1. 070803 0:29:43 InnoDB: Operating system error number 5 in a file operation. InnoDB: Error number 5 means 'Input/output error'. InnoDB: Some operating system error numbers are described at InnoDB: http://dev.mysql.com/doc/refman/5.0/en/operating-system-error-codes.html InnoDB: File operation call: 'read'. InnoDB: Cannot continue operation. I check my disk with smartd utility and it passes the test. I do not know where to look. Any help will be greatly appreciated. George Crewe -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
mysql crashes on drop database?
Hi, Each night I replicate a server running a 4.1 version of mysql via mysqldump and then import to a box running a 5.0.18-standard. It has been working well for some four or five months. Suddenly, the job started failing during the import. After stepping through the job, I determined that attempting to drop the first database causes mysql to crash. There are about seven or eight tables in said database, mostly empty, with about five or six records total in the database in question mysql drop database AccountingAdminDB; ERROR 2013 (HY000): Lost connection to MySQL server during query Per the mysql docs, I first tried rebooting the machine, to no avail. Interestingly, I can read all of the records in the all of the associated files. Check table on each table did not turn up anything. File permissions look ok. I use innodb file per table for most tables. The data directories and subordinates all use mysql.mysql as the owner and group. The data files are rw by owner. A mysql.error.log file is being generated: 060901 9:45:18 InnoDB: Database was not shut down normally! InnoDB: Starting crash recovery. InnoDB: Reading tablespace information from the .ibd files... InnoDB: Restoring possible half-written data pages from the doublewrite InnoDB: buffer... 060901 9:45:24 InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 68 3744135056. InnoDB: Doing recovery: scanned up to log sequence number 68 3744135056 InnoDB: Last MySQL binlog file position 0 0, file name 060901 9:45:24 InnoDB: Started; log sequence number 68 3744135056 060901 9:45:24 [Note] /usr/sbin/mysqld: ready for connections. Version: '5.0.18-standard' socket: '/srv/mysql/lx07sock' port: 3307 MySQL Community Edition - Standard (GPL) InnoDB: Error: trying to access page number 464309120 in space 0, InnoDB: space name /srv/mysql/lx07/ibdata1, InnoDB: which is outside the tablespace bounds. InnoDB: Byte offset 0, len 16384, i/o type 10 060901 10:03:37InnoDB: Assertion failure in thread 2934508464 in file fil0fil.c line 3869 InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to http://bugs.mysql.com. InnoDB: If you get repeated assertion failures or crashes, even InnoDB: immediately after the mysqld startup, there may be InnoDB: corruption in the InnoDB tablespace. Please refer to InnoDB: http://dev.mysql.com/doc/mysql/en/Forcing_recovery.html InnoDB: about forcing recovery. 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=268435456 read_buffer_size=8384512 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 = 2719343 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. thd=0x8a40170 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... Cannot determine thread, fp=0xaee8cd1c, backtrace may not be correct. Stack range sanity check OK, backtrace follows: 0x815bbb0 0xe420 0x82f2c3e 0x82f2c3e 0x82ea23c 0x8308090 0x83074ee 0x82b5e4f 0x826ff01 0x82a7ed6 0x82a813c 0x82a825c 0x8282ec0 0x8282bfb 0x82979e2 0x820cd73 0x81fffdb 0x8212f00 0x82128b4 0x8211cce 0x8211509 0x81728bf Stack trace seems successful - bottom reached Please read http://dev.mysql.com/doc/mysql/en/Using_stack_trace.html and follow instructions on how to resolve the stack trace. Resolved stack trace is much more helpful in diagnosing the problem, so please do resolve it Trying to get some variables. Some pointers may be invalid and cause the dump to abort... thd-query at 0x8a5fde8 = drop database AccountingAdminDB thd-thread_id=57 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. 060901 10:03:37 InnoDB: Database was not shut down normally! InnoDB: Starting crash recovery. InnoDB: Reading tablespace information from the .ibd files... InnoDB: Restoring possible half-written data pages from the doublewrite InnoDB: buffer... 060901 10:03:37 InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 68 3744135066. InnoDB: Doing recovery: scanned up to log sequence number 68 3744135066 InnoDB: Last MySQL binlog file position 0 0, file name 060901 10:03:37 InnoDB: Started; log sequence number 68 3744135066 060901 10:03:38 [Note] /usr/sbin/mysqld: ready for connections. Version: '5.0.18-standard' socket: '/srv/mysql/lx07sock' port: 3307 MySQL Community Edition -
MySQL crashes constantly and can't get MySQL 5.0.21 to write core-file
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=100 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]
Re: MySQL crashes constantly and can't get MySQL 5.0.21 to write core-file
On Tue, Jun 13, 2006 at 08:55:59AM +0200, Wouter de Jong wrote: The symptoms are that MySQL is constantly (eg. within every 30 minutes) getting signal 11's according to the logfile, and is restarting. Problem finally tracked down and filed bug report. 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]
MySQL crashes
I have a site running MySQL 4.1.19. When I was first given the problem, the site only stayed up for a couple of days - they then found they had to reboot (as opposed to just restarting MySQL). The error message they were getting is below (between the snip's). After looking at the site, I altered some my.cnf parameters, and then the site stayed up for 14 days before doing the same. This site is identical to others I have seen - that are running with no issues. Could this be hardware (memory related)? Regards, Ian Collins. snip === Version: '4.1.9-standard' socket: '/tmp/mysql.sock' port: 3306 Official MySQL RPM 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=134217728 read_buffer_size=131072 max_used_connections=80 max_connections=400 threads_connected=68 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 1001468 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. thd=0x8e6d0c0 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... Cannot determine thread, fp=0xbfb1f5d8, backtrace may not be correct. Stack range sanity check OK, backtrace follows: 0x808e1b7 0x82e5a08 0x80b68f6 0x804c0bd 0x804bfb3 0x808473c 0x808ddb3 0x809b8e6 0x82e31bc 0x830ca8a New value of fp=(nil) failed sanity check, terminating stack trace! Please read http://dev.mysql.com/doc/mysql/en/Using_stack_trace.html and follow instructions on how to resolve the stack trace. Resolved stack trace is much more helpful in diagnosing the problem, so please do resolve it Trying to get some variables. Some pointers may be invalid and cause the dump to abort... thd-query at (nil) is invalid pointer thd-thread_id=52266 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. Number of processes running now: 0 snip === -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: MySQL crashes
On 6/7/06, Ian Collins [EMAIL PROTECTED] wrote: I have a site running MySQL 4.1.19. When I was first given the problem, the site only stayed up for a couple of days - they then found they had to reboot (as opposed to just restarting MySQL). The error message they were getting is below (between the snip's). After looking at the site, I altered some my.cnf parameters, and then the site stayed up for 14 days before doing the same. This site is identical to others I have seen - that are running with no issues. Could this be hardware (memory related)? Regards, Ian Collins. snip === Version: '4.1.9-standard' socket: '/tmp/mysql.sock' port: 3306 Official MySQL RPM 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=134217728 read_buffer_size=131072 max_used_connections=80 max_connections=400 threads_connected=68 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 1001468 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. thd=0x8e6d0c0 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... Cannot determine thread, fp=0xbfb1f5d8, backtrace may not be correct. Stack range sanity check OK, backtrace follows: 0x808e1b7 0x82e5a08 0x80b68f6 0x804c0bd 0x804bfb3 0x808473c 0x808ddb3 0x809b8e6 0x82e31bc 0x830ca8a New value of fp=(nil) failed sanity check, terminating stack trace! Please read http://dev.mysql.com/doc/mysql/en/Using_stack_trace.html and follow instructions on how to resolve the stack trace. Resolved stack trace is much more helpful in diagnosing the problem, so please do resolve it Trying to get some variables. Some pointers may be invalid and cause the dump to abort... thd-query at (nil) is invalid pointer thd-thread_id=52266 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. Number of processes running now: 0 snip === You mean 4.1.9, not 4.1.19 right? Try upgrading your server to the latest 4.1, I believe its 4.1.20, and report back... I`ve seen various issues with versions below 4.1.12... -- Daniel da Veiga Computer Operator - RS - Brazil -BEGIN GEEK CODE BLOCK- Version: 3.1 GCM/IT/P/O d-? s:- a? C++$ UBLA++ P+ L++ E--- W+++$ N o+ K- w O M- V- PS PE Y PGP- t+ 5 X+++ R+* tv b+ DI+++ D+ G+ e h+ r+ y++ --END GEEK CODE BLOCK-- -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: MySQL crashes
Hi, This might be a bug try to create mysql stack trace file and find out what is causing for mysql crash, this might be a query hitting mysql and also memory related issues.Try to upgrade your mysql and report back. Daniel da Veiga wrote: On 6/7/06, Ian Collins [EMAIL PROTECTED] wrote: I have a site running MySQL 4.1.19. When I was first given the problem, the site only stayed up for a couple of days - they then found they had to reboot (as opposed to just restarting MySQL). The error message they were getting is below (between the snip's). After looking at the site, I altered some my.cnf parameters, and then the site stayed up for 14 days before doing the same. This site is identical to others I have seen - that are running with no issues. Could this be hardware (memory related)? Regards, Ian Collins. snip === Version: '4.1.9-standard' socket: '/tmp/mysql.sock' port: 3306 Official MySQL RPM 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=134217728 read_buffer_size=131072 max_used_connections=80 max_connections=400 threads_connected=68 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 1001468 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. thd=0x8e6d0c0 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... Cannot determine thread, fp=0xbfb1f5d8, backtrace may not be correct. Stack range sanity check OK, backtrace follows: 0x808e1b7 0x82e5a08 0x80b68f6 0x804c0bd 0x804bfb3 0x808473c 0x808ddb3 0x809b8e6 0x82e31bc 0x830ca8a New value of fp=(nil) failed sanity check, terminating stack trace! Please read http://dev.mysql.com/doc/mysql/en/Using_stack_trace.html and follow instructions on how to resolve the stack trace. Resolved stack trace is much more helpful in diagnosing the problem, so please do resolve it Trying to get some variables. Some pointers may be invalid and cause the dump to abort... thd-query at (nil) is invalid pointer thd-thread_id=52266 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. Number of processes running now: 0 snip === You mean 4.1.9, not 4.1.19 right? Try upgrading your server to the latest 4.1, I believe its 4.1.20, and report back... I`ve seen various issues with versions below 4.1.12... -- Thanks Regards, Dilipkumar DBA Support ** DISCLAIMER ** Information contained and transmitted by this E-MAIL is proprietary to Sify Limited and is intended for use only by the individual or entity to which it is addressed, and may contain information that is privileged, confidential or exempt from disclosure under applicable law. If this is a forwarded message, the content of this E-MAIL may not have been sent with the authority of the Company. If you are not the intended recipient, an agent of the intended recipient or a person responsible for delivering the information to the named recipient, you are notified that any use, distribution, transmission, printing, copying or dissemination of this information in any way or in any manner is strictly prohibited. If you have received this communication in error, please delete this mail notify us immediately at [EMAIL PROTECTED] Watch India vs. England LIVE, Hot videos and more only on Sify Max! Click Here. www.sifymax.com Get to see what's happening in your favourite City on Bangalore Live! www.bangalorelive.in -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
MySQL crashes randomly
So, our MySQL master database crashes about once a week, then immediately recovers. We are running a Dell 2850 -- 64-bit Fedora Core 3 box with 6G of memory, 4 Intel Xeon processors, at 3.60 GHz speed each (says /proc/cpuinfo), each cpu cache size is 2048 Kb. It replicates to 2 slaves, which have the same hardware and memory. (the slaves don't crash). I've done everything at http://dev.mysql.com/doc/refman/4.1/en/crashing.html uname -a Linux dbhotsl1.manhunt.net 2.6.12-1.1381_FC3smp #1 SMP Fri Oct 21 04:22:48 EDT 2005 x86_64 x86_64 x86_64 GNU/Linux cat /proc/meminfo MemTotal: 6142460 kB MemFree: 26564 kB Buffers: 15396 kB Cached: 805128 kB SwapCached: 1336 kB Active: 5503352 kB Inactive: 505792 kB HighTotal: 0 kB HighFree: 0 kB LowTotal: 6142460 kB LowFree: 26564 kB SwapTotal: 2096472 kB SwapFree: 2088036 kB Dirty: 1996 kB Writeback: 0 kB Mapped: 5195364 kB Slab: 78348 kB CommitLimit: 5167700 kB Committed_AS: 5532772 kB PageTables: 12384 kB VmallocTotal: 34359738367 kB VmallocUsed: 263636 kB VmallocChunk: 34359474295 kB HugePages_Total: 0 HugePages_Free: 0 Hugepagesize: 2048 kB The server regularly runs at 20-30 MB free memory all the time, so it's not (necessarily) a low memory issue. We get the dreaded Signal 11 error, and no core dumps even though we have core-file set in the [mysqld] of the my.cnf. Speaking of the my.cnf, here it is: --- [mysqld] core-file old-passwords tmpdir = /tmp/ datadir = /var/lib/mysql socket = /var/lib/mysql/mysql.sock port = 3306 key_buffer = 320M max_allowed_packet = 16M table_cache = 10240 thread_cache = 80 ft_min_word_len = 3 # Query Cache Settings - OFF due to overload of Session table query_cache_size = 32M query_cache_type = 2 # Log queries taking longer than long_query_time seconds long_query_time = 4 log-slow-queries = /var/log/mysql/slow-queries.log log-error = /var/log/mysql/mysqld.err # Try number of CPU's*2 for thread_concurrency thread_concurrency = 12 interactive_timeout = 28800 wait_timeout = 30 # up to 15 Apache Servers with 256 connections each = 3840 # 5.8 G of memory = 2200 cxns # when you change this recalculate total possible mysqld memory usage!! # innodb_buffer_pool_size + key_buffer_size # + max_connections*(sort_buffer_size+read_buffer_size+binlog_cache_size) # + max_connections*2MB max_connections = 2200 max_connect_errors = 128 # Replication Master Server (default) # binary logging is required for replication log-bin=/var/log/mysql/dbhotsl1-bin server-id = 18 binlog-do-db = db1 binlog-do-db = db2 binlog-do-db = db3 max_binlog_size = 2G # InnoDB tables innodb_data_home_dir = /var/lib/mysql/ innodb_data_file_path = ibdata1:3G;ibdata2:3G;ibdata3:3G;ibdata4:3G; innodb_log_group_home_dir = /var/log/mysql/ innodb_log_files_in_group = 2 innodb_log_arch_dir = /var/log/mysql/ innodb_buffer_pool_size = 4G innodb_additional_mem_pool_size = 40M innodb_log_file_size = 160M innodb_log_buffer_size = 80M innodb_flush_log_at_trx_commit = 0 innodb_lock_wait_timeout = 50 innodb_thread_concurrency = 8 innodb_file_io_threads = 4 ## [mysql.server] user=mysql basedir=/var/lib ## [safe_mysqld] err-log=/var/log/mysql/mysqld.log pid-file=/var/run/mysqld/mysqld.pid --- And then the error file, pretty standard, not really telling me anything (and no stack trace): -- 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=335544320 read_buffer_size=131072 max_used_connections=2201 max_connections=2200 threads_connected=152 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 5114862 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. 060427 23:56:44 InnoDB: Database was not shut down normally! InnoDB: Starting crash recovery. InnoDB: Reading tablespace information from the .ibd files... InnoDB: Restoring possible half-written data pages from the doublewrite InnoDB: buffer... 060427 23:56:44 InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 752 3907332354. InnoDB: Doing recovery: scanned up to log sequence number 752 3912574976 InnoDB: Doing recovery: scanned up to log sequence number 752 3917817856 [...more of the same] InnoDB: Doing recovery: scanned up to log sequence number 752 4144467558 060427 23:57:09 InnoDB: Starting an apply batch of log records to
Re: MySQL crashes randomly
On 5/12/06, sheeri kritzer [EMAIL PROTECTED] wrote: So, our MySQL master database crashes about once a week, then immediately recovers. We are running a Dell 2850 -- 64-bit Fedora Core 3 box with 6G of memory, 4 Intel Xeon processors, at 3.60 GHz speed each (says /proc/cpuinfo), each cpu cache size is 2048 Kb. It replicates to 2 slaves, which have the same hardware and memory. (the slaves don't crash). I've done everything at http://dev.mysql.com/doc/refman/4.1/en/crashing.html uname -a Linux dbhotsl1.manhunt.net 2.6.12-1.1381_FC3smp #1 SMP Fri Oct 21 04:22:48 EDT 2005 x86_64 x86_64 x86_64 GNU/Linux cat /proc/meminfo MemTotal: 6142460 kB MemFree: 26564 kB Buffers: 15396 kB Cached: 805128 kB SwapCached: 1336 kB Active: 5503352 kB Inactive: 505792 kB HighTotal: 0 kB HighFree: 0 kB LowTotal: 6142460 kB LowFree: 26564 kB SwapTotal: 2096472 kB SwapFree: 2088036 kB Dirty: 1996 kB Writeback: 0 kB Mapped: 5195364 kB Slab: 78348 kB CommitLimit: 5167700 kB Committed_AS: 5532772 kB PageTables: 12384 kB VmallocTotal: 34359738367 kB VmallocUsed: 263636 kB VmallocChunk: 34359474295 kB HugePages_Total: 0 HugePages_Free: 0 Hugepagesize: 2048 kB The server regularly runs at 20-30 MB free memory all the time, so it's not (necessarily) a low memory issue. We get the dreaded Signal 11 error, and no core dumps even though we have core-file set in the [mysqld] of the my.cnf. Speaking of the my.cnf, here it is: --- [mysqld] core-file old-passwords tmpdir = /tmp/ datadir = /var/lib/mysql socket = /var/lib/mysql/mysql.sock port = 3306 key_buffer = 320M max_allowed_packet = 16M table_cache = 10240 thread_cache = 80 ft_min_word_len = 3 # Query Cache Settings - OFF due to overload of Session table query_cache_size = 32M query_cache_type = 2 # Log queries taking longer than long_query_time seconds long_query_time = 4 log-slow-queries = /var/log/mysql/slow-queries.log log-error = /var/log/mysql/mysqld.err # Try number of CPU's*2 for thread_concurrency thread_concurrency = 12 interactive_timeout = 28800 wait_timeout = 30 # up to 15 Apache Servers with 256 connections each = 3840 # 5.8 G of memory = 2200 cxns # when you change this recalculate total possible mysqld memory usage!! # innodb_buffer_pool_size + key_buffer_size # + max_connections*(sort_buffer_size+read_buffer_size+binlog_cache_size) # + max_connections*2MB max_connections = 2200 max_connect_errors = 128 # Replication Master Server (default) # binary logging is required for replication log-bin=/var/log/mysql/dbhotsl1-bin server-id = 18 binlog-do-db = db1 binlog-do-db = db2 binlog-do-db = db3 max_binlog_size = 2G # InnoDB tables innodb_data_home_dir = /var/lib/mysql/ innodb_data_file_path = ibdata1:3G;ibdata2:3G;ibdata3:3G;ibdata4:3G; innodb_log_group_home_dir = /var/log/mysql/ innodb_log_files_in_group = 2 innodb_log_arch_dir = /var/log/mysql/ innodb_buffer_pool_size = 4G innodb_additional_mem_pool_size = 40M innodb_log_file_size = 160M innodb_log_buffer_size = 80M innodb_flush_log_at_trx_commit = 0 innodb_lock_wait_timeout = 50 innodb_thread_concurrency = 8 innodb_file_io_threads = 4 ## [mysql.server] user=mysql basedir=/var/lib ## [safe_mysqld] err-log=/var/log/mysql/mysqld.log pid-file=/var/run/mysqld/mysqld.pid --- And then the error file, pretty standard, not really telling me anything (and no stack trace): -- 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=335544320 read_buffer_size=131072 max_used_connections=2201 max_connections=2200 threads_connected=152 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 5114862 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. 060427 23:56:44 InnoDB: Database was not shut down normally! InnoDB: Starting crash recovery. InnoDB: Reading tablespace information from the .ibd files... InnoDB: Restoring possible half-written data pages from the doublewrite InnoDB: buffer... 060427 23:56:44 InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 752 3907332354. InnoDB: Doing recovery: scanned up to log sequence number 752 3912574976 InnoDB: Doing recovery: scanned up to log sequence number 752 3917817856 [...more of the same] InnoDB: Doing recovery: scanned up to log sequence number 752 4144467558 060427 23:57:09
Sudden Mysql Crashes - table damage?
HI MySQL 5.0 (windows XP) I have a problem where i think some of my tables have somehow been corrupted, if i try to run a check table command against some tables the mysql service crashes and i have to restart it. I am not sure how this damage has occurred but has anyone got any suggestions of what to apart from dropping the tables? everything i have done so far has caused the service to crash which makes it pretty hard to find out what is wrong?!?!?!?! Any help very much appreciated Ade -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: Sudden Mysql Crashes - table damage?
First of all I would check for file system corruption. IIRC there is a command line tool for repairing MyISAM tables, so you can use that without needing the MySQL database server. I'm sure there are full details in the manual: http://dev.mysql.com/doc/refman/5.0/en/ Good luck! James Harvard MySQL 5.0 (windows XP) I have a problem where i think some of my tables have somehow been corrupted, if i try to run a check table command against some tables the mysql service crashes and i have to restart it. I am not sure how this damage has occurred but has anyone got any suggestions of what to apart from dropping the tables? everything i have done so far has caused the service to crash which makes it pretty hard to find out what is wrong?!?!?!?! -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: Sudden Mysql Crashes - table damage?
On 1/31/06, Adrian Bruce [EMAIL PROTECTED] wrote: HI MySQL 5.0 (windows XP) I have a problem where i think some of my tables have somehow been corrupted, if i try to run a check table command against some tables the mysql service crashes and i have to restart it. I am not sure how this damage has occurred but has anyone got any suggestions of what to apart from dropping the tables? everything i have done so far has caused the service to crash which makes it pretty hard to find out what is wrong?!?!?!?! Ade, What ahppens when you perform a mysqldump of the database that contains the corrupts table(s)? Is the process bailing part way through? I've seen people recover from certain corruption issues by dumping the database and recreating from scratch. At any rate, you should take a back-up of either the MyISAM data and .frm files (use BACKUP TABLE) or a mysqldump before starting any repair procedure. Regards, Imran -- http://www.ImranChaudhry.info MySQL Database Management Design Services -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: Sudden Mysql Crashes - table damage?
Thanks for the reply yep mysqldump also causes the service to crash. i have a few innodb tables mixed in amongst the myisam, it seems that it is the innodb tables that may be causing the problems but i am not sure why ??? Imran Chaudhry wrote: On 1/31/06, Adrian Bruce [EMAIL PROTECTED] wrote: HI MySQL 5.0 (windows XP) I have a problem where i think some of my tables have somehow been corrupted, if i try to run a check table command against some tables the mysql service crashes and i have to restart it. I am not sure how this damage has occurred but has anyone got any suggestions of what to apart from dropping the tables? everything i have done so far has caused the service to crash which makes it pretty hard to find out what is wrong?!?!?!?! Ade, What ahppens when you perform a mysqldump of the database that contains the corrupts table(s)? Is the process bailing part way through? I've seen people recover from certain corruption issues by dumping the database and recreating from scratch. At any rate, you should take a back-up of either the MyISAM data and .frm files (use BACKUP TABLE) or a mysqldump before starting any repair procedure. Regards, Imran -- http://www.ImranChaudhry.info MySQL Database Management Design Services -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: Sudden Mysql Crashes - table damage?
On Jan 31, 2006, at 11:01 AM, Adrian Bruce wrote: Thanks for the reply yep mysqldump also causes the service to crash. i have a few innodb tables mixed in amongst the myisam, it seems that it is the innodb tables that may be causing the problems but i am not sure why ??? If it's InnoDB crashing it's usually pretty good at logging some error. What does your .err file say? That's going to determine how much you can save if it's InnoDB. --Ware Imran Chaudhry wrote: On 1/31/06, Adrian Bruce [EMAIL PROTECTED] wrote: HI MySQL 5.0 (windows XP) I have a problem where i think some of my tables have somehow been corrupted, if i try to run a check table command against some tables the mysql service crashes and i have to restart it. I am not sure how this damage has occurred but has anyone got any suggestions of what to apart from dropping the tables? everything i have done so far has caused the service to crash which makes it pretty hard to find out what is wrong?!?!?!?! Ade, What ahppens when you perform a mysqldump of the database that contains the corrupts table(s)? Is the process bailing part way through? I've seen people recover from certain corruption issues by dumping the database and recreating from scratch. At any rate, you should take a back-up of either the MyISAM data and .frm files (use BACKUP TABLE) or a mysqldump before starting any repair procedure. Regards, Imran -- http://www.ImranChaudhry.info MySQL Database Management Design Services -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql? [EMAIL PROTECTED] -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
mysql crashes
Hi Guys: Does anyone know how come I'm getting a lot of mysql processes when I start mysql server for the first time. When I type top it showed the following: 5:33pm up 15 min, 4 users, load average: 0.16, 0.19, 0.10 80 processes: 79 sleeping, 1 running, 0 zombie, 0 stopped CPU0 states: 0.1% user, 0.2% system, 0.0% nice, 99.2% idle CPU1 states: 0.1% user, 2.4% system, 0.0% nice, 96.4% idle CPU2 states: 5.3% user, 0.1% system, 0.0% nice, 94.0% idle CPU3 states: 28.3% user, 3.4% system, 0.0% nice, 67.2% idle Mem: 2065160K av, 1028956K used, 1036204K free, 0K shrd, 12964K buff Swap: 2096440K av, 0K used, 2096440K free 226252K cached PID USER PRI NI SIZE RSS SHARE STAT %CPU %MEM TIME COMMAND 715 mysql 15 0 627M 627M 2328 S 0.1 31.1 0:02 mysqld-max 722 mysql 16 0 627M 627M 2328 S 0.0 31.1 0:00 mysqld-max 723 mysql 20 0 627M 627M 2328 S 0.0 31.1 0:00 mysqld-max 724 mysql 16 0 627M 627M 2328 S 0.0 31.1 0:00 mysqld-max 725 mysql 16 0 627M 627M 2328 S 0.0 31.1 0:00 mysqld-max 726 mysql 15 0 627M 627M 2328 S 0.0 31.1 0:00 mysqld-max 746 mysql 15 0 627M 627M 2328 S 0.0 31.1 0:00 mysqld-max 747 mysql 15 0 627M 627M 2328 S 0.0 31.1 0:00 mysqld-max 752 mysql 15 0 627M 627M 2328 S 0.0 31.1 0:00 mysqld-max 753 mysql 15 0 627M 627M 2328 S 0.0 31.1 0:00 mysqld-max 774 mysql 16 0 627M 627M 2328 S 0.0 31.1 0:00 mysqld-max 784 mysql 15 0 627M 627M 2328 S 0.0 31.1 0:00 mysqld-max 788 mysql 16 0 627M 627M 2328 S 0.0 31.1 0:00 mysqld-max 789 mysql 15 0 627M 627M 2328 S 0.0 31.1 0:00 mysqld-max 795 mysql 16 0 627M 627M 2328 S 0.0 31.1 0:00 mysqld-max 858 mysql 15 0 627M 627M 2328 S 0.0 31.1 0:00 mysqld-max 862 mysql 15 0 627M 627M 2328 S 0.0 31.1 0:00 mysqld-max 867 mysql 15 0 627M 627M 2328 S 0.0 31.1 0:00 mysqld-max 889 mysql 16 0 627M 627M 2328 S 0.0 31.1 0:00 mysqld-max 899 mysql 16 0 627M 627M 2328 S 0.0 31.1 0:00 mysqld-max 908 mysql 15 0 627M 627M 2328 S 0.0 31.1 0:00 mysqld-max 914 mysql 15 0 627M 627M 2328 S 0.0 31.1 0:04 mysqld-max 967 mysql 15 0 627M 627M 2328 S 0.0 31.1 0:00 mysqld-max 1652 mysql 15 0 627M 627M 2328 S 0.0 31.1 0:00 mysqld-max Thanks in advanced and I hope someone can help me. Greetings _ MSN Fotos: la forma más fácil de compartir e imprimir fotos. http://photos.msn.es/support/worldwide.aspx -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
problem with mysql-crashes
Hey folks, before posting to the bugs-list I would like to try it here to get some help :). Every now and then MySQL-4.0.13 crashes on my Dual-Athlon-MP-machine. Its not reproducible nor I know a query which does it. (The log shows that at the end, so no query :-( : Trying to get some variables. Some pointers may be invalid and cause the dump to abort... thd-query at 0x5e13a478 is invalid pointer thd-thread_id=2223573 ) The server is the standalone db-server for one accessing webserver, its running RedHat-Linux 7.2 with all their latest patches. Kernel 2.4.19-XFS with MySQL running on an XFS-filesystem. No replication but query-cache enabled. Ok but now the worse thing started for 2 times I already got this problem in the logs: Number of processes running now: 16 mysqld-max process hanging, pid 17193 - killed mysqld-max process hanging, pid 17191 - killed mysqld-max process hanging, pid 17190 - killed mysqld-max process hanging, pid 17145 - killed mysqld-max process hanging, pid 17144 - killed mysqld-max process hanging, pid 17098 - killed mysqld-max process hanging, pid 17025 - killed mysqld-max process hanging, pid 16987 - killed mysqld-max process hanging, pid 28393 - killed mysqld-max process hanging, pid 28392 - killed mysqld-max process hanging, pid 28391 - killed mysqld-max process hanging, pid 28389 - killed mysqld-max process hanging, pid 28388 - killed mysqld-max process hanging, pid 28387 - killed mysqld-max process hanging, pid 28386 - killed mysqld-max process hanging, pid 28385 - killed 030722 20:46:26 mysqld restarted Afterwards there is a init-process taking 99% from one CPU. The first time I tried to reboot the machine, which didn't work as the shutdown process was hanging then. Any ideas whats wrong and how to fix it? Didn't see a mention of a fix for that problem in the 4.0.14-changelog, will it still fix it? Thanks in advance, Thomas -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: problem with mysql-crashes
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, On Wed, 23 Jul 2003 [EMAIL PROTECTED] wrote: before posting to the bugs-list I would like to try it here to get some help :). Every now and then MySQL-4.0.13 crashes on my Dual-Athlon-MP-machine. Is that a self-compiled binary or one of ours? Its not reproducible nor I know a query which does it. (The log shows that at the end, so no query :-( : Trying to get some variables. Some pointers may be invalid and cause the dump to abort... thd-query at 0x5e13a478 is invalid pointer thd-thread_id=2223573 ) Not very helpful. Does this occur under high load only? The server is the standalone db-server for one accessing webserver, its running RedHat-Linux 7.2 with all their latest patches. Kernel 2.4.19-XFS with MySQL running on an XFS-filesystem. No replication but query-cache enabled. What version of glibc is this system running on? Is it 2.2.3 by chance? Ok but now the worse thing started for 2 times I already got this problem in the logs: Number of processes running now: 16 mysqld-max process hanging, pid 17193 - killed mysqld-max process hanging, pid 17191 - killed mysqld-max process hanging, pid 17190 - killed mysqld-max process hanging, pid 17145 - killed mysqld-max process hanging, pid 17144 - killed mysqld-max process hanging, pid 17098 - killed mysqld-max process hanging, pid 17025 - killed mysqld-max process hanging, pid 16987 - killed mysqld-max process hanging, pid 28393 - killed mysqld-max process hanging, pid 28392 - killed mysqld-max process hanging, pid 28391 - killed mysqld-max process hanging, pid 28389 - killed mysqld-max process hanging, pid 28388 - killed mysqld-max process hanging, pid 28387 - killed mysqld-max process hanging, pid 28386 - killed mysqld-max process hanging, pid 28385 - killed 030722 20:46:26 mysqld restarted Afterwards there is a init-process taking 99% from one CPU. The first time I tried to reboot the machine, which didn't work as the shutdown process was hanging then. Any ideas whats wrong and how to fix it? Didn't see a mention of a fix for that problem in the 4.0.14-changelog, will it still fix it? What version of glibc is being used on that system? I noticed that you use the Max binary, which is dynamically linked - so it will use the locally installed libc.so. Is there any special reason for using Max? Or could you try to use our statically linked Standard binary instead? The problem above looks very similar to the problems we had when we linked against glibc 2.2.3 instead of 2.2.5: under high load, a mysqld thread starts eating up all CPU resources on an SMP system. Unfortunately we never found the reason for that - it did not seem to happen when using glibc 2.2.5... Bye, LenZ - -- Lenz Grimmer [EMAIL PROTECTED] Senior Production Engineer MySQL GmbH, http://www.mysql.de/ Hamburg, Germany For technical support contracts, visit https://order.mysql.com/?ref=mlgr -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2-rc1-SuSE (GNU/Linux) Comment: For info see http://quantumlab.net/pine_privacy_guard/ iD8DBQE/HoQOSVDhKrJykfIRAh+MAJ91+kr7H92xcK4JtFhz5HQ3r6LGgwCggT/v OCHlqAabKjd6FnL6PMOmKRg= =U2ag -END PGP SIGNATURE- -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: problem with mysql-crashes
Hi Lenz, thanks a lot for your reply! Is that a self-compiled binary or one of ours? It are the MySQL-4.0.13-MAX-RPMs from your site. Not very helpful. Does this occur under high load only? Yeah I know, otherwise I would have tried to generate a reproducible testcase with a given query or such. Any way to have valid pointers there? Nope, the load on that system is mostly around 0.5 with peaks up to 1.5, not something I would call a high load for a dual-system. Also the crashes are at many different times (even in the deep night) so I don't think its related to load :-(. What version of glibc is this system running on? Is it 2.2.3 by chance? Nope, sorry. Its glibc-2.2.4-32. What version of glibc is being used on that system? I noticed that you use the Max binary, which is dynamically linked - so it will use the locally installed libc.so. Is there any special reason for using Max? Or could you try to use our statically linked Standard binary instead? Yeah I could try that instead, maybe I should try with 4.0.13 to see if its a problem of that version. Or should I better try 4.0.14 already? I was hosting a couple of bdb-tables for some time, but no longer now. Currently only myisam and innodb-tables so I could try the standard-built too. The problem above looks very similar to the problems we had when we linked against glibc 2.2.3 instead of 2.2.5: under high load, a mysqld thread starts eating up all CPU resources on an SMP system. Unfortunately we never found the reason for that - it did not seem to happen when using glibc 2.2.5... Hmm, maybe 2.2.4 has the same problem? The problem is that the init-process is taking all the cpu, didn't see a mysql-process doing the same before. Thanks, Thomas -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
[mysql crashes with Memory access error]
Description: When accessing this mysql version from a WinXP client (running in a VMWare shel) the server crashes reproducable. How-To-Repeat: Access to server with DBTools 1.0.x from WinXP client. Fix: ? Submitter-Id: submitter ID Originator:Hans-Joerg Wolff Organization: MySQL support: [none] Synopsis: Memory access error with DBTools access Severity: Priority: Category: mysql Class: Release: mysql-3.23.52 (Source distribution) Server: /usr/bin/mysqladmin Ver 8.23 Distrib 3.23.54, for pc-linux on i686 Copyright (C) 2000 MySQL AB MySQL Finland AB TCX DataKonsult AB This software comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to modify and redistribute it under the GPL license Server version 3.23.52-log Protocol version10 Connection Localhost via UNIX socket UNIX socket /var/lib/mysql/mysql.sock Uptime: 2 min 50 sec Threads: 1 Questions: 1 Slow queries: 0 Opens: 6 Flush tables: 1 Open tables: 0 Queries per second avg: 0.006 Environment: System: Linux bu01 2.4.20-SMP #2 SMP Mon Dec 16 03:45:36 CET 2002 i686 unknown Architecture: i686 Some paths: /usr/bin/perl /usr/bin/make /usr/bin/gmake /usr/bin/gcc /usr/bin/cc GCC: Reading specs from /usr/lib/gcc-lib/i486-suse-linux/3.2/specs Configured with: ../configure --enable-threads=posix --prefix=/usr --with-local-prefix=/usr/local --infodir=/usr/share/info --mandir=/usr/share/man --libdir=/usr/lib --enable-languages=c,c++,f77,objc,java,ada --enable-libgcj --with-gxx-include-dir=/usr/include/g++ --with-slibdir=/lib --with-system-zlib --enable-shared --enable-__cxa_atexit i486-suse-linux Thread model: posix gcc version 3.2 Compilation info: CC='gcc' CFLAGS='-O2 -march=i586 -mcpu=i686 -fmessage-length=0 -DPIC -fPIC' CXX='g++' CXXFLAGS='-O2 -march=i586 -mcpu=i686 -fmessage-length=0 -felide-constructors-fno-exceptions -fno-rtti -fPIC -DPIC' LDFLAGS='' LIBC: -rwxr-xr-x1 root root 1312470 2002-09-10 18:51 /lib/libc.so.6 -rw-r--r--1 root root 23159812 2002-09-09 18:40 /usr/lib/libc.a -rw-r--r--1 root root 178 2002-09-09 18:40 /usr/lib/libc.so lrwxrwxrwx1 root root 20 2002-09-26 18:44 /usr/lib/libc-client.so - libc-client.so.2001a -rwxr-xr-x1 root root 735696 2002-09-09 22:47 /usr/lib/libc-client.so.2001a Configure command: ./configure '--disable-shared' '--with-mysqld-ldflags=-static' '--with-client-ldflags=-static' '--without-berkeley-db' '--without-innodb' '--enable-assembler' '--enable-large-files' '--infodir=/usr/share/info' '--libdir=/usr/lib' '--libexecdir=/usr/sbin' '--localstatedir=/var/lib/mysql' '--mandir=/usr/share/man' '--prefix=/usr' '--sysconfdir=/etc' '--with-mysqld-user=mysql' '--without-debug' '--datadir=/usr/share' '--includedir=/usr/include' '--with-extra-charsets=complex' '--with-unix-socket-path=/var/lib/mysql/mysql.sock' '--with-libwrap' 'CFLAGS=-O2 -march=i586 -mcpu=i686 -fmessage-length=0 -DPIC -fPIC' 'CXXFLAGS=-O2 -march=i586 -mcpu=i686 -fmessage-length=0-felide-constructors -fno-exceptions -fno-rtti -fPIC -DPIC' - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: MySQL crashes with foreign key restraints
Stefan, - Original Message - From: Stefan Hinz [EMAIL PROTECTED] To: Heikki Tuuri [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Sunday, December 15, 2002 1:39 AM Subject: Re: MySQL crashes with foreign key restraints Dear Heikki, ... Hmm ... seems like 4.0.5 is the first MySQL/InnoDB working for me ... Thanks alot for your help, anyway! can you send me your my.cnf? I could test on my XP computer. I do not know why 4.0.4 etc.should not work. Regards, -- Stefan Hinz [EMAIL PROTECTED] CEO / Geschäftsleitung iConnect GmbH http://iConnect.de Heesestr. 6, 12169 Berlin (Germany) Telefon: +49 30 7970948-0 Fax: +49 30 7970948-3 Best regards, Heikki Tuuri Innobase Oy --- InnoDB - transactions, row level locking, and foreign key support for MySQL See http://www.innodb.com, download MySQL-Max from http://www.mysql.com sql query - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: MySQL crashes with foreign key restraints
Stefan, - Original Message - From: Stefan Hinz [EMAIL PROTECTED] To: Heikki Tuuri [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Sunday, December 15, 2002 1:39 AM Subject: Re: MySQL crashes with foreign key restraints Dear Heikki, ... Hmm ... seems like 4.0.5 is the first MySQL/InnoDB working for me ... Thanks alot for your help, anyway! can you send me your my.cnf? I could test on my XP computer. I do not know why 4.0.4 etc.should not work. Regards, -- Stefan Hinz [EMAIL PROTECTED] CEO / Geschäftsleitung iConnect GmbH http://iConnect.de Heesestr. 6, 12169 Berlin (Germany) Telefon: +49 30 7970948-0 Fax: +49 30 7970948-3 Best regards, Heikki Tuuri Innobase Oy --- InnoDB - transactions, row level locking, and foreign key support for MySQL See http://www.innodb.com, download MySQL-Max from http://www.mysql.com sql query - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: MySQL crashes with foreign key restraints
Stefan, please upgrade to 4.0.5 and test again. 4.0.1 is a very old alpha release, and lots of bugs have been fixed since. Best regards, Heikki Tuuri Innobase Oy --- Order technical MySQL/InnoDB support at https://order.mysql.com/ See http://www.innodb.com for the online manual and latest news on InnoDB sql query Subject: MySQL crashes with foreign key restraints From: Stefan Hinz Date: Fri, 13 Dec 2002 16:17:56 +0100 Dear list, I am using MySQL-max 4.0.1 on Win 98 Second Edition with InnoDB as default table type. Using DeZign, I created the following SQL file with three tables (I left out all those other CHAR and TEXT fields here): CREATE TABLE Projekt( id SMALLINT UNSIGNED NOT NULL, PRIMARY KEY (id)); CREATE TABLE Teilnehmer( id SMALLINT UNSIGNED NOT NULL, pid SMALLINT UNSIGNED, FOREIGN KEY (pid) REFERENCES Projekt (id), PRIMARY KEY (id), INDEX IDX_Teilnehmer_1 (pid)); CREATE TABLE Bewertung( pid SMALLINT UNSIGNED NOT NULL, #FOREIGN KEY (pid) REFERENCES Projekt (id), INDEX IDX_Bewertung_1 (pid)); Importing this in MySQL batch mode makes the MySQL server crash immediately. Everything works fine for table Projekt and Teilnehmer, but the line I commented out here for table Bewertung makes MySQL crash. Table Bewertung doesn't have a primary key, that's all the difference. Starting the server again and logging in, I find the first two tables are fine, but SHOW TABLE STATUS reports only NULL fields for table Bewertung, and InnoDB complains that it has no fields at all. Trying to drop this broken table results in 'table Bewertung doesn't exist'. To be able to delete the table (and the database), I have to delete Bewertung.frm manually. This makes InnoDB complain at server start like this: InnoDB: MySQL database directory from another database? InnoDB: Have you copied the .frm file of the table to the InnoDB: data dictionary though MySQL is trying to drop it. InnoDB: Error: table projekt/bewertung does not exist in the InnoDB internal InnoDB: MySQL database directory from another database? InnoDB: Have you copied the .frm file of the table to the InnoDB: data dictionary though MySQL is trying to drop it. InnoDB: Error: table projekt/bewertung does not exist in the InnoDB internal have moved .frm files to another database? Is there something wrong with my foreign key restraints, or is this a bug in InnoDB / MySQL? P.S. I tried the same with 4.0.3-max-nt on a Win2K box. Here, the server doesn't crash, but the response is can't create '.\projekt\teilnehmer.frm' with error 150 (unknown error). Commenting out the FOREIGN KEY lines solves the problem, but then again, I have no f.k.restraints :( Regards, -- Stefan Hinz [EMAIL PROTECTED] Geschäftsführer / CEO iConnect GmbH http://iConnect.de Heesestr. 6, 12169 Berlin (Germany) Tel: +49 30 7970948-0 Fax: +49 30 7970948-3 - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
MySQL crashes with foreign key restraints
Dear list, I am using MySQL-max 4.0.1 on Win 98 Second Edition with InnoDB as default table type. Using DeZign, I created the following SQL file with three tables (I left out all those other CHAR and TEXT fields here): CREATE TABLE Projekt( id SMALLINT UNSIGNED NOT NULL, PRIMARY KEY (id)); CREATE TABLE Teilnehmer( id SMALLINT UNSIGNED NOT NULL, pid SMALLINT UNSIGNED, FOREIGN KEY (pid) REFERENCES Projekt (id), PRIMARY KEY (id), INDEX IDX_Teilnehmer_1 (pid)); CREATE TABLE Bewertung( pid SMALLINT UNSIGNED NOT NULL, #FOREIGN KEY (pid) REFERENCES Projekt (id), INDEX IDX_Bewertung_1 (pid)); Importing this in MySQL batch mode makes the MySQL server crash immediately. Everything works fine for table Projekt and Teilnehmer, but the line I commented out here for table Bewertung makes MySQL crash. Table Bewertung doesn't have a primary key, that's all the difference. Starting the server again and logging in, I find the first two tables are fine, but SHOW TABLE STATUS reports only NULL fields for table Bewertung, and InnoDB complains that it has no fields at all. Trying to drop this broken table results in 'table Bewertung doesn't exist'. To be able to delete the table (and the database), I have to delete Bewertung.frm manually. This makes InnoDB complain at server start like this: InnoDB: MySQL database directory from another database? InnoDB: Have you copied the .frm file of the table to the InnoDB: data dictionary though MySQL is trying to drop it. InnoDB: Error: table projekt/bewertung does not exist in the InnoDB internal InnoDB: MySQL database directory from another database? InnoDB: Have you copied the .frm file of the table to the InnoDB: data dictionary though MySQL is trying to drop it. InnoDB: Error: table projekt/bewertung does not exist in the InnoDB internal have moved .frm files to another database? Is there something wrong with my foreign key restraints, or is this a bug in InnoDB / MySQL? P.S. I tried the same with 4.0.3-max-nt on a Win2K box. Here, the server doesn't crash, but the response is can't create '.\projekt\teilnehmer.frm' with error 150 (unknown error). Commenting out the FOREIGN KEY lines solves the problem, but then again, I have no f.k.restraints :( Regards, -- Stefan Hinz [EMAIL PROTECTED] Geschäftsführer / CEO iConnect GmbH http://iConnect.de Heesestr. 6, 12169 Berlin (Germany) Tel: +49 30 7970948-0 Fax: +49 30 7970948-3 - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: MySQL crashes with foreign key restraints
Dear Heikki, thanks for the hint! please upgrade to 4.0.5 and test again. 4.0.1 is a very old alpha release, and lots of bugs have been fixed since. But please note what I said about 4.0.3: P.S. I tried the same with 4.0.3-max-nt on a Win2K box. Here, the server doesn't crash, but the response is can't create '.\projekt\teilnehmer.frm' with error 150 (unknown error). I had the same problems with 4.0.4 on Win2K. Regards, -- Stefan Hinz [EMAIL PROTECTED] CEO / Geschäftsleitung iConnect GmbH http://iConnect.de Heesestr. 6, 12169 Berlin (Germany) Telefon: +49 30 7970948-0 Fax: +49 30 7970948-3 - Original Message - From: Heikki Tuuri [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Friday, December 13, 2002 9:47 PM Subject: Re: MySQL crashes with foreign key restraints Stefan, please upgrade to 4.0.5 and test again. 4.0.1 is a very old alpha release, and lots of bugs have been fixed since. Best regards, Heikki Tuuri Innobase Oy --- Order technical MySQL/InnoDB support at https://order.mysql.com/ See http://www.innodb.com for the online manual and latest news on InnoDB sql query Subject: MySQL crashes with foreign key restraints From: Stefan Hinz Date: Fri, 13 Dec 2002 16:17:56 +0100 -- -- Dear list, I am using MySQL-max 4.0.1 on Win 98 Second Edition with InnoDB as default table type. Using DeZign, I created the following SQL file with three tables (I left out all those other CHAR and TEXT fields here): CREATE TABLE Projekt( id SMALLINT UNSIGNED NOT NULL, PRIMARY KEY (id)); CREATE TABLE Teilnehmer( id SMALLINT UNSIGNED NOT NULL, pid SMALLINT UNSIGNED, FOREIGN KEY (pid) REFERENCES Projekt (id), PRIMARY KEY (id), INDEX IDX_Teilnehmer_1 (pid)); CREATE TABLE Bewertung( pid SMALLINT UNSIGNED NOT NULL, #FOREIGN KEY (pid) REFERENCES Projekt (id), INDEX IDX_Bewertung_1 (pid)); Importing this in MySQL batch mode makes the MySQL server crash immediately. Everything works fine for table Projekt and Teilnehmer, but the line I commented out here for table Bewertung makes MySQL crash. Table Bewertung doesn't have a primary key, that's all the difference. Starting the server again and logging in, I find the first two tables are fine, but SHOW TABLE STATUS reports only NULL fields for table Bewertung, and InnoDB complains that it has no fields at all. Trying to drop this broken table results in 'table Bewertung doesn't exist'. To be able to delete the table (and the database), I have to delete Bewertung.frm manually. This makes InnoDB complain at server start like this: InnoDB: MySQL database directory from another database? InnoDB: Have you copied the .frm file of the table to the InnoDB: data dictionary though MySQL is trying to drop it. InnoDB: Error: table projekt/bewertung does not exist in the InnoDB internal InnoDB: MySQL database directory from another database? InnoDB: Have you copied the .frm file of the table to the InnoDB: data dictionary though MySQL is trying to drop it. InnoDB: Error: table projekt/bewertung does not exist in the InnoDB internal have moved .frm files to another database? Is there something wrong with my foreign key restraints, or is this a bug in InnoDB / MySQL? P.S. I tried the same with 4.0.3-max-nt on a Win2K box. Here, the server doesn't crash, but the response is can't create '.\projekt\teilnehmer.frm' with error 150 (unknown error). Commenting out the FOREIGN KEY lines solves the problem, but then again, I have no f.k.restraints :( - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: MySQL crashes with foreign key restraints
Stefan, are you sure you used the script: CREATE TABLE Projekt( id SMALLINT UNSIGNED NOT NULL, PRIMARY KEY (id)) TYPE=InnoDB; CREATE TABLE Teilnehmer( id SMALLINT UNSIGNED NOT NULL, pid SMALLINT UNSIGNED, FOREIGN KEY (pid) REFERENCES Projekt (id), PRIMARY KEY (id), INDEX IDX_Teilnehmer_1 (pid)) TYPE=InnoDB; SHOW CREATE TABLE Teilnehmer; ? On Linux I get: heikki@hundin:~/mysql-4.0.3-beta-pc-linux-gnu-i686/bin mysql test Welcome to the MySQL monitor. Commands end with ; or \g. Your MySQL connection id is 2 to server version: 4.0.3-beta-log Type 'help;' or '\h' for help. Type '\c' to clear the buffer. mysql CREATE TABLE Projekt( - id SMALLINT UNSIGNED NOT NULL, - PRIMARY KEY (id)) TYPE=InnoDB; Query OK, 0 rows affected (0.22 sec) mysql mysql CREATE TABLE Teilnehmer( - id SMALLINT UNSIGNED NOT NULL, - pid SMALLINT UNSIGNED, - FOREIGN KEY (pid) REFERENCES Projekt (id), - PRIMARY KEY (id), - INDEX IDX_Teilnehmer_1 (pid)) TYPE=InnoDB; Query OK, 0 rows affected (0.01 sec) mysql mysql SHOW CREATE TABLE Teilnehmer; ++-- --+ | Table | Create Table | ++-- --+ | Teilnehmer | CREATE TABLE `Teilnehmer` ( `id` smallint(5) unsigned NOT NULL default '0', `pid` smallint(5) unsigned default NULL, PRIMARY KEY (`id`), KEY `IDX_Teilnehmer_1` (`pid`), FOREIGN KEY (`pid`) REFERENCES `test.Projekt` (`id`) ) TYPE=InnoDB | ++-- --+ 1 row in set (0.00 sec) mysql Please test again! Do you have the default charset set to german? The default is latin1 which I use. Note that The syntax of a foreign key constraint definition in InnoDB: [CONSTRAINT symbol] FOREIGN KEY [id] (index_col_name, ...) REFERENCES table_name (index_col_name, ...) [ON DELETE CASCADE | ON DELETE SET NULL | RESTRICT] Both tables have to be InnoDB type and there must be an index where the foreign key and the referenced key are listed as the first columns. InnoDB does not auto-create indexes on foreign keys or referenced keys: you have to create them explicitly. Corresponding columns in the foreign key and the referenced key must have similar internal data types inside InnoDB so that they can be compared without a type conversion. The size and the signedness of integer types has to be the same. The length of string types need not be the same. ... If MySQL gives the error number 1005 from a CREATE TABLE statement, and the error message string refers to errno 150, then the table creation failed because a foreign key constraint was not correctly formed. Similarly, if an ALTER TABLE fails and it refers to errno 150, that means a foreign key definition would be incorrectly formed for the altered table. Best regards, Heikki Tuuri Innobase Oy --- InnoDB - transactions, hot backup, and foreign key support for MySQL See http://www.innodb.com, download MySQL-Max from http://www.mysql.com sql query - Original Message - From: Stefan Hinz, iConnect (Berlin) [EMAIL PROTECTED] To: Heikki Tuuri [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Saturday, December 14, 2002 10:37 PM Subject: Re: MySQL crashes with foreign key restraints Dear Heikki, thanks for the hint! please upgrade to 4.0.5 and test again. 4.0.1 is a very old alpha release, and lots of bugs have been fixed since. But please note what I said about 4.0.3: P.S. I tried the same with 4.0.3-max-nt on a Win2K box. Here, the server doesn't crash, but the response is can't create '.\projekt\teilnehmer.frm' with error 150 (unknown error). I had the same problems with 4.0.4 on Win2K. Regards, -- Stefan Hinz [EMAIL PROTECTED] CEO / Geschäftsleitung iConnect GmbH http://iConnect.de Heesestr. 6, 12169 Berlin (Germany) Telefon: +49 30 7970948-0 Fax: +49 30 7970948-3 - Original Message - From: Heikki Tuuri [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Friday, December 13, 2002 9:47 PM Subject: Re: MySQL crashes with foreign key restraints Stefan, please upgrade to 4.0.5 and test again. 4.0.1 is a very old alpha release, and lots of bugs have been fixed since. Best regards, Heikki Tuuri Innobase Oy --- Order technical MySQL/InnoDB support at https
Re: MySQL crashes with foreign key restraints
Dear Heikki, are you sure you used the script: CREATE TABLE Projekt( ... Yep. I tried 4.0.1 (on Win98), 4.0.3 and 4.0.4 (on Win2K with SP2), and tonight I tried 4.0.5a-max-nt on Win2K (with SP2, but another machine). Here's the result: C:\mysql\binmysql -usuperuser -p projekt my.dump.projekt.sql Enter password: C:\mysql\binmysql -usuperuser -p projekt Enter password: Welcome to the MySQL monitor. Commands end with ; or \g. Your MySQL connection id is 277 to server version: 4.0.5-beta-max-nt-log Type 'help;' or '\h' for help. Type '\c' to clear the buffer. mysql SHOW TABLES; +---+ | Tables_in_projekt | +---+ | bewertung | | projekt | | teilnehmer| +---+ 3 rows in set (0.00 sec) Hmm ... seems like 4.0.5 is the first MySQL/InnoDB working for me ... Thanks alot for your help, anyway! Regards, -- Stefan Hinz [EMAIL PROTECTED] CEO / Geschäftsleitung iConnect GmbH http://iConnect.de Heesestr. 6, 12169 Berlin (Germany) Telefon: +49 30 7970948-0 Fax: +49 30 7970948-3 - Original Message - From: Heikki Tuuri [EMAIL PROTECTED] To: Stefan Hinz, iConnect (Berlin) [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Saturday, December 14, 2002 10:28 PM Subject: Re: MySQL crashes with foreign key restraints Stefan, are you sure you used the script: CREATE TABLE Projekt( id SMALLINT UNSIGNED NOT NULL, PRIMARY KEY (id)) TYPE=InnoDB; CREATE TABLE Teilnehmer( id SMALLINT UNSIGNED NOT NULL, pid SMALLINT UNSIGNED, FOREIGN KEY (pid) REFERENCES Projekt (id), PRIMARY KEY (id), INDEX IDX_Teilnehmer_1 (pid)) TYPE=InnoDB; SHOW CREATE TABLE Teilnehmer; ? On Linux I get: heikki@hundin:~/mysql-4.0.3-beta-pc-linux-gnu-i686/bin mysql test Welcome to the MySQL monitor. Commands end with ; or \g. Your MySQL connection id is 2 to server version: 4.0.3-beta-log Type 'help;' or '\h' for help. Type '\c' to clear the buffer. mysql CREATE TABLE Projekt( - id SMALLINT UNSIGNED NOT NULL, - PRIMARY KEY (id)) TYPE=InnoDB; Query OK, 0 rows affected (0.22 sec) mysql mysql CREATE TABLE Teilnehmer( - id SMALLINT UNSIGNED NOT NULL, - pid SMALLINT UNSIGNED, - FOREIGN KEY (pid) REFERENCES Projekt (id), - PRIMARY KEY (id), - INDEX IDX_Teilnehmer_1 (pid)) TYPE=InnoDB; Query OK, 0 rows affected (0.01 sec) mysql mysql SHOW CREATE TABLE Teilnehmer; ++-- -- -- -- -- --+ | Table | Create Table | ++-- -- -- -- -- --+ | Teilnehmer | CREATE TABLE `Teilnehmer` ( `id` smallint(5) unsigned NOT NULL default '0', `pid` smallint(5) unsigned default NULL, PRIMARY KEY (`id`), KEY `IDX_Teilnehmer_1` (`pid`), FOREIGN KEY (`pid`) REFERENCES `test.Projekt` (`id`) ) TYPE=InnoDB | ++-- -- -- -- -- --+ 1 row in set (0.00 sec) mysql Please test again! Do you have the default charset set to german? The default is latin1 which I use. Note that The syntax of a foreign key constraint definition in InnoDB: [CONSTRAINT symbol] FOREIGN KEY [id] (index_col_name, ...) REFERENCES table_name (index_col_name, ...) [ON DELETE CASCADE | ON DELETE SET NULL | RESTRICT] Both tables have to be InnoDB type and there must be an index where the foreign key and the referenced key are listed as the first columns. InnoDB does not auto-create indexes on foreign keys or referenced keys: you have to create them explicitly. Corresponding columns in the foreign key and the referenced key must have similar internal data types inside InnoDB so that they can be compared without a type conversion. The size and the signedness of integer types has to be the same. The length of string types need not be the same. ... If MySQL gives the error number 1005 from a CREATE TABLE statement, and the error message string refers to errno 150, then the table creation failed because a foreign key constraint was not correctly formed. Similarly, if an ALTER TABLE fails and it refers to errno 150, that means a foreign key definition would be incorrectly formed for the altered table. Best regards, Heikki Tuuri Innobase Oy --- InnoDB - transactions, hot backup
MySQL Crashes When a Remote Connection Is Made
Description: MySQL crashes when a remote computer attempts to make a standard connection. Making a local connection does not cause this problem, connecting to other systems does not cause this problem, but a connection from a remote computer to mySQL immediately crashes mySQL. The details I have available (from safe_mysqld restarting) is [the segfault is at the exact moment we connect via mysql from a remote computer]: [root@george root]# Starting mysqld daemon with databases from /var/lib/mysql /usr/bin/safe_mysqld: line 269: 17274 Segmentation fault $NOHUP_NICENESS $ledir/$MYSQLD $defaults --basedir=$MY_BASEDIR_VERSION --datadir=$DATADIR $USER_OPTION --pid-file=$pid_file --skip-locking $err_log 21 Number of processes running now: 2 mysqld process hanging, pid 17277 - killed mysqld process hanging, pid 17277 - killed 021108 22:16:03 mysqld restarted How-To-Repeat: Connect from another computer on the internet. Use the mysql client. This syntax does it for us: mysql -hhostname -ppassword Fix: Unknown Submitter-Id: W_DW Originator:root Organization: sqlcoders MySQL support: none Synopsis: Remote connection crash server (also possible attack method) Severity: critical Priority: high Category: mysql Class: sw-bug Release: mysql-3.23.41 (Source distribution) Environment: System: Linux ensim.rackshack.net 2.4.18-17.7.x #1 Tue Oct 8 13:33:14 EDT 2002 i686 unknown Architecture: i686 Some paths: /usr/bin/perl /usr/bin/make /usr/bin/gmake /usr/bin/gcc /usr/bin/cc GCC: Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/2.96/specs gcc version 2.96 2731 (Red Hat Linux 7.2 2.96-108.7.2) Compilation info: CC='gcc' CFLAGS='-O2 -march=i386 -mcpu=i686 -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE' CXX='c++' CXXFLAGS='-O2 -march=i386 -mcpu=i686 -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE' LDFLAGS='' LIBC: lrwxrwxrwx1 root root 13 Oct 25 07:09 /lib/libc.so.6 - libc-2.2.4.so -rwxr-xr-x2 root root 1285884 Sep 9 12:10 /lib/libc-2.2.4.so -rw-r--r--1 root root 27336078 Sep 9 11:48 /usr/lib/libc.a -rw-r--r--1 root root 178 Sep 9 11:48 /usr/lib/libc.so Configure command: ./configure i386-redhat-linux --prefix=/usr --exec-prefix=/usr --bindir=/usr/bin --sbindir=/usr/sbin --sysconfdir=/etc --datadir=/usr/share --includedir=/usr/include --libdir=/usr/lib --libexecdir=/usr/libexec --localstatedir=/var --sharedstatedir=/usr/com --mandir=/usr/share/man --infodir=/usr/share/info --without-debug --without-readline --enable-shared --with-extra-charsets=complex --with-bench --localstatedir=/var/lib/mysql --with-unix-socket-path=/var/lib/mysql/mysql.sock --with-mysqld-user=mysql --with-extra-charsets=all --disable-assember --with-berkeley-db --enable-large-files=yes --enable-largefile=yes --with-thread-safe-client --enable-assembler - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: MySQL Crashes When a Remote Connection Is Made
On Fri, Nov 08, 2002 at 10:25:01PM -0500, [EMAIL PROTECTED] [EMAIL PROTECTED] is thought to have said: Description: MySQL crashes when a remote computer attempts to make a standard connection. Making a local connection does not cause this problem, connecting to other systems does not cause this problem, but a connection from a remote computer to mySQL immediately crashes mySQL. Update your glibc packages: https://rhn.redhat.com/errata/RHSA-2002-197.html The previous glibc security update caused things to break. -- Tabor J. Wells [EMAIL PROTECTED] Fsck It! Just another victim of the ambient morality - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
mysql crashes when the slave is started with incorrect master info
Description: When a slave is pointing to a non-existing master, doing slave start/slave stop will sometimes cause the MySQL server to crash How-To-Repeat: mysql change master to master_host='bogus', master_log_file=''; Query OK, 0 rows affected (0.00 sec) mysql slave start; ERROR 2006: MySQL server has gone away No connection. Trying to reconnect... Connection id:2 Current database: *** NONE *** ERROR 1198: This operation cannot be performed with a running slave, run SLAVE STOP first The server doesn't always crash. When I type slave start/slave stop, I maybe see a crash 10% of the time. Fix: Submitter-Id: submitter ID Originator:root Organization: MySQL support: [none | licence | email support | extended email support ] Synopsis: mysql crashes when the slave is started with incorrect master info Severity: Priority: Category: mysql Class: Release: mysql-3.23.53a (Official MySQL RPM) Server: /usr/bin/mysqladmin Ver 8.23 Distrib 3.23.53a, for pc-linux-gnu on i686 Copyright (C) 2000 MySQL AB MySQL Finland AB TCX DataKonsult AB This software comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to modify and redistribute it under the GPL license Server version 3.23.53a-Max Protocol version10 Connection Localhost via UNIX socket UNIX socket /var/lib/mysql/mysql.sock Uptime: 1 min 34 sec Threads: 1 Questions: 2 Slow queries: 0 Opens: 6 Flush tables: 1 Open tables: 0 Queries per second avg: 0.021 Environment: System: Linux exads28 2.4.18-smp #21 SMP Thu Oct 24 23:35:15 PDT 2002 i686 unknown Architecture: i686 Some paths: /usr/bin/perl /usr/bin/make /usr/bin/gmake Compilation info: CC='gcc' CFLAGS='-O6 -fno-omit-frame-pointer -mpentium' CXX='gcc' CXXFLAGS='-O6 -fno-omit-frame-pointer -felide-constructors -fno-exceptions -fno-rtti -mpentium' LDFLAGS='' LIBC: lrwxrwxrwx1 root root 13 Oct 24 13:43 /lib/libc.so.6 - libc-2.2.4.so -rwxr-xr-x1 root root 1282588 Sep 4 2001 /lib/libc-2.2.4.so Configure command: ./configure --disable-shared --with-mysqld-ldflags=-all-static --with-client-ldflags=-all-static --without-berkeley-db --without-innodb --enable-assembler --enable-local-infile --with-mysqld-user=mysql --with-unix-socket-path=/var/lib/mysql/mysql.sock --prefix=/ --with-extra-charsets=complex --exec-prefix=/usr --libexecdir=/usr/sbin --sysconfdir=/etc --datadir=/usr/share --localstatedir=/var/lib/mysql --infodir=/usr/share/info --includedir=/usr/include --mandir=/usr/share/man '--with-comment=Official MySQL RPM' CC=gcc 'CFLAGS=-O6 -fno-omit-frame-pointer -mpentium' 'CXXFLAGS=-O6 -fno-omit-frame-pointer -felide-constructors -fno-exceptions -fno-rtti -mpentium' CXX=gcc - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
MySQL crashes after an update statement
Description: MySQL crashes after issueing the following command : UPDATE BGW_Master, ICA_1_SplitInter SET ICA_1_SplitInter.I1_Proc_Dt = BGW_Master.I1_Proc_Dt WHERE BGW_Master.I1_FileName = ICA_1_SplitInter.I1_FileName AND BGW_Master.I1_runDate = ICA_1_SplitInter.I1_runDate AND ICA_1_SplitInter.I1_Proc_Dt is null; This is wierd since it not such a complex SQL after all... How-To-Repeat: Resumbit the SQL above Fix: Not found a workaround yet... Submitter-Id: Bas van Ritbergen Originator:Super-User Organization: O2 the Netherlands Haaksbergweg 75 1101 BR Amsterdam ZO +31-20-2004365 MySQL support: none Synopsis: MySQL crashes Severity: serious Priority: high Category: mysql Class: sw-bug Release: mysql-4.0.4-beta-max (Official MySQL-max binary) Environment: System: SunOS amBGw1 5.7 Generic_106541-17 sun4u sparc SUNW,Ultra-Enterprise Architecture: sun4 Some paths: /usr/bin/perl /usr/bin/make /usr/local/bin/gcc /usr/bin/cc GCC: Reading specs from /usr/local/lib/gcc-lib/sparc-sun-solaris2.7/3.2/specs Configured with: ../configure --with-as=/usr/ccs/bin/as --with-ld=/usr/ccs/bin/ld --disable-nls Thread model: posix gcc version 3.2 Compilation info: CC='gcc' CFLAGS='-O3 -fno-omit-frame-pointer' CXX='gcc' CXXFLAGS='-O3 -fno-omit-frame-pointer -felide-constructors -fno-exceptions -fno-rtti' LDFLAGS='' LIBC: -rw-r--r-- 1 bin bin 1707532 Oct 16 2001 /lib/libc.a lrwxrwxrwx 1 root root 11 Sep 5 2000 /lib/libc.so - ./libc.so.1 -rwxr-xr-x 1 bin bin 1125056 Oct 16 2001 /lib/libc.so.1 -rw-r--r-- 1 bin bin 1707532 Oct 16 2001 /usr/lib/libc.a lrwxrwxrwx 1 root root 11 Sep 5 2000 /usr/lib/libc.so - ./libc.so.1 -rwxr-xr-x 1 bin bin 1125056 Oct 16 2001 /usr/lib/libc.so.1 Configure command: ./configure --prefix=/usr/local/mysql '--with-comment=Official MySQL-max binary' --with-extra-charsets=complex --with-server-suffix=-max --enable-thread-safe-client --enable-local-infile --enable-assembler --disable-shared --with-berkeley-db CC=gcc 'CFLAGS=-O3 -fno-omit-frame-pointer' 'CXXFLAGS=-O3 -fno-omit-frame-pointer -felide-constructors -fno-exceptions -fno-rtti' CXX=gcc - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
re: MySQL crashes after an update statement
bas, Friday, October 18, 2002, 3:59:02 PM, you wrote: bdvaodc REALFROM: [EMAIL PROTECTED] Description: bdvaodc MySQL crashes after issueing the following command : bdvaodc UPDATE BGW_Master, ICA_1_SplitInter bdvaodc SET ICA_1_SplitInter.I1_Proc_Dt = BGW_Master.I1_Proc_Dt bdvaodc WHERE BGW_Master.I1_FileName = ICA_1_SplitInter.I1_FileName bdvaodc AND BGW_Master.I1_runDate = ICA_1_SplitInter.I1_runDate bdvaodc AND ICA_1_SplitInter.I1_Proc_Dt is null; bdvaodc This is wierd since it not such a complex SQL after all... Could you provide a structure of your tables with SHOW CREATE TABLE for testing? -- For technical support contracts, goto https://order.mysql.com/?ref=ma02-010c This email is sponsored by Ensita.net http://www.ensita.net/ __ ___ ___ __ / |/ /_ __/ __/ __ \/ /Victoria Reznichenko / /|_/ / // /\ \/ /_/ / /__ [EMAIL PROTECTED] /_/ /_/\_, /___/\___\_\___/ MySQL AB / Ensita.net ___/ www.mysql.com - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
mysql crashes after adding memory.
Yesterday, I increased the memory in my mysql server from 2 GByte to 4 GByte. Here the log file as it died: Number of processes running now: 1 mysqld process hanging, pid 1015 - killed 020808 09:40:12 mysqld restarted 020808 9:40:12 Can't start server: Bind on TCP/IP port: Address already in use020808 9:40:12 Do you already have another mysqld server running on port: 3306 ? 020808 9:40:12 Aborting 020808 9:40:12 /usr/local/mysql/bin/mysqld: Shutdown Complete 020808 09:40:12 mysqld ended The database was under heavy load at the time. The machine is a 'vanilla' dual 1 GHz P-III running RedHat Linux and a 2.4.17 kernel Server version: 3.23.49a-max-log After doing the memory upgrade, I also adjusted some of the parameters, in particular, I increased the key buffer to 2 Gig. The database has a very large (100,000,000 row, 30 GigByte) MyISAM table, and a few smaller myisam and innodb tables. It ran ok for at least half a year (last machine reboot). So far, it does not look like any data was corrupted. Usually, only a small number of client (10 or so) is connected. Here my my.cnf file: set-variable=max_connections=200 set-variable=max_allowed_packet=10M set-variable=key_buffer=2000M set-variable=join_buffer_size=200M set-variable=sort_buffer=150M set-variable=record_buffer=50M set-variable=record_rnd_buffer=50M set-variable=table_cache=200 set-variable=thread_concurrency=4 set-variable=long_query_time=5 innodb_data_home_dir=/usr/local/mysql/innodb innodb_data_file_path=data1/ibdata1:1M;data2/ibdata1:1M set-variable=innodb_buffer_pool_size=50M set-variable=innodb_additional_mem_pool_size=10M innodb_log_group_home_dir=/opt/innodb_logs innodb_log_arch_dir=/opt/innodb_logs innodb_log_archive=1 set-variable = innodb_log_files_in_group=3 set-variable = innodb_log_file_size=3M set-variable = innodb_log_buffer_size=100 innodb_flush_log_at_trx_commit=1 set-variable = innodb_file_io_threads=4 set-variable = innodb_lock_wait_timeout=50 - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: mysql crashes after adding memory.
If it is saying that it cannot bind to port 3306, then maybe the port is still locked by another process, mysqld or otherwise. netstat -na | grep 3306 should show you that. Kill that process and try again. Regards, Bhavin. - Original Message - From: Johannes Ullrich [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, August 08, 2002 11:31 AM Subject: mysql crashes after adding memory. Yesterday, I increased the memory in my mysql server from 2 GByte to 4 GByte. Here the log file as it died: Number of processes running now: 1 mysqld process hanging, pid 1015 - killed 020808 09:40:12 mysqld restarted 020808 9:40:12 Can't start server: Bind on TCP/IP port: Address already in use020808 9:40:12 Do you already have another mysqld server running on port: 3306 ? 020808 9:40:12 Aborting 020808 9:40:12 /usr/local/mysql/bin/mysqld: Shutdown Complete 020808 09:40:12 mysqld ended The database was under heavy load at the time. The machine is a 'vanilla' dual 1 GHz P-III running RedHat Linux and a 2.4.17 kernel Server version: 3.23.49a-max-log After doing the memory upgrade, I also adjusted some of the parameters, in particular, I increased the key buffer to 2 Gig. The database has a very large (100,000,000 row, 30 GigByte) MyISAM table, and a few smaller myisam and innodb tables. It ran ok for at least half a year (last machine reboot). So far, it does not look like any data was corrupted. Usually, only a small number of client (10 or so) is connected. Here my my.cnf file: set-variable=max_connections=200 set-variable=max_allowed_packet=10M set-variable=key_buffer=2000M set-variable=join_buffer_size=200M set-variable=sort_buffer=150M set-variable=record_buffer=50M set-variable=record_rnd_buffer=50M set-variable=table_cache=200 set-variable=thread_concurrency=4 set-variable=long_query_time=5 innodb_data_home_dir=/usr/local/mysql/innodb innodb_data_file_path=data1/ibdata1:1M;data2/ibdata1:1M set-variable=innodb_buffer_pool_size=50M set-variable=innodb_additional_mem_pool_size=10M innodb_log_group_home_dir=/opt/innodb_logs innodb_log_arch_dir=/opt/innodb_logs innodb_log_archive=1 set-variable = innodb_log_files_in_group=3 set-variable = innodb_log_file_size=3M set-variable = innodb_log_buffer_size=100 innodb_flush_log_at_trx_commit=1 set-variable = innodb_file_io_threads=4 set-variable = innodb_lock_wait_timeout=50 - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: MySQL crashes is fulltext search on with some words.
Hi! On Apr 16, Erlend Hopso Stromsvik wrote: I'm not sure if this has been reported earlier, but my mysql-server goes down if I run a query with two 'match against' where one of them contains/matches the word 'think'... Can you create a repeatable test case for this ? Regards, Sergei -- MySQL Development Team __ ___ ___ __ / |/ /_ __/ __/ __ \/ / Sergei Golubchik [EMAIL PROTECTED] / /|_/ / // /\ \/ /_/ / /__ MySQL AB, http://www.mysql.com/ /_/ /_/\_, /___/\___\_\___/ Osnabrueck, Germany ___/ - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
MySQL crashes is fulltext search on with some words.
I'm not sure if this has been reported earlier, but my mysql-server goes
down if I run a query with two 'match against' where one of them
contains/matches the word 'think'...
It terminates after the first query, but when I change the word 'think' to
'excel' or any other word it works flawlessy. I have written the queries
like this since '... against ('+windows +excel' IN BOOLEAN MODE)' doesn't
work in the 4.0.1 version of MySQL.
I find this pretty strange
If this is solved, are there som places where you can download the 4.0.2
source? I can try and put together a test case if it's not been seen before.
I've resovled the stack dump etc. etc.
From mysql consol:
mysql SELECT count(*) FROM DB_GNIST.varer WHERE MATCH (tittel) AGAINST
('windows' IN BOOLEAN MODE) AND match (tittel) against ('think' IN BOOLEAN
MODE);
ERROR 2006: MySQL server has gone away
No connection. Trying to reconnect...
Connection id:1
Current database: DB_GNIST
ERROR 2013: Lost connection to MySQL server during query
mysql SELECT count(*) FROM DB_GNIST.varer WHERE MATCH (tittel) AGAINST
('windows' IN BOOLEAN MODE) AND match (tittel) against ('excel' IN BOOLEAN
MODE);
ERROR 2006: MySQL server has gone away
No connection. Trying to reconnect...
Connection id:1
Current database: DB_GNIST
+--+
| count(*) |
+--+
| 149 |
+--+
1 row in set (0.17 sec)
mysql
mysql SELECT count(*) FROM DB_GNIST.varer WHERE MATCH (tittel) AGAINST
('windows' IN BOOLEAN MODE) AND match (tittel) against ('excel' IN BOOLEAN
MODE);
+--+
| count(*) |
+--+
| 149 |
+--+
1 row in set (0.16 sec)
Regards
Erlend Stromsvik
-
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail [EMAIL PROTECTED]
To unsubscribe, e-mail [EMAIL PROTECTED]
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Fwd: Bug#128473: [patch] the mysql crashes on the -D option
FYI
-christian-
On Wed, Jan 09, 2002 at 08:52:34PM +0100, Sjoerd Simons wrote:
Package: mysql-client
Version: 3.22.32-6
Severity: normal
Tags: patch
mysql -D something causes a segv, the attached patch to mysql.cc seems to fix
this..
...
--- mysql.cc.orig Wed Jan 9 20:46:07 2002
+++ mysql.cc Wed Jan 9 20:17:16 2002
@@ -500,7 +500,7 @@
bool tty_password=0;
set_all_changeable_vars(changeable_vars);
- while ((c=getopt_long(argc,argv,?ABCDLfHinNoqrstTvVwWEe:h:O:P:S:u:#::p::,
+ while ((c=getopt_long(argc,argv,?ABCD:LfHinNoqrstTvVwWEe:h:O:P:S:u:#::p::,
long_options, option_index)) != EOF)
{
switch(c) {
-
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail [EMAIL PROTECTED]
To unsubscribe, e-mail [EMAIL PROTECTED]
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Upgraded server, MySql Crashes with old databases
Need MySql 3.21 for Win2000 I have some old databases from MySql 3.21 and I want to move these to MySql 3.23, but the server just crashes. I've tried to start the MySql with --old-protocol, but no changes. My plan is to install MySql 3.21 on my PC to get the databases, but there is no download available. Is there a NT version of MySql 3.21? Does anybody know where to get this? Is there any other ways to read these databases? Thanks - Fredrik Lunde /Webutvikler/webdesigner Norwegiandesigner.net www.ndes.net [EMAIL PROTECTED] - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
MySQL crashes on a select query from select.test
MySQL crashes, when number of entries in table is greater than some number 'X', in mf_radix.c file on execution of a select query. Optimization used: O2 Please suggest some approach to debug this crash. It works fine with O0 optimization option. __ Do You Yahoo!? Find a job, post your resume. http://careers.yahoo.com - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
MYSQL crashes-SOLUTION found!
I am posting this in the hope it will be useful; I seem to have solved the problem. The problem was(on 3.23.38) and Linux 2.2.18 or 2.4.0 This is a huge system, all SCSI, 2GB or RAM, 2PIII x1000MHz processors and 37GB in the volume group corresponding to /var/lib/mysql There is an AHA29160 SCSI controller. A scipt was running continuously getting data into Mysql. Every so often the script peformed a mysqldump The problem was that at some point when I tried to access the database I would get a crash with error code 127. repair table of myisamchk -r could fix that, but not all data was being recovered. Similarly the dumps were corrupted. This was apparently caused by timeouts and the solution was to pass the boot parameter aic7xxx=seltime:0 in lilo. Perhaps this would be a useful addition to the the faqs S.Alexiou -- Here are some excerpts from /var/lib/mysql/'hostname'.err 010826 21:59:19 mysqld started /usr/sbin/mysqld: ready for connections 010827 14:05:37 mysqld started /usr/sbin/mysqld: ready for connections 010827 17:44:12 Aborted connection 171983 to db: 'CDR' user: 'spiros' host: `localhost' (Got an error reading communication packets) 010827 20:55:39 Aborted connection 513765 to db: 'CDR' user: 'spiros' host: `localhost' (Got an error reading communication packets) 010827 20:58:34 Aborted connection 521479 to db: 'CDR' user: 'spiros' host: `localhost' (Got an error reading communication packets) 010827 21:00:34 Aborted connection 524452 to db: 'CDR' user: 'spiros' host: `localhost' (Got an error reading communication packets) 010827 21:01:57 Aborted connection 529556 to db: 'CDR' user: 'spiros' host: `localhost' (Got an error reading communication packets) 010827 21:02:52 Aborted connection 533379 to db: 'CDR' user: 'spiros' host: `localhost' (Got an error reading communication packets) 010827 21:05:40 Aborted connection 540483 to db: 'CDR' user: 'spiros' host: `localhost' (Got an error reading communication packets) 010827 21:10:50 Aborted connection 554558 to db: 'CDR' user: 'spiros' host: `localhost' (Got an error reading communication packets) 010827 21:13:50 Aborted connection 556004 to db: 'CDR' user: 'spiros' host: `localhost' (Got an error reading communication packets) 010827 22:57:44 /usr/sbin/mysqld: Normal shutdown 010827 22:57:45 /usr/sbin/mysqld: Shutdown Complete 010830 18:17:47 mysqld started /usr/sbin/mysqld: ready for connections 010830 18:45:08 Aborted connection 41658 to db: 'CDR' user: 'spiros' host: `localhost' (Got an error reading communication packets) 010830 18:49:16 Aborted connection 50975 to db: 'CDR' user: 'spiros' host: `localhost' (Got an error reading communication packets) 010830 22:03:58 Aborted connection 528901 to db: 'CDR' user: 'spiros' host: `localhost' (Got an error reading communication packets) 010830 22:18:55 Aborted connection 565805 to db: 'CDR' user: 'spiros' host: `localhost' (Got an error reading communication packets) 010830 22:42:52 Warning: Found 11 of 17 rows when repairing './CDR/CDR_INCOMING_1360_1' 010830 22:56:39 Warning: Found 12 of 16 rows when repairing './CDR/CDR_INCOMING_1400_1' 010830 22:58:53 Warning: Found 7 of 12 rows when repairing './CDR/CDR_INCOMING_1412_0' 010830 23:00:26 Warning: Found 13 of 27 rows when repairing './CDR/CDR_INCOMING_1452_1' 010830 23:01:23 Warning: Found 5 of 18 rows when repairing './CDR/CDR_INCOMING_1491_1' 010830 23:02:28 Warning: Found 8 of 12 rows when repairing './CDR/CDR_INCOMING_1505_0' 010830 23:03:13 Warning: Found 1 of 6 rows when repairing './CDR/CDR_INCOMING_1522_1' 010830 23:09:00 Warning: Found 20 of 27 rows when repairing './CDR/CDR_INCOMING_1654_0' 010830 23:17:33 /usr/sbin/mysqld: Normal shutdown 010830 23:17:33 /usr/sbin/mysqld: Shutdown Some messages may also show up in /var/log/messages 29:36 quality4 PAM-unix2[1040]: session started for user root, service su change detected on device fd(2,0) Aug 25 21:17:07 quality4 kernel: scsi : aborting command due to timeout : pid 0, scsi0, channel 0, id 2, lun 0 Write (10) 00 03 92 cd 37 00 00 08 00 Aug 25 21:17:07 quality4 kernel: scsi : aborting command due to timeout : pid 0, scsi0, channel 0, id 2, lun 0 Write (10) 00 03 92 cd 3f 00 00 08 00 Aug 25 21:17:07 quality4 kernel: scsi : aborting command due to timeout : pid 0, scsi0, channel 0, id 2, lun 0 Write (10) 00 03 92 cd 47 00 00 08 00 Aug 25 21:17:07 quality4 kernel: scsi : aborting command due to timeout : pid 0, scsi0, channel 0, id 2, lun 0 Write (10) 00 03 92 cd 4f 00 00 08 00 Aug 25 21:17:07 quality4 kernel: scsi : aborting command due to timeout : pid 0, scsi0, channel 0, id 2, lun 0 Write (10) 00 03 92 cd 57 00 00 08 00 Aug 25 21:17:07 quality4 kernel: scsi : aborting command due to timeout : pid 0, scsi0, channel 0, id 2, lun 0 Write (10) 00 03 92 cd 5f 00 00 08 00 Aug 25 21:17:07 quality4 kernel: scsi
MySQL Crashes
Hi, I am new to MySQL. I downloaded MySQL for Windows version 3.23.38. When I installed in MyISAM mode, mysqld was running fine. Then I uncommented the configure parameters for innoDB in my.cnf. Mysqld initialized the database the folowing messages printed on screen. Can anyone help ? Thanks, Woyou InnoDB: The first specified data file \cygwin\usr\local\mysql\var\ibdata1 did not exist: InnoDB: a new database to be created! InnoDB: Setting file \cygwin\usr\local\mysql\var\ibdata1 size to 26214400 InnoDB: Database physically writes the file full: wait... InnoDB: Data file \cygwin\usr\local\mysql\var\ibdata2 did not exist: new to be c reated InnoDB: Setting file \cygwin\usr\local\mysql\var\ibdata2 size to 38797312 InnoDB: Database physically writes the file full: wait... InnoDB: Data file \cygwin\usr\local\mysql\var\ibdata3 did not exist: new to be c reated InnoDB: Setting file \cygwin\usr\local\mysql\var\ibdata3 size to 104857600 InnoDB: Database physically writes the file full: wait... InnoDB: Data file \cygwin\usr\local\mysql\var\ibdata4 did not exist: new to be c reated InnoDB: Setting file \cygwin\usr\local\mysql\var\ibdata4 size to 314572800 InnoDB: Database physically writes the file full: wait... InnoDB: Log file \cygwin\usr\local\mysql\var\ib_logfile0 did not exist: new to b e created InnoDB: Setting log file \cygwin\usr\local\mysql\var\ib_logfile0 size to 5242880 InnoDB: Log file \cygwin\usr\local\mysql\var\ib_logfile1 did not exist: new to b e created InnoDB: Setting log file \cygwin\usr\local\mysql\var\ib_logfile1 size to 5242880 InnoDB: Log file \cygwin\usr\local\mysql\var\ib_logfile2 did not exist: new to b e created InnoDB: Setting log file \cygwin\usr\local\mysql\var\ib_logfile2 size to 5242880 Innobase: Assertion failure in thread 4294535455 in file M:\mysql-3.23\innobase\ os\os0file.c line 187 Innobase: we intentionally generate a memory trap. Innobase: Send a bug report to [EMAIL PROTECTED] 010618 15:56:21 c:\MYSQL\BIN\mysqld.exe: Got signal 11. Aborting! 010618 15:56:21 Aborting InnoDB: Warning: shutting down not properly started database 010618 15:56:22 c:\MYSQL\BIN\mysqld.exe: Shutdown Complete __ Do You Yahoo!? Spot the hottest trends in music, movies, and more. http://buzz.yahoo.com/ - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: Provider claims 'it's normal that mysql crashes', is that true?
On Wed, Apr 04, 2001 at 05:26:39PM +0200, Gunnar von Boehn wrote: As I asked them why their mysql-server die so often, I got their standard problem email-answer that claims "mysql is scaling rather badly". The truth is probably closer to "we are scaling mysql badly". A well run MySQL server doesn't crash. There's no good reason you can't have hundreds of days of uptime. Jeremy -- Jeremy D. Zawodny, [EMAIL PROTECTED] Technical Yahoo - Yahoo Finance Desk: (408) 328-7878Fax: (408) 530-5454 Cell: (408) 439-9951 - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
RE: Provider claims 'it's normal that mysql crashes', is that true?
If its a hosting PROVIDER, the table locking issue should really only be a factor for your database. If your design is good, then the rest shouldn't matter. Machine memory and processing power are another issue entirely. Other users could drag the machine down with poor design issues. One issue that we encountered, due to our own ignorance of course, was not allowing enough swap space for our mysql installation. We had 64MB of swap on a machine with 64MB of RAM. When we tried to process large queries the machine ran out of memory and crashed hard. Our short term work around was to take another, unused, partition and reformat it as swap. With 1.5 GB of swap, we never saw another problem, but we don't let users build their own databases either. -Original Message- From: mysql-digest-help [mailto:[EMAIL PROTECTED]] Sent: Wednesday, April 04, 2001 11:27 AM To: mysql Cc: gvb Subject: Provider claims 'it's normal that mysql crashes', is that true? Hello My provider 11-Puretec (www.puretec.de) hosting more than 1.000.000 domains runs about 14 Databaseserver with MySQL 3.22.32-log on Linux dual Penti-III 500Mhz machines. In the last 6 month the average uptime of the mysql-servers was around 8 hours. As I asked them why their mysql-server die so often, I got their standard problem email-answer that claims "mysql is scaling rather badly". After further asking I got a personal answer that says: "it's normal the mysql-servers die because of heavy load". "We can't help that the mysql task keeps crashing if to many users access it. That's totally normal for a mysql database" Is that true? regards Gunnar von Boehn - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: Provider claims 'it's normal that mysql crashes', is that true?
No this is not true... a lot of the stability of the database server has to do with the #1 the load, and #2 the design of the database. But no MySQL should not be crashing this much. Scott At 05:26 PM 4/4/2001 +0200, Gunnar von Boehn wrote: Hello My provider 11-Puretec (www.puretec.de) hosting more than 1.000.000 domains runs about 14 Databaseserver with MySQL 3.22.32-log on Linux dual Penti-III 500Mhz machines. In the last 6 month the average uptime of the mysql-servers was around 8 hours. As I asked them why their mysql-server die so often, I got their standard problem email-answer that claims "mysql is scaling rather badly". After further asking I got a personal answer that says: "it's normal the mysql-servers die because of heavy load". "We can't help that the mysql task keeps crashing if to many users access it. That's totally normal for a mysql database" Is that true? regards Gunnar von Boehn - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php - Scott Baker - Webster Internet - Network Technician 503.266.8253 - [EMAIL PROTECTED] "It has been said that the primary function of schools is to impart enough facts to make children stop asking questions. Some, with whom the schools do not succeed, become scientists." - Knut Schmidt-Nielson - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: Provider claims 'it's normal that mysql crashes', is that true?
We've been running on RedHat distribution (starting with 5.2 or so) and Slackware before that for the last few years (currently running mysql 3.23.32... that update bug introduced in 3.23.34 really spanked us hard, we'll be moving to "latest" again soon). Currently, we've got dual and quad PII and PIII machines with upwards of 2GB of memory averaging around 400 queries/second (150-400 sessions at any given time). Our mysql uptime depends on how often we do software or hardware upgrades, not on mysql "mean time to crash". Translated: our mysql servers run for weeks/months. I consider our mysql databases to be very stable. :) Owen On Wed, 4 Apr 2001, Gunnar von Boehn wrote: Hello My provider 11-Puretec (www.puretec.de) hosting more than 1.000.000 domains runs about 14 Databaseserver with MySQL 3.22.32-log on Linux dual Penti-III 500Mhz machines. In the last 6 month the average uptime of the mysql-servers was around 8 hours. As I asked them why their mysql-server die so often, I got their standard problem email-answer that claims "mysql is scaling rather badly". After further asking I got a personal answer that says: "it's normal the mysql-servers die because of heavy load". "We can't help that the mysql task keeps crashing if to many users access it. That's totally normal for a mysql database" Is that true? regards Gunnar von Boehn - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php -- USMail: CareerSite Corporation, 310 Miller Avenue, Ann Arbor, MI 48103 Phone:+1 734 213-9500 FAX:+1 734 213-9011 mailto:[EMAIL PROTECTED] http://www.careersite.com/~osm/ - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: Provider claims 'it's normal that mysql crashes', is that true?
On Wed, 04 Apr 2001, Gunnar von Boehn wrote: Hello My provider 11-Puretec (www.puretec.de) hosting more than 1.000.000 domains runs about 14 Databaseserver with MySQL 3.22.32-log on Linux dual Penti-III 500Mhz machines. In the last 6 month the average uptime of the mysql-servers was around 8 hours. As I asked them why their mysql-server die so often, I got their standard problem email-answer that claims "mysql is scaling rather badly". After further asking I got a personal answer that says: "it's normal the mysql-servers die because of heavy load". "We can't help that the mysql task keeps crashing if to many users access it. That's totally normal for a mysql database" Is that true? Only if their servers/queries are set up wrong. We use Sparc/Solaris exclusively in our production network now but used to have more data than this hosted on a similar machine. They could be telling the truth is they have huge queries that lock the tables for extended periods. The table level locking of .ism tables can cause problems on very busy servers. MySQL's newer tables avoid this problem but I'm not sure how production ready they are. Nigel - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: Provider claims 'it's normal that mysql crashes', is that true?
After further asking I got a personal answer that says: "it's normal the mysql-servers die because of heavy load". "We can't help that the mysql task keeps crashing if to many users access it. That's totally normal for a mysql database" Running 3.22.32 that's prehistoric (sort of).. I think I even remember some problems with 3.22.32 .. not sure though.. Our own mysqlservers have an average downtime of 1 hour (maybe 2 hours) per year, per server!! mostly because of maintenance. To many users accessing their MySQL server.. can be.. but then you increase the amount of servers you've got. An average of 71000 users per server might be a little to must.. even if only 10 percent would use MySQL sound still as to many users. Time to find yourself another ISP.. if they can't be convinced in spending a few DM extra that is.. Bye, B. - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
MySQL crashes permanently on FreeBSD thru signal 11 or 10
Description: Database: total: about 500Mb now mostly used table: about 300Mb data, about 150Mb index, about 6,7 millions of records, two indexes(primary key contains 3 fields, and other index contains 2 fields) other tables is negligible (U see) How-To-Repeat: we repeating crash by make 1000 to 1 subsequent SQL requests (by scripts) Fix: how to correct or work around the problem, if known (multiple lines) Submitter-Id: [EMAIL PROTECTED] Originator: Organization: Rusian Space Research Institute, SMIS Laboratory MySQL support: none Synopsis: Permanent crashes thru signal 11 (without core) or thru signal 10 (with core) Severity: critical Priority: high Category: mysql Class: sw-bug Release: mysql-3.23.32 (Source distribution) Environment: Hardware: CPU: Dual PIII-933 Mother: SuperMicro SS-LE chipset (so hardware bugs are unlikely) Memory: 512Mb Registered ECC SDRAM in two modules (so memory rather works properly) HDD: Adaptec 2100S RAID controller 32Mb cache with 4*18Gb Quantum U160 SCSI HDDs configured as RAID5 Case: InWin server rackmount with MANY BIG coolers (so overheat is unlikely) System: FreeBSD fishdb.iki.rssi.ru 4.2-RELEASE FreeBSD 4.2-RELEASE #0: Mon Jan 29 17:47:36 MSK 2001 [EMAIL PROTECTED]:/usr/src/sys/compile/DUAL i386 Some paths: /usr/bin/perl /usr/bin/make /usr/bin/gcc /usr/bin/cc GCC: Using builtin specs. gcc version 2.95.2 19991024 (release) Compilation info: CC='gcc' CFLAGS='-O6' CXX='gcc' CXXFLAGS='-O6 -felide-constructors -fno-exceptions -fno-rtti' LDFLAGS='' LIBC: -r--r--r-- 1 root wheel 1169076 Nov 20 14:59 /usr/lib/libc.a lrwxrwxrwx 1 root wheel 9 Jan 29 19:44 /usr/lib/libc.so - libc.so.4 -r--r--r-- 1 root wheel 559196 Nov 20 14:59 /usr/lib/libc.so.4 Configure command: ./configure --with-debug --prefix=/usr/local/mysql-3.23.32debug Perl: This is perl, version 5.005_03 built for i386-freebsd (Kernel compiling was made without errors and no other software fails except MySQL - about system stability) Kernel configuration: Generic except SMP and APIC_IO options (dual CPUs) MySQL variables: --- mysql show variables; +-+- --+ | Variable_name | Value | +-+- --+ | ansi_mode | OFF | | back_log| 50 | | basedir | /usr/local/mysql-3.23.32debug/ | | binlog_cache_size | 32768 | | character_set | cp1251 | | character_sets | latin1 dec8 dos german1 hp8 koi8_ru latin2 swe7 usa7 |cp1251 danish hebrew win1251 estonia hungarian koi8 _ukr win1251ukr greek win1250 croat cp1257 latin5 | | concurrent_insert | ON | | connect_timeout | 5 | | datadir | /db/mysql/ | | delay_key_write | ON | delayed_insert_limit| 100 | | delayed_insert_timeout | 300 | | delayed_queue_size | 1000 | | flush | OFF | | flush_time | 0 | | have_bdb| NO | | have_gemini | NO | | have_innobase | NO | | have_isam | YES | | have_raid | NO | | have_ssl| NO | | init_file | | | interactive_timeout | 28800 | | join_buffer_size| 131072 | | key_buffer_size | 268431360 | | language|
Re: MySQL crashes permanently on FreeBSD thru signal 11 or 10
Hi!
As it has been posted to this mailinglist, you have to upgrade your
system to 4.2 STABLE.
Then, please use a contributed 3.23.33 binary for 4.2 stable from 3.23
download page.
And what do you use MySQL for in your esteemed Institute ??
Regards,
Sinisa
__ _ _ ___ == MySQL AB
/*/\*\/\*\ /*/ \*\ /*/ \*\ |*| Sinisa Milivojevic
/*/ /*/ /*/ \*\_ |*| |*||*| mailto:[EMAIL PROTECTED]
/*/ /*/ /*/\*\/*/ \*\|*| |*||*| Larnaca, Cyprus
/*/ /*/ /*/\*\_/*/ \*\_/*/ |*|
/*/^^^\*\^^^
/*/ \*\Developers Team
-
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail [EMAIL PROTECTED]
To unsubscribe, e-mail [EMAIL PROTECTED]
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
