Frequently Asked Questions

The NearlyFreeSpeech.NET FAQ (*)

MySQL (*)

How do I get a MySQL process?

Ok, I have a MySQL process. How do I create a database?

What is the DSN (hostname) I should use to connect to my MySQL database?

What is the difference between a MySQL process and a MySQL database?

If I lose my MySQL admin user password, can you help me get it back?

How do I access my MySQL database process from the ssh server command line?

Can I use ssh port forwarding to access my MySQL database from a remote location?

Where can I find more information on properly creating MySQL users?

What are the default databases present in my MySQL process?

Why do I have to pay for a stopped MySQL process?

When I change my member password, do my MySQL passwords change too?

Why do I get an error "Cannot log in to the MySQL server" when I try to log in to phpMyAdmin?

What does the MySQL Error Can't connect to local MySQL server through socket '/tmp/mysql.sock' (2) mean? (or socket 'please_see_the_faq')

When I try to log in to phpMyAdmin I get the error "the username was not provided." What should I do?

Why shouldn't I use my MySQL admin username from my web site?

What 'Host' value should I use when creating MySQL users?

How can I remove my MySQL process?

How do I enable or disable InnoDB for my MySQL process?

How can I make automatic backups of MySQL?

What username and password do I use to administer my MySQL process?

What does it mean that my MySQL process is "damaged?"

This indicates that you have altered or removed the contents of the "mysql" database of your MySQL process in a way that will prevent your process restarting, or render it unusable after restarting. MySQL processes don't restart very often, so it could be weeks or months before the effects of these actions surface, by which time you will probably have forgotten all about them.

If you catch the problem before your process restarts, you should still be able to connect to it and make a backup of your data.

If you don't catch the problem in time, there is essentially no way to repair it; your MySQL process either won't start anymore or will start but won't be accessible. You'll end up having to delete the process and start over with a new one. If you contact us before you delete the old MySQL process, we may be able to recover some or all of your data and restore it to the new one, but if this is possible and you wish it done, a non-trivial service fee will apply to cover MySQL administrator time.

Keep in mind that while our system does check periodically for this type of damage, it doesn't detect all cases and may not pick it up right away. To keep your MySQL process safe and happy, make sure you always leave the "mysql" database alone.

The "FLUSH PRIVILEGES" SQL command will also cause a running process to immediately fail if it has this type of damage.

How do I upgrade from MariaDB 5.3 to MariaDB 10.x?

Why do newly-created MySQL processes seem so expensive?

How do I enable or disable MySQL logs?