We've been running mysql for the last 20 months without any problems at all. However, it just stopped with a Dr. Watson error on last Friday's evening when there was not a single connection or scheduled process running. The mysql server version we have is 3.23.35a. The Stack Trace showed the following calls before it died: msafd!WSPGetSockOpt ws2_32!WSARecv wsock32!recv !<nosymbols> RtlpWaitForCriticalSection RtlEnableEarlyCriticalSectionEventCreation.....
I wonder if any of our fellow mysql users has experienced a similar problem?
i think it will be unlikely that any other runs mysql in version 3.23.35a
-- Sebastian Mendel
www.sebastianmendel.de www.tekkno4u.de www.nofetish.com
-- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
