Hi all...
MySQL version 4.0.3-beta
Compaq Deskpro PIII 933MHz
256MB RAM, 92MB SWAP
Binary distribution
>uname -a
Linux homer 2.4.19 #2 Thu Aug 15 19:53:55 NZST 2002 i686 unknown
I don't have another test machine unfortunately, so I don't know if the
problem is specific to my machine/database or not.
I have included below what happened when I tried to add a new ENUM field to
a table, but this problem now occurs when I also try to add any type of
field to the table, or drop any field.
I have checked the archives, and have not found anything like this relating
to the 4.0.x versions.
One thing I did think of - how many versions of 4.0.3-beta-linux were
rolled? I downloaded my copy from the site before the official announcement
was made - pretty much as soon as it was put up on the site.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
mysql> SHOW CREATE TABLE users;
CREATE TABLE `users` (
`ID` int(10) unsigned NOT NULL auto_increment,
`FullName` char(50) NOT NULL default '',
`UserName` char(50) NOT NULL default '',
`Password` char(50) NOT NULL default '',
`Level` enum('1','2') NOT NULL default '1',
PRIMARY KEY (`ID`,`UserName`),
UNIQUE KEY `ID` (`ID`),
KEY `ID_2` (`ID`)
) TYPE=MyISAM
matt@homer:/usr/local/mysql/bin# ./mysql -p
Enter password:
Welcome to the MySQL monitor. Commands end with ; or \g.
Your MySQL connection id is 30 to server version: 4.0.3-beta
Type 'help;' or '\h' for help. Type '\c' to clear the buffer.
mysql> USE zeviwm;
Reading table information for completion of table and column names
You can turn off this feature to get a quicker startup with -A
Database changed
mysql> ALTER TABLE `users` ADD `Level` ENUM('1','2') DEFAULT "1" NOT NULL;
ERROR 2006: MySQL server has gone away
No connection. Trying to reconnect...
Connection id: 1
Current database: zeviwm
Query OK, 3 rows affected (0.01 sec)
Records: 3 Duplicates: 0 Warnings: 0
mysql>
Results in this in the error log:
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=0x8706148
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=0xbfe7e918, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x806ebdb
0x8261718
0x8289f35
0x8289e13
0x82472c6
0x8230e84
0x80c0662
0x808f779
0x808a6c8
0x80cdd29
0x8079738
0x807c76a
0x807799b
0x80773e5
0x8076c2e
0x825edfc
0x82941fa
New value of fp=(nil) failed sanity check, terminating stack trace!
Please read http://www.mysql.com/doc/U/s/Using_stack_trace.html and follow
instructions on how to r
esolve 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 0x8706af0 = ALTER TABLE `users` ADD `Level` ENUM('1','2')
DEFAULT "1" NOT NULL
thd->thread_id=1
Successfully dumped variables, if you ran with --log, take a look at the
details of what thread 1 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: 1
020903 10:17:28 mysqld restarted
020903 10:17:28 InnoDB: Out of memory in additional memory pool.
InnoDB: InnoDB will start allocating memory from the OS.
InnoDB: You may get better performance if you configure a bigger
InnoDB: value in the MySQL my.cnf file for
InnoDB: innodb_additional_mem_pool_size.
020903 10:17:28 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 43922
InnoDB: Doing recovery: scanned up to log sequence number 0 43922
020903 10:17:28 InnoDB: Flushing modified pages from the buffer pool...
020903 10:17:28 InnoDB: Started
/usr/local/mysql/bin/mysqld: ready for connections
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
If you need any more info, please get back to me.
Thanks,
Matt Parlane
__________________
_____ _
|__ /_____ _(_)
/ // _ \ \ / / |
/ /| __/\ V /| |
/____\___| \_/ |_|
__________________
Web: www.zevi.net
Email: [EMAIL PROTECTED]
Phone: 04 902 5777
---------------------------------------------------------------------
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
