| Bug #29463 | server died, falcon recovery fails in loop, crashing over and over | ||
|---|---|---|---|
| Submitted: | 1 Jul 2007 1:11 | Modified: | 6 Jul 2007 15:49 |
| Reporter: | Shane Bester (Platinum Quality Contributor) | Email Updates: | |
| Status: | Can't repeat | Impact on me: | |
| Category: | MySQL Server: Falcon storage engine | Severity: | S1 (Critical) |
| Version: | 6.0.1-BK | OS: | Linux (suse 9.3) |
| Assigned to: | CPU Architecture: | Any | |
| Tags: | covery, crash | ||
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
[1 Jul 2007 1:13]
Shane Bester
[1 Jul 2007 1:14]
Shane Bester
run all these sql statements, making sure mysqld_safe will restart server if it crashes.
Attachment: bug29463_error_log.txt.bz2 (application/octet-stream, text), 16.53 KiB.
[1 Jul 2007 1:14]
Shane Bester
error logs from my crashes
Attachment: bug29463_error_log.txt.bz2 (application/octet-stream, text), 16.53 KiB.
[1 Jul 2007 1:15]
Shane Bester
run all *these* sql statements, making sure mysqld_safe will restart server if it crashes.
Attachment: bug29463_testcase.txt.bz2 (application/octet-stream, text), 12.07 KiB.
