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
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
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
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]
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]
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]
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
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
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
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
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
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
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
