Issue installing Kaltura latest release (11.2.0) on Centos 6.5

Hi,

We are testing Kaltura 11.2.0 on centos 6.5 server (this is a first time installation) and facing the following issue with kaltura-db-config.sh:

Stopping httpd: [ OK ]
Starting httpd: [ OK ]
Stopping memcached: [ OK ]
Starting memcached: [ OK ]
Shutting down monit: [FAILED]
Starting monit: Generated unique Monit id 2f49f2383f1141648d21e7ad4819d6ba and stored to '/root/.monit.id’
Starting Monit 5.13 daemon with http interface at [*]:2812
[ OK ]
Running Sphinx config…

kaltura-sphinx-2.2.1-17.x86_64
base-config completed successfully, if you ever want to re-configure your system (e.g. change DB hostname) run the following script:

rm /opt/kaltura/app/base-config.lock

/opt/kaltura/bin/kaltura-base-config.sh

Starting monit: Starting Monit 5.13 daemon with http interface at [*]:2812
[ OK ]

Configuring your Kaltura DB…

Checking MySQL version…
Ver 5.1.73 found compatible

CREATE USER kaltura;
CREATE USER etl;
CREATE DATABASE kaltura;
CREATE DATABASE kaltura_sphinx_log;
CREATE DATABASE kalturadw;
CREATE DATABASE kalturadw_ds;
CREATE DATABASE kalturadw_bisources;
CREATE DATABASE kalturalog;
Checking connectivity to needed daemons…
Connectivity test passed:)
Cleaning cache…
Populating DB with data… please wait…
Output for /opt/kaltura/app/deployment/base/scripts/installPlugins.php being logged into /opt/kaltura/log/installPlugins.log
Output for /opt/kaltura/app/deployment/base/scripts/insertDefaults.php being logged into /opt/kaltura/log/insertDefaults.log
Output for /opt/kaltura/app/deployment/base/scripts/insertPermissions.php being logged into /opt/kaltura/log/insertPermissions.log
Output for /opt/kaltura/app/deployment/base/scripts/insertContent.php being logged into /opt/kaltura/log/insertContent.log

kaltura-db-config.sh FAILED with: 9455 on line 178

Archving logs to /opt/kaltura/log/log_02_12_15_19_12.tar.gz…
ERROR: we failed on something else…

Hello,

Take a look at the errors in /opt/kaltura/log/insertContent.log.
My guess is the hostname/service URL you provided is not resolvable and hence, the DB deployment, which makes API requests, has failed. But it will be quite clear by checking this log.