Bug #17616 | Crash in creation of "mysql" database | ||
---|---|---|---|
Submitted: | 21 Feb 2006 14:48 | Modified: | 21 May 2006 14:24 |
Reporter: | Francesco Riosa | Email Updates: | |
Status: | No Feedback | Impact on me: | |
Category: | MySQL Server | Severity: | S3 (Non-critical) |
Version: | 5.1.6_alpha | OS: | Linux (linux (custom)) |
Assigned to: | CPU Architecture: | Any |
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
[21 Feb 2006 14:51]
Francesco Riosa
[22 Feb 2006 15:22]
Francesco Riosa
cut and paste from the console, resolved trough "resolve_stack_dump"
Attachment: mysqld.stack.resolved (application/octet-stream, text), 4.75 KiB.
[22 Feb 2006 15:25]
Francesco Riosa
debug trace of the server run by mysql_install_db
Attachment: mysqld.trace.bz2 (application/x-download, text), 8.40 KiB.
[2 Mar 2006 14:19]
Francesco Riosa
5.1.7 : ./bin/mysql_install_db (same options) trace
Attachment: mysqld.trace.bz2 (application/x-download, text), 11.31 KiB.
[2 Mar 2006 14:21]
Francesco Riosa
diff between traces of 5.1.6 and 5.1.7 (removed first 12 chars of each row)
Attachment: mysqld.trace-5.1.6-5.1.7.diff.bz2 (application/x-download, text), 15.13 KiB.