Tag Info

New answers tagged

0

The best solution I found, and settled with in production, was found at http://www.mysqldiary.com/if-you-copy-a-myisam-table-with-primary-key-don%E2%80%99t-forget-to-order-the-rows-first/ . Using SHOW INDEX IN a WHERE Key_name='PRIMARY', I identifie the primary key of the table(s), and append an ORDER BY to the query. The final solution looks like INSERT ...


1

EDIT: While the error is identified correctly, this solution does not help. When MySQL ADD PRIMARY KEYs, it again copies the table akin to INSERT INTO a_copy SELECT * FROM a, which leaves as at the same problem again. Check my other response in this thread. So, I've figured it out, through watching the file sizes in /var/lib/mysql/<mydb>/a*, where the ...


1

TL;DR : Stopping your services is not necessary with LVM snapshots. +1 for XtraBackup. It is not required to stop the services. The LVM snapshot is equivalent to pulling the power, which means it is consistent, but the same as a crash. When starting the service from one of your backups, it will have to do crash recovery. The time needed to do this varies ...


5

It looks to me like your datadir is in a file system of its own. Ext file systems, like most FSes under Unix, have at their root a directory called lost+found. It exists in order to allow files that become detached (that is, they have content, but no associated directory entry) to be reattached somewhere when an inconsistent file system is fscked (see, eg, ...


0

This is an old question, but we faced the same issues (High IO waits, and terrible insert / update speeds) the past week on a new dedicated server and this solution addresses this issue directly. Disabling journaling with tune2fs -O "^has_journal" /dev/<drive> was the quickest solution as it eliminates the IO wait because of the JDB2 process. But this ...


2

You need to use the same MySQL configuration on the Linux system as you used on the Mac. The error message in your question comes because InnoDB log file settings are different in your Linux.


0

Finally solved my issue, the problem was a tipo issue, I have in my database: 160 | e6867740-7d07-4783-b210-5cc3accb44eb | ClearText-Password | := | pass I wrote ClearText-Password with the T of "text" in capital letter. The right way is Cleartext-Password with the t of "text" non capital letter.


1

Try using a new user in your grant statement, you might have a user conflict in mysql user table. grant all privileges (or any other privileges) on *.* (or any other database) to '__NEWUSER__'@'%' identified by '__PASSWORD__'; Replace NEWUSER with new user and PASSWORD with a password, here is example. grant all privileges on *.* to 'xxx'@'%' identified ...


0

Mysql can be controlled by an init script (which you gave already /etc/init.d/mysql) But Ubuntu uses upstart has replaced old sysvinit style service control. and init script starts mysqld_safe (which runs mysqld as daemon mode) i know it's too complicated. Upstart is controlling the services (you are looking for this), here is the documentation. ...


0

If you can create a tunnel from the stepping stone to the original tunneling box, the solution is simply to chain the two tunnels. Setup one PuTTY instance to connect to the "stepping stone" and create a tunnel to the box, that you have used for tunneling previously. Setup another PuTTY instance to connect to the first tunnel and create a tunnel to the ...


0

Try making the tunnel yourself with ssh -f -L 3306:localhost:3306 11.22.33.44 -N Then just connect to localhost:3306 without SSH encryption.


0

When I had that problem, it was because the host name used in the 'connection' part of you mysql client wasn't resolving properly its name in the MySQL's server to the server itself. Usually I had to change the /etc/hosts and add localhost to the 127.0.0.1 entry. Your case doesn't seem to be the same as you are using the ip 127.0.0.1?! BTW, have you ...


-3

Check IPs and Date-time for all 408 status in logs, check consecutive requests from same ip and check their request time if time difference is low then congratulations you have mod_security enable and configured properly. for more info check this(https://www.modsecurity.org/) out on mod_security.


4

I noticed you're using the db.micro instance. As with EC2, the micro instances are designed to be budget-friendly, but at a cost of performance. That said, you'll get a much worse performance when loading these types of servers versus the normal instances because the CPU time is given to the instance "last" compared to other instances sharing the same ...


3

You can use the auto_increment_increment and auto_increment_offset settings. Each server will have a different offset value, and they will all increment enough each time to "hop over" and leave room for the numbers your other servers will generate. There's some good docs about it here: http://dev.mysql.com/doc/refman/5.6/en/replication-options-master.html ...


1

The common/recommended practive should work just fine. Just make sure you run this chown -R mysql:mysql /var/lib/mysql ALTERNATIVE Based on the query output and the data directory size, you have 13GB of wasted space due to some fragmentation. Now is your chance to eliminate that fragmentation. mysqldump your data and gzip it MYSQL_USER=root ...


0

Ok, answering my own question. It's a bug we've discovered in MySQL server. Making it simple we had nagios check which looked like mysqld --verbose --help 2>&1 >&- Ok here is the problem, stdout is closed. And mysql prints output to index file which is opened before. We've opened bug for this case: ...


0

Read the fine manual for error 2003 at http://dev.mysql.com/doc/refman/5.0/en/access-denied.html


-3

SELECT FLOOR(NUMBER_PAGES_GET/(NUMBER_PAGES_GET+NUMBER_PAGES_READ) * 100) as InnoDB_Buffer_Pool_Hit_Rate FROM information_schema.INNODB_BUFFER_POOL_STATS;


2

It looks like you are getting the Enter password: prompt when connecting to your mysql server from your php server but nothing after that. If so then the mysql user account settings for the root user are probably denying the connection. Have a look at your root mysql user account and make sure the Host field is set to allow the connection. From (MySQL) ...


2

Answer found elsewhere (credit: joshhighland.com) run the update manually but use one of the following example hashes; Hash: e10adc3949ba59abbe56e057f20f883e Password: 123456 Hash: $H$9Ae3Uk.ECdWW5ya13M4ErWhr4c.761/ Password: password e.g. mysql> update phpbb_users set user_password='e10adc3949ba59abbe56e057f20f883e' where username = 'YourUserName'; ...


2

Beyond the shadow of any doubt, I strongly believe it is the InnoDB Storage Engine. It is almost like a living, breathing organism. Here is a Pictorial Representation from Percona's CTO Vadim Tkachenko Please note the InnoDB Buffer Pool. If it has lots of dirty pages (changes to write back to the physical tables) and corresponding index changes (Insert ...


0

The issue is not related to storage engine, the problem might be because few SQL queries are taking too high CPU resource to process for that particular site/application. This might be because the query is using "un-indexed" columns or the query is not efficient. Better to understand the issue enable "slow query" log on the mysql. ...


0

While I have limited experience using MODx, I have over a decade of experience migrating websites. Generally speaking, the two servers could seems similar but can be very different. There are dozens or even hundreds of variable settings that can prevent your old installation from working on the new server. That being said, MODx seems to provide pretty ...


0

I know this is old, but in case anyone needs it: I was getting this with MySQL Server 5.6 on Windows 7 x64. Turns out it loads a my.ini file here: C:\ProgramData\MySQL\MySQL Server 5.6\my.ini Even though MySQL was installed and runs from here: C:\Program Files\MySQL\MySQL Server 5.6 Changing the sql mode in ProgramData ini to the following, then ...


1

The last line in your /etc/postfix/mysql-virtual_email2email.cf should be hosts = 127.0.0.1 instead of host = 127.0.0.1 If we specify 127.0.0.1 postfix should try to connect over TCP but your logline says that postfix cant connect to /var/run/mysqld/mysqld.sock and so it didn't recognize the host = 127.0.0.1 line. Hope that helps.


1

What is the difference between SHOW PROCESSLIST; and SHOW FULL PROCESSLIST; ? SHOW PROCESSLIST; displays the first 100 characters of the INFO column SHOW FULL PROCESSLIST; displays the entire INFO column From the INFORMATION_SCHEMA.PROCESSLIST point-of-view: SHOW PROCESSLIST; effectively runs SELECT ID,USER,HOST,DB,COMMAND,TIME,STATE,LEFT(INFO,100) ...


1

Yes, it is OK. Even if not, it would be MySQL's job to deal with the problem, e.g. by delaying the second until the first is finished.


2

I fixed. Unintentionally but fixed. I reinstall mysql with the following procedure below: sudo apt-get --purge remove mysql-server-5.5 sudo apt-get --reinstall install mysql-server-5.5 After reinstalling everything returned to normal. And all my database are in perfect condition. Without data loss.


1

So I never quite figured out exactly how to trigger the problem, but it had something to do with really large innodb tables in one of our databases. One of them was over 303 million lines long. When I setup some scripts to remove old data every night, the problem went away for good. These really weren't very important tables, and were for the most part only ...


-2

Hi there could be couple of things why its failing, go through a check list. Hope this was helpful 1 Anonymous user ''@'localhost' or ''@'127.0.0.1' http://stackoverflow.com/questions/10299148/mysql-error-1045-28000-access-denied-for-user-billlocalhost-using-passw 2 Causes of Access-Denied Errors, on MYSQL site ...


1

As in the comments beneath your post; I do not see where the mysqld service actually halted correctly, and to reiterate, you will need to forcibly kill each existent mysqld process before attempting to restart the service. Try running ps aux | grep mysql to get the list of running mysql processes and send a kill signal to each using ps kill -9 PID where ...


0

I had problem where telnet 127.0.0.1 9200 gave 503 Server unavailable response, but when I executed /usr/bin/clustercheck as root it showed that everything was fine. With this command I was able to execute clustercheck as user nobody and got real MySQL error to /tmp/cluster.log: sudo -H -u nobody bash -c "/usr/bin/clustercheck clustercheckuser ...


0

mysql_connect("localhost", "root", ""); Well, it's quite obvious what the reason is. PHP really good at some things, but not at directly translating 'localhost' into '127.0.0.1'. You must try that, it will really lower your overall website page loading time, because it holds PHP back from checking your HOSTS file and what not it's doing to get the real IP ...


1

As explained by @Shutupsquare, removing bind-address will make MySQL listen on all interfaces, including IP-address-of-mywebsite.com and loopback IP address 127.0.0.1. If your website reside on the same server of postfix, then it will be useful if you change MySQL parameter of your website so it will be connect to in 127.0.0.1 instead connect to ...


1

This log entry is the key to the most likely issue: 141207 20:50:34 mysqld_safe Number of processes running now: 0 If there is not an extremely verbose block of log messages, including a stack trace, immediately before this line, then MySQL's not actually crashing... the kernel is killing it because another process (such as the web server) is making ...


2

Change your config-file with SQL-query like that: . . . . . password_query= SELECT username as user, \ password \ FROM mailbox \ WHERE username = '%n@%d' \ AND active=1 user_query = SELECT maildir AS userdb_home, \ 150 AS userdb_uid, \ ...


2

In general case innodb_force_recovery mode is supposed to let a user to start InnoDB and dump valuable data. A common belief InnoDB will heal tablespace after enabling innodb_force_recovery. No, it won't. (In some cases you can fix a tablespace dropping particular tables, but that's another story). If you are lucky enough and MySQL starts the next step is ...


0

Use max_allowed_packet beneath [mysqldump] directive. Fixed my problem once. [mysqldump] quick max_allowed_packet = 3G


0

I had the same problem, and I solved it by added a 'restart' param to my ::mysql::server initialization. class { '::mysql::server': override_options => $override_options, restart => true, } This tells the mysql module to restart mysql whenever something changes.


1

You appear to already have MySQL-devel-5.6 and MySQL-server-5.6 installed as per the output from yum - you can either proceed to use those packages, or to get back onto the repo-maintained packages (as you seem to be attempting to do), remove those packages manually before re-trying the installations via yum. If you wish to manually remove the ...


1

Not using official packages. They would attempt to use the same configuration files and data directories, which would result in a crash at best, and data loss at worst. If you really want to do this, try using containers.


0

Try changing the backslashes to forward slashes: source C:/Users/xxx/Documents/Programs/Database/dump.sql; Back- and forward slashes are equivalent in path names in Windows, and the forward slash avoids misinterpretation of the backslash as a quoting character.


0

If your connection string ref's server node name and requires DNS, make sure it is not intermediate slow DNS resolve causing timeout in connection attempt. Use localhost if that is appropriate. Run local DNS if appropriate. Shortcircuit in LMHOSTS file if appropriate. Eliminate need for DNS totally and if appropriate, specify the IP address. ...


1

innodb_buffer_pool_size requires restarting MySQL. Why ? Take a look at Percona's Vadim Tkachenko's Pictorial Representation of InnoDB In the upper left corner, you see the InnoDB Buffer Pool. It has Data and Index Pages for InnoDB Tables and a giant scratch pad for migrating secondary index changes from the Buffer Pool to the Insert Buffer. All those ...


0

I spent over 10 hours on this question and the command that works is running sudo /usr/local/mysql/bin/mysqld_safe --defaults-file="/etc/my.cnf" on the API machine.


3

The OOM killer fired as the system was out of RAM and swap - the mysqld process was chosen as its victim, likely due to having a combination of high RAM use and relatively low activity on its RAM. Either adjust the available buffer pool size to make MariaDB take less RAM and not trigger the OOM killer (which might hurt performance) or give the system more ...


0

4 years later I will answer my own question! It seems at some point MariaDB HQ started offering Yum repos you can install inside CentOS to automate updates :) Here' a general description: https://mariadb.com/kb/en/mariadb/documentation/getting-started/binary-packages/rpm/yum/ Here's a page that lets you generate the Yum config code for your exact ...


0

As people said above, this is the request timeout. You could be under a slowloris attack, if it is the case you are happy to see all those 408 in the logs, it means your server is dropping the attackers, and yes check your timeout setting , check if you have mod_reqtimeout. If your server was not dropping them, it would most probably be down/unreachable. ...


0

Hi @AveryPayne . Thanks for taking the time to read the post. $paramaters['server'] is 'localhost'. Cheers – Fraser The short version is, You Can't Get There From Here. Based on this comment, and the error message, I'd say you have a problem with the type of connection. The socket in the error message is stated as /var/lib/mysql/mysql.sock but you ...



Top 50 recent answers are included