If both of the following conditions are true, you will need to take the extra steps outlined in this document during your supervisor upgrade process:
Only data from Qube schema version 37 (present from 6.9
0 onwards) can be brought forward into Qube 7. If you're upgrading a Qube supervisor from a version prior to 6.9
0, you can upgrade only the schema to version 37; see the second phase of "Step Two: Export MySQL data to .csv"
|Table of Contents|
Make sure that the MySQL server is running, and that you can connect to it using the mysql client, and that your qube table version is at 37.
If you haven't changed the database administrator user and password, you should be able to do the following on a command prompt to confirm that the MySQL server is running:
Linux: /usr/bin/mysql -u root -e 'SELECT * FROM qube.tableversion' Mac: /usr/local/mysql/bin/mysql -u root -e 'SELECT * FROM qube.tableversion' Windows: "C:\Program Files\pfx\qube\mysql\bin\mysql" -u root -e "SELECT * FROM qube.tableversion"
Make sure that the above command works and returns:
+---------+ | version | +---------+ | 37 | +---------+
If you get something less than 37 returned by the above command, it means that your current Qube supervisor version is older than 6.910-20, and that you need to update your MySQL database tables first, before you can upgrade the database schema. To do so:
Download the "
upgrade_supervisor" program suitable for your supervisor platform from http://repo.pipelinefx.com/downloads/pub/db_migration_tools/
On a command prompt, run the
upgrade_supervisor programthat you just downloaded.
- Check that there weren't any critical errors reported by
- Check that the version is now indeed updated to 37, by running the
mysql -u root -e 'SELECT * FROM qube.tableversion'command again
Choose a destination folder on your supervisor for the MySQL csv files. Make sure that your user and the mysql server process both have write permission to this folder and all its parent folders, and that the volume is sufficiently large. Also note that a faster disk, such as an SSD, will help speed up the export/import process.
Tip title On CentOS 7.x and possibly other Linux distros, create a working directory under /opt and do the export while running as the root user
Do NOT use /tmp, /var/tmp (/usr/tmp), or any subdirectories under them. These OSs give the MySQL service its own private /tmp and /var/tmp folders, which prevents the mysqldump command from running correctly. Creating a subdirectory under /root does not work either, nor will a subdirectory in any user's home directory, since non-root users home directories are usually mode 700, so the MariaDB server can't access it.
One approach that doeswork is creating a directory under /opt and opening up the permissions:
sudo mkdir -p /opt/mysql_dump sudo chmod 755 /opt/mysql_dump
Then, install the
export_data_from_mysql.pyscript from the next step into this directory as the root user, and run the export script as root.
- Download the
export_data_from_mysql.pyscript from http://repo.pipelinefx.com/downloads/pub/db_migration_tools/ and copy it into the destination folder.
On a command prompt, go to the destination folder, and run
export_data_from_mysql.py. Running it without any argument will create a subfolder in the current directory named "
qube_mysqldump" and dump all files into it.
You may override the dump subfolder and DB username, password, and mysql install location. Run "
export_data_from_mysql.py -h" to see the list of options.
Sit back. This process can take a long time to complete, depending on how many jobs you have on the system.
Once the process completes, make sure there were no errors reported on the terminal. Also have a look a the dump directory to confirm that there is a subfolder "
qube" and a bunch of subfolders like "
- Take a note of the dump directory location, and proceed to the next step, "Upgrade the Supervisor".