Template:OXLoadBalancingClustering Database - Revision history

Khgras: /* Configuration */

2021-09-16T09:03:32Z

Configuration

← Older revision		Revision as of 09:03, 16 September 2021
Line 54:		Line 54:
	Run <code>mysql_secure_installation</code> for a "secure by default" installation:		Run <code>mysql_secure_installation</code> for a "secure by default" installation:

	~~mysql_secure_installation~~		mariadb-secure-installation

	That tool will ask for the current root password (which is empty by default) and subsequently questions like:		That tool will ask for the current root password (which is empty by default) and subsequently questions like:

Malasa: typo ist

2019-10-08T19:01:06Z

typo ist

← Older revision		Revision as of 19:01, 8 October 2019
Line 15:		Line 15:
	=== Installation ===		=== Installation ===

	Note: the following list ~~ist~~ not an exclusive list or authorative statement about supported MySQL flavors / versions. Please consult the official support / system requirements statement.		Note: the following list is not an exclusive list or authorative statement about supported MySQL flavors / versions. Please consult the official support / system requirements statement.

	Please follow the upstream docs for your preferred flavor to get the software installed on your system.		Please follow the upstream docs for your preferred flavor to get the software installed on your system.

Dominik.epple: /* First node (continued) */

2018-09-27T14:25:22Z

First node (continued)

← Older revision		Revision as of 14:25, 27 September 2018
Line 207:		Line 207:
	Only applicable if you used <code>galera_new_cluster</code> before rather than the service script: In order to get the systemctl status consistent, restart the service on the first node:		Only applicable if you used <code>galera_new_cluster</code> before rather than the service script: In order to get the systemctl status consistent, restart the service on the first node:

	# mariadb 10.1: restart the service so that the systemctl status is consistent		# mariadb 10.1, 10.2: restart the service so that the systemctl status is consistent
	mysqladmin shutdown		mysqladmin shutdown
	service mysql bootstrap		service mysql bootstrap

Dominik.epple: /* First node */

2018-09-27T14:24:56Z

First node

← Older revision		Revision as of 14:24, 27 September 2018
Line 186:		Line 186:
	-- percona 5.6, mariadb 10.0		-- percona 5.6, mariadb 10.0
	GRANT RELOAD, LOCK TABLES, REPLICATION CLIENT ON . TO 'sstuser'@'localhost';		GRANT RELOAD, LOCK TABLES, REPLICATION CLIENT ON . TO 'sstuser'@'localhost';
	-- percona 5.7, mariadb 10.1		-- percona 5.7, mariadb 10.1, 10.2
	GRANT PROCESS, RELOAD, LOCK TABLES, REPLICATION CLIENT ON . TO 'sstuser'@'localhost';		GRANT PROCESS, RELOAD, LOCK TABLES, REPLICATION CLIENT ON . TO 'sstuser'@'localhost';
	FLUSH PRIVILEGES;		FLUSH PRIVILEGES;
Line 192:		Line 192:
	(Debian specific note: MariaDB provided startup scripts use the distro's mechanism of verifying startup/shutdown using a system user, so we create that as well:		(Debian specific note: MariaDB provided startup scripts use the distro's mechanism of verifying startup/shutdown using a system user, so we create that as well:

	# mariadb 10.0, 10.1		# mariadb 10.0, 10.1, 10.2
	GRANT ALL PRIVILEGES ON . TO "debian-sys-maint"@"localhost" IDENTIFIED BY "adBexthTsI5TaEps";		GRANT ALL PRIVILEGES ON . TO "debian-sys-maint"@"localhost" IDENTIFIED BY "adBexthTsI5TaEps";

Dominik.epple: /* First node */

2018-09-27T13:48:22Z

First node

← Older revision		Revision as of 13:48, 27 September 2018
Line 168:		Line 168:
	# mariadb 10.0		# mariadb 10.0
	service mysql bootstrap		service mysql bootstrap
	# mariadb 10.1~~: service mysql bootstrap seems to be broken~~, ~~does not pass the necessary options to mysqld~~		# mariadb 10.1, 10.2
	galera_new_cluster		galera_new_cluster

Dominik.epple: /* Configuration */

2018-09-27T13:35:03Z

Configuration

← Older revision		Revision as of 13:35, 27 September 2018
Line 124:		Line 124:
	Galera-specific MySQL configuration advise is included in our main [[My.cnf\|MySQL configuration article]]. Please consult that page for configuration information.		Galera-specific MySQL configuration advise is included in our main [[My.cnf\|MySQL configuration article]]. Please consult that page for configuration information.

	That page suggests a setup were we add three custom config files to <code>/etc/mysql/ox.conf.d/</~~pre~~>: <code>ox.cnf</code> for general tuning/sizing, <code>wsrep.cnf</code> for clusterwide galera configuration, and <code>host.cnf</code> for host-specific settings.		That page suggests a setup were we add three custom config files to <code>/etc/mysql/ox.conf.d/</code>: <code>ox.cnf</code> for general tuning/sizing, <code>wsrep.cnf</code> for clusterwide galera configuration, and <code>host.cnf</code> for host-specific settings.

	Adjust the general settings and tunings in <code>ox.cnf</code> according to your sizing etc.		Adjust the general settings and tunings in <code>ox.cnf</code> according to your sizing etc.

Dominik.epple: /* Configuration */

2018-09-06T13:50:40Z

Configuration

← Older revision		Revision as of 13:50, 6 September 2018
Line 351:		Line 351:
	# MariaDB 10.0, 10.1		# MariaDB 10.0, 10.1
	mysql_install_db		mysql_install_db

			# MariaDB 10.2
			mysql_install_db --user=mysql

	# Oracle 5.6		# Oracle 5.6

Dominik.epple: /* Configuration */

2018-09-06T13:50:17Z

Configuration

← Older revision		Revision as of 13:50, 6 September 2018
Line 147:		Line 147:
	# mariadb 10.0 and 10.1		# mariadb 10.0 and 10.1
	mysql_install_db		mysql_install_db
			# mariadb 10.2
			mysql_install_db --user=mysql
	# percona 5.6		# percona 5.6
	mysqld --user=mysql		mysqld --user=mysql

Dominik.epple: /* Configuration */

2018-09-06T13:49:46Z

Configuration

← Older revision		Revision as of 13:49, 6 September 2018
Line 39:		Line 39:
	# mariadb		# mariadb
	mysql_install_db		mysql_install_db
			# mariadb 10.2
			mysql_install_db --user=mysql
	# oracle 5.6		# oracle 5.6
	mysql_install_db -u mysql		mysql_install_db -u mysql

Dominik.epple: /* Configuration */

2018-06-06T14:20:19Z

Configuration

← Older revision		Revision as of 14:20, 6 June 2018
Line 46:		Line 46:
	(Don't be worried about the <code>insecure</code>, it just means we set the db root pw in the next steps.)		(Don't be worried about the <code>insecure</code>, it just means we set the db root pw in the next steps.)

	Start the service, and ~~run <code>mysql_secure_installation</code> for a "secure by default" installation:~~		Start the service. The actual command depends on your OS and on the MySQL flavor.

	service mysql start		service mysql start

			Run <code>mysql_secure_installation</code> for a "secure by default" installation:

	mysql_secure_installation		mysql_secure_installation

	~~Make sure~~ the ~~service~~ is ~~enabled~~ by the ~~OS's init system~~.		That tool will ask for the current root password (which is empty by default) and subsequently questions like:

			Change the root password? [Y/n]
			Remove anonymous users? [Y/n]
			Disallow root login remotely? [Y/n]
			Remove test database and access to it? [Y/n]
			Reload privilege tables now? [Y/n]

			You should answer all these questions with "yes".

			Configure a strong password for the MySQL <code>root</code> user.

	The further steps in this guide omit <code>-u -p</code> arguments to the MySQL client. Rather than passing them on the command line [https://dev.mysql.com/doc/refman/5.7/en/password-security-user.html] it is recommended to place the credentials in a file like <code>/root/.my.cnf</code> like		The further steps in this guide omit <code>-u -p</code> arguments to the MySQL client. Rather than passing them on the command line [https://dev.mysql.com/doc/refman/5.7/en/password-security-user.html] it is recommended to place the credentials in a file like <code>/root/.my.cnf</code> like
Line 58:		Line 71:
	user=root		user=root
	password=wip9Phae3Beijeed		password=wip9Phae3Beijeed

			Make sure the service is enabled by the OS's init system. The actual command depends on your OS and on the MySQL flavor.

			systemctl enable mysql.service

	You should now be able to restore your previously taken backup.		You should now be able to restore your previously taken backup.