Re: mysqld got signal 11;
Hi, Michael Fernández M. wrote: key_buffer_size=402653184 read_buffer_size=2093056 max_used_connections=323 max_connections=800 threads_connected=55 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 3666809 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. I have 4 GB RAM, and the value of this variable was: 1 MB, i increased to 500 MB, but i am not sure if this could solve the problem. Do you use 64 or 32bit Kernel? I think with 32bit a single process like MySQL can only allocate about 2GB of RAM in total. You might want to check that. How big is your InnoDB buffer pool? regards Nils -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: mysqld got signal 11;
El mar, 20-02-2007 a las 13:16 +0100, Nils Meyer escribió: Hi, Michael Fernández M. wrote: key_buffer_size=402653184 read_buffer_size=2093056 max_used_connections=323 max_connections=800 threads_connected=55 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 3666809 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. I have 4 GB RAM, and the value of this variable was: 1 MB, i increased to 500 MB, but i am not sure if this could solve the problem. Do you use 64 or 32bit Kernel? I think with 32bit a single process like MySQL can only allocate about 2GB of RAM in total. You might want to check that. How big is your InnoDB buffer pool? i use 32 Bits kernel. innodb_additional_mem_pool_size = 500 MB. innodb_buffer_pool_size = 8 MB Before the innodb_additional_mem_pool_size was 1 MB, (the default value) and yesterday i increased to 500MB. But i did not touch the innodb_buffer_pool_size this still have 8 MB. Mysql have around of 400 transactions per second- Regards! Michael.- regards Nils -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: mysqld got signal 11;
Hi, Michael Fernández M. wrote: i use 32 Bits kernel. Remember that you have to stay under 2GB total memory allocation! I think you hit that limit. innodb_additional_mem_pool_size = 500 MB. innodb_buffer_pool_size = 8 MB Before the innodb_additional_mem_pool_size was 1 MB, (the default value) and yesterday i increased to 500MB. But i did not touch the innodb_buffer_pool_size this still have 8 MB. Your buffer pool is a bit small, if you use innodb heavily. The innodb_additional_mem_pool is way to large I think the size could be lowered to something around 30MB. regards Nils -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: mysqld got signal 11;
El mar, 20-02-2007 a las 13:38 +0100, Nils Meyer escribió: Hi, Michael Fernández M. wrote: i use 32 Bits kernel. Remember that you have to stay under 2GB total memory allocation! I think you hit that limit. Sorry, but why do you say that?, because of the 32 bits kernel? innodb_additional_mem_pool_size = 500 MB. innodb_buffer_pool_size = 8 MB Before the innodb_additional_mem_pool_size was 1 MB, (the default value) and yesterday i increased to 500MB. But i did not touch the innodb_buffer_pool_size this still have 8 MB. Your buffer pool is a bit small, if you use innodb heavily. which is the recommended value for: innodb_buffer_pool_size? in my case? The innodb_additional_mem_pool is way to large I think the size could be lowered to something around 30MB. ok, i will decrease it. Thanks! regards Nils -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: mysqld got signal 11;
Michael Fernández M. wrote: Remember that you have to stay under 2GB total memory allocation! I think you hit that limit. Sorry, but why do you say that?, because of the 32 bits kernel? Yes exactly. Depending on kernel version you can allocate something between 2 or 2.7GB. Until 2GB it's safe, over 2GB there be dragons. If you have lots of MyISAM tables the remaining memory can still be used for the OS file cache. which is the recommended value for: innodb_buffer_pool_size? in my case? It's difficult to suggest a value here as I'd have to know full table schemas and queries. I have a server with a mixed InnoDB/MyISAM setup and 4GB RAM and set the buffer pool to 512M. You can fine-tune that with SHOW ENGINE INNODB STATUS; which will tell you how much of the buffer pool is in use. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: mysqld got signal 11
Privet! key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 441967 K Check that you have enough virtual memory for MySQL processes. Have a look at: http://dev.mysql.com/doc/refman/5.0/en/freebsd.html http://dev.mysql.com/doc/refman/5.0/en/crashing.html What version of MySQL are you using and in what way have you installed it. Please report an exact version of FreeBSD. Гаврилов Вячеслав wrote: Hello developers of MySql. It is my problem: --- 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=33554432 read_buffer_size=2093056 max_used_connections=22 max_connections=100 threads_connected=8 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 441967 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. -- This message from mysql_err.log. It up very often. At 1-2 days.How you comment this? In my system FreeBSD work RADIUS and write account in database on MySQL server . Calls friquency is 1-8 in one second. -- For technical support contracts, goto https://order.mysql.com/?ref=ensita This email is sponsored by Ensita.NET http://www.ensita.net/ __ ___ ___ __ / |/ /_ __/ __/ __ \/ /Gleb Paharenko / /|_/ / // /\ \/ /_/ / /__ [EMAIL PROTECTED] /_/ /_/\_, /___/\___\_\___/ MySQL AB / Ensita.NET ___/ www.mysql.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
RE: mysqld got signal 11; (CRASH max-3.23.51) What do I need to do to clean up?
I wouldn't run 3.23.51, there have been major security patches since then. I always mess up the byte math, but it looks to me like you have 2 gigs of ram in your box and you are allocating 2.3 gigs to mysql. With 263 connections you would have been using about 1.4 gigs, if you have anything else running on the box, this might be a problem. Whenever I've had a server getting the signal 11 crash adjusting my my.cnf has solved the problem. I would read the manual section on server tuning. I don't think you want mysql to use swap, I don't know, I try to stick with just under the total amount of ram in a box that is only running mySQL and under 40% in a box that is not dedicated (depending on what else is running). Of course there's not really any real logic, math or science to that, it's just what I have found works on our boxes. -Original Message- From: Joe Smith [mailto:[EMAIL PROTECTED] Sent: Friday, March 21, 2003 10:53 AM To: [EMAIL PROTECTED] Subject: mysqld got signal 11; (CRASH max-3.23.51) What do I need to do to clean up? Had my first mysqld crash today after a solid 4 month uptime.The details are below. The DB restarted, and I haven't been able to detect any corruption. Is there anything I should be running to ensure the integrity of the Innodb databases? Running: mysql-max-3.23.51, Innodb databases, Dual Intel 933s 2 Gigs ram 2 gigs swap 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=402649088 record_buffer=2093056 sort_buffer=2097144 max_used_connections=263 max_connections=500 threads_connected=31 It is possible that mysqld could use up to key_buffer_size + (record_buffer + sort_buffer)*max_connections = 2439208 K bytes of memory Hope that's ok, if not, decrease some variables in the equation 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... Stack range sanity check OK, backtrace follows: 0x806bb15 0x82c1328 0x82c28c3 0x82bfb44 0x80cbb40 0x8073a4d 0x80753c8 0x8071324 0x80707f7 Stack trace seems successful - bottom reached Please read http://www.mysql.com/doc/U/s/Using_stack_trace.html and follow instr uctions 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 0x6a856288 is invalid pointer thd-thread_id=42019698 Successfully dumped variables, if you ran with --log, take a look at the details of what thread 42019698 did to cause the crash. In some cases of really bad corruption, the values shown above may be invalid The manual page at http://www.mysql.com/doc/C/r/Crashing.html contains information that should help you find out what is causing the crash Number of processes running now: 0 /prod/mysql-max-3.23.51-log/bin/resolve_stack_dump -s mysqld.sym -n stack.trace 0x806bb15 handle_segfault__Fi + 425 0x82c1328 pthread_sighandler + 184 0x82c28c3 __pthread_unlock + 147 0x82bfb44 pthread_mutex_unlock + 164 0x80cbb40 mysqld_list_processes__FP3THDPCcb + 1780 0x8073a4d mysql_execute_command__Fv + 7161 0x80753c8 mysql_parse__FP3THDPcUi + 72 0x8071324 do_command__FP3THD + 1316 0x80707f7 handle_one_connection__FPv + 659 Is this a known issue? I'm guessing I should upgrade to mysql-4.12 now... Thanks! Joe - 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: mysqld got signal 11; (CRASH max-3.23.51) What do I need to do to clean up?
Joe, - Original Message - From: Jennifer Goodie [EMAIL PROTECTED] Newsgroups: mailing.database.mysql Sent: Friday, March 21, 2003 9:45 PM Subject: RE: mysqld got signal 11; (CRASH max-3.23.51) What do I need to do to clean up? I wouldn't run 3.23.51, there have been major security patches since then. I always mess up the byte math, but it looks to me like you have 2 gigs of ram in your box and you are allocating 2.3 gigs to mysql. With 263 connections you would have been using about 1.4 gigs, if you have anything else running on the box, this might be a problem. Whenever I've had a server getting the signal 11 crash adjusting my my.cnf has solved the problem. I would read the manual section on server tuning. I don't think you want mysql to use swap, I don't know, I try to stick with just under the total amount of ram in a box that is only running mySQL and under 40% in a box that is not dedicated (depending on what else is running). Of course there's not really any real logic, math or science to that, it's just what I have found works on our boxes. -Original Message- From: Joe Smith [mailto:[EMAIL PROTECTED] Sent: Friday, March 21, 2003 10:53 AM To: [EMAIL PROTECTED] Subject: mysqld got signal 11; (CRASH max-3.23.51) What do I need to do to clean up? Had my first mysqld crash today after a solid 4 month uptime.The details are below. The DB restarted, and I haven't been able to detect any corruption. Is there anything I should be running to ensure the integrity of the Innodb databases? Running: mysql-max-3.23.51, Innodb databases, Dual Intel 933s 2 Gigs ram 2 gigs swap 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=402649088 record_buffer=2093056 sort_buffer=2097144 max_used_connections=263 max_connections=500 threads_connected=31 It is possible that mysqld could use up to key_buffer_size + (record_buffer + sort_buffer)*max_connections = 2439208 K bytes of memory Hope that's ok, if not, decrease some variables in the equation 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... Stack range sanity check OK, backtrace follows: 0x806bb15 0x82c1328 0x82c28c3 0x82bfb44 0x80cbb40 0x8073a4d 0x80753c8 0x8071324 0x80707f7 Stack trace seems successful - bottom reached Please read http://www.mysql.com/doc/U/s/Using_stack_trace.html and follow instr uctions 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 0x6a856288 is invalid pointer thd-thread_id=42019698 Successfully dumped variables, if you ran with --log, take a look at the details of what thread 42019698 did to cause the crash. In some cases of really bad corruption, the values shown above may be invalid The manual page at http://www.mysql.com/doc/C/r/Crashing.html contains information that should help you find out what is causing the crash Number of processes running now: 0 /prod/mysql-max-3.23.51-log/bin/resolve_stack_dump -s mysqld.sym -n stack.trace 0x806bb15 handle_segfault__Fi + 425 0x82c1328 pthread_sighandler + 184 0x82c28c3 __pthread_unlock + 147 0x82bfb44 pthread_mutex_unlock + 164 0x80cbb40 mysqld_list_processes__FP3THDPCcb + 1780 0x8073a4d mysql_execute_command__Fv + 7161 0x80753c8 mysql_parse__FP3THDPcUi + 72 0x8071324 do_command__FP3THD + 1316 0x80707f7 handle_one_connection__FPv + 659 Is this a known issue? I'm guessing I should upgrade to mysql-4.12 now... Jennifer already gave very relevant advice. I can add that Monty fixed a crash in SHOW PROCESSLIST some 3 months ago. An upgrade could solve the crash problem. Your crash probably was a clean one and InnoDB recovered without problems. But best to run CHECK TABLE on your tables to be sure. Thanks! Joe 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 - 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: mysqld got signal 11; This could be because you hit a bug ....
Hello, I have followed your suggestion. I have installed mysql-debug-4.0.10-gamma-sun-solaris2.9-sparc-64bit on the Solaris 8 (Machine with 8 cpus, 32GB of Memory and 64 of swap) server. I have started the mysqld program as root I have specified the core-file in the /etc/my.cnf file. Other info that could be interesting in the /etc/my.cnf are _ set-variable = max_connections=16 set-variable = max_tmp_tables=512 set-variable= table_cache=512 set-variable = key_buffer=16384M set-variable= sort_buffer=1K set-variable= record_buffer=1K set-variable= thread_cache_size=8 set-variable= thread_cache=512 set-variable= thread_concurrency=12 _ I have started 7 concurrent mysql threads (7 OPTIMIZE TABLE from mysql command line) and after 9 hours I got a segmentation fault with Error ERROR 2013: Lost connection to MySQL server during query ERROR 2013: Lost connection to MySQL server during query ERROR 2013: Lost connection to MySQL server during query ERROR 2013: Lost connection to MySQL server during query ERROR 2013: Lost connection to MySQL server during query ERROR 2013: Lost connection to MySQL server during query ERROR 2013: Lost connection to MySQL server during query Segmentation Fault 030223 16:11:05 mysqld restarted I have looked at the mysqld error log file and this is the message 030223 07:03:11 mysqld started /usr/local/mysql-debug-4.0.10-gamma-sun-solaris2.9-sparc-64bit/bin/mysqld: ready for connections. Version: '4.0.10-gamma-debug-debug-log' socket: '/tmp/mysql.sock' port: 3306 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=17179869184 read_buffer_size=8192 sort_buffer_size=32768 max_used_connections=7 max_connections=16 threads_connected=8 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 16777856 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Writing a core file 030223 16:11:05 mysqld restarted __ I have looked for the core file, but I couldn't find it, even though in the error log it says Writing a core file. Does this give you any clue about what is causing the error ? Could you help please about the core file Do I need to specify the option differently ? Thanks in advance for your help, Mariella At 04:34 PM 1/29/03 +0200, Sinisa Milivojevic wrote: On Tue, 28 Jan 2003 17:12:14 -0700 Mariella Di Giacomo [EMAIL PROTECTED] wrote: Hello, I am running mysql server (mysql-standard-4.0.5-beta-64bit) 64 bit on Sun Solaris 2.8 and I have got the binaries form the mysql web site. The machine I am using has 32GB of RAM + 64GB of swap. Thanks in advance for your help, Mariella Hi! The reason why MySQL is crashing is not due to the fact that your memory is exhausted. It is possible that you have shell limits that are far below the available memory, but in your case even that is not a problem. What you should do is get a 4.0.10 debug binary for Solaris 2.8 from our site and send us a core file that is created on the crash. Also add --core-file to startup options. -- Regards, -- For technical support contracts, go to https://order.mysql.com/?ref=msmi __ ___ ___ __ / |/ /_ __/ __/ __ \/ /Mr. Sinisa Milivojevic [EMAIL PROTECTED] / /|_/ / // /\ \/ /_/ / /__ MySQL AB, FullTime Developer /_/ /_/\_, /___/\___\_\___/ Larnaca, Cyprus ___/ 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: mysqld got signal 11; This could be because you hit a bug ....
Mariella Di Giacomo writes: Hello, I have followed your suggestion. I have installed mysql-debug-4.0.10-gamma-sun-solaris2.9-sparc-64bit on the Solaris 8 (Machine with 8 cpus, 32GB of Memory and 64 of swap) server. I have started the mysqld program as root I have specified the core-file in the /etc/my.cnf file. Other info that could be interesting in the /etc/my.cnf are HI! Causes of the crashes could be many, among the others: * using 2.9 binary on Solaris 2.8 !! Please use 2.8 binary, we have it * setting sort and record buffers to 1K !! Please set them at 1M There are many other things that could be improved, but that can be done when and if you become a registered customer. I have looked for the core file, but I couldn't find it, even though in the error log it says Writing a core file. Make sure all ulimit values are OK, including the one for core file. Does this give you any clue about what is causing the error ? Could you help please about the core file Do I need to specify the option differently ? Thanks in advance for your help, Mariella Regards, -- For technical support contracts, go to https://order.mysql.com/?ref=msmi __ ___ ___ __ / |/ /_ __/ __/ __ \/ /Mr. Sinisa Milivojevic [EMAIL PROTECTED] / /|_/ / // /\ \/ /_/ / /__ MySQL AB, Fulltime Developer /_/ /_/\_, /___/\___\_\___/ Larnaca, Cyprus ___/ www.mysql.com Join MySQL Users Conference and Expo: http://www.mysql.com/events/uc2003/ - 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: mysqld got signal 11; This could be because you hit a bug ....
Hi, I will install the 2.8 debug version. The reason why I set setting sort and record buffers to 1K is because with a few tests I have noticed that I was getting a better response time for queries. The limit for the core file was unlimited. I will look into customer support. Mariella At 06:17 PM 2/24/03 +0200, you wrote: Mariella Di Giacomo writes: Hello, I have followed your suggestion. I have installed mysql-debug-4.0.10-gamma-sun-solaris2.9-sparc-64bit on the Solaris 8 (Machine with 8 cpus, 32GB of Memory and 64 of swap) server. I have started the mysqld program as root I have specified the core-file in the /etc/my.cnf file. Other info that could be interesting in the /etc/my.cnf are HI! Causes of the crashes could be many, among the others: * using 2.9 binary on Solaris 2.8 !! Please use 2.8 binary, we have it * setting sort and record buffers to 1K !! Please set them at 1M There are many other things that could be improved, but that can be done when and if you become a registered customer. I have looked for the core file, but I couldn't find it, even though in the error log it says Writing a core file. Make sure all ulimit values are OK, including the one for core file. Does this give you any clue about what is causing the error ? Could you help please about the core file Do I need to specify the option differently ? Thanks in advance for your help, Mariella Regards, -- For technical support contracts, go to https://order.mysql.com/?ref=msmi __ ___ ___ __ / |/ /_ __/ __/ __ \/ /Mr. Sinisa Milivojevic [EMAIL PROTECTED] / /|_/ / // /\ \/ /_/ / /__ MySQL AB, Fulltime Developer /_/ /_/\_, /___/\___\_\___/ Larnaca, Cyprus ___/ www.mysql.com Join MySQL Users Conference and Expo: http://www.mysql.com/events/uc2003/ - 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: mysqld got signal 11; This could be because you hit a bug ....
Mariella Di Giacomo writes: Hi, I will install the 2.8 debug version. The reason why I set setting sort and record buffers to 1K is because with a few tests I have noticed that I was getting a better response time for queries. The limit for the core file was unlimited. I will look into customer support. Mariella Please also make sure that mysqld is run under mysql user and that all UNIX permissions are fine. BTW 4.0.11 is out with some fixes for OPTIMIZE table. Regards, -- For technical support contracts, go to https://order.mysql.com/?ref=msmi __ ___ ___ __ / |/ /_ __/ __/ __ \/ /Mr. Sinisa Milivojevic [EMAIL PROTECTED] / /|_/ / // /\ \/ /_/ / /__ MySQL AB, FullTime Developer /_/ /_/\_, /___/\___\_\___/ Larnaca, Cyprus ___/ 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: mysqld got signal 11; This could be because you hit a bug ....
Hi, I would prefer the debug version which the latest I believe is the 4.0.10. The same error I get it when I run ALTER TABLES or I try to insert data into tables. I will try and let you know. Thanks, Mariella At 06:31 PM 2/24/03 +0200, you wrote: Mariella Di Giacomo writes: Hi, I will install the 2.8 debug version. The reason why I set setting sort and record buffers to 1K is because with a few tests I have noticed that I was getting a better response time for queries. The limit for the core file was unlimited. I will look into customer support. Mariella Please also make sure that mysqld is run under mysql user and that all UNIX permissions are fine. BTW 4.0.11 is out with some fixes for OPTIMIZE table. Regards, -- For technical support contracts, go to https://order.mysql.com/?ref=msmi __ ___ ___ __ / |/ /_ __/ __/ __ \/ /Mr. Sinisa Milivojevic [EMAIL PROTECTED] / /|_/ / // /\ \/ /_/ / /__ MySQL AB, FullTime Developer /_/ /_/\_, /___/\___\_\___/ Larnaca, Cyprus ___/ 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: mysqld got signal 11; This could be because you hit a bug ....
Mariella Di Giacomo writes: Hi, I would prefer the debug version which the latest I believe is the 4.0.10. The same error I get it when I run ALTER TABLES or I try to insert data into tables. I will try and let you know. Thanks, Mariella 4.0.11 will be quite soon, but your problems indicate that it is some system setup error, which would be very fast diagnosed if we would login to your system. Regards, -- For technical support contracts, go to https://order.mysql.com/?ref=msmi __ ___ ___ __ / |/ /_ __/ __/ __ \/ /Mr. Sinisa Milivojevic [EMAIL PROTECTED] / /|_/ / // /\ \/ /_/ / /__ MySQL AB, FullTime Developer /_/ /_/\_, /___/\___\_\___/ Larnaca, Cyprus ___/ 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: mysqld got signal 11; This could be because you hit a bug ....
- Original Message - From: Mariella Di Giacomo [EMAIL PROTECTED] To: [EMAIL PROTECTED]; [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Wednesday, January 29, 2003 1:12 AM Subject: mysqld got signal 11; This could be because you hit a bug Hello, I am running mysql server (mysql-standard-4.0.5-beta-64bit) 64 bit on Sun Solaris 2.8 and I have got the binaries form the mysql web site. The machine I am using has 32GB of RAM + 64GB of swap. Hi Mariella, My, that is a LOT of memory! :) What could you possibly have running that allows only 16 connections, yet uses up to the max of 96 GigaByte? :) Yikes! I take it this is high-quality ECC memory? If not, with that much memory, a seg fault could easily occur. I believe FreeBSD already advises to uses ECC memory when you have as little as 4 G. I'm sure you got that covered, though; just checking. :) - Mark - 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: mysqld got signal 11; This could be because you hit a bug ....
On Tue, 28 Jan 2003 17:12:14 -0700 Mariella Di Giacomo [EMAIL PROTECTED] wrote: Hello, I am running mysql server (mysql-standard-4.0.5-beta-64bit) 64 bit on Sun Solaris 2.8 and I have got the binaries form the mysql web site. The machine I am using has 32GB of RAM + 64GB of swap. Thanks in advance for your help, Mariella Hi! The reason why MySQL is crashing is not due to the fact that your memory is exhausted. It is possible that you have shell limits that are far below the available memory, but in your case even that is not a problem. What you should do is get a 4.0.10 debug binary for Solaris 2.8 from our site and send us a core file that is created on the crash. Also add --core-file to startup options. -- Regards, -- For technical support contracts, go to https://order.mysql.com/?ref=msmi __ ___ ___ __ / |/ /_ __/ __/ __ \/ /Mr. Sinisa Milivojevic [EMAIL PROTECTED] / /|_/ / // /\ \/ /_/ / /__ MySQL AB, FullTime Developer /_/ /_/\_, /___/\___\_\___/ Larnaca, Cyprus ___/ 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: mysqld got signal 11; This could be because you hit a bug ....
Hi Mark, Thanks. The memory that we are using is ECC. The reason I have only 16 connections is because that DB is used only for updates. In reality for that DB we use 3 or 4 connections maximum. We have a mirror copy used for customers which has a lot of connections. Mariella At 10:22 AM 1/29/03 +0100, Mark wrote: - Original Message - From: Mariella Di Giacomo [EMAIL PROTECTED] To: [EMAIL PROTECTED]; [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Wednesday, January 29, 2003 1:12 AM Subject: mysqld got signal 11; This could be because you hit a bug Hello, I am running mysql server (mysql-standard-4.0.5-beta-64bit) 64 bit on Sun Solaris 2.8 and I have got the binaries form the mysql web site. The machine I am using has 32GB of RAM + 64GB of swap. Hi Mariella, My, that is a LOT of memory! :) What could you possibly have running that allows only 16 connections, yet uses up to the max of 96 GigaByte? :) Yikes! I take it this is high-quality ECC memory? If not, with that much memory, a seg fault could easily occur. I believe FreeBSD already advises to uses ECC memory when you have as little as 4 G. I'm sure you got that covered, though; just checking. :) - Mark - 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: mysqld got signal 11;
Hi, MEMORY PROBLEM ... a pointers is gone a way ... The signal is SIGSEV and this mean in fact: Invalid memory reference. Regards, Gelu _ G.NET SOFTWARE COMPANY Permanent e-mail address : [EMAIL PROTECTED] [EMAIL PROTECTED] - Original Message - From: Luc Foisy [EMAIL PROTECTED] To: MYSQL-List (E-mail) [EMAIL PROTECTED] Sent: Friday, May 17, 2002 6:26 PM Subject: mysqld got signal 11; Can anyone tell me what this means?? mysqld got signal 11; The manual section 'Debugging a MySQL server' tells you how to use a stack trace and/or the core file to produce a readable backtrace that may help in finding out why mysqld died Attemping 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, ebp=0xb, backtrace may not be correct Bogus stack limit or frame pointer, aborting backtrace Number of processes running now: 0 Luc Foisy - 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: mysqld got signal 11;
Luc, Friday, May 17, 2002, 6:26:19 PM, you wrote: LF Can anyone tell me what this means?? LF mysqld got signal 11; LF The manual section 'Debugging a MySQL server' tells you how to use a LF stack trace and/or the core file to produce a readable backtrace that may LF help in finding out why mysqld died LF Attemping backtrace. You can use the following information to find out LF where mysqld died. If you see no messages after this, something went LF terribly wrong LF Cannot determine thread, ebp=0xb, backtrace may not be correct LF Bogus stack limit or frame pointer, aborting backtrace LF Number of processes running now: 0 Signal 11 is a Segmentation fault, when the program cames out of it's address space. There might be many causes of error, mostly incorrect compilation or broken hardware. What did you tried to do which caused SIG11? LF Luc Foisy -- For technical support contracts, goto https://order.mysql.com/?ref=ensita 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: mysqld got signal 11;
Luc Foisy writes: Can someone give me some clue as to what this means to me? mysqld got signal 11; The manual section 'Debugging a MySQL server' tells you how to use a stack trace and/or the core file to produce a readable backtrace that may help in finding out why mysqld died Attemping 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, ebp=0xb, backtrace may not be correct Bogus stack limit or frame pointer, aborting backtrace Number of processes running now: 0 Luc Foisy Hi! The above means that MySQL server has crashed for some reason. Can you provide us with more info. Is it our binary , what OS and system software do you use, what does error log contains and all other info that you can compile. You may use mysqlbug program to provide much of the above info. As corrupted tables can still cause crashes, please check your tables with CHECK TABLES command, or if MySQL server is not running, with myisamchk -s and repair all tables that are not OK. (note: I have editied some hostnames, don't need to advertise) Did some looking around and was very surprised. The signal 11 above occured on a slave server ( over LAN ), here is a little more of the err output 020513 9:06:13 Error reading packet from server: Could not find first log (read_errno 0,server_errno=65535) 020513 9:07:13 Slave: Failed reading log event, reconnecting to retry, log 'QBSLXDB1-bin.040 ' position 110194576 020513 9:07:13 Slave: reconnected to master '[EMAIL PROTECTED]:3306',replication resumed in log 'QBSLXDB1-bin.040 ' at position 110194576 020513 9:07:13 Error reading packet from server: Could not find first log (read_errno 0,server_errno=65535) 020513 9:07:15 Slave thread exiting, replication stopped in log 'QBSLXDB1-bin.040 ' at position 110194576 020513 9:07:15 Slave: connected to master '[EMAIL PROTECTED]:3306', replication started in log 'QBSLXDB1-bin.040' at position 110194576 020514 5:55:00 Slave thread exiting, replication stopped in log 'QBSLXDB1-bin.041' at position 18927577 020514 5:55:00 Slave: connected to master '[EMAIL PROTECTED]:3306', replication started in log 'QBSLXDB1-bin.041' at position 18927577 020515 5:55:00 Slave thread exiting, replication stopped in log 'QBSLXDB1-bin.041' at position 51129469 020515 5:55:00 Slave: connected to master '[EMAIL PROTECTED]:3306', replication started in log 'QBSLXDB1-bin.041' at position 51129469 020516 5:55:00 Slave thread exiting, replication stopped in log 'QBSLXDB1-bin.041' at position 73667044 020516 5:55:00 Slave: connected to master '[EMAIL PROTECTED]:3306', replication started in log 'QBSLXDB1-bin.041' at position 73667044 mysqld got signal 11; The manual section 'Debugging a MySQL server' tells you how to use a stack trace and/or the core file to produce a readable backtrace that may help in finding out why mysqld died Attemping 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, ebp=0xb, backtrace may not be correct Bogus stack limit or frame pointer, aborting backtrace Number of processes running now: 0 020516 14:52:47 mysqld restarted /usr/sbin/mysqld: ready for connections -- So after seeing this, we decided to check our other slave server ( replicating the same master, over WAN ) It too got a signal 11, here is output from err log 020516 14:55:10 Error reading packet from server: Lost connection to MySQL server during query (read_errno 0,server_errno=2013) 020516 14:55:10 Slave: Failed reading log event, reconnecting to retry, log 'QBSLXDB1-bin.041' position 89957769 020516 14:55:11 Slave: reconnected to master 'repslave2@address:3306',replication resumed in log 'QBSLXDB1-bin.041' at position 89957769 020516 15:01:14 Error reading packet from server: Lost connection to MySQL server during query (read_errno 0,server_errno=2013) 020516 15:01:14 Slave: Failed reading log event, reconnecting to retry, log 'QBSLXDB1-bin.041' position 90472635 020516 15:01:14 Slave: reconnected to master 'repslave2@address:3306',replication resumed in log 'QBSLXDB1-bin.041' at position 90472635 020516 15:23:43 Error reading packet from server: Lost connection to MySQL server during query (read_errno 0,server_errno=2013) 020516 15:23:43 Slave: Failed reading log event, reconnecting to retry, log 'QBSLXDB1-bin.041' position 91888510 020516 15:23:43 Slave: reconnected to master 'repslave2@address:3306',replication resumed in log 'QBSLXDB1-bin.041' at position 91888510 020516 15:26:53 Error reading packet from server: Lost connection to MySQL server during query (read_errno 0,server_errno=2013) 020516 15:26:53 Slave: Failed reading log event, reconnecting to retry, log 'QBSLXDB1-bin.041' position 92103271 020516 15:26:53
RE: mysqld got signal 11;
Compiliation Error : Official MySQL RPM Broken Hardware : Two computers of different design at two completely different locations, at the same time?? What did I try to do which caused SIG11 : Nothing, servers were replicating See other message posted for other details about versions and server info -Original Message- From: Victoria Reznichenko [mailto:[EMAIL PROTECTED]] Sent: Friday, May 17, 2002 11:52 AM To: [EMAIL PROTECTED] Subject: Re: mysqld got signal 11; Luc, Friday, May 17, 2002, 6:26:19 PM, you wrote: LF Can anyone tell me what this means?? LF mysqld got signal 11; LF The manual section 'Debugging a MySQL server' tells you how to use a LF stack trace and/or the core file to produce a readable backtrace that may LF help in finding out why mysqld died LF Attemping backtrace. You can use the following information to find out LF where mysqld died. If you see no messages after this, something went LF terribly wrong LF Cannot determine thread, ebp=0xb, backtrace may not be correct LF Bogus stack limit or frame pointer, aborting backtrace LF Number of processes running now: 0 Signal 11 is a Segmentation fault, when the program cames out of it's address space. There might be many causes of error, mostly incorrect compilation or broken hardware. What did you tried to do which caused SIG11? LF Luc Foisy -- For technical support contracts, goto https://order.mysql.com/?ref=ensita 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 - 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: mysqld got signal 11;
- Original Message - From: Victoria Reznichenko [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Friday, May 17, 2002 6:52 PM Subject: Re: mysqld got signal 11; Luc, Friday, May 17, 2002, 6:26:19 PM, you wrote: LF Can anyone tell me what this means?? LF mysqld got signal 11; LF The manual section 'Debugging a MySQL server' tells you how to use a LF stack trace and/or the core file to produce a readable backtrace that may LF help in finding out why mysqld died LF Attemping backtrace. You can use the following information to find out LF where mysqld died. If you see no messages after this, something went LF terribly wrong LF Cannot determine thread, ebp=0xb, backtrace may not be correct LF Bogus stack limit or frame pointer, aborting backtrace LF Number of processes running now: 0 Signal 11 is a Segmentation fault, when the program cames out of it's address space. All signal which have action C generate Segmentation fault. There might be many causes of error, mostly incorrect compilation or broken hardware. What did you tried to do which caused SIG11? LF Luc Foisy -- For technical support contracts, goto https://order.mysql.com/?ref=ensita 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 - 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: mysqld got signal 11;
What version of MySQL you use ? I hope is not 3.23.4x. - Original Message - From: Luc Foisy [EMAIL PROTECTED] To: [EMAIL PROTECTED]; MYSQL-List (E-mail) [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Friday, May 17, 2002 7:25 PM Subject: RE: mysqld got signal 11; Luc Foisy writes: Can someone give me some clue as to what this means to me? mysqld got signal 11; The manual section 'Debugging a MySQL server' tells you how to use a stack trace and/or the core file to produce a readable backtrace that may help in finding out why mysqld died Attemping 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, ebp=0xb, backtrace may not be correct Bogus stack limit or frame pointer, aborting backtrace Number of processes running now: 0 Luc Foisy Hi! The above means that MySQL server has crashed for some reason. Can you provide us with more info. Is it our binary , what OS and system software do you use, what does error log contains and all other info that you can compile. You may use mysqlbug program to provide much of the above info. As corrupted tables can still cause crashes, please check your tables with CHECK TABLES command, or if MySQL server is not running, with myisamchk -s and repair all tables that are not OK. (note: I have editied some hostnames, don't need to advertise) Did some looking around and was very surprised. The signal 11 above occured on a slave server ( over LAN ), here is a little more of the err output 020513 9:06:13 Error reading packet from server: Could not find first log (read_errno 0,server_errno=65535) 020513 9:07:13 Slave: Failed reading log event, reconnecting to retry, log 'QBSLXDB1-bin.040 ' position 110194576 020513 9:07:13 Slave: reconnected to master '[EMAIL PROTECTED]:3306',replication resumed in log 'QBSLXDB1-bin.040 ' at position 110194576 020513 9:07:13 Error reading packet from server: Could not find first log (read_errno 0,server_errno=65535) 020513 9:07:15 Slave thread exiting, replication stopped in log 'QBSLXDB1-bin.040 ' at position 110194576 020513 9:07:15 Slave: connected to master '[EMAIL PROTECTED]:3306', replication started in log 'QBSLXDB1-bin.040' at position 110194576 020514 5:55:00 Slave thread exiting, replication stopped in log 'QBSLXDB1-bin.041' at position 18927577 020514 5:55:00 Slave: connected to master '[EMAIL PROTECTED]:3306', replication started in log 'QBSLXDB1-bin.041' at position 18927577 020515 5:55:00 Slave thread exiting, replication stopped in log 'QBSLXDB1-bin.041' at position 51129469 020515 5:55:00 Slave: connected to master '[EMAIL PROTECTED]:3306', replication started in log 'QBSLXDB1-bin.041' at position 51129469 020516 5:55:00 Slave thread exiting, replication stopped in log 'QBSLXDB1-bin.041' at position 73667044 020516 5:55:00 Slave: connected to master '[EMAIL PROTECTED]:3306', replication started in log 'QBSLXDB1-bin.041' at position 73667044 mysqld got signal 11; The manual section 'Debugging a MySQL server' tells you how to use a stack trace and/or the core file to produce a readable backtrace that may help in finding out why mysqld died Attemping 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, ebp=0xb, backtrace may not be correct Bogus stack limit or frame pointer, aborting backtrace Number of processes running now: 0 020516 14:52:47 mysqld restarted /usr/sbin/mysqld: ready for connections -- So after seeing this, we decided to check our other slave server ( replicating the same master, over WAN ) It too got a signal 11, here is output from err log 020516 14:55:10 Error reading packet from server: Lost connection to MySQL server during query (read_errno 0,server_errno=2013) 020516 14:55:10 Slave: Failed reading log event, reconnecting to retry, log 'QBSLXDB1-bin.041' position 89957769 020516 14:55:11 Slave: reconnected to master 'repslave2@address:3306',replication resumed in log 'QBSLXDB1-bin.041' at position 89957769 020516 15:01:14 Error reading packet from server: Lost connection to MySQL server during query (read_errno 0,server_errno=2013) 020516 15:01:14 Slave: Failed reading log event, reconnecting to retry, log 'QBSLXDB1-bin.041' position 90472635 020516 15:01:14 Slave: reconnected to master 'repslave2@address:3306',replication resumed in log 'QBSLXDB1-bin.041' at position 90472635 020516 15:23:43 Error reading packet from server: Lost connection to MySQL server during query (read_errno 0,server_errno=2013) 020516 15:23:43 Slave: Failed reading log event, reconnecting to retry, log 'QBSLXDB1-bin.041' position 91888510 020516 15:23:43 Slave
Re: mysqld got signal 11;
try to restart master and see what happen - Original Message - From: Luc Foisy [EMAIL PROTECTED] To: [EMAIL PROTECTED]; MYSQL-List (E-mail) [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Friday, May 17, 2002 7:25 PM Subject: RE: mysqld got signal 11; Luc Foisy writes: Can someone give me some clue as to what this means to me? mysqld got signal 11; The manual section 'Debugging a MySQL server' tells you how to use a stack trace and/or the core file to produce a readable backtrace that may help in finding out why mysqld died Attemping 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, ebp=0xb, backtrace may not be correct Bogus stack limit or frame pointer, aborting backtrace Number of processes running now: 0 Luc Foisy Hi! The above means that MySQL server has crashed for some reason. Can you provide us with more info. Is it our binary , what OS and system software do you use, what does error log contains and all other info that you can compile. You may use mysqlbug program to provide much of the above info. As corrupted tables can still cause crashes, please check your tables with CHECK TABLES command, or if MySQL server is not running, with myisamchk -s and repair all tables that are not OK. (note: I have editied some hostnames, don't need to advertise) Did some looking around and was very surprised. The signal 11 above occured on a slave server ( over LAN ), here is a little more of the err output 020513 9:06:13 Error reading packet from server: Could not find first log (read_errno 0,server_errno=65535) 020513 9:07:13 Slave: Failed reading log event, reconnecting to retry, log 'QBSLXDB1-bin.040 ' position 110194576 020513 9:07:13 Slave: reconnected to master '[EMAIL PROTECTED]:3306',replication resumed in log 'QBSLXDB1-bin.040 ' at position 110194576 020513 9:07:13 Error reading packet from server: Could not find first log (read_errno 0,server_errno=65535) 020513 9:07:15 Slave thread exiting, replication stopped in log 'QBSLXDB1-bin.040 ' at position 110194576 020513 9:07:15 Slave: connected to master '[EMAIL PROTECTED]:3306', replication started in log 'QBSLXDB1-bin.040' at position 110194576 020514 5:55:00 Slave thread exiting, replication stopped in log 'QBSLXDB1-bin.041' at position 18927577 020514 5:55:00 Slave: connected to master '[EMAIL PROTECTED]:3306', replication started in log 'QBSLXDB1-bin.041' at position 18927577 020515 5:55:00 Slave thread exiting, replication stopped in log 'QBSLXDB1-bin.041' at position 51129469 020515 5:55:00 Slave: connected to master '[EMAIL PROTECTED]:3306', replication started in log 'QBSLXDB1-bin.041' at position 51129469 020516 5:55:00 Slave thread exiting, replication stopped in log 'QBSLXDB1-bin.041' at position 73667044 020516 5:55:00 Slave: connected to master '[EMAIL PROTECTED]:3306', replication started in log 'QBSLXDB1-bin.041' at position 73667044 mysqld got signal 11; The manual section 'Debugging a MySQL server' tells you how to use a stack trace and/or the core file to produce a readable backtrace that may help in finding out why mysqld died Attemping 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, ebp=0xb, backtrace may not be correct Bogus stack limit or frame pointer, aborting backtrace Number of processes running now: 0 020516 14:52:47 mysqld restarted /usr/sbin/mysqld: ready for connections -- So after seeing this, we decided to check our other slave server ( replicating the same master, over WAN ) It too got a signal 11, here is output from err log 020516 14:55:10 Error reading packet from server: Lost connection to MySQL server during query (read_errno 0,server_errno=2013) 020516 14:55:10 Slave: Failed reading log event, reconnecting to retry, log 'QBSLXDB1-bin.041' position 89957769 020516 14:55:11 Slave: reconnected to master 'repslave2@address:3306',replication resumed in log 'QBSLXDB1-bin.041' at position 89957769 020516 15:01:14 Error reading packet from server: Lost connection to MySQL server during query (read_errno 0,server_errno=2013) 020516 15:01:14 Slave: Failed reading log event, reconnecting to retry, log 'QBSLXDB1-bin.041' position 90472635 020516 15:01:14 Slave: reconnected to master 'repslave2@address:3306',replication resumed in log 'QBSLXDB1-bin.041' at position 90472635 020516 15:23:43 Error reading packet from server: Lost connection to MySQL server during query (read_errno 0,server_errno=2013) 020516 15:23:43 Slave: Failed reading log event, reconnecting to retry, log 'QBSLXDB1-bin.041' position 91888510 020516 15:23:43 Slave: reconnected to master
Re: mysqld got signal 11;
On vendredi, mai 17, 2002, at 05:26 , Luc Foisy wrote: Can anyone tell me what this means?? mysqld got signal 11; [...] (Could be) Bad RAM ? R. - 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: mysqld got signal 11;
A post from the MySQL list MEMORY PROBLEM ... a pointers is gone a way ... The signal is SIGSEV and this mean in fact: Invalid memory reference. If this is a memory problem, how did it hit two servers ( several kilometers apart ) at the same time? There could be several reasons for this, and one of them is a bug in MySQL. You are using version 3.23.32 which has plenty of known bugs that can coredump MySQL server. The first thing to do in this situation is upgrade the coredumping MySQL. -- MySQL Development Team For technical support contracts, visit https://order.mysql.com/?ref=mspa __ ___ ___ __ / |/ /_ __/ __/ __ \/ / Sasha Pachev [EMAIL PROTECTED] / /|_/ / // /\ \/ /_/ / /__ MySQL AB, http://www.mysql.com/ /_/ /_/\_, /___/\___\_\___/ Provo, Utah, USA ___/ - 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: mysqld got signal 11;
Steve writes:
Hi,
I am running mysql 3.23.33 getting this error about once a day causeing
mysql to restart
Thanks and Regards,
Steve Reed
Network Administrator
Oznetwork Pty. Ltd.
8233 1900
142 Phillip St
Sydney NSW 2000
Hi!
Please can you check whether your hyperseek_links table is corrupted
or not ??
If it is not corrupted and the above query crashes again MySQL, please
compress your table and upload it to
ftp://support.mysql.com:/pub/mysql/secret.
Just let us know a file name.
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
Re: mysqld got signal 11;
On Monday 21 May 2001 23:29, Steve wrote: Hi, I am running mysql 3.23.33 getting this error about once a day causeing mysql to restart mysqld got signal 11; The manual section 'Debugging a MySQL server' tells you how to use a stack trace and/or the core file to produce a readable backtrace that may help in finding out why mysqld died Attemping backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong stack range sanity check, ok, backtrace follows 0x400737c6 0x80ff2af 0x80ff1e1 0x8101227 0x80e4873 0x80e45b8 0x80dd605 0x80c3265 0x80c72bf 0x80c2675 0x80c1cde stack trace successful, now will try to get some variables. Some pointers may be invalid and cause dump abort thd-query at 0x81f9bf0 = SELECT * FROM hyperseek_links WHERE ID in(988779528,988588937,988779473,988599648,988630588,988634546,988 600011,988613411,988613424,988605698,988614258,988614259,988613615,988619035 ,988616328,988596036,988599643,988613419,988635422,98862 2151,988627434,988613538,988627431,988622188,988613415,988621976,988592381,9 88636427,988613413,988631044,988623929,988614599,9886231 05,988635148,988595545,988597946,988610251,988616059,988627430,988608473,988 598139,988627429,988611026,988598120,988625124,988634377 ,988627427,988604205,988629277,988631289,988612742,988592490,988635848,98862 8639,988593015,988611041,988589630,988593784,988593696,9 88590456,988590457,988610004,988609853,988609428,988628676,988625092,9885967 10,988614174,988611930,988628208,988628684,988589448,988 634777,988631086,988627424,988589395,988629406,988593093,988627423,988605901 ,988619264,988589911,988624763,988610330,988588752,98863 3204,988605807,988627421,988613695,988626494,988613013,988606490,988600691,9 88627420,988628061,988614780,988592519,988594515,9 thd-thread_id = 7951 successfully dumped variables, if you ran with --log take a look at the details of what thread 7951 did to cause the crash. In some cases of really bad corruption, this value can be invalid Please use the information above to create a repeatable test case for the crash, and send it to [EMAIL PROTECTED] Number of processes running now: 2 010521 19:14:19 mysqld restarted /usr/local/mysql/libexec/mysqld: ready for connections 010521 19:59:34 Aborted connection 1646 to db: 'search' user: 'search' host: `203.111.10.101' (Got an error reading communication p ackets) then ran (note this was on a previous error, I included the above error as it was the most informative in the log file): root@netmsc1:/tmp# resolve_stack_dump -s /tmp/mysqld.sym -n mysql.stack Cannot determine thread, ebp=0xb14c, backtrace may not be correct stack range sanity check, ok, backtrace follows 0x400737c6 _end + 938024678 0x40072d66 _end + 938022022 0x80be19a create_new_thread__FP3THD + 606 0x80be61b handle_connections_sockets__FPv + 1015 0x80bdd90 main + 2412 0x400f5577 _end + 938556567 0x808891d _start + 33 New value of ebp failed sanity check terminating backtrace First, you seem to be resolving a different stack trace than the one you have posted. Can you resolve the original one too? Can you try our 3.23.38 binary and see if it solves the problem? Your own source build is not going to be very stable as the number of connections increases unless you take some measures to fix up LinuxThreads - see http://www.mysql.com/doc/L/i/Linux.html . -- MySQL Development Team __ ___ ___ __ / |/ /_ __/ __/ __ \/ / Sasha Pachev [EMAIL PROTECTED] / /|_/ / // /\ \/ /_/ / /__ MySQL AB, http://www.mysql.com/ /_/ /_/\_, /___/\___\_\___/ Provo, Utah, USA ___/ - 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: mysqld got signal 11
Hi, OK, I now still have the same problem after upgrading to 3.23.33-pc-linux-gnu-i686 binary. After myisamchking all tables, this time it took just about one minute before crashing: mysqld got signal 11; The manual section 'Debugging a MySQL server' tells you how to use a stack trace and/or the core file to produce a readable backtrace that may help in finding out why mysqld died Attemping backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong Bogus stack limit or frame pointer, aborting backtrace Number of processes running now: 0 010306 15:13:38 mysqld restarted I'm off to compiling a debug version. :( Will send a real bug report if it dies again. Sincerely, Steven Roussey Network54.com http://network54.com/?pp=e Sincerely, Steven Roussey Network54.com http://network54.com/?pp=e - 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: mysqld got signal 11
Hi, Ah, today's problems are from a bug that dates back a year or more. Streaming a large number of insert delayeds into a table that does not exist causes the crash. The table was not created correctly last night. Is there a web version of mysql code like PHP has http://lxr.php.net ? I'd like to browse through and see what I can find, but using vi is just not worth my time. Sincerely, Steven Roussey Network54.com http://network54.com/?pp=e - 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: mysqld got signal 11
You may have a corrupt library or mysqld. Signal 11 is a memory error (likely overwrite). I would try deleting and reinstalling mysqld from a fresh download. Pat... [EMAIL PROTECTED] - Original Message - From: "Steven Roussey" [EMAIL PROTECTED] To: "Mysql" [EMAIL PROTECTED] Sent: Tuesday, March 06, 2001 6:29 PM Subject: Re: mysqld got signal 11 Hi, OK, I now still have the same problem after upgrading to 3.23.33-pc-linux-gnu-i686 binary. After myisamchking all tables, this time it took just about one minute before crashing: mysqld got signal 11; The manual section 'Debugging a MySQL server' tells you how to use a stack trace and/or the core file to produce a readable backtrace that may help in finding out why mysqld died Attemping backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong Bogus stack limit or frame pointer, aborting backtrace Number of processes running now: 0 010306 15:13:38 mysqld restarted I'm off to compiling a debug version. :( Will send a real bug report if it dies again. Sincerely, Steven Roussey Network54.com http://network54.com/?pp=e Sincerely, Steven Roussey Network54.com http://network54.com/?pp=e - 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: mysqld got signal 11
Steven Roussey writes:
Hi,
Ah, today's problems are from a bug that dates back a year or more.
Streaming a large number of insert delayeds into a table that does not exist
causes the crash. The table was not created correctly last night.
Is there a web version of mysql code like PHP has http://lxr.php.net ? I'd
like to browse through and see what I can find, but using vi is just not
worth my time.
Sincerely,
Steven Roussey
Network54.com
http://network54.com/?pp=e
Hi!
I have tried the above with 3.23.33 and was not able to reproduce it.
You can browse through our sources with any editor. Just download
source code tarball.
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
RE: mysqld got signal 11
I have tried the above with 3.23.33 and was not able to reproduce it. I could be wrong (imagine that!). It crashed again today even with the table in place. In order to take one item out of the equation, I stopped the replace delayed process I had running. It still crashed (about 8 hours later). Since it takes this long, I can't do a trace file -- it would be larger than our hard drives. I'm enabling the log on this server today -- hopefully that will help, and will be smaller... Right now the only thing I can think of that is different (since the server never used to crash before): 1) Fulltext searches (selects) are happening on this server. 2) I switched the apache servers to _not_ use persistent connections (in most cases -- I just realized we are currently using a 50/50 mix). So my plan right now is to do this: 1) Turn on the log and see what is there when it crashes. 2) start again but don't have fulltext searches 3) start again but use persistent connection and do have FT searches 4) start again but use persistent connections no FT searches 5) cry if it is still crashing ;| Pertinient information(?): 010307 2:03:36 Aborted connection 580760 to db: 'logging' user: 'apache' host: `tank' (Got timeout reading communication packets) mysqld got signal 11; The manual section 'Debugging a MySQL server' tells you how to use a stack trace and/or the core file to produce a readable backtrace that may help in finding out why mysqld died Attemping backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong stack range sanity check, ok, backtrace follows 0x40097532 0x400fc24e 0x400fbf9a 0x8180797 0x80b2c23 0x80b92e4 0x80bf706 stack trace successful, now will try to get some variables. Some pointers may be invalid and cause dump abort thd-query at (nil) = 010307 2:25:10 Aborted connection 623630 to db: 'logging' user: 'apache' host: `neo' (Got timeout reading communication packets) 010307 2:25:29 Aborted connection 624240 to db: 'logging' user: 'apache' host: `neo' (Got timeout reading communication packets) Sincerely, Steven Roussey Network54.com http://network54.com/?pp=e - 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: mysqld got signal 11
An update: o I found other queries that were insert delayed into non-existent tables and others that had wrong column names. Removing these, I thought would fix things. Nope. o I tried writing a log and a trace file. Too slow and unworkable. I tried just log (worked OK -- I got a crash but nothing looks abnormal in the log) and I tried just trace (still too slow). Trace with just info and error runs but didn't give me enough info to help. Lots of 'vio_read returned -1, errno: 11'. o Right now we are going to see how long we can run with no fulltext insert/replace/update/select. No FT at all. o The stack traces have been different but always have 'thd-query at (nil) = ' in the error log. Looks like a null pointer to me. The last stack trace: 010307 15:13:36 mysqld started /usr/local/mysql/libexec/mysqld: ready for connections mysqld got signal 11; The manual section 'Debugging a MySQL server' tells you how to use a stack trace and/or the core file to produce a readable backtrace that may help in finding out why mysqld died Attemping backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong stack range sanity check, ok, backtrace follows 0x40097532 0x80b3360 0x80b3595 0x80bf1a4 0x80bf4d9 stack trace successful, now will try to get some variables. Some pointers may be invalid and cause dump abort thd-query at (nil) = # resolve_stack_dump -s /tmp/mysqld.sym -n mysqld.stack 0x40097532 __evoke_link_warning_llseek + 937652786 0x80b3360 mysql_update__FP3THDP13st_table_listRt4List1Z4ItemT2P4ItemUl15enum_duplicate s13thr_lock_type + 2480 0x80b3595 mysql_update__FP3THDP13st_table_listRt4List1Z4ItemT2P4ItemUl15enum_duplicate s13thr_lock_type + 3045 0x80bf1a4 pack_fields__FiRt4List1Z12create_field + 320 0x80bf4d9 make_empty_rec__Fi7db_typeUiRt4List1Z12create_fieldUiUi + 309 Sincerely, Steven Roussey Network54.com http://network54.com/?pp=e - 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: mysqld got signal 11
mysqld got signal 11; The manual section 'Debugging a MySQL server' tells you how to use a stack trace and/or the core file to produce a readable backtrace that may help in finding out why mysqld died Attemping backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong stack range sanity check, ok, backtrace follows 0x813f4aa 0x8157e85 0x814f0ee 0x81565c5 0x807c0ac 0x8084f28 stack trace successful, now will try to get some variables. Some pointers may be invalid and cause dump abort thd-query at (nil) = 010306 Two odd things this time. One, the frame pointer is there, so it not being there on other messages really worries me. Two, in the case above is the thd-query equal to nil? BTW: the binary distribution does not contain resolve_stack_dump, which it should. :) If the binary does not omit the frame pointer, then it should be there. Or the binary could omit the frame pointer and it would make sense to not have resolve_stack_dump included. One way or the other. Using resolve_stack_dump: 0x813f4aa pthread_sighandler + 154 0x8157e85 _IO_default_xsputn + 113 0x814f0ee vfprintf + 414 0x81565c5 vsprintf + 69 0x807c0ac net_printf__FP6st_netUie + 108 0x8084f28 handle_one_connection__FPv + 360 Hmm... Greek to me. OK, so I'm starting over. Compliled my own version of mysql-3.23.33 --with-debug as per manual. I'll be back when I have more info Sincerely, Steven Roussey Network54.com http://network54.com/?pp=e - 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: mysqld got signal 11
One more thing: In the processlist: | Delayed_insert | 578 | reschedule | log_day_20010307 After another minute (now over 10 minutes to reschedule) I get a _lot_ of these: | Query | 9| waiting for handler insert | insert delayed into logging.log_day_20010307 ... Which fills up all processes and locks up the server and in the error log there is: 010307 18:08:33 Delayed insert thread couldn't get requested lock for table log_day_20010307 Also, I have a BIG trace file for this, but I forgot to let it continue until a crash. Oops. FYI -steve- - 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: mysqld got signal 11 every 10 minutes
"Matis, Jan" wrote : Hallo, I have small problem with my sql (again :) version:3.23.32 linux: SuSE 6.2 kernel: 2.2.16, 2.2.18, 2.4.1 lib: libc-2.1.2-31 (suse) compiled: gcc-2.95.2, egcs 2.7.2.3 compilation parameters: --prefix=/opt/mysql ( --without-debug --enable-assembler) memory: 1GB processor: 2* PIII 550Mhz ps uax | grep mysqld | wc -l : between 100 and 600 (really :) this machine is db backend for one wide used portal ( 3 web machines with apache and php 4.0.4pl1 with patched persistent connections) I tryed all combinations of this but in my db.err is really often mysqld got signal 11. Does anybody have an idea what can I do ? is it possible that this is caused by bad written php scripts ? (because I'm not developer but I know how our developers work :) if yes where in php scripts should I search a bug ? Jan Matis Hi Jan, If you check this mailing list archive, you will see that there are other reports of "signal 11" problems either on FreeBSD or Linux. I posted such a message myself on Jan 18th and I am still getting this kind of problem since then. It may run several days without problem or crash 3 times within 2 hours. I did not post anything again since I could not set up a reproducible test case. I really think the problem is with MySQL not your PHP frontend. I use MySQL with 2 web front-ends coded in Perl (mod_perl) and this problem appeared when I switched the backend from miniSQL to MySQL (going back to miniSQL is not an option since it has its own limitations). My configuration is close to yours (Linux RedHat 6.2, 2.2.14 kernel; PIII-733, 2Gb RAM) and MySQL load similar (between 300 and 500 persistent connections, about 300 queries/s). Hope this helps -- Joseph Bueno NetClub/Trader.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: mysqld got signal 11 every 10 minutes
On Thu, Feb 01, 2001 at 09:14:36AM +0100, Matis, Jan wrote: Hallo, I have small problem with my sql (again :) version:3.23.32 linux: SuSE 6.2 kernel: 2.2.16, 2.2.18, 2.4.1 lib: libc-2.1.2-31 (suse) compiled: gcc-2.95.2, egcs 2.7.2.3 compilation parameters: --prefix=/opt/mysql ( --without-debug --enable-assembler) memory: 1GB processor: 2* PIII 550Mhz ps uax | grep mysqld | wc -l : between 100 and 600 (really :) this machine is db backend for one wide used portal ( 3 web machines with apache and php 4.0.4pl1 with patched persistent connections) I tryed all combinations of this but in my db.err is really often mysqld got signal 11. Does anybody have an idea what can I do ? is it possible that this is caused by bad written php scripts ? (because I'm not developer but I know how our developers work :) if yes where in php scripts should I search a bug ? Have you tried using the binary tarball from the MySQL web site? http://www.mysql.com/Downloads/MySQL-3.23/mysql-3.23.32-pc-linux-gnu-i686.tar.gz 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: mysqld got signal 11 every 10 minutes
Have you tried using the binary tarball from the MySQL web site? http://www.mysql.com/Downloads/MySQL-3.23/mysql-3.23.32-pc-linux-gnu-i686.ta r.gz Jeremy no I didn't ...so I changed it now and we will see on afternoon :) Jan - 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: mysqld got signal 11 every 10 minutes
Now I can say I tryed http://www.mysql.com/Downloads/MySQL-3.23/mysql-3.23.32-pc-linux-gnu-i686.ta r.gz too and it dind't helped mysqld got signal 11; The manual section 'Debugging a MySQL server' tells you how to use a stack trace and/or the core file to produce a readable backtrace that may help in finding out why mysqld died Attemping backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong Bogus stack limit or frame pointer, aborting backtrace Number of processes running now: 0 Jan - 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
