Upgrade Configuration Error Kaltura CE 12.6.0 release

hiphopservers · December 12, 2016, 10:34pm

When upgrade to the new version of Kaltura CE on CentOS v6.7 I get the following error when trying to run the configuration all script.

searchd (pid 18387 18386) is running...
Stopping searchd: Sphinx 2.2.1-id64-dev (r4097)
Copyright (c) 2001-2013, Andrew Aksyonoff
Copyright (c) 2008-2013, Sphinx Technologies Inc (http://sphinxsearch.com)

using config file '/opt/kaltura/app/configurations/sphinx/kaltura.conf'...
stop: successfully sent SIGTERM to pid 18387

Backing up files to /opt/kaltura/sphinx.bck.1481576899. Once the upgrade is done and tested, please remove this di                                                                                                                                                                                                                      rectory to save space
Starting searchd: Sphinx 2.2.1-id64-dev (r4097)
Copyright (c) 2001-2013, Andrew Aksyonoff
Copyright (c) 2008-2013, Sphinx Technologies Inc (http://sphinxsearch.com)

using config file '/opt/kaltura/app/configurations/sphinx/kaltura.conf'...
listening on all interfaces, port=9312
WARNING: index 'kaltura_base': no fields configured (use rt_field directive) - NOT SERVING
WARNING: index 'kaltura_base_gt_in_charset': no fields configured (use rt_field directive) - NOT SERVING
precaching index 'kaltura_entry'
precaching index 'kaltura_category'
precaching index 'kaltura_kuser'
precaching index 'kaltura_category_kuser'
precaching index 'kaltura_cue_point'
precaching index 'kaltura_entry_distribution'
precaching index 'kaltura_caption_item'
precaching index 'kaltura_tag'
precaching index 'kaltura_metadata'
precaching index 'kaltura_schedule_event'
precached 10 indexes in 0.049 sec

2016-12-12 21:08:19 [DbManager::connectFallbackLogic] ERR: exception 'Exception' with message 'failed to connect t                                                                                                                                                                                                                      o propel3' in /opt/kaltura/app/infra/log/KalturaLog.php:83
Stack trace:
#0 /opt/kaltura/app/alpha/apps/kaltura/lib/db/DbManager.php(279): KalturaLog::err('failed to conne...')
#1 /opt/kaltura/app/alpha/apps/kaltura/lib/myDbHelper.class.php(35): DbManager::connectFallbackLogic(Array, Array,                                                                                                                                                                                                                       Array)
#2 /opt/kaltura/app/deployment/base/scripts/populateSphinxEntries.php(21): myDbHelper::getConnection('propel2')
#3 {main}
2016-12-12 21:08:19 [DbManager::connectFallbackLogic] ERR: exception 'Exception' with message 'failed to connect t                                                                                                                                                                                                                      o propel2' in /opt/kaltura/app/infra/log/KalturaLog.php:83
Stack trace:
#0 /opt/kaltura/app/alpha/apps/kaltura/lib/db/DbManager.php(279): KalturaLog::err('failed to conne...')
#1 /opt/kaltura/app/alpha/apps/kaltura/lib/myDbHelper.class.php(35): DbManager::connectFallbackLogic(Array, Array,                                                                                                                                                                                                                       Array)
#2 /opt/kaltura/app/deployment/base/scripts/populateSphinxEntries.php(21): myDbHelper::getConnection('propel2')
#3 {main}
2016-12-12 21:08:19 [DbManager::connectFallbackLogic] ERR: exception 'Exception' with message 'failed to connect t                                                                                                                                                                                                                      o propel3' in /opt/kaltura/app/infra/log/KalturaLog.php:83
Stack trace:
#0 /opt/kaltura/app/alpha/apps/kaltura/lib/db/DbManager.php(279): KalturaLog::err('failed to conne...')
#1 /opt/kaltura/app/alpha/apps/kaltura/lib/myDbHelper.class.php(35): DbManager::connectFallbackLogic(Array, Array,                                                                                                                                                                                                                       Array)
#2 /opt/kaltura/app/deployment/base/scripts/populateSphinxEntries.php(21): myDbHelper::getConnection('propel2')
#3 {main}
2016-12-12 21:08:19 [DbManager::connectFallbackLogic] ERR: exception 'Exception' with message 'failed to connect t                                                                                                                                                                                                                      o propel2' in /opt/kaltura/app/infra/log/KalturaLog.php:83
Stack trace:
#0 /opt/kaltura/app/alpha/apps/kaltura/lib/db/DbManager.php(279): KalturaLog::err('failed to conne...')
#1 /opt/kaltura/app/alpha/apps/kaltura/lib/myDbHelper.class.php(35): DbManager::connectFallbackLogic(Array, Array,                                                                                                                                                                                                                       Array)
#2 /opt/kaltura/app/deployment/base/scripts/populateSphinxEntries.php(21): myDbHelper::getConnection('propel2')
#3 {main}
PHP Fatal error:  Uncaught exception 'PropelException' with message 'Could not connect to any database server' in                                                                                                                                                                                                                       /opt/kaltura/app/alpha/apps/kaltura/lib/myDbHelper.class.php:37
Stack trace:
#0 /opt/kaltura/app/deployment/base/scripts/populateSphinxEntries.php(21): myDbHelper::getConnection('propel2')
#1 {main}
  thrown in /opt/kaltura/app/alpha/apps/kaltura/lib/myDbHelper.class.php on line 37
Failed to run /opt/kaltura/app/deployment/base/scripts/populateSphinxEntries.php.
        Please try to run it manually and look at the logs
ERROR: /opt/kaltura/bin/kaltura-sphinx-config.sh failed:( You can re-run it when the issue is fixed.

Install breaks at the sphinx configuration and will not move forward.

jess · December 13, 2016, 4:18pm

The problem is a failure to connect to the DB. Start by checking the credentials in /opt/kaltura/app/configurations/db.ini and making sure you can connect manually from the shell using the mysql client.

hiphopservers · December 13, 2016, 5:50pm

@jess

It seems my whole ‘kaltura’ database is missing. It isn’t a issue since this is a non-production system having this issue but I have no idea what happen to the database files.

mysql> show databases;
+---------------------+
| Database            |
+---------------------+
| information_schema  |
| kaltura_sphinx_log  |
| kalturadw           |
| kalturadw_bisources |
| kalturadw_ds        |
| kalturalog          |
| mysql               |
+---------------------+
7 rows in set (0.00 sec)

I will run the removal script and drop everything and start with a fresh install of the system. Then see if this resolves the issues by starting from scratch.

hiphopservers · December 13, 2016, 8:02pm

My fresh install worked without an issue. I had to drop databases and users then reinstall Kaltura CE from scratch on this development cloud server. Still not sure what happen to cause the database to drop in the first place but it likely not related to Kaltura CE installations or upgrades.