MySQL Bugs: #41908: Trying to start MySQL while another instance is starting: confusing error messag

Bug #41908	Trying to start MySQL while another instance is starting: confusing error messag
Submitted:	7 Jan 2009 2:33	Modified:	6 Jan 2017 19:33
Reporter:	Roel Van de Paar	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Server: General	Severity:	S3 (Non-critical)
Version:	5.0, 5.1, 6.0 bzr	OS:	Any
Assigned to:		CPU Architecture:	Any
Tags:	InnoDB Crash, innodb recovery, pid, pid file

File:	Maximum allowed size is 50MB.
Description:
Privacy:

If the data you need to attach is more than 50MB, you should create a compressed archive of the data, split it to 50MB chunks, and upload each of them as a separate attachment.

To split a large file:

On *nix platforms use the split command e.g. split -b 50MB <my_large_archive> <my_split_archive_prefix>
On windows use WinZip or a similar utility to split the large file

InnoDB: Operating system error number 32 in a file operation.

Attachment: os_error_32.txt (text/plain), 7.27 KiB.

InnoDB: Starting crash recovery.

Attachment: crash_recovery_1.txt (text/plain), 3.57 KiB.

090312 14:57:16 - mysqld got exception 0xc0000005 ; / 090312 14:57:16 InnoDB: Assertion failure in thread 6572 in file G: ...

Attachment: crash1.txt (text/plain), 7.21 KiB.

A patch to change when the pid file is created and clean up some of the extra functions that have to do with pid file creation

Attachment: create_pid_file_sooner.patch (application/octet-stream, text), 2.16 KiB.