Changes between Version 1 and Version 2 of proxysql

Timestamp:

Dec 12, 2022, 2:31:44 PM (3 years ago)

Author:

Jamie McClelland

Comment:

--

proxysql

@@ -26 +26 @@
 
 5. When complete, check the ProxySQL database for any remaining local database users: `mysql -e "SELECT * FROM mysql_users WHERE default_hostgroup = 999" main`
+
+== Trouble Shooting ==
+
+You can login to the local MySQL instance via: `mysql --defaults-file=/root/.my.legacy.cnf`.
+
+You can manually re-load the MySQL users into the proxysql server by running (from the mosh, as root): `proxysql-load`
+
+You can test access to the database servers for a given user with:
+
+1. Local MySQL access: `mysql -u <username> -p --port 3307`
+2. Network MySQL access: `mysql -u <username> -p --host pachamama.mayfirst.cx` (the .cx domain signals the use of our internal, private IP range)
+
+You can login to the ProxySQL instance with:
+
+`mysql`
+
+Use the `main` database and peruse the `mysql_users` table to see which users should be configured to use which backend MySQL servers. The `default_hostgroup` of 999 is the localhost. `default_hostgroup` 1 is lumumba and 2 is pachamama.
+
+== Post Transition ==
+
+When the transition is complete:
+
+ * Remove the `/root/.my.legacy.cnf` file. This file signals that we are in a transition period.
+ * Remove `transition => ture` from the puppet file.
+ * Add `mysql => 'n'` to the `m_mosh` definition in the puppet file to prevent puppet from trying to re-install MySQL
+ * Purge `mariadb-server` from the host
+ * Delete `/var/lib/mysql/`