Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

Upgrade Procedure

Warning:

If you are upgrading from 2.34, please make sure you use the special upgrade procedure described in the document Upgrading Control Center from Version 2.34.

Below are general instructions for upgrading Control Center. Note that for specific releases, additional actions may be required; separate instructions are then given in each case in what follows.

Be sure to refer to the current Paragon Active Assurance Installation Guide.

  • Disable the apache2 and netrounds-callexecuter services completely:

  • Stop all Paragon Active Assurance services:

  • Make backups according to the Operations Guide, chapter Backing Up Product Data, starting with the section "Backing Up the PostgreSQL Database".

  • Verify the integrity of the tarball containing the new Control Center version:

  • Unpack the Control Center tarball:

  • Install new Control Center packages:

    You will be asked how to proceed with the configuration files. In most cases you will want to keep your old settings. We recommend that you inspect the difference between your old configuration and the new one using the "D" choice.

    New optional and updated settings may be available in the example configuration files provided in the packages. Feel free to review these and add new options as appropriate for your installation.

    Warning:

    For the file /etc/netrounds/netrounds.conf you need to choose "Y" in order to pick up the mandatory new SPEEDTEST_ADDRESS setting. Therefore, if you have made other modifications to this file, be sure to first copy those and reinsert them afterwards. As a side note, we may mention that the STRICT_TRANSPORT_SECURITY_HEADER setting has been removed.

    Warning:

    For the Apache configuration files found in

    you need to choose "Y", which is the "package maintainer's version".

    If you have installed proper SSL certificates (as recommended) instead of the default snakeoil ones, you will have to modify the file again to point to the correct path in the SSLCertificateFile and SSLCertificateKeyFile settings after the Debian package installation has completed. See the Installation Guide, chapter Service Configuration, section "SSL Certificate Configuration".

  • Run the database migration:

    Warning:

    If you have changed the database password from the default, make sure you also change this in the db-password setting in the /etc/netrounds/plugin.yaml file before running ncc migrate. Otherwise, the command will fail.

    Note:

    This is a sensitive command, and care should be taken when executing it on a remote machine. In such a scenario it is strongly recommended that you use a program like screen (generally installed by default on popular Linux distributions) or tmux (run sudo apt-get install tmux to install) so that the migrate command will continue running even if the ssh session breaks.

    Note:

    This command takes considerable time to execute.

  • Install the new Test Agent repository and plugins.

    The plugins are used by Test Agent Applications.

  • Enable the apache2, kafka, and netrounds-callexecuter services:

  • Start all Paragon Active Assurance services:

    Note:

    You must do this to get the services up and running again after the upgrade.

  • To activate the new configuration, you also need to run:

  • Check that the system is up and running with the commands

  • Log in to the Control Center GUI and go to the Test Agents view. Next to each Test Agent for which an upgrade is available, an up-arrow icon appears. Click that icon to go ahead with the upgrade.

Troubleshooting

Password Authentication Failed For User

If the ncc migrate command fails with an error message

you must update the variable db-password in the /etc/netrounds/plugin.yaml file as explained in the warning above. Edit this file and then rerun ncc migrate.

Target WSGI Script Not Found

If you accidentally selected "N" for the Apache configuration files (see this step above) and got an error message like the one below

run the following commands to get back on track:

This overwrites the old configuration with the new one in the updated package.

Again, if you have installed proper SSL certificates (as recommended) instead of the default snakeoil ones, you will have to modify the file again to point to the correct path in the SSLCertificateFile and SSLCertificateKeyFile settings after the Debian package installation has completed. See the Installation Guide, chapter Service Configuration, section "SSL Certificate Configuration".