Document toolboxDocument toolbox

Vidispine

Upgrading [VC 21.3.1 GEN]

Owned by Andreas Schmidt
Oct 05, 2021
2 min read

Upgrading Vidispine

  1. Install the latest server and transcoder packages.

  2. Use the check command to verify that the configuration file is still valid.

    $ vidispine check
$ vidispine db check

  3. Make sure that the server is stopped.

    $ systemctl stop vidispine

  4. Migrate the database:

    $ vidispine db migrate

    Before migrating you can verify the pending migrations using the --dry-run flag.

    $ vidispine db migrate --dry-run

    The dry-run output is for informational use only. Do not execute any SQL statements in the output directly.

  5. Start all Vidispine services.

  6. Wait for Vidispine to start and then run APIinit to create any new system metadata fields or task definitions.

    $ # wait for 8080 to become available, and then
$ curl -X POST localhost:8080/APIinit

Upgrading to Vidispine 5.0

Because of a change in our internal system for the handling of database migrations, all users MUST upgrade to version 4.17 of Vidispine server and complete the database migration process before attempting to upgrade to Vidispine Server 5.0.

To upgrade to 5.0 from 4.17, just follow the normal upgrade steps.

Solr

The Solr version has been updated from 4.10 to 8.1. The Lucene index written by the previous version is not compatible with that of the newer version. This means that a full re-index is required to rebuild the search index.

The location of the Solr index has changed from /var/lib/vidispine/solr/collection1/ to /var/lib/vidispine/solr/8.x/collection1/ to avoid having Solr read the old index.

After upgrading, the old index can be removed.

ActiveMQ

ActiveMQ has been updated from 5.10 to 5.15. Any installations of ActiveMQ that use JDBC persistence may need to clear the ActiveMQ database tables as the format of the messages in the activemq_msgs table has changed and can not be consumed by the new ActiveMQ version (AMQ-5995).

Another option is to change ActiveMQ to persist data in different tables by setting a table prefix in the activemq.xml. For example:

<persistenceAdapter>
  <jdbcPersistenceAdapter>
    <statements>
      <statements tablePrefix="amq515_"/>
    </statements>
  </jdbcPersistenceAdapter>
</persistenceAdapter>

If KahaDB is used then ActiveMQ should still be able to read the existing transaction log:

INFO  [2019-10-02 07:25:08,843] [1] org.apache.activemq.broker.BrokerService: Using Persistence Adapter: KahaDBPersistenceAdapter[/var/lib/vidispine/activemq]
INFO  [2019-10-02 07:25:09,169] [1] org.apache.activemq.store.kahadb.MessageDatabase: KahaDB is version 6
WARN  [2019-10-02 07:25:09,428] [1] org.apache.activemq.store.kahadb.KahaDBStore: Existing Store uses a different OpenWire version[6] than the version configured[11] reverting to the version used by this store, some newer broker features may not work as expected.
INFO  [2019-10-02 07:25:09,526] [1] org.apache.activemq.store.kahadb.plist.PListStoreImpl: PListStore:[/var/lib/vidispine/server/activemq-data/localhost/tmp_storage] started