rocketright.blogg.se

1. #Clean install mysql mac os x how to
2. #Clean install mysql mac os x install
3. #Clean install mysql mac os x password

NOTE 1 the log-bin option is enabled by default. Check the contents of these my*.cnf files for the one that's right for you. There is also my-huge.cnf, or my-medium.cnf depending on your hardware setup. Ensure the backups are okay and ready for restore, in case anything goes wrong. If you're running MySQL 5.5 and wish to convert to MariaDB 5.5 (which then allows a higher MariaDB later on), then you can do the following:

#Clean install mysql mac os x install

This also applies to the restores of the databases, even if the backed up tar.gz DBs do not not have any access_hosts listed in the backup.Īs of DirectAdmin 1.57.0, you can install DirectAdmin without MySQL, allowing you to specify a remote box ahead of time: open in new window # Converting from MySQL 5.5 to MariaDB 5.5 it can be any number, any order, out of order, eg: access_host76345834=1.2.3.4 is allowed.Īny database created with these values set will have the listed access_hosts added to their database (eg, 1.2.3.4, 2.3.4.5, 3.4.5.6). the number you use after the access_hostX= value doesn't matter.If you don't have the first one, then the numbered values won't be loaded. the first access_host= entry must already exist.the host= value must be set to some value other than localhost.TO command again, but you change localhost to the IP of your DA server: We'll need to add another access host (ip) to allow the DA server to connect to it.īasically, you just run the "GRANT ALL PRIVILEGES ON. Note that the above guide will only grants da_admin on the "localhost", meaning you have to already be on that remote mysql server to use the account. On a related note, if the remote server is on a LAN IP and the connecting IP to that remote server will not be your server IP (but rather some other IP such as a .x type of IP), then you can use this guide open in new window to specify a default access host instead of the server IP.

#Clean install mysql mac os x password

The username and password you set up have to be set in the /usr/local/directadmin/conf/nf file for DA to use. You can use this guide to set up the da_admin user on your server. The default DA user is da_admin, so staying with that name is a good idea, but not required. The next step is to set up a user that DA can connect to on the remote MySQL server.

#Clean install mysql mac os x how to

I won't go into the detail on how to do this (use Google). DA is not require on this server, as it is just used for MySQL and nothing else. The first step is to install MySQL onto the remote server. It's generally a good idea to do this before you add users.Īlso, MySQL will continue to run on your local DA, so existing databases and scripts should continue to function, however users will not be able to control them through DA. Note that this guide does not transfer any databases over. But in the case of one large database using up the whole server, then you don't have much choice. This shouldn't be needed too often, as usually, you can just move entire user accounts to another server to ease the load.

If you host a large database that can't be split up, and your server doesn't have the resources to handle it, you can set up MySQL to be run on an external server. # Setting up DA to use a remote MySQL server Note that the correct login/password is still required, the Access Host is just another layer of security.Īlso make sure that port 3306 is open in your firewall on the DirectAdmin box, so the remote box can connect.

To allow any IP (if you're unsure of the remote IP, or if it may change). # local-infile=0 in your /etc/my.cnfįor security reasons, it's often a good idea to have: No other my.cnf file should have a user/pass set within it. Of your 2 my.cnf files, only /usr/local/directadmin/conf/my.cnf should have a user/password value. This should not exist as our call to mysqldump will find it, which breaks our calls to mysqldump if it contains a user/password. You shouldn't even have a /etc/mysql directory, as it will conflict with your /etc/my.cnf. It's found atĪnd should not be changed as it's overwritten regularly (based on the nf in the same directory).Īpart from those 2 my.cnf files, you should not have any my.cnf files anywhere else. Which usually does include a files from /etc/my.cnf.d/ directory.ĭirectAdmin does create a secondary my.cnf, but it's only used for the mysqldump calls. # General MariaDB and MySQL # Where is my my.cnf?

Sending outbound email through remote mail server.Autodiscover information for mail clients.