Description:
Mysql crashed
How-To-Repeat:
Don't know how to reproduce - server running a busy site with multiple
concurrent clients. Impossible to tell which caused the crash, but I'll gather more
evidence (try --log) and follow up if I can find anything specific.
Fix:
On Monday 10 December 2001 07:00 pm, Petro wrote:
?On Monday 10 December 2001 05:45 pm, you wrote:
? root@dbacp01d-red:/usr/local/mysql/bin# ./resolve_stack_dump -s /tmp/a
? -n /tmp/b
? 0x807b75f handle_segfault__Fi + 383
? 0x812bcaa pthread_sighandler + 154
? 0x815059c chunk_free + 596
?
We've just migrated this app from solaris to linux. for several days,
this machine was a tracking slave to this application. last night we
actually switched to make this machine the master for the application.
this was the master and had a connected slave at the time of failure.
the machines
On Monday 10 December 2001 05:45 pm, you wrote:
root@dbacp01d-red:/usr/local/mysql/bin# ./resolve_stack_dump -s /tmp/a
-n /tmp/b
0x807b75f handle_segfault__Fi + 383
0x812bcaa pthread_sighandler + 154
0x815059c chunk_free + 596
0x8152573 free + 155
0x811579c my_no_flags_free + 16
0x8077284
Description:
Mysql crashed on this machine, stack trace already submitted via email.
Please see previous email for details.
How-To-Repeat:
If I knew how to repeat it, I'd make sure that didn't happen. :
Fix:
Submitter-Id: [EMAIL PROTECTED]
Originator: [EMAIL
On Mon, Dec 10, 2001 at 06:36:16PM -0700, Sasha Pachev wrote:
On Monday 10 December 2001 05:45 pm, you wrote:
root@dbacp01d-red:/usr/local/mysql/bin# ./resolve_stack_dump -s /tmp/a
-n /tmp/b
0x807b75f handle_segfault__Fi + 383
0x812bcaa pthread_sighandler + 154
0x815059c chunk_free +
