I'm not sure if anyone cares but... here's my final post on this topic.
I believe my signal 11 problem was due to me installing the 3.23.34 rpms
from mysql.com on top of my Redhat 7.0 system. I had heard that the RPMs
on mysql.com are Redhat 6.2 based and thus may be expecting different
On Mon, 12 Mar 2001 10:02:51 -0500
[EMAIL PROTECTED] wrote:
I just upgraded from Mysql 3.23.28 to 3.23.34 and I'm now seeing mysql
errors from my scripts that say "mysqld has gone away". The
/var/lib/mysql/host.err log says this repeatedly:
same here.
Compiling with Innobase, and
On Tue, Mar 13, 2001 at 09:48:22PM -0800, Jeremy D. Zawodny wrote:
On Wed, Mar 14, 2001 at 02:42:30PM +0900, Tatsuhiko Miyagawa wrote:
On Mon, 12 Mar 2001 10:02:51 -0500
[EMAIL PROTECTED] wrote:
I just upgraded from Mysql 3.23.28 to 3.23.34 and I'm now seeing mysql
errors
Oops, really :-)
On Tue, 13 Mar 2001 22:48:58 -0800
"Jeremy D. Zawodny" [EMAIL PROTECTED] wrote:
I can produce a core/backtrace if necessary, but it sounds like this
easy to reproduce.
Damn. Monty has already patched it. :-)
--
Tatsuhiko Miyagawa Livin' On The EDGE, Co.,Ltd.
On Wed, Mar 14, 2001 at 03:51:18PM +0900, Tatsuhiko Miyagawa wrote:
Oops, really :-)
Yes, he posted it in the message with
Message-ID: [EMAIL PROTECTED]
Jeremy
On Tue, 13 Mar 2001 22:48:58 -0800
"Jeremy D. Zawodny" [EMAIL PROTECTED] wrote:
I can produce a core/backtrace if
Description:
I just upgraded from Mysql 3.23.28 to 3.23.34 and I'm now seeing mysql
errors from my scripts that say "mysqld has gone away". The
/var/lib/mysql/host.err log says this repeatedly:
mysqld got signal 11;
The manual section 'Debugging a MySQL server' tells you how to use a
stack
HI!
Please try to make a repeatable test case if possible.
This means a set of commands that would always lead to MySQL crashing.
Regards,
Sinisa
__ _ _ ___ == MySQL AB
/*/\*\/\*\ /*/ \*\ /*/ \*\ |*| Sinisa Milivojevic
/*/ /*/ /*/ \*\_ |*|
At 05:14 PM 3/12/2001 +0200, Sinisa Milivojevic wrote:
Please try to make a repeatable test case if possible.
This means a set of commands that would always lead to MySQL crashing.
The problem does seem caused by a sequential set of operations. The script
that I've seen cause the problem
The problem does seem caused by a sequential set of operations. The script
oops, I'm meant to say "doesn't seem caused"
-bill
-
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
FYI,
This problem got worse as more users began using the system. I had to
revert back to 3.23.28, which did solve the problem.
I'm sorry that I didn't come up with a reproducible test case. As near as
I could tell it seemed to be intermittent in nature. Things would work,
then not work.
10 matches
Mail list logo
