Bug #63847 Server does not start after succesful installation
Submitted: 23 Dec 2011 7:16 Modified: 4 Mar 2012 12:55
Reporter: Jyri Jämsä Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL for Windows: Installer Severity:S2 (Serious)
Version:5.5.19 OS:Windows (2003 R2 server)
Assigned to: CPU Architecture:Any

[23 Dec 2011 7:16] Jyri Jämsä
Description:
MySQL does not start after installation. When using it from command line, following info displayed:

C:\Program Files\MySQL\MySQL Server 5.5\bin>mysqld --console
111223  9:50:25 [Note] Plugin 'FEDERATED' is disabled.
mysqld: Table 'mysql.plugin' doesn't exist
111223  9:50:25 [ERROR] Can't open the mysql.plugin table. Please run mysql_upgr
ade to create it.
111223  9:50:25 InnoDB: The InnoDB memory heap is disabled
111223  9:50:25 InnoDB: Mutexes and rw_locks use Windows interlocked functions
111223  9:50:25 InnoDB: Compressed tables use zlib 1.2.3
111223  9:50:26 InnoDB: Initializing buffer pool, size = 165.0M
111223  9:50:26 InnoDB: Completed initialization of buffer pool
111223  9:50:26 InnoDB: highest supported file format is Barracuda.
InnoDB: Log scan progressed past the checkpoint lsn 49439
111223  9:50:26  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: Doing recovery: scanned up to log sequence number 1595675
111223  9:50:26  InnoDB: Assertion failure in thread 3872 in file fsp0fsp.c line
 2101
InnoDB: Failing assertion: inode
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
111223  9:50:26 - 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=89128960
read_buffer_size=65536
max_used_connections=0
max_threads=100
thread_count=0
connection_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 119766 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x0
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...
006405A8    mysqld.exe!my_osmaperr()
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.

How to repeat:
Install mysql
[23 Dec 2011 9:20] Valeriy Kravchuk
Looks like a duplicate of bug #61356. What exact version, 5.5.x, do you install? Is it a fresh install or upgrade from some older version?
[23 Dec 2011 9:30] Jyri Jämsä
It is a fresh installation with mysql-installer-5.5.19.0.msi
[23 Dec 2011 10:38] MySQL Verification Team
If is fresh install and assuming you don't have data to preserve are you tried to remove then to delete manually the data directory and re-install?. Thanks.
[23 Dec 2011 11:59] Jyri Jämsä
I did that, and now database  starts. This time I included everything, also SQL Workbench.
[24 Dec 2011 13:26] Valeriy Kravchuk
Do you remember your options during previous, unsuccessful installation? I wonder if it was just some incomplete installation attempt or we do have some set of options that leads to bad server installation.
[27 Dec 2011 6:11] Jyri Jämsä
I was trying to install a minimum server, so I left out MySQL workbench and Examples/samples.
[4 Feb 2012 12:55] Valeriy Kravchuk
Please, check if the same problem still happens in your environment with a newer version of Installer, 5.5.20.0.
[5 Mar 2012 1:00] Bugs System
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".