Upgrade from CA 1.3

twheel

I have inherited an installation of CA 1.3 running on Ubuntu 14. I would like to upgrade to the current version of CA and move to an Alma Linux 9 server.

Questions:

Is this possible?
Is there documentation for upgrading such an old version? The GitHub page says “To update from a version 1.6.x or older installation, you must first update to version 1.7, then follow the 1.7 update instructions.” However, I haven’t found instructions for updating to 1.7.
Are there issues moving from a debian-based distro to a RedHat-based one?
Would it be possible to port the files and data into a fresh install instead of upgrading the old machine?

seth

If you install the current 2.0.x version and try to run it with the 1.3 database it will prompt you to run the command-line caUtils update-from-1-7 command. This should be able to take it from 1.3 all the way to 2.0, although it'll take a bit of time.

We've recently updated a group of systems running 1.0 (from 2010) this way without issue. Your mileage may vary though.

twheel

seth Thanks, I’ll give it a shot.

twheel

Running caUtils update-from-1-7 gives this error:
PHP Fatal error: Uncaught DatabaseException: Table 'db_name.ca_search_indexing_queue' doesn't exist in /path/to/app/lib/Db/mysqli.php:358

seth

I'd try running caUtils update-database-schema and see if that gets the database up-to-date. If it does then you'll need to subsequently reindex everything using caUtils rebuild-search-index.

The update-from-1-7 command was only tested with 1.7.x systems (as the name would imply), although I've managed to use it with 1.6 systems as well. We've not seen a 1.3 system in a very log time, so we didn't test it at all with that.

twheel

Yeah, I can imagine!

Here’s the result of rebuild-search-index:

PHP Fatal error: Uncaught DatabaseException: Can't create table db_name.ca_editor_uis_x_roles (errno: 150 "Foreign key constraint is incorrectly formed") in /path/to/app/lib/Db/mysqli.php:358

twheel

Is there a way to update from 1.3 to 1.7?

seth

Yes. I've updated from everything going back to 0.9 => 2.0 in one shot automatically. First thing is to run update-database-schema. If that doesn't work then you probably have something wrong with the 1.3 database. In that case we can help you sort it out.

twheel

Here is the result of update-database-schema:

Can't create table db_name.ca_editor_uis_x_roles (errno: 150 "Foreign key constraint is incorrectly formed")

seth

What version of MySQL are you running?

twheel

Server version: 10.6.23-MariaDB-log MariaDB Server

seth

I would try opening up support/sql/migrations/124.sql and changing this line:

role_id int unsigned not null references ca_user_roles(role_id),

role_id smallint unsigned not null references ca_user_roles(role_id),

then try updating again. (In other words change "int" to "smallint"). There will be two lines in the file that need to be changed. MariaDB 10.6 cares about this apparently.

twheel

Getting somewhere! First I got

Couldn't load configured search engine plugin. Check your application configuration and make sure 'search_engine_plugin' directive is set properly.

I checked app/conf/local/app.conf and search_engine_plugin was set to SqlSearch. I changed it to SqlSearch2, dropped and re-added the database and ran update-database-schema again and got this result: Unknown column 'cme.deleted' in 'WHERE' in app/lib/Db/mysqli.php:358

Stack trace:
#0 app/lib/Db/DbStatement.php(150): Db_mysqli->execute()
#1 app/lib/Db.php(261): DbStatement->executeWithParamsAsArray()
#2 app/models/ca_metadata_elements.php(908): Db->query()
#3 app/models/ca_metadata_elements.php(783): ca_metadata_elements::getElementsAsList()
#4 app/lib/Plugins/SearchEngine/SqlSearch2.php(161): ca_metadata_elements::getRootElementsAsList()
#5 app/lib/Search/SearchBase.php(84): WLPlugSearchEngineSqlSearch2->construct()
#6 app/lib/Search/SearchBase.php(60): SearchBase::newSearchEngine()
#7 app/lib/Search/SearchIndexer.php(80): SearchBase->construct()
#8 app/lib/BaseModel.php(3457): SearchIndexer->__construct()
#9 app/lib/BaseModel.php(3435): BaseModel->getSearchIndexer()
#10 app/lib/BaseModelWithAttributes.php(865): BaseModel->doSearchIndexing()
#11 app/lib/BundlableLabelableBaseModelWithAttributes.php(259): BaseModelWithAttributes->insert()
#12 app/models/ca_editor_uis.php(276): BundlableLabelableBaseModelWithAttributes->insert()
#13 support/sql/migrations/VersionUpdate137.php(72): ca_editor_uis->insert()
#14 app/lib/System/Updater.php(72): VersionUpdate137->addMetadataAlertsEditor()
#15 app/lib/Utils/CLIUtils/Migration.php(163): System\Updater::performDatabaseSchemaUpdate()
#16 support/bin/caUtils(171): CLIUtils::update_database_schema()
#17 {main}

twheel

Do you have any suggestions about how to handle the "unknown column 'cme.deleted'" error?

monica

twheel you might need to try moving all the files out of app/conf/local while you do the upgrade, then put them back afterwards one file at a time, comparing the settings of each with those files in app/conf

The cme.deleted refers to ca_metadata_elements.deleted which isn’t added until migration 174, this is stopping on migration 137

twheel

monica Thanks for the suggestion. I moved all the files out of app/conf/local/ but still got the same error. I also tried downloading providence-2.0.9.zip again and starting from that, with only setup.php and support/sql/migrations/124.sql changed but still got the "unknown column 'cme.deleted'" error.

monica

twheel if I was facing the same, I would upgrade to 1.7 first, then to 2.0.

There is a function being called in migration 137 that was changed in migration 174 (version 2) and is causing this error.

Version 1.7.17 https://github.com/collectiveaccess/providence/releases/tag/1.7.17

twheel

monica How do I upgrade to 1.7 first? I found a reference to doing that on the GitHub page, but I couldn’t find the actual instructions.

Do I install that release and then run caUtils update-database-schema?

monica

twheel yes, put the 1.7 code into place and run the update.

twheel

It worked! Thank you so much!