Re: MYSQL dies after FreeBSD 4.6.2-cvsup-4.7
Well, just a suggestion, but if you did not install world (where the threads are) then you have a mismatch between kernel and world. OT (but what the heck!) proper procedure for freebsd cvsup to desired version cd /usr/src mergemaster -p make buildworld make buildkernel KERNCONF=yourkernel make installkernel KERNCON=yourkernel reboot make installworld mergemaster (your favorite otpions eg: -i ) reboot once more. Have several server running 3.23 and 4.0 with no problems. Ken - Original Message - From: Tuc [EMAIL PROTECTED] To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Wednesday, January 29, 2003 11:25 AM Subject: MYSQL dies after FreeBSD 4.6.2-cvsup-4.7 Hi, We just cvsup'd a FreeBSD machine from 4.6.2 to 4.7, made world, and installed a new kernel. Now mysql is complaining : Fatal error 'Can't create gc thread' at line ? in file /usr/src/lib/libc_r/uthre ad/uthread_create.c (errno = ?) 030129 10:36:35 mysqld restarted Fatal error 'Can't create gc thread' at line ? in file /usr/src/lib/libc_r/uthre ad/uthread_create.c (errno = ?) 030129 10:36:35 mysqld restarted Fatal error 'Can't create gc thread' at line ? in file /usr/src/lib/libc_r/uthre ad/uthread_create.c (errno = ?) Any ideas where to start? Tried to recompile mysql to see if it just needed that, and it didn't change anything. (This is 3.23.54a) Thanks, Tuc/TTSG Internet Services, Inc. - 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 dies at startup after upgrade form 3.23 to 4.0.3
jschleigh, Tuesday, October 01, 2002, 4:06:15 PM, you wrote: jahdc I had a working install of mysql 3.23 in /usr/bin and /var/lib/mysql. I installed 4.0.3 to /usr/local/mysql and can't get it to run. I followed the installation instructions to the jahdc T. When I run '/usr/local/mysql/bin/mysqld_safe' I get: jahdc Starting mysqld daemon with databases from /usr/local/mysql/data jahdc 021001 08:53:00 mysqld ended jahdc The old mysql still works fine (/usr/bin/safe_mysqld). How-To-Repeat: jahdc I only have to try to run /usr/local/mysql/bin/mysqld_safe to get the same results. Look at the error log file to see the causes of failed start. -- 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: Mysql dies with Signal 11
On Saturday 23 February 2002 05:34 pm, you wrote: (gdb) thread 1 [Switching to thread 1 (process 31905, thread 1)] #0 ?0x82011ce in memcpy () (gdb) bt #0 ?0x82011ce in memcpy () #1 ?0x82a33c0 in mysql_bin_log () #2 ?0x80b7cd8 in ha_commit_trans () #3 ?0x8076e24 in mysql_execute_command () #4 ?0x80788c8 in mysql_parse () #5 ?0x8073454 in dispatch_command () #6 ?0x80784c5 in do_command () #7 ?0x80728f4 in handle_one_connection () #8 ?0x81d446d in _thread_start () #9 ?0x0 in ?? () Richard: Thanks for taking the time to debug this. This looks like there could be a bug in the binary logging on commit. It might be resolved in the current source or even in 4.0.1, but I will doublecheck that code to make sure. It would really help if you could come up with a repeatable test case and send it to [EMAIL PROTECTED] -- MySQL Development Team For technical support contracts, visit https://order.mysql.com/ __ ___ ___ __ / |/ /_ __/ __/ __ \/ / 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: Mysql dies with Signal 11
Richard, (gdb) thread 1 [Switching to thread 1 (process 31905, thread 1)] #0 0x82011ce in memcpy () (gdb) bt #0 0x82011ce in memcpy () #1 0x82a33c0 in mysql_bin_log () #2 0x80b7cd8 in ha_commit_trans () #3 0x8076e24 in mysql_execute_command () #4 0x80788c8 in mysql_parse () #5 0x8073454 in dispatch_command () #6 0x80784c5 in do_command () #7 0x80728f4 in handle_one_connection () #8 0x81d446d in _thread_start () #9 0x0 in ?? () looks like mysqld crashed when it was writing to the MySQL binlog. If you can repeat the crash easily, please do CFLAGS=-g CXXFLAGS=-g ./configure --with-innodb gmake so that you get a mysqld binary with the debug info compiled in. Then run mysqld inside gdb, and do gdbbt full when it crashes. Also do 'bt full' for other 'interesting' threads than the one which crashed. What is your my.cnf like? What table types you use? Lots of bugs have been fixed since 4.0.0, but I did not notice anything connected to the binlog. When Monty gets back from the Galapagos Islands on March 4, he will start building 4.0.2. Why do you run 4.0? 3.23.49 might be a safer bet. What FreeBSD version you run? What threads you use? There are problems with some thread implementations in FreeBSD. 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 -Original Message- From: Richard Clarke [EMAIL PROTECTED] Newsgroups: mailing.database.mysql Date: Sunday, February 24, 2002 2:42 AM Subject: Mysql dies with Signal 11 Hi, I seem to be getting intermittant crashes of mysql. The error log prints the following, 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=268431360 record_buffer=1044480 sort_buffer=1048568 max_used_connections=5 max_connections=100 threads_connected=5 It is possible that mysqld could use up to key_buffer_size + (record_buffer + sort_buffer)*max_connections = 466539 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. 020223 13:00:01 mysqld restarted InnoDB: Database was not shut down normally. InnoDB: Starting recovery from log files... InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 82 1555315003 etc... Can some please suggest what steps I can take to discovering what is wrong. I have attached server info and gdb output to bottom of email. This is a very active server processing 150 apache hits a second. A seperate looped process takes cgi data inserted into an IPC MSGQ and sticks it in the db and another seperate looped process takes data from this db and dumps to a db on a remote machine. Richard p.s. Your MySQL connection id is 7 to server version: 4.0.0-alpha-log I'm running a dual 1ghz FreeBSD box with 1gig of ram. (gdb) run -u mysql Starting program: /usr/local/mysql/libexec/mysqld -u mysql 020223 14:09:16 InnoDB: Started /usr/local/mysql/libexec/mysqld: ready for connections (after about 8hrs.) Program received signal SIGSEGV, Segmentation fault. 0x82011ce in memcpy () (gdb) info threads 14 process 31905, thread 14 0x81df52d in _thread_kern_sched () 13 process 31905, thread 13 0x81df52d in _thread_kern_sched () 12 process 31905, thread 12 0x81df52d in _thread_kern_sched () 11 process 31905, thread 11 0x81df52d in _thread_kern_sched () 10 process 31905, thread 10 0x81df52d in _thread_kern_sched () 9 process 31905, thread 9 0x81df52d in _thread_kern_sched () 8 process 31905, thread 8 0x81df52d in _thread_kern_sched () 7 process 31905, thread 7 0x81df52d in _thread_kern_sched () 6 process 31905, thread 6 0x81df52d in _thread_kern_sched () 5 process 31905, thread 5 0x81df52d in _thread_kern_sched () 4 process 31905, thread 4 0x81df52d in _thread_kern_sched () 3 process 31905, thread 3 0x82013dc in _thread_sys_close () 2 process 31905, thread 2 0x81df52d in _thread_kern_sched () * 1 process 31905, thread 1 0x82011ce in memcpy () (gdb) thread 1 [Switching to thread 1 (process 31905, thread 1)] #0 0x82011ce in memcpy () (gdb) bt #0 0x82011ce in memcpy () #1 0x82a33c0 in mysql_bin_log () #2 0x80b7cd8 in ha_commit_trans () #3 0x8076e24 in mysql_execute_command () #4 0x80788c8 in mysql_parse () #5 0x8073454 in dispatch_command () #6 0x80784c5 in do_command () #7 0x80728f4 in handle_one_connection () #8 0x81d446d in _thread_start () #9 0x0 in ?? () (gdb) thread 2 [Switching to thread 2 (process 31905, thread 2)] #0 0x81df52d in _thread_kern_sched () (gdb) bt #0 0x81df52d in _thread_kern_sched () #1 0x81dfdb7 in
Re: Mysql dies with Signal 11
Ok well the only reason I was using 4.0.0 is because I hadn't finished developing the application and figured I'd just leave what I installed at start before upgrading. I will install 4.0.1-max now and try that out and if I have further problems I will let you know. All my tables are innodb and for future reference, here is my my.cnf # The MySQL server [mysqld] port= 3306 socket = /tmp/mysql.sock skip-locking set-variable= key_buffer=256M set-variable= max_allowed_packet=1M set-variable= table_cache=256 set-variable= sort_buffer=1M set-variable= record_buffer=1M set-variable= myisam_sort_buffer_size=64M set-variable= thread_cache=8 set-variable= max_binlog_size=2097152 # Try number of CPU's*2 for thread_concurrency set-variable= thread_concurrency=8 log-bin server-id = 1 # Uncomment the following if you are using BDB tables #set-variable = bdb_cache_size=64M #set-variable = bdb_max_lock=10 # Uncomment the following if you are using Innobase tables innodb_data_file_path = ibdata/ibdata1:4000M innodb_data_home_dir = /usr/local/mysql/var/ innodb_log_group_home_dir = /usr/local/mysql/var/ innodb_log_arch_dir = /usr/local/mysql/var/ set-variable = innodb_mirrored_log_groups=1 set-variable = innodb_log_files_in_group=3 set-variable = innodb_log_file_size=5M set-variable = innodb_log_buffer_size=8M innodb_flush_log_at_trx_commit=1 innodb_log_archive=0 set-variable = innodb_buffer_pool_size=100M set-variable = innodb_additional_mem_pool_size=20M set-variable = innodb_file_io_threads=4 set-variable = innodb_lock_wait_timeout=50 Richard - Original Message - From: Heikki Tuuri [EMAIL PROTECTED] To: Richard Clarke [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Sunday, February 24, 2002 5:32 PM Subject: Re: Mysql dies with Signal 11 Richard, (gdb) thread 1 [Switching to thread 1 (process 31905, thread 1)] #0 0x82011ce in memcpy () (gdb) bt #0 0x82011ce in memcpy () #1 0x82a33c0 in mysql_bin_log () #2 0x80b7cd8 in ha_commit_trans () #3 0x8076e24 in mysql_execute_command () #4 0x80788c8 in mysql_parse () #5 0x8073454 in dispatch_command () #6 0x80784c5 in do_command () #7 0x80728f4 in handle_one_connection () #8 0x81d446d in _thread_start () #9 0x0 in ?? () looks like mysqld crashed when it was writing to the MySQL binlog. If you can repeat the crash easily, please do CFLAGS=-g CXXFLAGS=-g ./configure --with-innodb gmake so that you get a mysqld binary with the debug info compiled in. Then run mysqld inside gdb, and do gdbbt full when it crashes. Also do 'bt full' for other 'interesting' threads than the one which crashed. What is your my.cnf like? What table types you use? Lots of bugs have been fixed since 4.0.0, but I did not notice anything connected to the binlog. When Monty gets back from the Galapagos Islands on March 4, he will start building 4.0.2. Why do you run 4.0? 3.23.49 might be a safer bet. What FreeBSD version you run? What threads you use? There are problems with some thread implementations in FreeBSD. 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 -Original Message- From: Richard Clarke [EMAIL PROTECTED] Newsgroups: mailing.database.mysql Date: Sunday, February 24, 2002 2:42 AM Subject: Mysql dies with Signal 11 Hi, I seem to be getting intermittant crashes of mysql. The error log prints the following, 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=268431360 record_buffer=1044480 sort_buffer=1048568 max_used_connections=5 max_connections=100 threads_connected=5 It is possible that mysqld could use up to key_buffer_size + (record_buffer + sort_buffer)*max_connections = 466539 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. 020223 13:00:01 mysqld restarted InnoDB: Database was not shut down normally. InnoDB: Starting recovery from log files... InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 82 1555315003 etc... Can some please suggest what steps I can take to discovering what is wrong. I have attached server info and gdb output to bottom of email. This is a very active server processing 150 apache hits a second. A seperate looped process takes cgi data inserted into an IPC MSGQ and sticks it in the db and another seperate looped process takes data from this db and dumps to a db on a remote machine. Richard
RE: MySQL dies
You might want to increase your max_connections using : -O max_connections=1000 as an option in mysqld_safe. See http://www.mysql.com/doc/S/e/Server_parameters.html for more information. -Original Message- From: Müller, Markus [mailto:[EMAIL PROTECTED]] Sent: Friday, January 11, 2002 8:00 AM To: '[EMAIL PROTECTED]' Subject: MySQL dies Hi, I'm in desperate need of help. MySQL keeps dying and I just can't figure out why... Here goes: Clients connect from Windows machines via VB and Delphi apps through myodbc doing queries on databases with *big* tables containing over 1.6 million records Often they're losing connection because mysql dies, queries have to be done again. Error log says that mysqld restarted, i.e. safe_mysqld immediately restarts the server. Only mysql is running on the machine. Queries may look like this: CREATE TEMPORARY TABLE tmpTable(FRM varchar(5),ARKL varchar(5),KNR varchar(10),ZWT float(11,5),VPN float(11,5),GRS varchar(32),MNG float(11,5),BRW float(11,5), NTW float(11,5)); INSERT INTO tmpTable(FRM,ARKL,KNR,ZWT,VPN,GRS,MNG,BRW, NTW)SELECT left(MNR,5),right(MNR,5),KNR,ZWT/MNG,VPN,substring_index(GRS,'X',1)* right(substring_index(GRS,'X',2),length(substring_index(GRS,'X',2))-length(s ubstring_index(GRS,'X',1))-1)* right(GRS,length(GRS)-length(substring_index(GRS,'X',2))-1)/1000,MNG,BRW,NTW FROM MASTER WHERE (BLDAT = 20010901 AND BLT = 20011231 AND SRT = '04' AND SRT = '06') MASTER is one *big* table containing 1.6 Million records... Info on the system: netbsd 1.5.2, 512 mb RAM mysql --version mysql Ver 11.13 Distrib 3.23.35, for -netbsd (i386) mysqladmin variables: +-+- --+ | Variable_name | Value | +-+- --+ | ansi_mode | OFF | | back_log| 50 | | basedir | /usr/pkg/ | | binlog_cache_size | 32768 | | character_set | latin1 | | character_sets | latin1 dec8 dos german1 hp8 koi8_ru latin2 swe7 usa7 cp1251 danish hebrew win1251 estonia hungarian koi8_ukr win1251ukr greek win1250 croat cp1257 latin5 | | concurrent_insert | ON | | connect_timeout | 10 | | datadir | /usr/var/mysql/ | | delay_key_write | ON | | delayed_insert_limit| 100 | | delayed_insert_timeout | 300 | | delayed_queue_size | 1000 | | flush | OFF | | flush_time | 0 | | have_bdb| NO | | have_gemini | NO | | have_innobase | NO | | have_isam | YES | | have_raid | NO | | have_ssl| NO | | init_file | | | interactive_timeout | 28800 | | join_buffer_size| 131072 | | key_buffer_size | 16773120 | | language| /usr/pkg/share/mysql/english/ | | large_files_support | ON | | locked_in_memory| OFF | | log | ON | | log_update | OFF | | log_bin | OFF | | log_slave_updates | OFF | | long_query_time | 10 | | low_priority_updates| OFF | | lower_case_table_names | 0 | | max_allowed_packet | 1047552 | | max_binlog_cache_size | 4294967295 | | max_binlog_size | 1073741824 | | max_connections | 100 | | max_connect_errors | 10 | | max_delayed_threads | 20 | | max_heap_table_size | 16777216 | | max_join_size | 4294967295 | | max_sort_length | 1024 | | max_user_connections| 0 | | max_tmp_tables | 32 | | max_write_lock_count| 4294967295 | | myisam_recover_options | OFF | | myisam_sort_buffer_size | 8388608 | | net_buffer_length | 7168 | | net_read_timeout| 120 | | net_retry_count | 40 | | net_write_timeout | 240 | | open_files_limit| 0 | | pid_file| /usr/var/mysql/unixtest.pid | | port| 3306 | | protocol_version| 10 | | record_buffer | 131072 | | query_buffer_size | 1044480 | | safe_show_database | OFF | | server_id | 1 | | skip_locking| ON | | skip_networking | OFF | | skip_show_database | OFF | | slow_launch_time| 2 | | socket | /tmp/mysql.sock | | sort_buffer | 524280 | | table_cache | 64 | | table_type | MYISAM | | thread_cache_size | 0 | | thread_stack| 65536 | | timezone| CET | | tmp_table_size | 1048576 | | tmpdir | /var/tmp/ | | version | 3.23.35-log | | wait_timeout| 115200 |
