>Description: A freshly installed mysql 4.0.11a crashes at first startup: (mysql_install_db runs fine), mysqld-safe --user=mysql chrashes and restarts in an endless loop. This is true for both the linux binary and the source distro. The same mysql version is stable on a system with identical softrware makeup. The system seems stable otherwise (compiled kernel, apache, php, etc.. no problems)
hostname.err 030303 21:58:33 mysqld started InnoDB: The first specified data file ./ibdata1 did not exist: InnoDB: a new database to be created! 030303 21:58:33 InnoDB: Setting file ./ibdata1 size to 10 MB InnoDB: Database physically writes the file full: wait... 030303 21:58:35 InnoDB: Log file ./ib_logfile0 did not exist: new to be created InnoDB: Setting log file ./ib_logfile0 size to 5 MB InnoDB: Database physically writes the file full: wait... 030303 21:58:36 InnoDB: Log file ./ib_logfile1 did not exist: new to be created InnoDB: Setting log file ./ib_logfile1 size to 5 MB InnoDB: Database physically writes the file full: wait... 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 030303 21:58:37 InnoDB: Started 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 Number of processes running now: 9 mysqld process hanging, pid 17434 - killed mysqld process hanging, pid 17433 - killed mysqld process hanging, pid 17432 - killed mysqld process hanging, pid 17431 - killed mysqld process hanging, pid 17430 - killed mysqld process hanging, pid 17429 - killed mysqld process hanging, pid 17428 - killed mysqld process hanging, pid 17427 - killed mysqld process hanging, pid 17426 - killed 030303 21:58:38 mysqld restarted 030303 21:58:38 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 0 37082 InnoDB: Doing recovery: scanned up to log sequence number 0 37082 030303 21:58:38 InnoDB: Flushing modified pages from the buffer pool... InnoDB: Creating foreign key constraint system tables InnoDB: Foreign key constraint system tables created 030303 21:58:38 InnoDB: Started 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 .... and so on and so on until the manual killing of mysqld_safe key_buffer_size=8388600 read_buffer_size=131072 sort_buffer_size=-286397205 max_used_connections=0 max_connections=100 threads_connected=0 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 141264 2 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. thd=0x83befc8 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... Bogus stack limit or frame pointer, fp=0xbfffe278, stack_bottom=0x18171615, thre ad_stack=196608, aborting backtrace. Trying to get some variables. Some pointers may be invalid and cause the dump to abort... thd->query at 0x14131211 is invalid pointer thd->thread_id=138147512 Successfully dumped variables, if you ran with --log, take a look at the details of what thread 138147512 did to cause the crash. In some cases of reall y 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. 030303 21:58:41 mysqld ended >How-To-Repeat: install binary / compile source on the target machine Tried recommended CFLAGS etc. settings (from onlein manual) without any difference in outcome. >Fix: no known fix >Submitter-Id: <submitter ID> >Originator: [EMAIL PROTECTED] >Organization: Larissa Naber fachhochschule technikum wien [EMAIL PROTECTED] >MySQL support: [none] >Synopsis: mysqld 4.0.11a crashes on start up >Severity: critical >Priority: medium >Category: mysql >Class: sw-bug >Release: mysql-4.0.11a-gamma (Source distribution) >C compiler: 2.95.3 >C++ compiler: 2.95.3 >Environment: System: Linux btecserv 2.4.18 #4 Fri May 31 01:25:31 PDT 2002 i686 unknown Architecture: i686 Slackware Linux 8.1 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/2.95.3/specs gcc version 2.95.3 20010315 (release) Compilation info: CC='gcc' CFLAGS='-O3 -mpentiumpro' CXX='gcc' CXXFLAGS='-O3 -mpentiumpro -felide-constructors -fno-exceptions -fno-rtti' LDFLAGS='' ASFLAGS='' LIBC: lrwxrwxrwx 1 root root 13 Nov 17 21:32 /lib/libc.so.6 -> libc-2.2.5.so -rwxr-xr-x 1 root root 5029105 May 18 2002 /lib/libc-2.2.5.so -rw-r--r-- 1 root root 24991240 May 18 2002 /usr/lib/libc.a -rw-r--r-- 1 root root 178 May 18 2002 /usr/lib/libc.so Configure command: ./configure '--prefix=/usr/local/mysql' '--mandir=/usr/man' '--infodir=/usr/info' '--with-mysqld-user=mysql' '--without-debug' '--with-openssl' 'CFLAGS=-O3 -mpentiumpro' 'CXXFLAGS=-O3 -mpentiumpro -felide-constructors -fno-exceptions -fno-rtti' 'CXX=gcc' --------------------------------------------------------------------- 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
