Migrating single server to cluster level installation

rmahawar · August 31, 2015, 5:58am

Hi,

Can we migrate single server Kaltura installation to Cluster level installation ? Site is live on single server installation of around 3k videos and analytics.

What are all dependencies we need to resolve for it like, entry id, analytics etc.?

Thanks.

jess · August 31, 2015, 3:31pm

Hello,

Take a look at:

github.com

kaltura/platform-install-packages/blob/Jupiter-10.19.0/doc/deb-cluster-deployment-instructions.md

# Deploying Kaltura Clusters

Below are **deb** based instructions for deploying Kaltura Clusters.    
Refer to the [All-In-One Kaltura Server Installation Guide](https://github.com/kaltura/platform-install-packages/blob/master/doc/install-kaltura-deb-based.md) for more notes about deploying Kaltura in deb supported environments.    

### Instructions here are for a cluster with the following members:

* [Load Balancer](#apache-load-balancer)
* [NFS server](#the-nfs-server)
* [MySQL Database](#the-mysql-database)
* [Sphinx Indexing](#the-sphinx-indexing-server)
* [Front servers](#the-front)
* [Batch servers](#the-batch)
* [DWH server](#the-datawarehouse)
* [Nginx VOD server](#nginx-vod-server)
* [Streaming Server](#the-streaming-server)
* [Upgrade Kaltura](#upgrade-kaltura)
* [Platform Monitoring](#platform-monitoring)
* [Backup and Restore](#backup-and-restore-practices)

This file has been truncated. show original

or, in the event you installed the RPM version:

github.com

kaltura/platform-install-packages/blob/Jupiter-10.19.0/doc/rpm-cluster-deployment-instructions.md

# Deploying Kaltura Clusters

Below are **RPM** based instructions for deploying Kaltura Clusters.    
Refer to the [All-In-One Kaltura Server Installation Guide](https://github.com/kaltura/platform-install-packages/blob/master/doc/install-kaltura-redhat-based.md) for more notes about deploying Kaltura in RPM supported environments.    
Refer to the [Deploying Kaltura Clusters Using Chef](https://github.com/kaltura/platform-install-packages/blob/master/doc/rpm-chef-cluster-deployment.md) for automated Chef based deployments.

### Instructions here are for a cluster with the following members:

* [Load Balancer](#apache-load-balancer)
* [NFS server](#the-nfs-server)
* [MySQL Database](#the-mysql-database)
* [Sphinx Indexing](#the-sphinx-indexing-server)
* [Front servers](#the-front)
* [Batch servers](#the-batch)
* [DWH server](#the-datawarehouse)
* [Nginx VOD server](#nginx-vod-server)
* [Streaming Server](#the-streaming-server)
* [Upgrade Kaltura](#upgrade-kaltura)
* [Platform Monitoring](#platform-monitoring)
* [Backup and Restore](#backup-and-restore-practices)

This file has been truncated. show original

Basically, you can just provide the conn. info for the existing DB instead of creating a new one and skip the DB creation phase specified in the doc.

jaiswal · September 21, 2015, 7:58am

Hello,

After migrate getting below error

PHP Fatal error: Uncaught exception ‘PropelException’ with message ‘No connection information in your runtime configuration file for datasource [sphinx_log_read]’ in /opt/kaltura/app/vendor/propel/Propel.php:529
Stack trace:
#0 /opt/kaltura/app/alpha/apps/kaltura/lib/myDbHelper.class.php(30): Propel::getConnection(‘sphinx_log_read’)

jess · September 21, 2015, 8:26am

Hello,

This was fixed by this pull:

And is released in 10.20.0. It will become the stable version in about an hour, running final CI tests as I type.

jaiswal · September 21, 2015, 8:38am

Hello Jess,

Still getting same error below.

[root@kmc ~]# /etc/init.d/kaltura-populate restart
Mon Sep 21 14:03:48 IST 2015
Shutting down:
Service populate isn’t currently running.
Starting:
Service populate isn’t running but stale lock file exists
Removing stale lock file at /opt/kaltura/log/populate.pid
/usr/bin/php populateFromLog.php >> /opt/kaltura/log/kaltura_populate.log 2>&1 &
[ OK ]
[root@kmc ~]# /etc/init.d/kaltura-sphinx restart
Stopping searchd: Sphinx 2.2.1-id64-dev (r4097)
Copyright © 2001-2013, Andrew Aksyonoff
Copyright © 2008-2013, Sphinx Technologies Inc (http://sphinxsearch.com)

using config file ‘/opt/kaltura/app/configurations/sphinx/kaltura.conf’…
stop: successfully sent SIGTERM to pid 9088

Starting searchd: Sphinx 2.2.1-id64-dev (r4097)
Copyright © 2001-2013, Andrew Aksyonoff
Copyright © 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_kuser_base’: 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’
precached 9 indexes in 0.025 sec

[root@kmc ~]# /etc/init.d/kaltura-populate restart
Mon Sep 21 14:04:15 IST 2015
Shutting down:
Service populate isn’t currently running.
Starting:
Service populate isn’t running but stale lock file exists
Removing stale lock file at /opt/kaltura/log/populate.pid
/usr/bin/php populateFromLog.php >> /opt/kaltura/log/kaltura_populate.log 2>&1 &
[ OK ]

–
==> /opt/kaltura/log/kaltura_populate.log <==
PHP Fatal error: Uncaught exception ‘PropelException’ with message ‘No connection information in your runtime configuration file for datasource [sphinx_log_read]’ in /opt/kaltura/app/vendor/propel/Propel.php:529
Stack trace:
#0 /opt/kaltura/app/alpha/apps/kaltura/lib/myDbHelper.class.php(30): Propel::getConnection(‘sphinx_log_read’)

jess · September 21, 2015, 8:44am

Not sure I understand… did you upgrade to 10.20.0? this requires changing the repo file to sync against ‘10.20.0’ instead of ‘latest’.

what version of kaltura-base do you currently have?
# rpm -q kaltura-base
or:
# dpkg -l kaltura-base

Also, after upgrading, you need to re-run the config scripts.

jaiswal · September 21, 2015, 8:49am

Hello jess,

I am manually add below line in db.template.ini then restart populate and sphinx service.
but its not working.

+sphinx_log_read.adapter = mysql
+sphinx_log_read.connection.classname = KalturaPDO
+sphinx_log_read.connection.phptype = mysql
+sphinx_log_read.connection.database = @SPHINX_DB_NAME@
+sphinx_log_read.connection.hostspec = @SPHINX_DB_HOST@
+sphinx_log_read.connection.user = @DB1_USER@
+sphinx_log_read.connection.password = @DB1_PASS@
+sphinx_log_read.connection.dsn = “mysql:host=@SPHINX_DB_HOST@;port=@SPHINX_DB_PORT@;dbname=@SPHINX_DB_NAME@;”
+sphinx_log_read.connection.options.kaltura.noTransaction = true
+

I am not upgrade kaltura yet,please suggest.

[root@kmckaltura]# rpm -q kaltura-base
kaltura-base-10.19.0-10.noarch

jess · September 21, 2015, 9:01am

Hi,

You need to replace all tokens “@.*@” with the actual values and then reload apache and the kaltura-populate services.

jaiswal · September 21, 2015, 9:16am

Thanks a lot Jess…

jess · September 21, 2015, 9:34am

Surething. All is well now?