Hi!
>>>>> "Voytek" == Voytek Lapinski <[EMAIL PROTECTED]> writes:
Voytek> Ok... I've posted briefly regarding this, but heres a complete bug report.
Voytek> Yeah I know its kinda long, but I thought it better to include more rather
Voytek> than less.
Voytek> We are seeing a problem which results in mysqld dying with a SIGSEGV. The
Voytek> problem has been confirmed on both these machines
<cut>
Voytek> The error message takes the following form:
Voytek> mysqld got signal 11;
Voytek> The manual section 'Debugging a MySQL server' tells you how to use a
Voytek> stack trace and/or the core file to produce a readable backtrace that may
Voytek> help in finding out why mysqld died.
Voytek> Attempting backtrace. You can use the following information to find out
Voytek> where mysqld died. If you see no messages after this, something went
Voytek> terribly wrong...
Voytek> Cannot determine thread, ebp=0xbffff108, backtrace may not be correct.
Voytek> Stack range sanity check OK, backtrace follows:
Voytek> 0x813fefa
Voytek> 0x813f6dd
Voytek> 0x8081690
Voytek> 0x8081b14
Voytek> 0x808127e
Voytek> 0x8145e4b
Voytek> 0x8048111
Voytek> New value of ebp failed sanity check, terminating backtrace!
Voytek> Naturally with different values for the stack backtrace depending on version
Voytek> (the addresses look similarly spaced though, so it's probably the same thing).
Could you please follow the instructions in the MySQL manual (search
after stack trace) to produce a symbolic stack trace of the above?
Voytek> The problem appears to be related to connections which occur at roughly the
Voytek> same time. I have written a script which reliably causes it to occur and have
Voytek> included it below. It operates by forking off lots of processes all of which
Voytek> connect and disconnect to the database repeatedly until it goes down. In most
Voytek> cases, the database will crash within seconds, although rarely it seems
Voytek> to take significantly longer (several minutes). The problem I am referring to
Voytek> is associated with local UNIX domain socket connections, but when I briefly
Voytek> tested connecting over TCP/IP it (or something else similar) still occurs in
Voytek> that it eventually stops accepting connections on that port (although the
Voytek> database is still running and generates no errors). This may be something
Voytek> else entirely though, and I have not investigated that at all.
<cut>
I will test this today on my SMP Linux box.
<cut>
Voytek> Oh yeah, another weird thing that we noticed while testing this that may or
Voytek> may not be related is that once in a while when running the test script, a
Voytek> user would appear to be logged in as their password instead of their login
Voytek> name. No investigation was done on this issue.
I will test this also.
Thanks for the good bug report!
Regards,
Monty
---------------------------------------------------------------------
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
