Our normally reliable back-end server for our web site has now gone
completely crazy ... it's falling over every few seconds. Automatic
restarts are nice, but it really makes the web site unusable.
mysqld got signal 11;
The manual section 'Debugging a MySQL server' tells you how to use a
stack trace and/or the core file to produce a readable backtrace that may
help in finding out why mysqld died.
010611 10:06:28 mysqld restarted
/usr/local/libexec/mysqld: ready for connections
mysqld got signal 11;
The manual section 'Debugging a MySQL server' tells you how to use a
stack trace and/or the core file to produce a readable backtrace that may
help in finding out why mysqld died.
010611 10:06:30 mysqld restarted
/usr/local/libexec/mysqld: ready for connections
mysqld got signal 11;
The manual section 'Debugging a MySQL server' tells you how to use a
stack trace and/or the core file to produce a readable backtrace that may
help in finding out why mysqld died.
010611 10:06:32 mysqld restarted
/usr/local/libexec/mysqld: ready for connections
There is very little information available here. I have tried check table,
and myisamchk with -r, -o and -e options ... and no help.
This is running MySQL 3.23.36 on NetBSD/i386 1.4.1. Are there any
significant bug fixes in 3.23.38 to make it worthwhile downloading, building
and installing it?
Tom Haapanen
[EMAIL PROTECTED]
---------------------------------------------------------------------
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
