Tag Info

New answers tagged

1

Our DBA uninstalled mysql version 5.0.95 instead of just upgrading to 5.5.39. The uninstall backed up the /etc/my.cnf to /etc/my.cnf.rpmsave then removed it, and this prevented MySQL from starting up properly: 140902 15:00:57 [ERROR] Plugin 'InnoDB' init function returned error. 140902 15:00:57 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE ...


0

You can see which vulnerabilities where discovered for each version of MySQL at the CVE Database. See if your distribution has patched them already and asses your risk of using the 5.1 available to you versus some other version you might be considering. It's very likely the latest version of 5.1 has received considerable more attention than the latest ...


1

What operating system are they using? Most likely they use the versions of MySQL and Apache that are in their operating system's package repos, in which case they are on old versions of the software but are getting security fixes backported (assuming they're installing those updates). But it's definitely not a good sign that they can't give you a good ...


3

MySQL 5.1 is the currently supported and safe version on e.g. RHEL/CentOS 6 and as long as there is no project-specific reason to upgrade, no hoster on this platforms will do this. The same is true for Apache. Since RedHat etc. are backporting fixes into their versions, they are not less secure than newer releases. Lastly, if you had attacks, you need to ...


1

Here is your problem: InnoDB: mmap(137363456 bytes) failed; errno 12 That errno means you ran out of memory when MySQL attempted to start up. Either reduce the amount of memory MySQL uses, or give the machine more RAM.


0

Use the replicate-do-db setting, and note that replication is not the same as a backup... TRUNCATE TABLE very_important or UPDATE credit_cards SET number='whoops' will replicate across and delete everything on the slave as well.


3

To reliably copy database tables, the database has to be stopped (not just flushed). If it is not, a consistent copy is not guaranteed, but is it impossible to say if and what data might be lost. That said, if the database was not active and some time passed since the last write operation before you started the copy, it's likely the cache has been committed ...


1

errno 13 is Permission denied. Which means the database files exist, but MySQL doesn't have permission to access them. To resolve the problem, fix the permissions and SELinux contexts.


0

In phpMyAdmin , in Settings tab, you can try checking the following values: Settings -> SQL Queries -> Ignore multiple statement errors If you are using CSV format: Settings -> Import -> CSV -> Do not abort on INSERT error If you are using SQL format: Settings -> Export -> SQL -> Use ignore inserts you use my answer here with details


0

Is this a new mysql server or an existing one? It appears to be missing it's data folder. There is also no data folder defined in the configuration, so it'll use the default. If you have not yet created a MySQL data directory, you need to create it with the command: mysql_install_db


1

I have configured postfix+Dovecot+MySQL+postfixAdmin+roundcub+ClamAV+amavis.. on CentOS. When I try to use postfixAdmin to create virtual domain and users, it is so slow, then the following error occurs "Invalid query: MySQL server has gone away". Steps to attempt: Change /etc/my.cnf argument into wait_timeout=28800 (it is default) Disable name resolve ...


0

why are the queries doing "single page reads at all? Because the pages need to be read into the buffer pool at least once before they are available to the engine. Looking at your numbers the 263,500 reads would account to 263,500 pages x 16 KB/page = 4,216,000 KB read which is not even as much as your database's size. Also, compared to your ...


0

Have you tried: mysql --user=root -p and then when asked for the password, just pressing enter? Sorry it this is obvious and you have, thought it worth a mention just in case.


2

Try running mysql_secure_installation - improve MySQL installation security, as Michael mention, it almost sounds like you already have mysql database with something other than fresh install. You can also try stop mariadb.service delete mysql database and then try to give it another try with mysql_install_db - initialize MySQL data directory.


0

The recommended upgrade procedure appears to be to: back-up the existing database upgrade cacti then let cacti upgrade the existing database schema, rather than creating a new database and trying for a manual data migration.


0

I just had the same problem. In my case, when I set the SLAVE server, I just imported my application database dump, thus users created at default MySQL database are not on my SLAVE db server, then, the GRANT statement fails. The way I see it, now either I create the users by hand, or start from scratch importing also the default database to my SLAVE server. ...


3

I found this article which seems to address the issue pretty well http://ximunix.blogspot.co.uk/2014/01/howto-cleanup-puppet-reports-and-db.html posted by Ximena Cardinali The short story is start deleting reports in small batches and then reclaim the space from MySQL HOWTO Cleanup Puppet Reports and DB If the database for Puppet Dashboard is using ...


0

At first - i don't think some other app could be more safety then mysqldump. At second - i know next alternatives to mysqldump: mydumper Percona XtraBackup sypex dumper (work from command line too - recommended)


2

If you use additional repositories for non-standard CentOS packages and want to use newer releases of some components you might benefit from reading their announcements too: Update 2013-07-21 – A new package “php54w-mysqlnd” has been added as an alternative to “php54w-mysql”. This will instead provide mysql, mysqli, and pdo_mysql built against the PHP ...


0

My solution to the problem at the end is: I remove the LAMP stack with this command: sudo apt-get remove apache2 apache2-mpm-prefork apache2-utils apache2.2-common libapache2-mod-php5 libapr1 libaprutil1 libdbd-mysql-perl libdbi-perl libmysqlclient15off libnet-daemon-perl libplrpc-perl libpq5 mysql-client-5.0 mysql-common mysql-server mysql-server-5.0 ...


2

Simple - take a snapshot of your current RDS instance and then restore that snapshot to a new instance in your VPC.


0

Fresh install of xampp, will wipe config file settings. The password will not be recognized To fix: http://localhost/security/index.php update password


1

Your InnoDB database buffer pool is about 6,6 gigabytes. When inserting data to the database, InnoDB engine first adds the data to the buffer pool, and then writes it to the disk. So, what happened here is that when the buffer pool got full, InnoDB started to write its contents to the disk. Therefore the insert performance dropped. Now, when you stopped ...


0

We had the same issue - seems you need to wait for mysql to startup (or at least get the start the listeners). Otherwise you'll get the 2013 issue that you got. We just added sleep 60 which is a fairly inelegant hack but seems to work. Would love to hear a better workaround.


2

Try to install php-mysql if it not there yum install php-mysql -y It looks like you're using a 3rd-party repo to provide PHP 5.4, and the package php54w-common from that repo is conflicting with php-mysql (which is presumably coming from epel), which is expecting the default CentOS version of php-common. Your 3rd-party PHP provider might provide their ...


0

this warning means that your php-mysql module is an older version. you need to update it. For example in RHEL/Fedora yum update php-mysql Then, do not forget to restary web server.


1

Since you're dealing with Drupal many parts of your website configuration will not just live in code. This has been solved many times before, but I don't think it has ever been solved once and for all. There will be pain. You can ease this pain by ensuring that developers are putting as much as possible in code, through Features and custom Drupal modules, ...


1

First step: reinstall Apache. Second step: Take a look on your Apache settings, and make sure that the line LoadModule php5_module /usr/lib/apache2/modules/libphp5.so points to the correct path (/usr/lib/apache2/modules/libphp5.so on my case). Use find to, well, find where PHP module is: find /usr -name libphp5.so Installing things from PPA generally ...


1

Your mysqld is definitely running MySQL 5.5.39 to make sure please run mysqld --version | awk '{print $3}' PHPMyadmin might be using a 5.1.73 client You could also login to mysql from the command line and run this mysql> status You will get output resembling this /usr/bin/mysql Ver 14.14 Distrib 5.5.30, for Linux (x86_64) using readline 5.1 ...


0

You don't actually have MySQL's yum repository installed. As the directions advised you, you need to do that first.


1

solved the whole thing. original problem was the numflock in openvz. the error after i increased the numflock where based on an abandoned file in the mysql data directory. i drop the table, deleted the remaining files from the table and then it worked.


0

It is absolutely significant that last line contain ONLY "EOF\n". Single space symbol at the end of the line can make the marker different from one used at first line. In your case just add the empty string after the "EOF" line. It is the good habit to add comment-line to the last line of code. /usr/bin/mysql -u username -ppassword -h localhost database ...


1

For memory tables this is normal behavior. With InnoDB tables, this is a known bug and have been for years. See http://bugs.mysql.com/bug.php?id=14374 http://bugs.mysql.com/bug.php?id=69689


0

When you set up a CMS using its Install page, it wants this information to know where your website lives, and what to call it - So all links it creates on your Backend are pointing in the right place. So if your website is example.ddns.net then that will be your hostname on your CMS as well as in IIS. Your IP address in IIS will be your local IP address ...


0

I don't think this is a memory leak. It could simply be that without large pages your memory usage hit an upper bounds (ceiling) which was why memory usage looks flat. After switching to large pages MySQL may have simply been able to better make use of the available memory. The system isn't hitting swap. I'd say closely monitor and stop flushing tables.


0

You can try to find the database configuration xml. Copied from https://www.igniterealtime.org/builds/openfire/docs/latest/documentation/db-integration-guide.html Configuration Stop Openfire. Edit conf/openfire.xml in your Openfire installation folder as described below using your favorite editor. Restart Openfire. Database Connection Settings ...


0

I used: # Generate a CA key and certificate with SHA1 digest openssl genrsa 2048 > ca-key.pem; openssl req -sha1 -new -x509 -nodes -days 3650 -key ca-key.pem > ca-cert.pem; # Create server key and certficate with SHA1 digest, sign it and convert # the RSA key from PKCS #8 (OpenSSL 1.0 and newer) to the old PKCS #1 format openssl req -sha1 -newkey ...


0

This has been somewhat useful to me: https://sourceforge.net/projects/win-mysql-bench/


0

I found my mistake. GRANT ALL ON user.* << this should be diddata. I noticed it when I went to change the database name in the question.


5

Rsyslog can group multiline log message into a single message via imfile module, however only following three read modes are supported: Line based (default) - each line is a new message. Paragraph - there is a blank line between log messages. Indented - new log messages start at the beginning of a line. If a line starts with a space it is part of the log ...


0

It's because if the DB is not on the same server as the frontend you have to do a round trip for each query (potentially more, depending on the size of the answer). It can easily take up to 1 ms to ping another server in the same datacenter. Much less if the two servers are on the same rack, but 1 ms is a good rule of thumb. That means that for ~300 small ...


2

There is a program mysqlcheck which ships with mysql that allows you to repair tables, if you can start mysql and your tables are corrupt. It doesn't sound like that's the case. There is another program myisamchk, which allows you to ensure the integrity of your MyISAM tables (you weren't using innodb for this, were you?) as long as you have the files ...


0

after shutting down mysql service (using mysqladmin -h127.0.0.1 -uroot -p shutdown) and start it again, I could not connect to that server from external clients I looked up the problem and I found this question, applied the answer, so that the problem is solved. that was because of waste DNS reverse query of mysqld.


0

It's pretty difficult to say what is the best backup strategy - it all depends on the value of your data, and the penalty you will pay if you lose last X hours. You have correctly identified a problem with incrementals - if you lose one, you lose everything after that one. Another problem is if the full gets corrupted, you have lost everything, period. ...


0

OK i resolved the issue. Culprit was setting my /etc/pw.conf umask from 022 to 007 (trying to make it a bit more secure) which resulted in creating basejail's /usr directory with 750 permissions instead of 755 so offending /usr/sbin/daemon couldn't get reached from jail. Immediately after rebooting the jail service started and works as it supposed to. I ...


-1

You'll need to add the localhost user separately. You can do it in one command (rather than two). GRANT ALL on database.* to 'user'@'localhost' identified by 'paswword'; If you want to add the user so it can connect from anywhere (less secure), use this: GRANT ALL on database.* to 'user'@'%' identified by 'password';


2

The error message indicates that you're not connecting to the remote MySQL at all, but to localhost. Make sure you connect to the remote server.


0

The error message: IOError: failed to write data generally indicates that the HTTP client communicating with your web site is dropping the connection. One would normally only see it if you are using mod_wsgi embedded mode. It is usually a transient issue and should not be a permanent issue. If it is a permanent issue and your site is no longer accepting ...


1

This is legit, as this is a user that gets created by default. It's a fairly dumb default and you should delete the user.


1

There are several things you can do: Check dmesg output for segmentation faults (maybe its segfaulting) Do minutely dumps of mysql and unix process lists Graph memory, disk, buffer pool usage and any other metric you can think of Use sysdig to try and catch whatever is going wrong



Top 50 recent answers are included