Hi!

InnoDB seems to have created the database and started ok. This does not look
like an InnoDB bug.

I think gethostbyaddr asks from a connection the hostname, and subsequent
code checks that the host has access rights to mysqld.

For some reason gethostbyaddr_r crashes.

Hmm.. if you could run inside gdb and look what parameters mysqld passes to
gethostbyaddr in mysql/sql/hostname.cc, then it would be easier to determine
what goes wrong.

Regards,

Heikki
Innobase Oy

Jeremy Zawodny wrote in message ...
>I just attempted to upgrade a 3.23.41-max server on Linux 2.4.12 to
>3.23.47-max.  Before starting up 3.23.47-max, I added several Innodb
>options to the my.cnf file:
>
>---snip---
>innodb_data_file_path =
ibdata1:2000M;ibdata2:2000M;ibdata3:2000M;ibdata4:2000M
>innodb_data_home_dir = /home/mysql/yahoo/ibdata
>innodb_log_group_home_dir = /home/mysql/yahoo/iblog
>innodb_log_arch_dir = /home/mysql/yahoo/iblog
>set-variable = innodb_mirrored_log_groups=1
>set-variable = innodb_log_files_in_group=3
>set-variable = innodb_log_file_size=128M
>set-variable = innodb_log_buffer_size=32M
>innodb_flush_log_at_trx_commit=0
>innodb_log_archive=0
>set-variable = innodb_buffer_pool_size=384M
>set-variable = innodb_additional_mem_pool_size=4M
>set-variable = innodb_file_io_threads=4
>set-variable = innodb_lock_wait_timeout=50
>---snip---
>
>And then started the server.  It created the 4 data files as well as
>the the log files.  Then I got:
>
>InnoDB: Doublewrite buffer not found: creating new
>InnoDB: Doublewrite buffer created
>InnoDB: Creating foreign key constraint system tables
>InnoDB: Foreign key constraint system tables created
>020204  1:24:13  InnoDB: Started
>/home/mysql/bin/mysqld: ready for connections
>mysqld got signal 11;
>
>and a stack trace, which resolved into:
>
>0x807bb5f handle_segfault__Fi + 383
>0x82a94aa pthread_sighandler + 154
>0x7cb80076 __evoke_link_warning_llseek + 1954074198
>0x7cb7fe19 __evoke_link_warning_llseek + 1954073593
>0x7cb713e6 __evoke_link_warning_llseek + 1954013638
>0x7c97db8b __evoke_link_warning_llseek + 1951967595
>0x7c980668 __evoke_link_warning_llseek + 1951978568
>0x7c981200 __evoke_link_warning_llseek + 1951981536
>0x7c96dee4 __evoke_link_warning_llseek + 1951902916
>0x82ddd0a gethostbyaddr_r + 346
>0x82ddb44 gethostbyaddr + 196
>0x807ff98 ip_to_hostname__FP7in_addrPUi + 232
>0x808082c check_connections__FP3THD + 152
>0x8080c79 handle_one_connection__FPv + 321
>
>I'm going back to 3.23.41-max for now.
>
>Any idea what's up?  The configuration, other than InnoDB was
>virtually identical to the previous version.  In fact, I copied the
>working my.cnf file and added the innodb bits.
>
>Thanks,
>
>Jeremy
>--
>Jeremy D. Zawodny, <[EMAIL PROTECTED]>
>Technical Yahoo - Yahoo Finance
>Desk: (408) 349-7878   Fax: (408) 349-5454   Cell: (408) 685-5936
>
>MySQL 3.23.41-max: up 0 days, processed 4,634,010 queries (446/sec. avg)
>



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

Reply via email to