•  

Announcement

Announcement Module
Collapse
No announcement yet.

lost connection to mysql server during query

Page Title Module
Move Remove Collapse
Conversation Detail Module
Collapse
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts

  • lost connection to mysql server during query

    #1
    HI

    I'm running mysql stored procedure using VB as front end. While clicking Ok button in application it calls 3 stored procedures and returns a resultset. First time it works properly. If second time clicked the error 'lost connection to mysql server during query' displayed. Third time works fine. Like this alternatively throws error message.


    Any one explain What is the reason for this error 'lost connection to mysql server during query'
    Tags: None

  • #2
    julian wrote on Tue, 12 June 2007 14:27

    HI
    Any one explain What is the reason for this error 'lost connection to mysql server during query'


    Read here: http://dev.mysql.com/doc/refman/5.0/en/gone-away.html

    Comment


    • #3
      While throwing 'lost connection to mysql error during query' following are entries in mysqld.log




      mysqld got signal 11;
      This could be because you hit a bug. It is also possible that this binary
      or one of the libraries it was linked against is corrupt, improperly built,
      or misconfigured. This error can also be caused by malfunctioning hardware.
      We will try our best to scrape up some info that will hopefully help diagnose
      the problem, but since we have already crashed, something is definitely wrong
      and this may fail.
      key_buffer_size=8388600
      read_buffer_size=131072
      max_used_connections=1
      max_connections=100
      threads_connected=1
      It is possible that mysqld could use up to
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 225791 K
      bytes of memory
      Hope that's ok; if not, decrease some variables in the equation.

      thd=0xa49e170
      Attempting backtrace. You can use the following information to find out
      where mysqld died. If you see no messages after this, something went
      terribly wrong...
      Cannot determine thread, fp=0xb4bc9f48, backtrace may not be correct.
      Stack range sanity check OK, backtrace follows:
      0x81746a3
      0x237420
      0x827fe95
      0x81dd105
      0x827fe95
      0x8284c1a
      0x82838c4
      0x8283cc5
      0x818f06f
      0x81901e9
      0x8190791
      0x819193c
      0x81923fc
      0x4ea702db
      0x4e9ca14e
      New value of fp=(nil) failed sanity check, terminating stack trace!
      Please read http://dev.mysql.com/doc/mysql/en/Us...ack_trace.html and follow instructions on how to resolve the stack trace. Resolved
      stack trace is much more helpful in diagnosing the problem, so please do
      resolve it
      Trying to get some variables.
      Some pointers may be invalid and cause the dump to abort...
      thd->query at 0xa51e1b0 = SELECT
      Case when ErrorLog <> 'DL' then a.ErrorLog
      End ErrorLog,b.Imagepath
      FROM
      postingerrorlog a,
      entrycheck b
      WHERE
      a.ImageID = b.ImageID AND
      cdlabel = v_cdlabel and
      b.ImageID not In(Select
      a.ImageID
      from
      entrycheck a,
      keyqc b
      .....
      .....
      Union
      select
      'DUAL START PAGE' AS ErrorL
      thd->thread_id=1
      The manual page at http://www.mysql.com/doc/en/Crashing.html contains
      information that should help you find out what is causing the crash.

      Comment

      Working...
      X