[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: mysqld on debian-amd64/testing crashing with signal 11

On 23 Jun 2005, at 16:09, Ed Fisher wrote:

Hi folks,

I've been experiencing a problem with mysql-server-4.1 on two different amd64 machines, running two different versions of the package.

The errors in the log are similar to http://lists.debian.org/debian- amd64/2005/03/msg00481.html -- but I don't know if the source of the segfault is a client QUIT command. I don't think it is.

It's occurred about 10 times in the past 7 days, at seemingly random intervals. I switched to a second server yesterday afternoon, and less than 6 hours later mysqld on the new server segfaulted.

The servers get about 300qps on average, about half updates and half selects.

I turned on query logging after about the third day, despite the performance hit, and couldn't see any abnormal queries in the logs. Presumably whatever query that causes the segfault, though, wouldn't get logged.

Since the mysqld in debian doesn't seem to output a backtrace on crash, I can't use that for further debugging.

I'm open to any suggestions, and please let me know if there's any further information I can provide.

I'd try the debug build from MySQL themselves; this should give you more information about the source of the crash (if it happens again with their build).

Either way, this will help you give more info to the Debian MySQL maintainer; if the bug is not reproduced with MySQL AB's own build, then it's likely a problem with the Debian build, specifically, which is useful information. If the bug is reproduced on the MySQL AB build, then you can try the latest MySQL AB build (4.1.12a, I think) and see if that fixes it. If so, that again is useful information for the Debian maintainer. If it doesn't fix it, you can then file a bug report directly with MySQL AB, and then file one with the Debian package that references the upstream bug report.

Bugs in MySQL are not uncommon - I found a pretty basic one in MySQL 4.1.8 a few months back, and used the above process; reported the bug to MySQL AB, and their fix emerged in 4.1.10, so they weren't too slow.

To be honest, on our machines at work, I don't use the Debian MySQL packages, except for client-only machines. I prefer to have more direct control over the version of MySQL the servers are running...


Reply to: