Diagnosing Error 2013, Syslog and Stack Trace
06/11/2018 11:47
Hi, System is MySQL 5.0.51a-3ubuntu5.1 on Ubuntu 8.04 running on VMWare. I'veassigned the virtual machine 1GB of ram.

I'm currently running a join on a couple of views that cause the server torespond with Error Code : 2013Lost connection to MySQL server during query(0 ms taken) The same query runs fine if you trim the where clause (by taking out an isnull check).

I've had a look at the syslog and get the following: Jul 14 19:34:26 vmsql mysqld[6962]: 080714 19:34:26 - mysqld got signal 11;Jul 14 19:34:26 vmsql mysqld[6962]: This could be because you hit a bug. Itis also possible that this binaryJul 14 19:34:26 vmsql mysqld[6962]: or one of the libraries it was linkedagainst is corrupt, improperly built,Jul 14 19:34:26 vmsql mysqld[6962]: or misconfigured. This error can also becaused by malfunctioning hardware.

Jul 14 19:34:26 vmsql mysqld[6962]: We will try our best to scrape up someinfo that will hopefully help diagnoseJul 14 19:34:26 vmsql mysqld[6962]: the problem, but since we have alreadycrashed, something is definitely wrongJul 14 19:34:26 vmsql mysqld[6962]: and this may fail.

Jul 14 19:34:26 vmsql mysqld[6962]: Jul 14 19:34:26 vmsql mysqld[6962]: key_buffer_size=16777216Jul 14 19:34:26 vmsql mysqld[6962]: read_buffer_size=131072Jul 14 19:34:26 vmsql mysqld[6962]: max_used_connections=1Jul 14 19:34:26 vmsql mysqld[6962]: max_connections=100Jul 14 19:34:26 vmsql mysqld[6962]: threads_connected=1Jul 14 19:34:26 vmsql mysqld[6962]: It is possible that mysqld could use uptoJul 14 19:34:26 vmsql mysqld[6962]: key_buffer_size + (read_buffer_size +sort_buffer_size)*max_connections = 233983 KJul 14 19:34:26 vmsql mysqld[6962]: bytes of memoryJul 14 19:34:26 vmsql mysqld[6962]: Hope that's ok; if not, decrease somevariables in the equation.

Jul 14 19:34:26 vmsql mysqld[6962]: Jul 14 19:34:26 vmsql mysqld[6962]: thd=0x2362b80Jul 14 19:34:26 vmsql mysqld[6962]: Attempting backtrace. You can use thefollowing information to find outJul 14 19:34:26 vmsql mysqld[6962]: where mysqld died. If you see nomessages after this, something wentJul 14 19:34:26 vmsql mysqld[6962]: terribly wrong...

Jul 14 19:34:26 vmsql mysqld[6962]: Cannot determine thread, fp=0x44c46fd0,backtrace may not be correct.

Jul 14 19:34:26 vmsql mysqld[6962]: Stack range sanity check OK, backtracefollows: Jul 14 19:34:26 vmsql mysqld[6962]: (nil)Jul 14 19:34:26 vmsql mysqld[6962]: New value of fp=0x2362b80 failed sanitycheck, terminating stack trace!Jul 14 19:34:26 vmsql mysqld[6962]: Please readhttp://dev.mysql.com/doc/mysql/en/using-stack-trace.html and followinstructions on how to resolve the stack trace. ResolvedJul 14 19:34:26 vmsql mysqld[6962]: stack trace is much more helpful indiagnosing the problem, so please doJul 14 19:34:26 vmsql mysqld[6962]: resolve itJul 14 19:34:26 vmsql mysqld[6962]: Trying to get some variables.

Jul 14 19:34:26 vmsql mysqld[6962]: Some pointers may be invalid and causethe dump to abort...

Jul 14 19:34:26 vmsql mysqld[6962]: thd->query at 0x23a1070 = select^MJul 14 19:34:26 vmsql mysqld[6962]: ^Ifirstname.AccountID,^MJul 14 19:34:26 vmsql mysqld[6962]: ^Ifirstname.StringValue FirstName,^MJul 14 19:34:26 vmsql mysqld[6962]: ^Isecondname.StringValue SecondName,^MJul 14 19:34:26 vmsql mysqld[6962]: ^Iemail.StringValue Email^M [snip] Jul 14 19:34:26 vmsql mysqld[6962]: thd->thread_id=1Jul 14 19:34:26 vmsql mysqld[6962]: The manual page athttp://www.mysql.com/doc/en/Crashing.html containsJul 14 19:34:26 vmsql mysqld[6962]: information that should help you findout what is causing the crash.

Jul 14 19:34:26 vmsql mysqld_safe[6989]: Number of processes running now: 0Jul 14 19:34:26 vmsql mysqld_safe[6991]: restartedJul 14 19:34:27 vmsql mysqld[6995]: InnoDB: The log sequence number inibdata files does not matchJul 14 19:34:27 vmsql mysqld[6995]: InnoDB: the log sequence number in theib_logfiles!Jul 14 19:34:27 vmsql mysqld[6995]: 080714 19:34:27 InnoDB: Database wasnot shut down normally!Jul 14 19:34:27 vmsql mysqld[6995]: InnoDB: Starting crash recovery.

Jul 14 19:34:27 vmsql mysqld[6995]: InnoDB: Reading tablespace informationfrom the .ibd files...

Jul 14 19:34:27 vmsql mysqld[6995]: InnoDB: Restoring possible half-writtendata pages from the doublewriteJul 14 19:34:27 vmsql mysqld[6995]: InnoDB: buffer...

Jul 14 19:34:27 vmsql mysqld[6995]: 080714 19:34:27 InnoDB: Started; logsequence number 0 3874396Jul 14 19:34:27 vmsql mysqld[6995]: 080714 19:34:27 [Note] /usr/sbin/mysqld: ready for connections.

Jul 14 19:34:27 vmsql mysqld[6995]: Version: '5.0.51a-3ubuntu5.1' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (Ubuntu) I'm now stuck as to what to look at next. Why would a backtrace not work? Shak

Source is Usenet: comp.databases.mysql
Sign in to add a comment

Answer score: 5
06/11/2018 11:47 - Yes, you only need to download the source and compileit yourself with debug set: http://dev.mysql.com/doc/refman/5.0/en/compiling-for-debugging.htmlshould get you started.


Source is Usenet: comp.databases.mysql
Sign in to add a comment

Answer score: 5
06/11/2018 11:47 - <big snip> Per the log, check http://dev.mysql.com/doc/refman/5.0/en/crashing.htmland follow the instructions. If you post the query and the output of aSHOW CREATE TABLE, I can check the query on a v5.0.66 debug build andsee if the same crash happens. As to why a backtrace wouldn't work, thatwould be because the stack has been corrupted. A debug build will outputa lot more information to the log, making it possible to point the fingerat some specific code, and making a bug report more useful.

Best regards,

Source is Usenet: comp.databases.mysql
Sign in to add a comment

Answer score: 5
06/11/2018 11:47 - Charles Polisher <cpolish@nonesuch.com> wrote in message news:slrng7qmgf.tqs.cpolish@kevin.peecee3.com...

It's a bit tough to write a test case since the query runs on multiple views, some of which are based on further views.

Would it be possible for me to run MySQL under debug myself? Shak

Source is Usenet: comp.databases.mysql
Sign in to add a comment

eDiscover
Helpforce eDiscover provides technical articles updated each dayHelpforce eDiscover RSS feed contains the latest technical articles in RSS
Click the logo to go back to the main page
Search eDiscover
  
Categories

Click an icon to go to that category

Helpforce eDiscover contains articles about Microsoft Windows Helpforce eDiscover contains articles about Apple products and MacOS Helpforce eDiscover contains articles about Linux and POSIX operating systems Helpforce eDiscover contains articles about Helpforce Helpforce has a large variety of technical information and articles for you to read Helpforce eDiscover contains articles about databases, MYSQL, SQL Server Oracle Helpforce eDiscover contains articles about Java, JVM and the JRE Helpforce eDiscover contains articles about the QNX operating system Helpforce eDiscover contains articles about Oracle Solaris and Open Solaris Helpforce eDiscover contains articles about RISC OS, Acorn and the BBC Micro Helpforce eDiscover contains articles about Amiga and AmigaOS

Type your comment into the box below