Tag Info

Hot answers tagged

5

I just had the same problem, this was fixed by issuing a command, assuming mysql data dir is on /var/lib/mysql/mysql myisamchk -q -r /var/lib/mysql/mysql/proc Source : http://dev.mysql.com/doc/refman/5.0/en/myisam-repair.html


3

In the end, it was only after changing my hosting plan (and moving away from cPanel, which seemed to obscure some of the logging) that I was able to see the issue. Turns out that from time to time, memory usage would spike (I'm guessing that this was because of a dramatic spike in apache child processes) and this would cause memory pressure. The ...


1

I'm sorry, I don't have a corrupt pg_conversion table to help perform any verifications. My answers here must, by necessity, be heavily based on speculation. With the limited information we have, I am guessing that you are attempting to do a full database pg_dump, along the lines of pg_dump --host 127.0.0.1 --port 5432 --username "postgres" ... ...


1

You will have to mysqldump around moments_production_wp I have old posts to bypass databases and tables Dec 16, 2011 : How do you mysqldump specific table(s)? Feb 20, 2013 : There is any option for mysqldump to ignore databases for backup in mysql Using the same concepts, here is how to mysqldump all except moments_production_wp MYSQL_USER=root ...


1

I am not totally convinced MySQL is running out of memory. Here is why: ASPECT #1 When you use mysqltuner.pl, it calculates the total usage in the worst case scenario. It does it by adding 3 figures together key_buffer_size innodb_buffer_pool_size thread_memory : max_connections * the sum of sort_buffer_size join_buffer_size read_buffer_size ...


1

After a bunch more googling, etc., I finally came upon the solution: http://notesonit.blogspot.hk/2013/05/innodb-unable-to-lock-ibdata1-error-11.html


1

Your master is not compatible with the 5.6 slave. binlog_checksum is only available on 5.6, and so is UUID. I have successfully replicated servers between 5.5 and 5.6. Perhaps you can check if these options can be disabled. 2014-11-13 14:03:07 1022 [Warning] Slave I/O: Notifying master by SET @master_binlog_checksum= @@global.binlog_checksum failed ...


1

No, rollbacks cannot be done in the background. Both that and the double write checks have to be done before accepting connections again (meaning that if you kill it, you will have to start again on restart). REDO process, however, can and is done in the background. What you can do is kill mysql (again) and restart it skipping that step: /etc/init.d/mysqld ...



Only top voted, non community-wiki answers of a minimum length are eligible