I’ve attempted to run an update again on my kaltura server, but I’ve run into a few issues. Initially, when running /opt/kaltura/bin/kaltura-db-update.sh, the db update fails. When I look in the file /opt/kaltura/app/deployment/sql_updates, I see:
which all seem to be very old updates and have already been completed. Since they were completed, the db-update script fails. This doesn’t seem to be a big deal (the tables appear to be changed already), but I thought it’s worth mentioning.
After performing the next step (/opt/kaltura/bin/kaltura-config-all.sh) with the answer file I used for the original install, the sanity test fails (create partner fails, which prevents dependent tests from running).
Running kaltlog lists these two errors (or similar) over and over:
==> /opt/kaltura/log/batch/dropfoldercontentprocessor-0-2016-08-03.err.log <==
PHP Fatal error: Class ‘KalturaWorkerQueueFilter’ not found in /opt/kaltura/app/batch/batches/KJobHandlerWorker.class.php on line 265
PHP Warning: file_put_contents(/opt/kaltura/app/cache//batch/controls/KAsyncTransformMetadata.0.run): failed to open stream: Permission denied in /opt/kaltura/app/batch/scheduler/KScheduleHelperManager.class.php on line 199
Trying to access the admin console throws this error:
==> /opt/kaltura/log/kaltura_apache_errors_ssl.log <==
[Wed Aug 03 09:12:28.304275 2016] [:error] [pid 20494] [client 22.214.171.124:55331] PHP Fatal error: Class ‘Kaltura_Client_Enum_PermissionName’ not found in /opt/kaltura/app/plugins/admin_console/kaltura_internal_tools/admin/KalturaInternalToolsSystemHelperAction.php on line 26, referer: https://[servername_removed]/start/index.php
I thought perhaps something was wrong with the DB, so I dropped it (/opt/kaltura/bin/kaltura-drop-db.sh) and re-ran the install. However, the same errors persist when running kaltlog.
I’d be very grateful for any help. It seems like there’s a path missing or not getting set. For example, there are a few files that define the KalturaWorkerQueueFilter class, but presumably none are getting included from a missing config somewhere.