#1067 Server crash on connecting a 5.1.32/win32 MySQL server

[Anonymous]

Originally created by: marty.ko...@gmail.com

I just installed wamp2 (on WinXP) with mysql 5.1.32 and i'm having a lot of
problems with heidi [r2328]. When i want to connect i get this error:

The instruction at 0x005bda76 referenced memory at 0x00000000. The memory
could not be "read".

Click on OK to terminate the program
Click on CANCEL to debug the program

When i click on Cancel Heidi tries to start up, but then i get an error
saying connection to the server has been lost. Also, when i look at my wamp
server, the mysql-server has gone offline indeed. If i restart the server
and then click on Retry (to connect), same error appears

Before i was using wamp5 server with mysql 5.0.something and i didn't have
these issues. Also, when i connect with [r2095] (the latest i have
before 2328) i don't have any problems at all. Also, when i connect to
mysql using the console, i don't have any problems.

p.s. wamp2 is newer than wamp5

[Anonymous]

Originally posted by: a...@anse.de

Looks like not HeidiSQL has crashed but your MySQL server on the same machine. That
would explain that the server is offline.

To make debugging easier you could activate file logging in MySQL. Edit or create
your c:\my.ini and add these options to the [mysqld] section:
log=c:\mysql.log
log-output=file
After restarting reproducing the crash you can open your c:\mysql.log and see what
the last query was. Would be nice if you would talk back here so we're able to fix
something.

In the meantime I will try to reproduce that by installing MySQL 5.1.32 .

Summary: Server crash on connecting a 5.1.32/win32 MySQL server
Status: NeedInfo

[Anonymous]

Originally posted by: marty.ko...@gmail.com

I can't recreate this bug anymore. I do have an idea what caused the problem though.
I had made a all-databases dump of the old mysql version and restored that dump after
i installed the new wamp server. However, the configuration of the new servers had
the lower_case_table_names directive switched on. I noticed this only later and after
that, I wiped out everything set lower_case_table_names to 0 and then restored the
data again. I think this has also fixed the problem with [r2328], because it's
not happening anymore.

Fortunately it seems debugging was already switched on. So, if you're interested,
here is part of the output:

InnoDB: The first specified data file .\ibdata1 did not exist:
InnoDB: a new database to be created!
090324  9:48:41  InnoDB: Setting file .\ibdata1 size to 10 MB
InnoDB: Database physically writes the file full: wait...
090324  9:48:42  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...
090324  9:48:42  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
090324  9:48:43  InnoDB: Started; log sequence number 0 0
090324  9:48:43 [Note] Event Scheduler: Loaded 0 events
090324  9:48:43 [Note] wampmysqld: ready for connections.
Version: '5.1.32-community-log'  socket: ''  port: 3306  MySQL Community Server (GPL)
090324  9:55:38 - mysqld got exception 0xc0000005 ;
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=16777216
read_buffer_size=262144
max_used_connections=1
max_threads=151
threads_connected=1
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 133304 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd: 0x22ccbf8
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...
005BDA76    mysqld.exe!???
022EE550   
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 022F4D70=(SELECT TABLE_NAME AS `Name`, TABLE_TYPE AS `Type`, ENGINE AS
`Engine`, VERSION AS `Version`, ROW_FORMAT AS `Row_format`, TABLE_ROWS AS `Rows`,
AVG_ROW_LENGTH AS `Avg_row_length`, DATA_LENGTH AS `Data_length`, MAX_DATA_LENGTH AS
`Max_data_length`, INDEX_LENGTH AS `Index_length`, DATA_FREE AS `Data_free`,
AUTO_INCREMENT AS `Auto_increment`, CREATE_TIME AS `Create_time`, UPDATE_TIME AS
`Update_time`, CHECK_TIME AS `Check_time`, TABLE_COLLATION AS `Collation`, CHECKSUM
AS `Checksum`, CREATE_OPTIONS AS `Create_options`, TABLE_COMMENT AS `Comment` FROM
`information_schema`.TABLES WHERE TABLE_SCHEMA = 'information_schema') UNION (SELECT
ROUTINE_NAME AS `Name`, ROUTINE_TYPE AS `Type`, NULL AS `Engine`, NULL AS `Version`,
NULL AS `Row_format`, NULL AS `Rows`, NULL AS `Avg_row_length`, NULL AS
`Data_length`, NULL AS `Max_data_length`, NULL AS `Index_length`, NULL AS
`Data_free`, NULL AS `Auto_increment`, CREATED AS `Create_time`, LAST_ALTERED AS
`Update_time`, NULL AS `Check_time`, NULL AS `Collation`, NULL AS `Checks
thd->thread_id=7
thd->killed=NOT_KILLED
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
090324  9:56:10  InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
InnoDB: Last MySQL binlog file position 0 1350334, file name .\mysql-bin.000001
090324  9:56:11  InnoDB: Started; log sequence number 0 632313
090324  9:56:11 [Note] Recovering after a crash using mysql-bin
090324  9:56:11 [Note] Starting crash recovery...
090324  9:56:11 [Note] Crash recovery finished.
090324  9:56:11 [ERROR] Column count of mysql.db is wrong. Expected 22, found 20. The
table is probably corrupted
090324  9:56:11 [ERROR] mysql.user has no `Event_priv` column at position 29
090324  9:56:11 [ERROR] Event Scheduler: An error occurred when initializing system
tables. Disabling the Event Scheduler.
090324  9:56:11 [Note] wampmysqld: ready for connections.
Version: '5.1.32-community-log'  socket: ''  port: 3306  MySQL Community Server (GPL)

[Anonymous]

Originally posted by: marty.ko...@gmail.com

I was too quick....i still get the error. This is the output of the log:

090326 16:19:05 [Note] wampmysqld: ready for connections.
Version: '5.1.32-community-log'  socket: ''  port: 3306  MySQL Community Server (GPL)
090326 16:19:43 - mysqld got exception 0xc0000005 ;
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=16777216
read_buffer_size=262144
max_used_connections=2
max_threads=151
threads_connected=1
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 133304 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd: 0x23158c8
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...
005BDA76    mysqld.exe!???
03ADE7F8   
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 02319858=(SELECT TABLE_NAME AS `Name`, TABLE_TYPE AS `Type`, ENGINE AS
`Engine`, VERSION AS `Version`, ROW_FORMAT AS `Row_format`, TABLE_ROWS AS `Rows`,
AVG_ROW_LENGTH AS `Avg_row_length`, DATA_LENGTH AS `Data_length`, MAX_DATA_LENGTH AS
`Max_data_length`, INDEX_LENGTH AS `Index_length`, DATA_FREE AS `Data_free`,
AUTO_INCREMENT AS `Auto_increment`, CREATE_TIME AS `Create_time`, UPDATE_TIME AS
`Update_time`, CHECK_TIME AS `Check_time`, TABLE_COLLATION AS `Collation`, CHECKSUM
AS `Checksum`, CREATE_OPTIONS AS `Create_options`, TABLE_COMMENT AS `Comment` FROM
`information_schema`.TABLES WHERE TABLE_SCHEMA = 'kibbutz_excudo_net') UNION (SELECT
ROUTINE_NAME AS `Name`, ROUTINE_TYPE AS `Type`, NULL AS `Engine`, NULL AS `Version`,
NULL AS `Row_format`, NULL AS `Rows`, NULL AS `Avg_row_length`, NULL AS
`Data_length`, NULL AS `Max_data_length`, NULL AS `Index_length`, NULL AS
`Data_free`, NULL AS `Auto_increment`, CREATED AS `Create_time`, LAST_ALTERED AS
`Update_time`, NULL AS `Check_time`, NULL AS `Collation`, NULL AS `Checks
thd->thread_id=2
thd->killed=NOT_KILLED
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.

[Anonymous]

Originally posted by: a...@anse.de

Looks like the crash is due to the concatenated UNION query in information_schema.
Well that's a hint at least. Will try to reproduce (I can't yet, using 5.1.28/win32)

Status: Accepted

[Anonymous]

Originally posted by: a...@anse.de

Tested 5.1.32 and failed to reproduce this crash. Selected the information_schema
database which you also leads to firing this UNION in the same db where you got the
crash.

Here are your (my) settings:
key_buffer_size=16777216 (8384512)
read_buffer_size=262144 (131072)
max_used_connections=2 (1)
max_threads=151 (don't have this setting or variable)
threads_connected=1 (1)

I have no clue what's going on here.

Labels: Severity-Broken

[Anonymous]

Originally posted by: a...@anse.de

I believe you have some corrupt data in your server directory which leads to errors
reading table data in information_schema. The debug hints talk about several InnoDB
related file errors:
> The log sequence number in ibdata files does not match
> the log sequence number in the ib_logfiles!
> ...
> Restoring possible half-written data pages from the doublewrite buffer...
> etc. ...

Additionally you seem to have copied table files from an older version in the mysql
database:

> [ERROR] Column count of mysql.db is wrong. Expected 22, found 20. The table is
probably corrupted
> [ERROR] mysql.user has no `Event_priv` column at position 29

Could be worth a look if you're able to work using a different client, let's say
MySQL Query Browser, on the information_schema database. I guess you'll get the same
server crashes. Please report back here.

Status: NeedInfo