Question about the correct way to upgrade Kaltura on CentOS

Hello all,
I’m very new in Kaltura and recently had been succeeded deploying Kaltura cluster, version 10.13.0
Now I need to upgrade to version 10.17.0 but I couldn’t find a correct way to upgrade.

In the guide mentioned here: https://github.com/kaltura/platform-install-packages/blob/Jupiter-10.17.0/doc/rpm-cluster-deployment-instructions.md#upgrade-kaltura
The first step is to upgrade database using command:

## This operates on the DB and hence only needs to be done one. It requires the kaltura-base package and so must be run on a node that has it installed.
# /opt/kaltura/bin/kaltura-db-update.sh

But when I did this command it doesn’t upgrade the database, instead it only do the old database. Below is command output after I added echo command into the update.sh file:

[root@batch ~]# /opt/kaltura/bin/kaltura-db-update.sh
10.90.151.147 /opt/kaltura/app/deployment/updates/sql/2014_01_19_category_entry_add_privacy_context.sql
10.90.151.147 /opt/kaltura/app/deployment/updates/sql/2013_10_22_add_drm_policy_table.sql
10.90.151.147 /opt/kaltura/app/deployment/updates/sql/2014_03_04_update_drm_device_table.sql
10.90.151.147 /opt/kaltura/app/deployment/updates/sql/2014_03_20_add_root_id_batch_job_lock.sql
10.90.151.147 /opt/kaltura/app/deployment/updates/sql/2014_01_22_create_delivery_table.sql

It can be seen that it only re-insert the old database, and no upgrade done.

Next command is:

# kaltura-base-config.sh [/path/to/ans/file]
# kaltura-front-config.sh [/path/to/ans/file]

But this also doesn’t change anything…

So, if anyone could help, what is the correct step to upgrade Kaltura? Do I have to run yum install again from scratch?

Regards,
Arofat

Hello,

You should first:

yum clean all
yum update kaltura-release
yum clean all
yum update "*kaltura*"

Then do the rest.

Thank you for your reply, Jess.

Should I also insert the filenames in /opt/kaltura/app/deployment/updates/sql into /opt/kaltura/app/deployment/sql_updates ?

Because when I check sql_updates file, it only contains old “.sql” file list.

[root@batch deployment]# mv sql_updates.done sql_updates
[root@batch deployment]# /opt/kaltura/bin/kaltura-db-update.sh
10.90.151.147 /opt/kaltura/app/deployment/updates/sql/2014_01_19_category_entry_add_privacy_context.sql
10.90.151.147 /opt/kaltura/app/deployment/updates/sql/2013_10_22_add_drm_policy_table.sql
10.90.151.147 /opt/kaltura/app/deployment/updates/sql/2014_03_04_update_drm_device_table.sql
10.90.151.147 /opt/kaltura/app/deployment/updates/sql/2014_03_20_add_root_id_batch_job_lock.sql
10.90.151.147 /opt/kaltura/app/deployment/updates/sql/2014_01_22_create_delivery_table.sql
Manual DB updates finished with RC 0
[root@batch deployment]# ls base
scripts sql
[root@batch deployment]# ls updates
create_version_mng_table.sql scripts sql update.php
[root@batch deployment]# ls updates/sql
2013_10_01_add_drm_profile_table.sql 2014_07_01_activate_delivery_profiles.sql
2013_10_17_create_media_server_table.sql 2014_07_27_delivery_profile_default_false.sql
2013_10_22_add_drm_policy_table.sql 2014_08_04_create_play_partner.sql
2013_10_29_add_type_column_to_conversion_profile_table.sql 2014_09_02_add_session_type_invalid_session.sql
2013_11_06_add_partner_tags_column_to_ui_conf_table.sql 2014_11_02_add_max_total_count_allowed_column_to_scheduled_task_table.sql
2013_11_07_file_asset_table.sql 2014_11_11_set_thumb_cue_point_default_sub_type.sql
2013_11_18_create_media_partner_permissions.sql 2014_11_20_business_process_server.sql
2013_12_10_add_drm_device_table.sql 2014_11_27_alter_kuser_picture_size.sql
2013_12_19_entry_add_last_played_at.sql 2014_14_07_permission_getcurrentpermissions_remove_widget_permission.sql
2013_12_31_add_drm_key_table.sql 2015_01_13_kuser_add_type_column.sql
2013_25_11_scheduled_task_table.sql 2015_01_18_alter_drop_folder_index.sql
2014_01_01_create_live_channel_segment_table.sql 2015_01_20_kuser_kgroup_table.sql
2014_01_14_audit_trail_config_admin_console_partner_updates.sql 2015_02_23_response_profile_table.sql
2014_01_19_category_entry_add_privacy_context.sql 2015_03_18_alter_metadata_profile_field_with_custom_data_field.sql
2014_01_22_bulk_upload_result_bulk_job_id_to_bigint.sql 2015_04_25_alter_delivery_profile_add_priority.sql
2014_01_22_create_delivery_table.sql 2015_04_28_alter_file_sync_table_custom_data_field.sql
2014_02_09_change_drm_key_key_column_name.sql 2015_05_14_metadata_profile_file_sync_version.sql
2014_03_04_update_drm_device_table.sql 2015_05_27_create_edge_server_table.sql
2014_03_19_fix_admin_console_permission_names.sql 2015_06_15_create_user_entry_table.sql
2014_03_20_add_root_id_batch_job_lock.sql 2015_06_22_create_app_token_table.sql
2014_04_03_storage_profile_name.sql 2015_07_26_alter_edge_server_column_name.sql
[root@batch deployment]#

Hi,

No, its fine. So long as you run all the scripts post upgrade you should be covered.
You can run
# kaltura-sanity.sh
to validate everything is working properly.

Hi,

All done, except the video conversion is not working. Which server responsible for conversion? My guess is sphinx.
There is error in sphinx kaltlog:

PHP Warning: require_once(/opt/kaltura/app/plugins/multi_centers/lib/api/KalturaFileSyncImportJobData.php): failed to open stream: No such file or directory in /opt/kaltura/app/infra/KAutoloader.php on line 81
PHP Fatal error: require_once(): Failed opening required ‘/opt/kaltura/app/plugins/multi_centers/lib/api/KalturaFileSyncImportJobData.php’ (include_path=’/opt/kaltura/app/vendor/ZendFramework/library:.:/usr/share/pear:/usr/share/php:/opt/kaltura/app:/opt/kaltura/app/vendor/symfony:/opt/kaltura/app/vendor/symfony/vendor:/opt/kaltura/app/vendor/ZendFramework/library:/opt/kaltura/app/alpha:/opt/kaltura/app/alpha/lib:/opt/kaltura/app/alpha/apps/kaltura/lib’) in /opt/kaltura/app/infra/KAutoloader.php on line 81
PHP Warning: require_once(/opt/kaltura/app/plugins/multi_centers/lib/api/KalturaFileSyncImportJobData.php): failed to open stream: No such file or directory in /opt/kaltura/app/infra/KAutoloader.php on line 81
PHP Fatal error: require_once(): Failed opening required ‘/opt/kaltura/app/plugins/multi_centers/lib/api/KalturaFileSyncImportJobData.php’ (include_path=’/opt/kaltura/app/vendor/ZendFramework/library:.:/usr/share/pear:/usr/share/php:/opt/kaltura/app:/opt/kaltura/app/vendor/symfony:/opt/kaltura/app/vendor/symfony/vendor:/opt/kaltura/app/vendor/ZendFramework/library:/opt/kaltura/app/alpha:/opt/kaltura/app/alpha/lib:/opt/kaltura/app/alpha/apps/kaltura/lib’) in /opt/kaltura/app/infra/KAutoloader.php on line 81
PHP Warning: require_once(/opt/kaltura/app/plugins/multi_centers/lib/api/KalturaFileSyncImportJobData.php): failed to open stream: No such file or directory in /opt/kaltura/app/infra/KAutoloader.php on line 81
PHP Fatal error: require_once(): Failed opening required ‘/opt/kaltura/app/plugins/multi_centers/lib/api/KalturaFileSyncImportJobData.php’ (include_path=’/opt/kaltura/app/vendor/ZendFramework/library:.:/usr/share/pear:/usr/share/php:/opt/kaltura/app:/opt/kaltura/app/vendor/symfony:/opt/kaltura/app/vendor/symfony/vendor:/opt/kaltura/app/vendor/ZendFramework/library:/opt/kaltura/app/alpha:/opt/kaltura/app/alpha/lib:/opt/kaltura/app/alpha/apps/kaltura/lib’) in /opt/kaltura/app/infra/KAutoloader.php on line 81

I couldn’t find ‘KalturaFileSyncImportJobData.php’ file anywhere, even on github.

Another question. In this guide (https://github.com/kaltura/platform-install-packages/blob/master/doc/rpm-cluster-deployment-instructions.md#upgrade-kaltura) the step only done on:

  • Front
  • Batch
  • Sphinx

Do the upgrade also needed on other node, such as DWH and VOD?

Error log when adding a file into dropfolder, and the batch starting to process it:

2015-08-15 03:24:53 [0.027853] [10.90.151.83] [955376849] [128] [API] [KalturaStatement->execute] DEBUG: Sql took - 0.027610063552856 seconds
2015-08-15 03:24:53 [0.000577] [10.90.151.83] [955376849] [129] [API] [kCoreException->__construct] ERR: exception ‘kCoreException’ with message ‘Dynamic enum not found [thumbCuePoint.Thumb] for type [CuePointType]’ in /opt/kaltura/app/alpha/lib/kPluginableEnumsManager.php:167
Stack trace:
#0 /opt/kaltura/app/plugins/cue_points/thumb_cue_point/ThumbCuePointPlugin.php(175): kPluginableEnumsManager::apiToCore(‘CuePointType’, ‘thumbCuePoint.T…’)

2015-08-15 03:24:53 [0.007329] [10.90.151.83] [1658694110] [72] [API] [KalturaStatement->execute] DEBUG: Sql took - 0.0070829391479492 seconds
2015-08-15 03:24:53 [0.000273] [10.90.151.83] [955376849] [130] [API] [kSphinxSearchManager->getSphinxSaveSql] ERR: exception ‘Exception’ with message ‘Dynamic enum not found [thumbCuePoint.Thumb] for type [CuePointType]’ in /opt/kaltura/app/infra/log/KalturaLog.php:83
Stack trace:
#0 /opt/kaltura/app/plugins/sphinx_search/lib/kSphinxSearchManager.php(257): KalturaLog::err(‘Dynamic enum no…’)

2015-08-15 03:24:54 [0.000703] [10.90.151.83] [955376849] [374] [API] [KalturaStatement->execute] DEBUG: Sql took - 0.0005490779876709 seconds
2015-08-15 03:24:54 [0.000248] [10.90.151.83] [955376849] [375] [API] [kCoreException->__construct] ERR: exception ‘kCoreException’ with message ‘Dynamic enum not found [thumbCuePoint.Thumb] for type [CuePointType]’ in /opt/kaltura/app/alpha/lib/kPluginableEnumsManager.php:167
Stack trace:
#0 /opt/kaltura/app/plugins/cue_points/thumb_cue_point/ThumbCuePointPlugin.php(175): kPluginableEnumsManager::apiToCore(‘CuePointType’, ‘thumbCuePoint.T…’)

#16 {main}
2015-08-15 03:24:54 [0.000186] [10.90.151.83] [955376849] [376] [API] [kSphinxSearchManager->getSphinxSaveSql] ERR: exception ‘Exception’ with message ‘Dynamic enum not found [thumbCuePoint.Thumb] for type [CuePointType]’ in /opt/kaltura/app/infra/log/KalturaLog.php:83
Stack trace:
#0 /opt/kaltura/app/plugins/sphinx_search/lib/kSphinxSearchManager.php(257): KalturaLog::err(‘Dynamic enum no…’)

2015-08-15 03:25:09 [0.000791] [10.90.151.83] [616943977] [139] [API] [KalturaStatement->execute] DEBUG: Sql took - 0.00057697296142578 seconds
2015-08-15 03:25:09 [0.000551] [10.90.151.83] [616943977] [140] [API] [kCoreException->__construct] ERR: exception ‘kCoreException’ with message ‘Dynamic enum not found [thumbCuePoint.Thumb] for type [CuePointType]’ in /opt/kaltura/app/alpha/lib/kPluginableEnumsManager.php:167
Stack trace:
#0 /opt/kaltura/app/plugins/cue_points/thumb_cue_point/ThumbCuePointPlugin.php(175): kPluginableEnumsManager::apiToCore(‘CuePointType’, ‘thumbCuePoint.T…’)

#15 {main}
2015-08-15 03:25:09 [0.000251] [10.90.151.83] [616943977] [141] [API] [kSphinxSearchManager->getSphinxSaveSql] ERR: exception ‘Exception’ with message ‘Dynamic enum not found [thumbCuePoint.Thumb] for type [CuePointType]’ in /opt/kaltura/app/infra/log/KalturaLog.php:83
Stack trace:
#0 /opt/kaltura/app/plugins/sphinx_search/lib/kSphinxSearchManager.php(257): KalturaLog::err(‘Dynamic enum no…’)

2015-08-15 03:25:11 [0.000890] [10.90.151.83] [341467221] [316] [API] [KalturaStatement->execute] DEBUG: Sql took - 0.00064611434936523 seconds
2015-08-15 03:25:11 [0.000613] [10.90.151.83] [341467221] [317] [API] [kCoreException->__construct] ERR: exception ‘kCoreException’ with message ‘Dynamic enum not found [thumbCuePoint.timedThumb] for type [assetType]’ in /opt/kaltura/app/alpha/lib/kPluginableEnumsManager.php:167
Stack trace:
#0 /opt/kaltura/app/plugins/cue_points/thumb_cue_point/ThumbCuePointPlugin.php(184): kPluginableEnumsManager::apiToCore(‘assetType’, ‘thumbCuePoint.t…’)

exception ‘kCoreException’ with message ‘Dynamic enum not found [thumbCuePoint.timedThumb] for type [assetType]’ in /opt/kaltura/app/alpha/lib/kPluginableEnumsManager.php:167
Stack trace:
#0 /opt/kaltura/app/plugins/cue_points/thumb_cue_point/ThumbCuePointPlugin.php(184): kPluginableEnumsManager::apiToCore(‘assetType’, ‘thumbCuePoint.t…’)

#19 {main}’ in /opt/kaltura/app/infra/log/KalturaLog.php:65
Stack trace:
#0 /opt/kaltura/app/alpha/apps/kaltura/lib/batch2/kFlowManager.php(456): KalturaLog::alert(‘Error in job [9…’)

2015-08-15 03:25:11 [0.002017] [10.90.151.83] [341467221] [338] [API] [KalturaStatement->execute] DEBUG: Sql took - 0.0017929077148438 seconds
2015-08-15 03:25:11 [0.000378] [10.90.151.83] [341467221] [339] [API] [kFlowManager->updatedJob] ERR: exception ‘Exception’ with message ‘Error:Dynamic enum not found [thumbCuePoint.timedThumb] for type [assetType]’ in /opt/kaltura/app/infra/log/KalturaLog.php:83
Stack trace:
#0 /opt/kaltura/app/alpha/apps/kaltura/lib/batch2/kFlowManager.php(443): KalturaLog::err(‘Error:Dynamic e…’)

2015-08-15 03:25:11 [0.000856] [10.90.151.83] [341467221] [373] [API] [KalturaStatement->execute] DEBUG: Sql took - 0.00062394142150879 seconds
2015-08-15 03:25:11 [0.000382] [10.90.151.83] [341467221] [374] [API] [kCoreException->__construct] ERR: exception ‘kCoreException’ with message ‘Dynamic enum not found [thumbCuePoint.Thumb] for type [CuePointType]’ in /opt/kaltura/app/alpha/lib/kPluginableEnumsManager.php:167
Stack trace:
#0 /opt/kaltura/app/plugins/cue_points/thumb_cue_point/ThumbCuePointPlugin.php(175): kPluginableEnumsManager::apiToCore(‘CuePointType’, ‘thumbCuePoint.T…’)

#15 {main}
2015-08-15 03:25:11 [0.000253] [10.90.151.83] [341467221] [375] [API] [kSphinxSearchManager->getSphinxSaveSql] ERR: exception ‘Exception’ with message ‘Dynamic enum not found [thumbCuePoint.Thumb] for type [CuePointType]’ in /opt/kaltura/app/infra/log/KalturaLog.php:83
Stack trace:
#0 /opt/kaltura/app/plugins/sphinx_search/lib/kSphinxSearchManager.php(257): KalturaLog::err(‘Dynamic enum no…’)

Can you please try to remove the contents for the cache dir [without removing the directory though]:
# rm -rf /opt/kaltura/app/cache/*

And then reconfigure using kaltura-config-all.sh?