Hi Sasha,
> Looks like you found two bugs at once. The first one is that someone
mysqld
> segfaults, probably a bug in processing some query or possibly some
OS issue,
> but there is not much we can tell at this point - the only way to
track it
> down would be if you had full logging enabled and saved the last few
queries
Yes, full logging was enabled.
> before the crash, and took a full snapshot of the database at the
time of the
> crash.
No I did not take a snapshot. (sorry didn't think of it).
>
> Second bug is that BDB could not recover after the crash - I hope
you have
> backed up the logs before you deleted them - we will need them to
debug the
> problem. If you still have them, upload them to
> ftp://support.mysql.com/pub/mysql/secret/
Unfortunately being in a hurry to get the daemon running again I
deleted the files.
I will attempt to reproduce the problem on an unused server. I think
it should be easy to recreate, just drop a database after you have
something for it in the log.0000xx file then after the db is gone,
stop and restart the server. I'll try to come up with a simple test
case tomorrow.
Thanks
Ken
---------------------------------------------------------------------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
