Dennis, are you building on Red Hat 8.0?
Our guess is that there is some bug in glibc-2.2.92 there. mysqld crashes just after thread creation on many Red Hat 8.0 computers if built from source on that computer. Workaround: use an official binary from www.mysql.com or build on Red Hat <= 7.3. Best regards, Heikki Tuuri Innobase Oy http://www.innodb.com Transactions, foreign keys, and a hot backup tool for MySQL Order MySQL technical support from https://order.mysql.com/ ----- Original Message ----- From: "Dennis van der Meer" <[EMAIL PROTECTED]> Newsgroups: mailing.database.mysql Sent: Sunday, June 01, 2003 4:04 PM Subject: Unable to install from source due to crash > >Description: > The file scripts/mysql_install_db crashes when trying to create the > databases. Since the system isn't configured MySQL cannot start > >How-To-Repeat: > Just a simple build from source will do the trick. There are no > compile errors and even the make install works without problems > >Fix: > Unknown > > >Submitter-Id: > >Originator: > >Organization: > >MySQL support: none > >Synopsis: Unable to install from source due to crash of mysql_install_db > >Severity: critical > >Priority: medium > >Category: mysql > >Class: support > >Release: mysql-4.0.13 (Source distribution) > > >C compiler: gcc (GCC) 3.2.2 > >C++ compiler: gcc (GCC) 3.2.2 > >Environment: > <machine, os, target, libraries (multiple lines)> > System: Linux caveman 2.4.20-ac2 #14 Mon Apr 14 23:57:48 CEST 2003 i686 unknown > Architecture: i686 > > Some paths: /usr/bin/perl /usr/bin/make /usr/bin/gmake /usr/bin/gcc > /usr/bin/cc > GCC: Reading specs from /usr/lib/gcc-lib/i386-slackware-linux/3.2.2/specs > Configured with: ../gcc-3.2.2/configure --prefix=/usr --enable-shared > --enable-threads=posix --enable-__cxa_atexit --disable-checking > --with-gnu-ld --verbose --target=i386-slackware-linux > --host=i386-slackware-linux > Thread model: posix > gcc version 3.2.2 > Compilation info: CC='gcc' CFLAGS='-O2' CXX='gcc' CXXFLAGS='-O2 > -felide-constructors -fno-exceptions -fno-rtti' LDFLAGS='' ASFLAGS='' > LIBC: > lrwxrwxrwx 1 root root 13 Apr 13 19:44 /lib/libc.so.6 -> > libc-2.3.1.so > -rwxr-xr-x 1 root root 1435624 Mar 5 06:57 /lib/libc-2.3.1.so > -rw-r--r-- 1 root root 2425490 Mar 5 06:57 /usr/lib/libc.a > -rw-r--r-- 1 root root 178 Mar 5 06:50 /usr/lib/libc.so > Configure command: ./configure '--prefix=/usr/local/mysql' > '--enable-assembler' '--with-mysqld-ldflags=-all-static' 'CFLAGS=-O2' > 'CXXFLAGS=-O2 -felide-constructors -fno-exceptions -fno-rtti' 'CXX=gcc' > > >Full output from scripts/mysql_install_db > Preparing db table > Preparing host table > Preparing user table > Preparing func table > Preparing tables_priv table > Preparing columns_priv table > Installing all prepared tables > 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=8388600 > read_buffer_size=131072 > sort_buffer_size=2097144 > max_used_connections=0 > max_connections=100 > threads_connected=1 > It is possible that mysqld could use up to > key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = > 225791 K > bytes of memory > Hope that's ok; if not, decrease some variables in the equation. > > thd=0x83d8eb8 > Attempting backtrace. You can use the following information to find out > where mysqld died. If you see no messages after this, something went > terribly wrong... > Cannot determine thread, fp=0xbf5fea48, backtrace may not be correct. > Stack range sanity check OK, backtrace follows: > 0x8087af8 > 0x822811a > 0x8239057 > 0x8096d79 > 0x8098f69 > 0x8096b98 > 0x8092003 > 0x822228e > 0x825cda4 > scripts/mysql_install_db: line 1: 31598 Segmentation > fault /usr/local/mysql/libexec/mysqld --bootstrap --skip-grant-tables > --basedir=/usr/local/mysql --datadir=/usr/local/mysql/var --skip-innodb > --skip-bdb > Installation of grant tables failed! > > Examine the logs in /usr/local/mysql/var for more information. > You can also try to start the mysqld daemon with: > /usr/local/mysql/libexec/mysqld --skip-grant & > You can use the command line tool > /usr/local/mysql/bin/mysql to connect to the mysql > database and look at the grant tables: > > shell> /usr/local/mysql/bin/mysql -u root mysql > mysql> show tables > > Try 'mysqld --help' if you have problems with paths. Using --log > gives you a log in /usr/local/mysql/var that may be helpful. > > The latest information about MySQL is available on the web at > http://www.mysql.com > Please consult the MySQL manual section: 'Problems running mysql_install_db', > and the manual section that describes problems on your OS. > Another information source is the MySQL email archive. > Please check all of the above before mailing us! > And if you do mail us, you MUST use the /usr/local/mysql/bin/mysqlbug script! > > > -- > MySQL General Mailing List > For list archives: http://lists.mysql.com/mysql > To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] > -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
