DBD::mysql::st execute failed: Lost connection to MySQL server

bloatedstoat

• March 22, 2014 17:45

Hello, Last night the data centre had an issue with a switch which apparently led to the filesystem on our server being rendered read only. After the switch issue was resolved we rebooted our server and all appears to be running as expected except for the following where we receive errors every 4 hours. DBD::mysql::st execute failed: Lost connection to MySQL server during query at bin/update_db_cache line 334. DBD::mysql::st execute failed: Lost connection to MySQL server during query at bin/update_db_cache line 334. Has anyone come across this before? Is there a fix for this? Thanks in advance for any help. ---- CENTOS 6.5 x86_64 xenpv WHM 11.42.0 (build 22) Load Averages: 0.07 0.17 0.14

• 

  cPanelMichael

  • April 02, 2014 19:19

  Hello :) Do you notice any error messages in /var/lib/mysql/$hostname.err when restarting the MySQL service or when running "/usr/local/cpanel/scripts/update_db_cache" manually? Thank you.

  0
• 

  Solokron

  • June 08, 2014 07:33

  140608 00:31:50 mysqld_safe Number of processes running now: 0 140608 00:31:50 mysqld_safe mysqld restarted 140608 0:31:50 [Warning] '--safe-show-database' is deprecated and will be removed in a future release. Please use 'GRANT SHOW DATABASES' instead. 140608 0:31:50 [Note] Plugin 'FEDERATED' is disabled. 140608 0:31:50 InnoDB: Initializing buffer pool, size = 1.2G 140608 0:31:51 InnoDB: Completed initialization of buffer pool InnoDB: Log scan progressed past the checkpoint lsn 22 4199971154 140608 0:31:51 InnoDB: Database was not shut down normally! InnoDB: Starting crash recovery. InnoDB: Reading tablespace information from the .ibd files... InnoDB: Restoring possible half-written data pages from the doublewrite InnoDB: buffer... InnoDB: Doing recovery: scanned up to log sequence number 22 4199973037 140608 0:31:51 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 InnoDB: Apply batch completed 140608 0:31:52 InnoDB: Started; log sequence number 22 4199973037
  

  0
• 

  cPanelPeter cPanel Staff

  • June 08, 2014 15:27

  Hello, The above log error shows some possible InnoDB corruption. It also however shows that it may have been repaired. Are you still having issues with running "/usr/local/cpanel/scripts/update_db_cache" manually? If so, please feel free to open a support ticket using the link in my signature. Please post the ticket number in this thread so we can update it accordingly.

  0
• 

  Solokron

  • June 09, 2014 01:45

  Still occurs.

  0
• 

  cPanelMichael

  • June 10, 2014 14:59

  Please see the following document regarding InnoDB corruption: [url=http://dev.mysql.com/doc/refman/5.5/en/innodb-backup.html]MySQL :: MySQL 5.5 Reference Manual :: 14.19 InnoDB Backup and Recovery Thank you.

  0

Please sign in to leave a comment.