Problems installing Kaltura CE on ubuntu 14.x

Hi,

I am completely new to installing a server, so please forgive any obvious mistakes.

I am installing via a docker container with an ans file. The ans file is below

local TZ to be used by PHP code. Note that it MUST be the same as your DB TZ.

TIME_ZONE=“America/New_York”

Apache port

KALTURA_VIRTUAL_HOST_PORT="443"
KALTURA_VIRTUAL_HOST_NAME=“ip-172-31-59-69”

host and port

KALTURA_FULL_VIRTUAL_HOST_NAME="$KALTURA_VIRTUAL_HOST_NAME:$KALTURA_VIRTUAL_HOST_PORT"

operational DB user and passwd

DB1_NAME="kaltura"
DB1_USER="kaltura"
PROTOCOL=“https"
SERVICE_URL=”$PROTOCOL://$KALTURA_FULL_VIRTUAL_HOST_NAME"
SPHINX_SERVER1=“ip-172-31-59-69"
SPHINX_SERVER2=” "
SPHINX_DB_HOST="ip-172-31-59-69"
SPHINX_DB_PORT=“3306”

user name for the Kaltura Admin Console, MUST be in the form of an email

ADMIN_CONSOLE_ADMIN_MAIL="timothy.roberts@ymail.com"

passwd for the Kaltura Admin Console

ADMIN_CONSOLE_PASSWORD=“blackstrawberry”

for installs that have no remote CDN storage, use the same as $KALTURA_VIRTUAL_HOST_NAME

CDN_HOST="$KALTURA_VIRTUAL_HOST_NAME"

display name used when sending the ‘welcome’ mail.

ENVIRONMENT_NAME=“Kaltura Video Platform”

what web I/F would you want to enable, options:

0 - All web interfaces

1 - Kaltura Management Console [KMC], Hosted Apps, HTML5 lib and ClipAp

2 - KAC - Kaltura Admin Console

CONFIG_CHOICE=“0”

are we working over SSL? needed since, if so, we perform cert validity checks

IS_SSL=“y”

hostname for Red5

RED5_HOST=“ip-172-31-59-69”

allow the install scripts to send install data for analytics and support purposes:

1 - allow

0 - prevent

USER_CONSENT=1

SSL cert path

CRT_FILE=/etc/ssl/certs/localhost.crt

SSL key path

KEY_FILE=/etc/pki/tls/private/localhost.key

if such exists enter path here, otherwise leave as is.

CHAIN_FILE=NONE

Operational DB MySQL

DB1_HOST=“ip-172-31-59-69”

MySQL PORT

DB1_PORT=“3306”

desired passwd, make it good.

DB1_PASS=“KALT_DB_PASS”

analytics MySQL DB

DWH_HOST=“ip-172-31-59-69”

analytics MySQL port

DWH_PORT=“80”

analytics MySQL port

DWH_PASS=“ip-172-31-59-69”

MySQL super user, this is only used for bootstrap, the app itself will not connect with it.

SUPER_USER="root"
SUPER_USER_PASSWD=“MYSQL_SUPER_USER_PASSWD”

For nginx packager module

VOD_PACKAGER_HOST="ip-172-31-59-69"
VOD_PACKAGER_PORT=“ip-172-31-59-69”

whether or not to configure Nginx over SSL

IS_NGINX_SSL=“N”

path to SSL cert

SSL_CERT

path to SSL key

SSL_KEY

NGINX SSL PORT - note, if you have Apache running over SSL as well and on port 443, do not select 443 here too

VOD_PACKAGER_SSL_PORT=8443

WWW_HOST=“ip-172-31-59-69”

Range of ip addresses belonging to internal kaltura servers

The range is used when checking service actions permissions and allowing to access certain services without KS from the internal servers.

The default is only good for testing, on a production ENV you should adjust according to your network.

IP_RANGE=“0.0.0.0-255.255.255.255”

This is the output that I am getting:

setenforce: SELinux is disabled
Starting mysqld: [ OK ]
mysql-server-5.1.73-7.el6.x86_64
Stopping mysqld: [ OK ]
Starting mysqld: [ OK ]
Running base config…

kaltura-base-12.2.0-10.noarch
Welcome to Kaltura Server 12.2.0 post install setup.
Checking MySQL version…
ERROR 2003 (HY000): Can’t connect to MySQL server on ‘ip-172-31-59-69’ (111)

kaltura-base-config.sh FAILED with: 1 on line 307

Archving logs to /opt/kaltura/log/log_22_11_16_04_56.tar.gz…
cp: cannot stat `/opt/kaltura/log/*log’: No such file or directory
tar: *log: Cannot stat: No such file or directory
tar: Exiting with failure status due to previous errors

kaltura-config-all.sh FAILED with: 967 on line 42

Archving logs to /opt/kaltura/log/log_22_11_16_04_57.tar.gz…
cp: cannot stat `/opt/kaltura/log/*log’: No such file or directory
tar: *log: Cannot stat: No such file or directory
tar: Exiting with failure status due to previous errors

======================

Can someone please help?

~trob

Hello @trob215879,

Your problem starts here:
ERROR 2003 (HY000): Can't connect to MySQL server on 'ip-172-31-59-69' (111)

There can be two reasons for that: either ip-172-31-59-69 is not resolvable inside the container [remember the hostname you choose MUST be resolvable both from inside the container and from any machine you’ll be using the kaltura API/web I/Fs and player embeds from] OR it is resolvable but the MySQL authorization mechanism is preventing access when trying to use ip-172-31-59-69 as hostname.

Start by logging into the container’s shell and making sure that ip-172-31-59-69 is resolvable, then, for MySQL, see if you can login using:
# mysql -hlocalhost -uroot -pMYSQL_SUPER_USER_PASSWD
if you can log in this way, I would suggest just setting 127.0.0.1 as your DB1_HOST and DWH_HOST.

In a stand alone configuration, you wouldn’t need to connect to MySQL from outside the container anyhow so, it is best to use localhost.
If you’re interested in looking at the currently allowed hosts and user configuration, you can see that with:

mysql> select host,user from mysql.user;

If you’re unable to login to MySQL using localhost and the passwd you set in the SUPER_USER_PASSWD, you can always reset it by stopping the mysql daemon and calling:

# mysqld_safe --skip-grant-tables

Then you can run:
# mysql_secure_installation
and set a new root passwd, at which point, you should also adjust your ans file accordingly.

Once again, remember the host you use MUST be resolvable from both inside the Kaltura server [docker container in your case] AND any machine/device you plan to interact with Kaltura from.

Hi,

I got a new error. I am not sure what is appropriate for these 2 values:

Apache port

KALTURA_VIRTUAL_HOST_PORT="443"
KALTURA_VIRTUAL_HOST_NAME=“54.174.227.99”

My output is below.

root@ip-172-31-59-69:~# docker run -d --name=kaltura -p 80:80 -p 443:443 -p 1935:1935 kaltura/server
e361e9d8c26b0938c12cbdf9c94be4255529464afedf34161f82baf72a13885f
root@ip-172-31-59-69:~# nano
root@ip-172-31-59-69:~# docker cp config.ans kaltura:/root/install/
root@ip-172-31-59-69:~# docker exec -i -t kaltura /root/install/install.sh
setenforce: SELinux is disabled
Starting mysqld: [ OK ]
mysql-server-5.1.73-7.el6.x86_64
Stopping mysqld: [ OK ]
Starting mysqld: [ OK ]
Running base config…

kaltura-base-12.2.0-10.noarch
Welcome to Kaltura Server 12.2.0 post install setup.
Checking MySQL version…
Ver 5.1.73 found compatible

========================================================================================================================
Kaltura install answer file written to /tmp/kaltura_24_11_04_52.ans - Please save it!
This answers file can be used to silently-install re-install this machine or deploy other hosts in your cluster.

Generating client libs…
This can take a few minutes to complete, see log at /opt/kaltura/log/generate.php.log.

    Configuration of 12.2.0 finished successfully!

Running FrontEnd config…

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

kaltura-front-12.2.0-1.noarch

Enabling Apache config - apps.conf
Enabling Apache config - var.conf
Enabling Apache config - admin.conf

========================================================================================================================
Kaltura install answer file written to /tmp/kaltura_24_11_04_53.ans - Please save it!
This answers file can be used to silently-install re-install this machine or deploy other hosts in your cluster.

Stopping httpd: [ OK ]
Starting httpd: httpd: Could not reliably determine the server’s fully qualified domain name, using 172.17.0.2 for ServerName
[ OK ]
Stopping memcached: [ OK ]
Starting memcached: [ OK ]
Shutting down monit: [FAILED]
Starting monit: New Monit id: 836b0a02dba476dbe19342ed9441a5f0
Stored in ‘/root/.monit.id’
Starting Monit 5.18 daemon with http interface at [*]:2812
[ OK ]
sed: -e expression #1, char 41: unterminated s' command sed: -e expression #1, char 21: unterminateds’ command

Running Sphinx config…

kaltura-sphinx-2.2.1-20.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.18 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:)
ERROR: Couldn’t make an API request to https://54.174.227.99:443/api_v3/index.php?service=system&action=ping.
Please check your setup and then run /opt/kaltura/bin/kaltura-db-config.sh again.

Do you wish to remove the Kaltura DBs? [n/Y]
Hit ‘n’ to keep it for debugging purposes.

n
ERROR: we failed on something else…

I see you’re using HTTPs, did you set the paths to the SSL certificate, key and CA in the answer file and copy these files into the container?

What does:
$ curl -I -v https://54.174.227.99:443/api_v3/index.php?service=system&action=ping

return when you run it from the shell?

Hi,

You are right, I did not set it up. Truth be told, I did not know to. I will try to set it up and get back to you.

I suspect I have to install apache on the host, then set the paths to the SSL certificate, key and CA in the answer file and copy these files to the same paths the container?

Am I correct? In your instruction above, you did not mention installing apache on the host. I am not sure if the installation was the correct thing to do, and something that I was supposed to know.

~Tim

Hi,

Obviously, if you want to use SSL, you need a valid SSL cert. You can get one for free from http://letsencrypt.org/.
You do not need to edit the Apache configuration yourself, the post install script does that but you DO need to copy the cert, key and CA files onto the container and set the proper paths for them in the answer file.
Alternatively, you can set

IS_SSL="N"
IS_NGINX_SSL="N"

In which case both Apache and Nginx will be configured without SSL and the service URL/endpoint should then be **http://**YOUR_IP_OR_HOST and NOT https:// as you’ve set it before.

Still no luck.

Here is my ans file:

# local TZ to be used by PHP code. Note that it MUST be the same as your DB TZ.
TIME_ZONE="America/New_York"
# Apache port
KALTURA_VIRTUAL_HOST_PORT="443"
KALTURA_VIRTUAL_HOST_NAME="54.174.227.99"
# host and port
KALTURA_FULL_VIRTUAL_HOST_NAME="$KALTURA_VIRTUAL_HOST_NAME:$KALTURA_VIRTUAL_HOST_PORT"
# operational DB user and passwd
DB1_NAME="kaltura"
DB1_USER="kaltura"
PROTOCOL="https"
SERVICE_URL="$PROTOCOL://$KALTURA_FULL_VIRTUAL_HOST_NAME"
SPHINX_SERVER1="127.0.0.1"
SPHINX_SERVER2=" "
SPHINX_DB_HOST="127.0.0.1"
SPHINX_DB_PORT="3306"
# user name for the Kaltura Admin Console, MUST be in the form of an email
ADMIN_CONSOLE_ADMIN_MAIL="timothy.roberts@ymail.com"
# passwd for the Kaltura Admin Console
ADMIN_CONSOLE_PASSWORD="blackstrawberry"
# for installs that have no remote CDN storage, use the same as $KALTURA_VIRTUAL_HOST_NAME
CDN_HOST="$KALTURA_VIRTUAL_HOST_NAME"
# display name used when sending the 'welcome' mail.
ENVIRONMENT_NAME="Kaltura Video Platform"
# what web I/F would you want to enable, options:
# 0 - All web interfaces 
# 1 - Kaltura Management Console [KMC], Hosted Apps, HTML5 lib and ClipAp
# 2 - KAC - Kaltura Admin Console
CONFIG_CHOICE="0"
# are we working over SSL? needed since, if so, we perform cert validity checks
IS_SSL="N"
# hostname for Red5
RED5_HOST="127.0.0.1"
# allow the install scripts to send install data for analytics and support purposes:
# 1 - allow
# 0 - prevent
USER_CONSENT=1
# SSL cert path
CRT_FILE=/etc/ssl/certs/localhost.crt
# SSL key path
KEY_FILE=/etc/pki/tls/private/localhost.key
# if such exists enter path here, otherwise leave as is.
CHAIN_FILE=NONE
# Operational DB MySQL 
DB1_HOST="127.0.0.1"
# MySQL PORT 
DB1_PORT="3306"
# desired passwd, make it good.
DB1_PASS="KALT_DB_PASS"
# analytics MySQL DB
DWH_HOST="127.0.0.1"
# analytics MySQL port 
DWH_PORT="80"
# analytics MySQL port 
DWH_PASS="80"
# MySQL super user, this is only used for bootstrap, the app itself will not connect with it.
SUPER_USER="root"
SUPER_USER_PASSWD="MYSQL_SUPER_USER_PASSWD"
# For nginx packager module
VOD_PACKAGER_HOST="127.0.0.1"
VOD_PACKAGER_PORT="8080"
# whether or not to configure Nginx over SSL
IS_NGINX_SSL="N"
# path to SSL cert 
# SSL_CERT
# path to SSL key
# SSL_KEY
# NGINX SSL PORT - note, if you have Apache running over SSL as well and on port 443, do not select 443 here too
# VOD_PACKAGER_SSL_PORT=8443
WWW_HOST="127.0.0.1"
# Range of ip addresses belonging to internal kaltura servers
# The range is used when checking service actions permissions and allowing to access certain services without KS from the internal servers.
# The default is only good for testing, on a production ENV you should adjust according to your network.
IP_RANGE="0.0.0.0-255.255.255.255"

=======================

Here is my error:
ERROR: Couldn’t make an API request to (http)://54.174.227.99:443/api_v3/index.php?service=system&action=ping.
Please check your setup and then run /opt/kaltura/bin/kaltura-db-config.sh again.

=========

root@ip-172-31-59-69:~# curl -I -v https://54.174.227.99:443/api_v3/index.php?service=system&action=ping
[1] 833
root@ip-172-31-59-69:~# * Hostname was NOT found in DNS cache

  • Trying 54.174.227.99…
  • Connected to 54.174.227.99 (54.174.227.99) port 443 (#0)
  • successfully set certificate verify locations:
  • CAfile: none
    CApath: /etc/ssl/certs
  • SSLv3, TLS handshake, Client hello (1):
  • SSLv3, TLS handshake, Server hello (2):
  • SSLv3, TLS handshake, CERT (11):
  • SSLv3, TLS alert, Server hello (2):
  • SSL certificate problem: unable to get local issuer certificate
  • Closing connection 0
    curl: (60) SSL certificate problem: unable to get local issuer certificate
    More details here: http://curl.haxx.se/docs/sslcerts.html

curl performs SSL certificate verification by default, using a "bundle"
of Certificate Authority (CA) public keys (CA certs). If the default
bundle file isn’t adequate, you can specify an alternate file
using the --cacert option.
If this HTTPS server uses a certificate signed by a CA represented in
the bundle, the certificate verification probably failed due to a
problem with the certificate (it might be expired, or the name might
not match the domain name in the URL).
If you’d like to turn off curl’s verification of the certificate, use
the -k (or --insecure) option.

Your answer file has:

PROTOCOL="https"

Should be:

PROTOCOL="http"

Also, when pasting code or configs which contain ‘#’ chars, please use “```” before and after these lines. This forum supports markdown where “#” means a header so when you paste lines with “#” it generates H1 tags, making it very hard to read.

I made the change. It failed.

Stopping httpd: [ OK ]
Starting httpd: httpd: Could not reliably determine the server’s fully qualified domain name, using 172.17.0.2 for ServerName
[Thu Dec 15 05:15:28 2016] [warn] default VirtualHost overlap on port 443, the first has precedence
[FAILED]

kaltura-front-config.sh FAILED with: 1 on line 290

Archving logs to /opt/kaltura/log/log_15_12_16_05_15.tar.gz…

kaltura-config-all.sh FAILED with: 966 on line 61

Archving logs to /opt/kaltura/log/log_15_12_16_05_15.tar.gz…

Please post your full ans file again.

Hi,

I am unfamiliar with the what the port numbers correspond to ports in the conifg file. Here is the copy of the config file.

~Tim

“# local TZ to be used by PHP code. Note that it MUST be the same as your DB TZ.
TIME_ZONE=“America/New_York”
”# Apache port
KALTURA_VIRTUAL_HOST_PORT=“443"
KALTURA_VIRTUAL_HOST_NAME=“54.174.227.99"
”# host and port
KALTURA_FULL_VIRTUAL_HOST_NAME=”$KALTURA_VIRTUAL_HOST_NAME:$KALTURA_VIRTUAL_HOST
_PORT"
"# operational DB user and passwd
DB1_NAME=“kaltura"
DB1_USER=“kaltura"
PROTOCOL=“http"
SERVICE_URL=”$PROTOCOL://$KALTURA_FULL_VIRTUAL_HOST_NAME"
SPHINX_SERVER1=“127.0.0.1"
SPHINX_SERVER2=” “
SPHINX_DB_HOST=“127.0.0.1"
SPHINX_DB_PORT=“3306"
”# user name for the Kaltura Admin Console, MUST be in the form of an email
ADMIN_CONSOLE_ADMIN_MAIL="timothy.roberts@ymail.com
”# passwd for the Kaltura Admin Console
ADMIN_CONSOLE_PASSWORD=“blackstrawberry”
”# for installs that have no remote CDN storage, use the same as $KALTURA_VIRTUAL
_HOST_NAME
CDN_HOST=”$KALTURA_VIRTUAL_HOST_NAME"
"# display name used when sending the ‘welcome’ mail.
ENVIRONMENT_NAME=“Kaltura Video Platform”
"# what web I/F would you want to enable, options:
"# 0 - All web interfaces
"# 1 - Kaltura Management Console [KMC], Hosted Apps, HTML5 lib and ClipAp
"# 2 - KAC - Kaltura Admin Console
CONFIG_CHOICE=“0"
”# are we working over SSL? needed since, if so, we perform cert validity checks
IS_SSL=“N”
"# hostname for Red5
RED5_HOST=“127.0.0.1"
”# allow the install scripts to send install data for analytics and support purpo
ses:
"# 1 - allow
"# 0 - prevent
USER_CONSENT=1
"# SSL cert path
CRT_FILE=/etc/ssl/certs/localhost.crt
"# SSL key path
KEY_FILE=/etc/pki/tls/private/localhost.key
"# if such exists enter path here, otherwise leave as is.
CHAIN_FILE=NONE
"# Operational DB MySQL
DB1_HOST=“127.0.0.1"
”# MySQL PORT
DB1_PORT=“3306"
”# desired passwd, make it good.
DB1_PASS=“KALT_DB_PASS”
"# analytics MySQL DB
DWH_HOST=“127.0.0.1"
”# analytics MySQL port
DWH_PORT=“80"
”# analytics MySQL port
DWH_PASS=“80"
”# MySQL super user, this is only used for bootstrap, the app itself will not con
nect with it.
SUPER_USER=“root"
SUPER_USER_PASSWD=“MYSQL_SUPER_USER_PASSWD”
”# desired passwd, make it good.
DB1_PASS=“KALT_DB_PASS”
"# analytics MySQL DB
DWH_HOST=“127.0.0.1"
”# analytics MySQL port
DWH_PORT=“80"
”# analytics MySQL port
DWH_PASS=“80"
”# MySQL super user, this is only used for bootstrap, the app itself will not con
nect with it.
SUPER_USER=“root"
SUPER_USER_PASSWD=“MYSQL_SUPER_USER_PASSWD”
”# For nginx packager module
VOD_PACKAGER_HOST=“127.0.0.1"
VOD_PACKAGER_PORT=“8080"
”# whether or not to configure Nginx over SSL
IS_NGINX_SSL=“N”
”# path to SSL cert
"# SSL_CERT
"# path to SSL key
"# SSL_KEY
"# NGINX SSL PORT - note, if you have Apache running over SSL as well and on port
443, do not select 443 here too
"# VOD_PACKAGER_SSL_PORT=8443
WWW_HOST=“127.0.0.1"
”# Range of ip addresses belonging to internal kaltura servers
"# The range is used when checking service actions permissions and allowing to ac
cess certain services without KS from the internal servers.
"# The default is only good for testing, on a production ENV you should adjust ac
cording to your network.
IP_RANGE=“0.0.0.0-255.255.255.255”

Hi,

You’ve got:

KALTURA_VIRTUAL_HOST_PORT="443"

Which is wrong. 443 is the default port for HTTPs. Since you want HTTP and do not have an SSL cert and key, you need:

KALTURA_VIRTUAL_HOST_PORT="80"
# Also, DWH is Data WareHouse it's a DB and should be 3306, the default MySQL port
DWH_PASS="3306"
# and, while 80 as password can work, I'd choose a better passwd:
DWH_PASS="80"

Still no luck.

‘# local TZ to be used by PHP code. Note that it MUST be the same as your DB TZ.
TIME_ZONE=“America/New_York”
’# Apache port
KALTURA_VIRTUAL_HOST_PORT=“80"
KALTURA_VIRTUAL_HOST_NAME=“54.174.227.99”
’# host and port
KALTURA_FULL_VIRTUAL_HOST_NAME=”$KALTURA_VIRTUAL_HOST_NAME:$KALTURA_VIRTUAL_HOST_PORT"
’# operational DB user and passwd
DB1_NAME="kaltura"
DB1_USER=“kaltura"
PROTOCOL=“http"
SERVICE_URL=”$PROTOCOL://$KALTURA_FULL_VIRTUAL_HOST_NAME"
SPHINX_SERVER1=“127.0.0.1"
SPHINX_SERVER2=” “
SPHINX_DB_HOST=“127.0.0.1"
SPHINX_DB_PORT=“3306”
’# user name for the Kaltura Admin Console, MUST be in the form of an email
ADMIN_CONSOLE_ADMIN_MAIL="timothy.roberts@ymail.com
’# passwd for the Kaltura Admin Console
ADMIN_CONSOLE_PASSWORD=“blackstrawberry”
’# for installs that have no remote CDN storage, use the same as $KALTURA_VIRTUAL_HOST_NAME
CDN_HOST=”$KALTURA_VIRTUAL_HOST_NAME”
’# display name used when sending the ‘welcome’ mail.
ENVIRONMENT_NAME=“Kaltura Video Platform”
’# what web I/F would you want to enable, options:
’# 0 - All web interfaces
’# 1 - Kaltura Management Console [KMC], Hosted Apps, HTML5 lib and ClipAp
’# 2 - KAC - Kaltura Admin Console
CONFIG_CHOICE=“0”
’# are we working over SSL? needed since, if so, we perform cert validity checks
IS_SSL=“N”
’# hostname for Red5
RED5_HOST=“127.0.0.1”
’# allow the install scripts to send install data for analytics and support purposes:
’# 1 - allow
’# 0 - prevent
USER_CONSENT=1
’# SSL cert path
CRT_FILE=/etc/ssl/certs/localhost.crt
’# SSL key path
KEY_FILE=/etc/pki/tls/private/localhost.key
’# if such exists enter path here, otherwise leave as is.
CHAIN_FILE=NONE
’# Operational DB MySQL
DB1_HOST=“127.0.0.1”
’# MySQL PORT
DB1_PORT=“3306”
’# desired passwd, make it good.
DB1_PASS=“KALT_DB_PASS”
’# analytics MySQL DB
DWH_HOST=“127.0.0.1”
’# analytics MySQL port
DWH_PORT=“3306”
’# analytics MySQL port
DWH_PASS=“KALTURADWH”
’# MySQL super user, this is only used for bootstrap, the app itself will not connect with it.
SUPER_USER="root"
SUPER_USER_PASSWD=“MYSQL_SUPER_USER_PASSWD”
’# For nginx packager module
VOD_PACKAGER_HOST="127.0.0.1"
VOD_PACKAGER_PORT=“8080”
’# whether or not to configure Nginx over SSL
IS_NGINX_SSL=“N”
’# path to SSL cert
’# SSL_CERT
’# path to SSL key
’# SSL_KEY
’# NGINX SSL PORT - note, if you have Apache running over SSL as well and on port 443, do not select 443 here too
’# VOD_PACKAGER_SSL_PORT=8443
WWW_HOST=“127.0.0.1”
’# Range of ip addresses belonging to internal kaltura servers
’# The range is used when checking service actions permissions and allowing to access certain services without KS from the internal servers.
’# The default is only good for testing, on a production ENV you should adjust according to your network.
IP_RANGE=“0.0.0.0-255.255.255.255”

Here is the error:
ERROR: Couldn’t make an API request to http://54.174.227.99:80/api_v3/index.php?service=system&action=ping.
Please check your setup and then run /opt/kaltura/bin/kaltura-db-config.sh again.