Hot answers tagged

28

Please review my answer to this recent question. I believe the circumstances are identical. Do not change your MySQL configuration at this point, as MySQL is not the problem -- it's only a symptom of the problem... which is that you appear to have a system with a small amount of memory and zero swap space. Your server is not crashing "because" memory ...


25

I have good news, and bad news. The good news is, your filesystem and mysql are most likely fine... but check /var/log/syslog or equivalent to see what else was happening on your system before 10:21:05. When the first message you posted was logged, your mysql server had already died. 120927 10:21:05 mysqld_safe Number of processes running now: 0 So, ...


19

I was able to repro on 2008 R1 SP3 10.00.5512 but installing the latest CU (14) fixed it. Reviewing the bugs fixed in the intervening versions it looks as though you need to upgrade to a build that includes the following fix. Access violation when you run a query that contains many constant values in an IN clause in SQL Server 2008 or in SQL Server 2012 ...


7

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


6

TL;DR: Except for a specific bug in PostgreSQL 9.3 prior to 9.3.4 which it's vital that you patch, index corruption after crash is never expected and hasn't been since PostgreSQL 7.1 was released in 2001. The advice/folklore you got was wrong. I am told that a long time ago in a galaxy far, far away (PostgreSQL 8.4 under Ubuntu 12.04), PostgreSQL ...


4

ASPECT #1 The first thing that caught my eye was this line InnoDB: Error: trying to load index PRIMARY for table / This indicates you have a table using the InnoDB Storage Engine What is interesting about InnoDB is the way a PRIMARY KEY is stored. It is stored in a structure called the gen_clust_index, or more commonly known as the Clustered Index. ...


4

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 out-of-...


3

Follow the steps outlines in How to use the DBCC MEMORYSTATUS command to monitor memory usage on SQL Server. The remedy action will depend on your findings. You can also read How to Identify Microsoft SQL Server Memory Bottlenecks which is more accessible. One word of caution though: is unlikely you will find individual queries to blame. Tracking downs ...


3

This error: ERROR 145 (HY000) at line 2970: Table './mysql/proc' is marked as crashed and should be repaired 228MB mysqldump: Got errno 32 on write ... suggests that the problem is writing not reading, so do a repair on the destination database.


2

It seems theoretically possible that table could still dump properly if the corruption were in the indexes, which aren't dumped. It should not be possible for anything in your configuration to cause MySQL to crash with a Signal 11, a segmentation fault. I've been staring at this for a while, now, and I haven't come up with answers... just questions (in no ...


2

I need the tables to be InnoDB and in sync. Those two statements crashing. Does it crash with a stack trace in the server logs? Could you share it here? I tried the above two commands on a 2-node MariaDB-5.5.47 cluster and it worked as expected. As @jkavalik suggested, you could do something like the following : Create a new INNODB table with the same ...


2

I finally figured it out. The main reason for the crashes and the mysql_upgrade error was related to missing and/or corrupted primary keys of the mysql table. There were also a couple missing records in the mysql.db table, which likely couldn't update previously due to the GRANT crashes and would have been related to Plesk "Database Servers" ...


1

I exected startup nomount with explicit pfile paremeter and it works. I have the init < SID >.ora in the $ORACLE_HOME/dbs/ directory, and always was working.


1

MyISAM support in galera is cough beta at best. The best thing to do is: mysqldump ... -T db table_name > dump.sql (this will make a .sql and .txt file) drop the myisam table edit the .sql file and change ENGINE=MYISAM to ENGINE=INNODB LOAD DATA INFILE 'table.txt' INTO TABLE table_name; Do this on whatever node that you want to treat as the "source of ...


1

SHOW VARIABLES LIKE 'open_files_limit'; That will reflect the OS's ulimit -n. In some OSs, that limit is set too low. Change it. Then set table_open_cache to be about one-third of it.


1

this is surely a resources or limits problem. For the first check if you have RemoveIPC enabled (Man for login.conf If it does not solve, review the Database Quick Installation Guide in the sections Configuring Kernel Parameters and Resource Limits and Creating Required Operating System Groups and Users Regards Giova


1

You can do many things to prevent this. Move DB server to somewhere else (hosting) Buy an UPS Change to a simpler DB software (SQLite, Files) Make your code to always save the latest changes, so when power up, programs keep running from last saved point.


1

The best database will be the one you (or the person in charge) know how to administer and handle. Besides software resources, one important question is the human resources you have available for your project. Oracle, Sql Server... will all be useless if no one in your company knows how to use those DBMS.


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 ...


1

I just know a workaround: manually resync the member of the replica set. Basically, it is done like this: Shutdown the mongod instance in question Delete the contents of the dbpath directory Restart the instance. It will sync then


1

I take it you are using REPAIR TABLE by hand. I also take it your are doing an automatic table repair for MyISAM. (You have to remove or comment out the option of my.cnf to disable automatic MyISAM table repair). You can actually repair the table without using MySQL but mysqld cannot be accessing it. How? You have to use the offline utility myisamchk ...


1

Following these steps probably offers a decent shot at making the MySQL instance happy again... recreate the database's directory that you deleted create an InnoDB table with the same exact column names and definitions and the same table name, but in a different schema (or on a different server) copy only the .frm file for that table into the database's ...


1

This happened to me recently and this thread has been invaluable for helping me understand what's happening. I'm running a LAMP stack on Ubuntu 14.04 with 1GB Ram. My server kept crashing due to web traffic spikes. For me, fiddling with the mysql config file only extended the amount of time I'd experience another random crash. To test and fix this, I ...


1

I have had the same problem as originally posted plus recurring InnoDB corruptions at random intervals after mysterious Mysql_safe restarts . I was usually able to restart Mysql by first stopping Apache. After reading this post i looked in my syslog logs and i found : kernel: Out of memory: Kill process 19468 (mysqld) score 256 or sacrifice child With ...



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