Kaltura-base configuration halts due to timezone

Community Forums
15

Hi @SrikarVR,

You seem to either not have the kaltura DBs set up at all or you have a half baked DB from previous attempts.
I suggest you remove any left overs you may have of Kaltura MySQL users and DBs and purge the kaltura-db package with:

# /opt/kaltura/bin/kaltura-drop-db.sh
# aptitude purge kaltura-db
 
Just to be on the safe side, also reconfigure the kaltura-base package with:

# dpkg-reconfigure kaltura-base

and then reinstall kaltura-db with:

# aptitude install kaltura-db

It will prompt you for the MySQL root passwd and other inputs and then repopulate the DB. Please keep a close eye for errors at the stage.
If you get any, paste them here, otherwise, once done, rerun the install script, it’ll pick up where the last one left off and perform the missing tasks.

Alternatively, if you want to simply purge everything and start anew [might be faster] run:

/opt/kaltura/bin/kaltura-drop-db.sh ; aptitude purge "~Nkaltura" -y && aptitude purge "~Napache2" -y && rm -rf /opt/kaltura

and then rerun the install script.

16

Hi Jess - I dropped the Database, ran “dpkg-reconfigure kaltura-base” and reinstalled kaltura-db. Following is the output below. What is not clear to me is what is causing user “kaltura” login to fail with “localhost” while it works for user “root”. See below:

> root@684386-slrs01va9f1sv01:/opt/kaltura/bin# mysql -ukaltura -padmin -hlocalhost -P3306
> ERROR 1045 (28000): Access denied for user ‘kaltura’@‘localhost’ (using password: YES)

If I telnet on port 3306 with localhost connection is established, where telnet with IP / Hostname fails. /etc/hosts file entries are here. Are these correct? Do I have to get any of the ports open? Any specific firewall changes needed?

127.0.0.1 localhost
10.89.12.140 684386-slrs01va9f1sv01

root@684386-slrs01va9f1sv01:/opt/kaltura/bin# telnet localhost 3306
Trying 127.0.0.1…
Connected to localhost.
Escape character is ‘^]’.
[
5.5.55-0ubuntu0.14.04.11FYm:t]U▒YJGeHt2:k0Jemysql_native_password^]

root@684386-slrs01va9f1sv01:/opt/kaltura/bin# telnet 10.89.12.140 3306
Trying 10.89.12.140…
telnet: Unable to connect to remote host: Connection refused

root@684386-slrs01va9f1sv01:/opt/kaltura/bin# ./kaltura-drop-db.sh

  • ‘[’ ‘!’ -r /opt/kaltura/bin/db_actions.rc ‘]’

  • . /opt/kaltura/bin/db_actions.rc
    ++ DBS=‘kaltura kaltura_sphinx_log kalturadw kalturadw_ds kalturadw_bisources kalturalog’
    ++ DB_USERS=‘kaltura etl’
    ++ kaltura_PRIVILEGES=INSERT,UPDATE,DELETE,SELECT,ALTER,CREATE,DROP
    ++ kaltura_USER=kaltura
    ++ kaltura_SQL_FILES=’/opt/kaltura/app/deployment/base/sql/01.kaltura_ce_tables.sql /opt/kaltura/app/deployment/base/sql/04.stored_procedures.sql’
    ++ kaltura_sphinx_log_PRIVILEGES=SELECT,INSERT,UPDATE
    ++ kaltura_sphinx_log_USER=kaltura
    ++ kaltura_sphinx_log_SQL_FILES=/opt/kaltura/app/deployment/base/sql/01.kaltura_sphinx_ce_tables.sql
    ++ kalturadw_PRIVILEGES=INSERT,UPDATE,DELETE,SELECT,EXECUTE
    ++ kalturadw_USER=etl
    ++ kalturadw_ds_PRIVILEGES=INSERT,UPDATE,DELETE,SELECT,EXECUTE
    ++ kalturadw_ds_USER=etl
    ++ kalturadw_bisources_PRIVILEGES=INSERT,UPDATE,DELETE,SELECT,EXECUTE
    ++ kalturadw_bisources_USER=etl
    ++ kalturalog_PRIVILEGES=‘INSERT,UPDATE,DELETE,SELECT,LOCK TABLES’
    ++ kalturalog_USER=etl

  • . /opt/kaltura/bin/colors.sh
    ++ DULL=0
    ++ BRIGHT=1
    ++ FG_BLACK=30
    ++ FG_RED=31
    ++ FG_GREEN=32
    ++ FG_YELLOW=33
    ++ FG_BLUE=34
    ++ FG_VIOLET=35
    ++ FG_CYAN=36
    ++ FG_WHITE=37
    ++ FG_NULL=00
    ++ BG_BLACK=40
    ++ BG_RED=41
    ++ BG_GREEN=42
    ++ BG_YELLOW=43
    ++ BG_BLUE=44
    ++ BG_VIOLET=45
    ++ BG_CYAN=46
    ++ BG_WHITE=47
    ++ BG_NULL=00
    ++ ETCOLOR_ERROR=’\033[1;31m’
    ++ ESC=’\033’
    ++ NORMAL=’\033[m’
    ++ RESET=’\033[0;37;00m’
    ++ BLACK=’\033[0;30m’
    ++ RED=’\033[0;31m’
    ++ GREEN=’\033[0;32m’
    ++ YELLOW=’\033[0;33m’
    ++ BLUE=’\033[0;34m’
    ++ VIOLET=’\033[0;35m’
    ++ CYAN=’\033[0;36m’
    ++ WHITE=’\033[0;37m’
    ++ BRIGHT_BLACK=’\033[1;30m’
    ++ BRIGHT_RED=’\033[1;31m’
    ++ BRIGHT_GREEN=’\033[1;32m’
    ++ BRIGHT_YELLOW=’\033[1;33m’
    ++ BRIGHT_BLUE=’\033[1;34m’
    ++ BRIGHT_VIOLET=’\033[1;35m’
    ++ BRIGHT_CYAN=’\033[1;36m’
    ++ BRIGHT_WHITE=’\033[1;37m’
    ++ REV_CYAN=’\033[0;47;46m’
    ++ REV_RED=’\033[0;33; 41m’
    ++ JESS=‘Jess likes this one :)’

  • RC_FILE=/etc/kaltura.d/system.ini

  • ‘[’ ‘!’ -r /etc/kaltura.d/system.ini ‘]’

  • . /etc/kaltura.d/system.ini
    ++ WEB_DIR=/opt/kaltura/web
    ++ LOG_DIR=/opt/kaltura/log
    ++ APP_DIR=/opt/kaltura/app
    ++ BASE_DIR=/opt/kaltura
    ++ PHP_BIN=/usr/bin/php
    ++ OS_KALTURA_USER=kaltura
    ++ MAILTO=myemailaddress
    ++ ADMIN_CONSOLE_ADMIN_MAIL=myemailaddress
    ++ DB1_HOST=localhost
    ++ DB1_NAME=kaltura
    ++ DB1_USER=kaltura
    ++ DB1_PASS=admin
    ++ DWH_HOST=localhost
    ++ DWH_PORT=3306
    ++ DWH_USER=etl
    ++ DWH_PASS=@DWH_PASS@
    ++ SERVICE_URL=http://684386-slrs01va9f1sv01
    ++ SPHINX_HOST=127.0.0.1
    ++ DB1_PORT=3306
    ++ SUPER_USER=root
    ++ SUPER_USER_PASSWD=admin
    ++ KALTURA_VIRTUAL_HOST_NAME=684386-slrs01va9f1sv01
    ++ RED5_HOST=

  • echo -en '\033[0;36mThis will drop the following DBs:
    kaltura kaltura_sphinx_log kalturadw kalturadw_ds kalturadw_bisources kalturalog
    and remove users:
    kaltura etl
    on localhost
    \033[m
    ’
    This will drop the following DBs:
    kaltura kaltura_sphinx_log kalturadw kalturadw_ds kalturadw_bisources kalturalog
    and remove users:
    kaltura etl
    on localhost

  • ‘[’ -n ‘’ ‘]’

  • echo -en '\033[1;31m
    NOTE: this is not reversible.
    It is recommended you also back up the current data using mysqldump before continuing.
    You can use /opt/kaltura/bin/kaltura-export-db.sh to export the data.

Are you absolutely certain you want this? [n/Y]
\033[m

’

NOTE: this is not reversible.
It is recommended you also back up the current data using mysqldump before continuing.
You can use /opt/kaltura/bin/kaltura-export-db.sh to export the data.

Are you absolutely certain you want this? [n/Y]

  • read AN
    Y
  • ‘[’ Y ‘!=’ Y ‘]’
  • echo 'root DB passwd:'
    root DB passwd:
  • read -s DBPASSWD
  • for i in ‘$DB_USERS’
  • echo ‘drop user kaltura’
  • mysql -uroot -hlocalhost -padmin -P3306
  • for i in ‘$DB_USERS’
  • echo ‘drop user etl’
  • mysql -uroot -hlocalhost -padmin -P3306
  • for i in ‘$DBS’
  • echo -en '\033[0;36mRemoving kaltura…\033[m’
    Removing kaltura…+ echo ‘drop database kaltura’
  • mysql -uroot -hlocalhost -padmin -P3306
  • for i in ‘$DBS’
  • echo -en '\033[0;36mRemoving kaltura_sphinx_log…\033[m’
    Removing kaltura_sphinx_log…+ echo ‘drop database kaltura_sphinx_log’
  • mysql -uroot -hlocalhost -padmin -P3306
  • for i in ‘$DBS’
  • echo -en '\033[0;36mRemoving kalturadw…\033[m’
    Removing kalturadw…+ echo ‘drop database kalturadw’
  • mysql -uroot -hlocalhost -padmin -P3306
  • for i in ‘$DBS’
  • echo -en '\033[0;36mRemoving kalturadw_ds…\033[m’
    Removing kalturadw_ds…+ echo ‘drop database kalturadw_ds’
  • mysql -uroot -hlocalhost -padmin -P3306
  • for i in ‘$DBS’
  • echo -en '\033[0;36mRemoving kalturadw_bisources…\033[m’
    Removing kalturadw_bisources…+ echo ‘drop database kalturadw_bisources’
  • mysql -uroot -hlocalhost -padmin -P3306
  • for i in ‘$DBS’
  • echo -en '\033[0;36mRemoving kalturalog…\033[m’
    Removing kalturalog…+ echo ‘drop database kalturalog’
  • mysql -uroot -hlocalhost -padmin -P3306
  • echo -e ‘\n\033[0;32m Successfully dropped kaltura databases and users\033[m’

Successfully dropped kaltura databases and users
root@684386-slrs01va9f1sv01:/opt/kaltura/bin# aptitude purge kaltura-db
The following packages will be REMOVED:
kaltura-db{p}
0 packages upgraded, 0 newly installed, 1 to remove and 1 not upgraded.
Need to get 0 B of archives. After unpacking 8,192 B will be freed.
Do you want to continue? [Y/n/?] Y
(Reading database … 248286 files and directories currently installed.)
Removing kaltura-db (12.15.0-1+b4) …
Purging configuration files for kaltura-db (12.15.0-1+b4) …

root@684386-slrs01va9f1sv01:/opt/kaltura/bin# dpkg-reconfigure kaltura-base

  • apache2 is running
  • Stopping web server apache2 *
  • Stopping daemon monitor monit [ OK ]
  • Starting web server apache2 *
    root@684386-slrs01va9f1sv01:/opt/kaltura/bin# aptitude install kaltura-db
    The following NEW packages will be installed:
    kaltura-db
    0 packages upgraded, 1 newly installed, 0 to remove and 1 not upgraded.
    Need to get 0 B/4,444 B of archives. After unpacking 8,192 B will be used.
    Preconfiguring packages …
    Selecting previously unselected package kaltura-db.
    (Reading database … 248286 files and directories currently installed.)
    Preparing to unpack …/kaltura-db_12.15.0-1+b4_all.deb …
    Unpacking kaltura-db (12.15.0-1+b4) …
    Setting up kaltura-db (12.15.0-1+b4) …
    Checking MySQL version…

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…
ERROR: Couldn’t connect with mysql -ukaltura -padmin -hlocalhost -P3306.
dpkg: error processing package kaltura-db (–configure):
subprocess installed post-installation script returned error exit status 6
Errors were encountered while processing:
kaltura-db
E: Sub-process /usr/bin/dpkg returned an error code (1)
A package failed to install. Trying to recover:
Setting up kaltura-db (12.15.0-1+b4) …
Checking MySQL version…

root@684386-slrs01va9f1sv01:/opt/kaltura/bin# mysql -uroot -padmin -hlocalhost -P3306
Welcome to the MySQL monitor. Commands end with ; or \g.
Your MySQL connection id is 1583
Server version: 5.5.55-0ubuntu0.14.04.1 (Ubuntu)

Copyright © 2000, 2017, Oracle and/or its affiliates. All rights reserved.

Oracle is a registered trademark of Oracle Corporation and/or its
affiliates. Other names may be trademarks of their respective
owners.

Type ‘help;’ or ‘\h’ for help. Type ‘\c’ to clear the current input statement.

mysql> quit
Bye
root@684386-slrs01va9f1sv01:/opt/kaltura/bin# mysql -ukaltura -padmin -hlocalhost -P3306
ERROR 1045 (28000): Access denied for user ‘kaltura’@‘localhost’ (using password: YES)
root@684386-slrs01va9f1sv01:/opt/kaltura/bin# telnet localhost 3306
Trying 127.0.0.1…
Connected to localhost.
Escape character is ‘^]’.
[
5.5.55-0ubuntu0.14.04.11FYm:t]U▒YJGeHt2:k0Jemysql_native_password^]
telnet> quit
Connection closed.
root@684386-slrs01va9f1sv01:/opt/kaltura/bin# telnet 10.89.12.140 3306
Trying 10.89.12.140…
telnet: Unable to connect to remote host: Connection refused

Regards - Srikar

17

Hi @SrikarVR,

For an all in one machine, it’s not necessary for the DB to be accessible from the outside [for a cluster, it should be made accessible to all front and batch nodes, of course].
I suggest you start with:
# mysql -uroot -p
and run:
mysql> select host,user,password from mysql.user;
let’s see what users exist and from which hosts access is currently allowed and try to understand why:
mysql -ukaltura -p$DB1_PASS -hlocalhost -P3306
fails…

18

Hi Jess - Here is the output:

root@684386-slrs01va9f1sv01:/opt/_installable/kaltura# mysql -uroot -p
Enter password:
Welcome to the MySQL monitor. Commands end with ; or \g.
Your MySQL connection id is 1597
Server version: 5.5.55-0ubuntu0.14.04.1 (Ubuntu)

Copyright © 2000, 2017, Oracle and/or its affiliates. All rights reserved.

Oracle is a registered trademark of Oracle Corporation and/or its
affiliates. Other names may be trademarks of their respective
owners.

Type ‘help;’ or ‘\h’ for help. Type ‘\c’ to clear the current input statement.

mysql> select host,user,password from mysql.user;
±-----------------------±-----------------±------------------------------------------+
| host | user | password |
±-----------------------±-----------------±------------------------------------------+
| localhost | root | *4ACFE3202A5FF5CF467898FC58AAB1D615029441 |
| 684386-slrs01va9f1sv01 | root | *4ACFE3202A5FF5CF467898FC58AAB1D615029441 |
| 127.0.0.1 | root | *4ACFE3202A5FF5CF467898FC58AAB1D615029441 |
| ::1 | root | *4ACFE3202A5FF5CF467898FC58AAB1D615029441 |
| localhost | debian-sys-maint | *561883FFEAC810559BDC1C79BE9E489A43FFD78E |
| localhost | kaltura | *60AA43F79506C401098E4097A1B489CE5AA6E129 |
| % | kaltura | *4ACFE3202A5FF5CF467898FC58AAB1D615029441 |
| % | etl | *AA2E46314A017AAF820A492C2A420680865A1F24 |
±-----------------------±-----------------±------------------------------------------+
8 rows in set (0.00 sec)

mysql>

Regards - Srikar

19

I dropped DB with “/opt/kaltura/bin/kaltura-drop-db.sh” and ran “bash -x /opt/kaltura/bin/kaltura-db-config.sh” but I found the script failing @ line 214 with error in the trail below. Also found that “kaltura” user was not getting dropped, so I manually dropped use “kaltura” and reinstalled DB as below.

/opt/kaltura/bin/kaltura-drop-db.sh

mysql> drop user kaltura@localhost; (removed “kaltura” user manually)

aptitude purge kaltura-db

dpkg-reconfigure kaltura-base

aptitude install kaltura-db

With this DB installed successfully and I can connect to MySQL with “kaltura” user @localhost. I also checked that login to KMC also works but the page does not display anything under the tabs after login. Admin console link is yet to work.

KMC_login.png1366×728 28.6 KB

…
…

++ TAR_PATH=/opt/kaltura/log/log_17_06_17_03_38.tar.gz
++ echo -en ’

\033[1;31mkaltura-db-config.sh FAILED with: 1 on line 214\033[m
Archving logs to /opt/kaltura/log/log_17_06_17_03_38.tar.gz…
’
kaltura-db-config.sh FAILED with: 1 on line 214

Archving logs to /opt/kaltura/log/log_17_06_17_03_38.tar.gz…
++ mkdir -p /tmp/tmpdir_kaltura

20

Hi @SrikarVR,

You’ve logged into the KMC with the Admin Console partner [ID -2, created during the installation], this is why the KMC views are empty.
You should first login to the Admin Console and create a new partner from Publishers->Add New Publisher.
For this, of course, we first need to debug the Admin Console login issue.
From a root shell on the server, run:
# source /etc/profile.d/kaltura-base.sh
# kaltlog
and look at the errors thrown to STDOUT, in parallel, before making a login attempt, open your browser’s dev tools and look for errors and failing requests under the “Console” and “Network” tabs and paste the info here.

As for the error while running /opt/kaltura/bin/kaltura-db-config.sh, you shouldn’t be running that script, it is meant for RPM where interactive prompting during the package installation is not supported.
The deb package format DOES support it so all you need to run is:

# aptitude install kaltura-db

which will trigger /var/lib/dpkg/info/kaltura-db.postinst

It’s very important to make certain the installation of the kaltura-db deb package finishes successfully.

21

Hi Jess - Kindly find the output below from kaltlog and the screen shot of DEV tools Network tab. There is a .map file missing but I do not see any errors/messages in browser console.

root@684386-slrs01va9f1sv01:/opt/_installable/kaltura# source /etc/profile.d/kaltura-base.sh
root@684386-slrs01va9f1sv01:/opt/_installable/kaltura# kaltlog
[Mon Jun 19 01:55:07.171604 2017] [:error] [pid 18872] [client 64.39.99.67:37077] script ‘/opt/kaltura/app/alpha/web/moadmin.php’ not found or unable to stat
[Mon Jun 19 03:14:43.354855 2017] [:error] [pid 15852] [client 10.89.237.225:50083] PHP Fatal error: Uncaught exception ‘Infra_Exception’ with message ‘Kaltura client not found, maybe it wasn’t generated’ in /opt/kaltura/app/ui_infra/InfraBootstrapper.php:31\nStack trace:\n#0 /opt/kaltura/app/vendor/ZendFramework/library/Zend/Application/Bootstrap/BootstrapAbstract.php(662): InfraBootstrapper->_initClient()\n#1 /opt/kaltura/app/vendor/ZendFramework/library/Zend/Application/Bootstrap/BootstrapAbstract.php(615): Zend_Application_Bootstrap_BootstrapAbstract->_executeResource(‘client’)\n#2 /opt/kaltura/app/vendor/ZendFramework/library/Zend/Application/Bootstrap/BootstrapAbstract.php(579): Zend_Application_Bootstrap_BootstrapAbstract->_bootstrap(NULL)\n#3 /opt/kaltura/app/vendor/ZendFramework/library/Zend/Application.php(347): Zend_Application_Bootstrap_BootstrapAbstract->bootstrap(NULL)\n#4 /opt/kaltura/app/admin_console/web/index.php(37): Zend_Application->bootstrap()\n#5 {maintail: }\n thrown in /opt/kaltura/app/ui_infra/InfraBootstrapper.php on line 31, referer: http://684386-slrs01va9f1sv01/start/index.php
[Mon Jun 19 03:25:36.069465 2017] [:error] [pid 16524] [client 10.89.237.225:50255] PHP Fatal error: Uncaught exception ‘Infra_Exception’ with message ‘Kaltura client not found, maybe it wasn’t generated’ in /opt/kaltura/app/ui_infra/InfraBootstrapper.php:31\nStack trace:\n#0 /opt/kaltura/app/vendor/ZendFramework/library/Zend/Application/Bootstrap/BootstrapAbstract.php(662): InfraBootstrapper->_initClient()\n#1 /opt/kaltura/app/vendor/ZendFramework/library/Zend/Application/Bootstrap/BootstrapAbstract.php(615): Zend_Application_Bootstrap_BootstrapAbstract->_executeResource(‘client’)\n#2 /opt/kaltura/app/vendor/ZendFramework/library/Zend/Application/Bootstrap/BootstrapAbstract.php(579): Zend_Application_Bootstrap_BootstrapAbstract->_bootstrap(NULL)\n#3 /opt/kaltura/app/vendor/ZendFramework/library/Zend/Application.php(347): Zend_Application_Bootstrap_BootstrapAbstract->bootstrap(NULL)\n#4 /opt/kaltura/app/admin_console/web/index.php(37): Zend_Application->bootstrap()\n#5 {main}\n thrown in /opt/kaltura/app/ui_infra/InfraBootstrapper.php on line 31

cannot open ‘/opt/kaltura/log/batch/*.log’ for reading: No such file or directory–
==> /opt/kaltura/log/kaltura_batch.log <==

PHP Warning: file_put_contents(/opt/kaltura/app/cache//batch/config.ini): failed to open stream: Permission denied in /opt/kaltura/app/batch/scheduler/KSchedulerConfig.class.php on line 185
PHP Fatal error: Uncaught exception ‘Zend_Config_Exception’ with message ‘Section ‘684386-slrs01va9f1sv01’ cannot be found in /opt/kaltura/app/cache//batch/config.ini’ in /opt/kaltura/app/vendor/ZendFramework/library/Zend/Config/Ini.php:150
Stack trace:
#0 /opt/kaltura/app/batch/scheduler/KSchedulerConfig.class.php(59): Zend_Config_Ini->__construct(’/opt/kaltura/ap…’, ‘684386-slrs01va…’, true)

10.89.237.225 - - [19/Jun/2017:03:41:49 +0000] “GET /favicon.ico HTTP/1.1” 200 1752 0/401 “-” “Mozilla/5.0 (Windows NT 10.0; WOW64; Trident/7.0; managedpc; gdn/adcp; rv:11.0) like Gecko” “-” 10.89.237.225 “-” “684386-slrs01va9f1sv01” 18877 - - 351 “-” “-” “-” “-” “max-age=7776000, public” -
::1 - - [19/Jun/2017:03:41:55 +0000] “OPTIONS * HTTP/1.0” 200 125 0/91 “-” “Apache/2.4.7 (Ubuntu) PHP/5.5.9-1ubuntu4.21 (internal dummy connection)” “-” ::1 “-” “-” 15852 - - 107 “-” “-” “-” “-” “-” -
::1 - - [19/Jun/2017:03:41:56 +0000] “OPTIONS * HTTP/1.0” 200 125 0/109 “-” “Apache/2.4.7 (Ubuntu) PHP/5.5.9-1ubuntu4.21 (internal dummy connection)” “-” ::1 “-” “-” 18316 - - 107 “-” “-” “-” “-” “-” -
::1 - - [19/Jun/2017:03:41:57 +0000] “OPTIONS * HTTP/1.0” 200 125 0/198 “-” “Apache/2.4.7 (Ubuntu) PHP/5.5.9-1ubuntu4.21 (internal dummy connection)” “-” ::1 “-” “-” 17247 - - 107 “-” “-” “-” “-” “-” -

–
2017-06-19 03:42:14 [0.000000] [1498467002] [1] [BATCH] [KSchedulerConfig->load] NOTICE: loading configuration /opt/kaltura/app/configurations/batch at 1497672570
PHP Warning: file_put_contents(/opt/kaltura/app/cache//batch/config.ini): failed to open stream: Permission denied in /opt/kaltura/app/batch/scheduler/KSchedulerConfig.class.php on line 185
PHP Fatal error: Uncaught exception ‘Zend_Config_Exception’ with message ‘Section ‘684386-slrs01va9f1sv01’ cannot be found in /opt/kaltura/app/cache//batch/config.ini’ in /opt/kaltura/app/vendor/ZendFramework/library/Zend/Config/Ini.php:150
Stack trace:
#0 /opt/kaltura/app/batch/scheduler/KSchedulerConfig.class.php(59): Zend_Config_Ini->__construct(’/opt/kaltura/ap…’, ‘684386-slrs01va…’, true)

==> /opt/kaltura/log/kaltura_apache_errors.log <==
[Mon Jun 19 03:42:29.191665 2017] [:error] [pid 17248] [client 10.89.237.225:50422] PHP Fatal error: Uncaught exception ‘Infra_Exception’ with message ‘Kaltura client not found, maybe it wasn’t generated’ in /opt/kaltura/app/ui_infra/InfraBootstrapper.php:31\nStack trace:\n#0 /opt/kaltura/app/vendor/ZendFramework/library/Zend/Application/Bootstrap/BootstrapAbstract.php(662): InfraBootstrapper->_initClient()\n#1 /opt/kaltura/app/vendor/ZendFramework/library/Zend/Application/Bootstrap/BootstrapAbstract.php(615): Zend_Application_Bootstrap_BootstrapAbstract->_executeResource(‘client’)\n#2 /opt/kaltura/app/vendor/ZendFramework/library/Zend/Application/Bootstrap/BootstrapAbstract.php(579): Zend_Application_Bootstrap_BootstrapAbstract->_bootstrap(NULL)\n#3 /opt/kaltura/app/vendor/ZendFramework/library/Zend/Application.php(347): Zend_Application_Bootstrap_BootstrapAbstract->bootstrap(NULL)\n#4 /opt/kaltura/app/admin_console/web/index.php(37): Zend_Application->bootstrap()\n#5 {main}\n thrown in /opt/kaltura/app/ui_infra/InfraBootstrapper.php on line 31, referer: http://684386-slrs01va9f1sv01/start/index.php

Kaltura_admin_network_error.png1366×728 60.1 KB

root@684386-slrs01va9f1sv01:/opt/kaltura/app/start/css# ll
total 280
drwxr-xr-x 2 root root 4096 Jun 14 08:13 ./
drwxr-xr-x 7 root root 4096 Jun 14 08:13 …/
-rw-r–r-- 1 root root 146010 Jun 4 08:13 bootstrap.css
-rw-r–r-- 1 root root 121200 Jun 4 08:13 bootstrap.min.css
-rw-r–r-- 1 root root 1210 Jun 4 08:13 google_font.css
-rw-r–r-- 1 root root 3201 Jun 4 08:13 landing-page.css

Regards - Srikar

22

Hi @SrikarVR,

I really think it’ll be faster for you to simply reinstall from scratch.
According to your output, the needed client libs were never generated. This is done during the kaltura-base.postinst with:

php $KALTURA_PREFIX/app/generator/generate.php
 
does:

# php -v

now works for you? If you recall, that was your original issue and you’ve manually changed:

php -r "if (timezone_open('$TIME_ZONE') === false){exit(1);}
to:
php5 -r "if (timezone_open('$TIME_ZONE') === false){exit(1);}

which as explained if not a good solution as the php command is used in multiple contexts from many scripts.

You must ensure the php command is available [revisit my explanation about the alternatives mechanism] and then reinstall.

23

Hi Jess - Yes, the command #php -v works for me. here is the output.

root@684386-slrs01va9f1sv01:/opt/_installable/kaltura# php -v
PHP 5.5.9-1ubuntu4.21 (cli) (built: Feb 9 2017 20:54:58)
Copyright © 1997-2014 The PHP Group
Zend Engine v2.5.0, Copyright © 1998-2014 Zend Technologies
with Zend OPcache v7.0.3, Copyright © 1999-2014, by Zend Technologies

Please should I follow the below commands to uninstall. Or do I need to anything additional before doing the clean up and reinstall.

/opt/kaltura/bin/kaltura-drop-db.sh

aptitude purge “~Nkaltura”

rm -rf /opt/kaltura

rm -rf /etc/kaltura.d

Regards - Srikar

24

Hi @SrikarVR,

That’s all you need. Simply run these commands to purge everything and then re-run the install script.
Please make sure to look closely for errors in the output and post them here should you have any.

25

While uninstalling I am getting errors. I am afraid with broken or left overs my re-installation may fail. Please can you advice here, how to clear these? Also I would like to remove php7 as there are errors related to it. Suggest how do I remove it.

Successfully dropped kaltura databases and users
root@684386-slrs01va9f1sv01:/opt/_installable/kaltura# mysql -uroot -ppassword
Welcome to the MySQL monitor. Commands end with ; or \g.
Your MySQL connection id is 2565
Server version: 5.5.55-0ubuntu0.14.04.1 (Ubuntu)

Copyright © 2000, 2017, Oracle and/or its affiliates. All rights reserved.

Oracle is a registered trademark of Oracle Corporation and/or its
affiliates. Other names may be trademarks of their respective
owners.

Type ‘help;’ or ‘\h’ for help. Type ‘\c’ to clear the current input statement.

mysql> select host,user,password from mysql.user;
±-----------------------±-----------------±------------------------------------------+
| host | user | password |
±-----------------------±-----------------±------------------------------------------+
| localhost | root | *4ACFE3202A5FF5CF467898FC58AAB1D615029441 |
| 684386-slrs01va9f1sv01 | root | *4ACFE3202A5FF5CF467898FC58AAB1D615029441 |
| 127.0.0.1 | root | *4ACFE3202A5FF5CF467898FC58AAB1D615029441 |
| ::1 | root | *4ACFE3202A5FF5CF467898FC58AAB1D615029441 |
| localhost | debian-sys-maint | *561883FFEAC810559BDC1C79BE9E489A43FFD78E |
±-----------------------±-----------------±------------------------------------------+
5 rows in set (0.00 sec)

mysql> exit
Bye
root@684386-slrs01va9f1sv01:/opt/_installable/kaltura# aptitude purge "~Nkaltura"
The following packages will be REMOVED:
kaltura-base{p} kaltura-batch{p} kaltura-clipapp{p} kaltura-db{p} kaltura-dwh{p} kaltura-ffmpeg{p} kaltura-ffmpeg-aux{p} kaltura-front{p} kaltura-html5-studio{p}
kaltura-html5lib{p} kaltura-kclip{p} kaltura-kcw{p} kaltura-kdp{p} kaltura-kdp3{p} kaltura-kdp3wrapper{p} kaltura-kdpwrapper{p} kaltura-kmc{p} kaltura-krecord{p}
kaltura-kupload{p} kaltura-nginx{p} kaltura-pentaho{p} kaltura-php7-memcache{ap} kaltura-postinst{p} kaltura-sphinx{p} kaltura-widgets{p}
0 packages upgraded, 0 newly installed, 25 to remove and 1 not upgraded.
Need to get 0 B of archives. After unpacking 1,593 MB will be freed.
Do you want to continue? [Y/n/?] Y
(Reading database … 248286 files and directories currently installed.)
Removing kaltura-sphinx (2.2.1-4) …
Removing any system startup links for /etc/init.d/kaltura-sphinx …
/etc/rc0.d/K20kaltura-sphinx
/etc/rc1.d/K20kaltura-sphinx
/etc/rc2.d/S20kaltura-sphinx
/etc/rc3.d/S20kaltura-sphinx
/etc/rc4.d/S20kaltura-sphinx
/etc/rc5.d/S20kaltura-sphinx
/etc/rc6.d/K20kaltura-sphinx
Purging configuration files for kaltura-sphinx (2.2.1-4) …
dpkg: warning: while removing kaltura-sphinx, directory ‘/opt/kaltura/sphinx’ not empty so not removed
Removing kaltura-widgets (10.9.0-1+b4) …
Removing kaltura-kupload (1.2.16-1) …
Removing kaltura-batch (12.17.0-1) …

  • set -e
  • [ -x /etc/init.d/kaltura-batch ]
  • [ remove = remove ]
  • invoke-rc.d kaltura-batch stop
    Stopping Batch Manager…
    Service Batch Manager not running [ FAILED ]
    invoke-rc.d: initscript kaltura-batch, action “stop” failed.
  • exit 1
    dpkg: error processing package kaltura-batch (–purge):
    subprocess installed pre-removal script returned error exit status 1
    Removing kaltura-clipapp (1.3-1+b2) …
    Removing kaltura-db (12.15.0-1+b4) …
    Purging configuration files for kaltura-db (12.15.0-1+b4) …
    Removing kaltura-dwh (12.14.0-1+b1) …
    Purging configuration files for kaltura-dwh (12.14.0-1+b1) …
    dpkg: warning: while removing kaltura-dwh, directory ‘/opt/kaltura/dwh/.kettle’ not empty so not removed
    dpkg: warning: while removing kaltura-dwh, directory ‘/opt/kaltura/dwh/logs’ not empty so not removed
    dpkg: warning: while removing kaltura-dwh, directory ‘/opt/kaltura/dwh/setup’ not empty so not removed
    Removing kaltura-nginx (1.12-3) …
    Removing any system startup links for /etc/init.d/kaltura-nginx …
    /etc/rc0.d/K20kaltura-nginx
    /etc/rc1.d/K20kaltura-nginx
    /etc/rc2.d/S20kaltura-nginx
    /etc/rc3.d/S20kaltura-nginx
    /etc/rc4.d/S20kaltura-nginx
    /etc/rc5.d/S20kaltura-nginx
    /etc/rc6.d/K20kaltura-nginx
    Purging configuration files for kaltura-nginx (1.12-3) …
    dpkg: warning: while removing kaltura-nginx, directory ‘/opt/kaltura/log/nginx’ not empty so not removed
    dpkg: warning: while removing kaltura-nginx, directory ‘/opt/kaltura/nginx/conf’ not empty so not removed
    Removing kaltura-front (12.17.0-1) …
    Site admin disabled.
    Site apps disabled.
    Site var disabled.
    Site zzzkaltura disabled.
    Site zzzkaltura.ssl already disabled
    To activate the new configuration, you need to run:
    service apache2 reload
    Purging configuration files for kaltura-front (12.17.0-1) …
    Removing kaltura-kmc (5.42.0-2) …
    dpkg: warning: while removing kaltura-kmc, directory ‘/opt/kaltura/web/content/docs’ not empty so not removed
    Removing kaltura-html5-studio (2.0.9-1) …
    Removing kaltura-html5lib (2.57-1) …
    Removing kaltura-kclip (1.1.2.1-1) …
    Removing kaltura-kcw (2.2.4-1+b3) …
    dpkg: warning: while removing kaltura-kcw, directory ‘/opt/kaltura/web/content/uiconf/kaltura’ not empty so not removed
    Removing kaltura-kdp (2.7.0-1) …
    Removing kaltura-kdp3 (3.9.9-1+b3) …
    Removing kaltura-kdp3wrapper (37-1) …
    Removing kaltura-kdpwrapper (11-1) …
    Removing kaltura-krecord (1.7-1) …
    Removing kaltura-pentaho (4.2.1+b2) …
    dpkg: warning: while removing kaltura-pentaho, directory ‘/opt/kaltura/pentaho/pdi/libext’ not empty so not removed
    dpkg: warning: while removing kaltura-pentaho, directory ‘/opt/kaltura/pentaho/pdi/plugins/steps’ not empty so not removed
    Removing kaltura-php7-memcache (3.0.9-2) …
    /var/lib/dpkg/info/kaltura-php7-memcache.prerm: 9: /var/lib/dpkg/info/kaltura-php7-memcache.prerm: /opt/kaltura/bin/php7dismod: not found
    dpkg: error processing package kaltura-php7-memcache (–purge):
    subprocess installed pre-removal script returned error exit status 127
    dpkg: kaltura-base: dependency problems, but removing anyway as you requested:
    kaltura-batch depends on kaltura-base.

Removing kaltura-base (12.17.0-2) …
Purging configuration files for kaltura-base (12.17.0-2) …
dpkg: warning: while removing kaltura-base, directory ‘/opt/kaltura/log’ not empty so not removed
dpkg: warning: while removing kaltura-base, directory ‘/opt/kaltura/app/tests/monitoring’ not empty so not removed
dpkg: warning: while removing kaltura-base, directory ‘/opt/kaltura/app/admin_console/lib/Kaltura’ not empty so not removed
dpkg: warning: while removing kaltura-base, directory ‘/opt/kaltura/app/configurations/cron’ not empty so not removed
dpkg: warning: while removing kaltura-base, directory ‘/opt/kaltura/app/configurations/php’ not empty so not removed
dpkg: warning: while removing kaltura-base, directory ‘/opt/kaltura/app/configurations/apache/conf.d’ not empty so not removed
dpkg: warning: while removing kaltura-base, directory ‘/opt/kaltura/app/configurations/batch’ not empty so not removed
dpkg: warning: while removing kaltura-base, directory ‘/opt/kaltura/app/configurations/sphinx/populate’ not empty so not removed
dpkg: warning: while removing kaltura-base, directory ‘/opt/kaltura/app/configurations/logrotate’ not empty so not removed
dpkg: warning: while removing kaltura-base, directory ‘/opt/kaltura/app/configurations/monit/monit.d’ not empty so not removed
dpkg: warning: while removing kaltura-base, directory ‘/opt/kaltura/app/configurations/logstash’ not empty so not removed
dpkg: warning: while removing kaltura-base, directory ‘/opt/kaltura/app/cache’ not empty so not removed
dpkg: warning: while removing kaltura-base, directory ‘/opt/kaltura/app/var_console/lib/Kaltura’ not empty so not removed
dpkg: warning: while removing kaltura-base, directory ‘/opt/kaltura/app/api_v3/web’ not empty so not removed
dpkg: warning: while removing kaltura-base, directory ‘/opt/kaltura/app/batch/batches/Mailer’ not empty so not removed
dpkg: warning: while removing kaltura-base, directory ‘/opt/kaltura/app/deployment/base/scripts/init_content’ not empty so not removed
dpkg: warning: while removing kaltura-base, directory ‘/opt/kaltura/app/deployment/base/scripts/init_data’ not empty so not removed
dpkg: warning: while removing kaltura-base, directory ‘/opt/kaltura/app/plugins/monitor/nagios/config’ not empty so not removed
dpkg: warning: while removing kaltura-base, directory ‘/opt/kaltura/tmp’ not empty so not removed
dpkg: warning: while removing kaltura-base, directory ‘/opt/kaltura/web/content/entry’ not empty so not removed
dpkg: warning: while removing kaltura-base, directory ‘/opt/kaltura/web/content/batchfiles’ not empty so not removed
dpkg: warning: while removing kaltura-base, directory ‘/opt/kaltura/web/content/uploads’ not empty so not removed
dpkg: kaltura-ffmpeg: dependency problems, but removing anyway as you requested:
kaltura-batch depends on kaltura-ffmpeg.

Removing kaltura-ffmpeg (3.2-1+b1) …
dpkg: kaltura-ffmpeg-aux: dependency problems, but removing anyway as you requested:
kaltura-batch depends on kaltura-ffmpeg-aux; however:
Package kaltura-ffmpeg-aux is to be removed.

Removing kaltura-ffmpeg-aux (2.1.3-1) …
Removing kaltura-postinst (1.0.33-1+b1) …
dpkg: warning: while removing kaltura-postinst, directory ‘/opt/kaltura/bin’ not empty so not removed
Errors were encountered while processing:
** kaltura-batch**
** kaltura-php7-memcache**
E: Sub-process /usr/bin/dpkg returned an error code (1)
A package failed to install. Trying to recover:

Current status: 1 broken [+1].
root@684386-slrs01va9f1sv01:/opt/_installable/kaltura#

26

Hi @SrikarVR

You’ve got two errors here:

Removing kaltura-php7-memcache (3.0.9-2) ...
/var/lib/dpkg/info/kaltura-php7-memcache.prerm: 9: /var/lib/dpkg/info/kaltura-php7-memcache.prerm: /opt/kaltura/bin/php7dismod: not found
dpkg: error processing package kaltura-php7-memcache (--purge):

and

Stopping Batch Manager....
Service Batch Manager not running [ FAILED ]
invoke-rc.d: initscript kaltura-batch, action "stop" failed.
+ exit 1

The first issue, with removing kaltura-php7-memcache stems from the fact it’s prerm tries to call /opt/kaltura/bin/php7dismod which is provided by the kaltura-php7-common package. However, you never mentioned you’re trying to use the PHP 7 packages as far as I recall. We always discussed using the PHP 5 packages from the official distro repo, in which case, the PHP memcache extension should be supplied by php5-memcache and not kaltura-php7-memcache. Either way, to get over this problem and remove the package, edit /var/lib/dpkg/info/kaltura-php7-memcache.prerm and add:

exit 0

right after #!/bin/sh
This will cause the package to be removed without executing the prerm hook.

For batch, edit /var/lib/dpkg/info/kaltura-batch.prerm and also place exit 0 right after #!/bin/sh

After you do that and repeat the purge command, let’s make sure all is removed with:
# dpkg -l “kaltura”|grep ii
if no output is returned, then we’re good.
Then, remove the entire /opt/kaltura dir with:
# rm -rf /opt/kaltura
then, manually run:
# aptitude install php5-cli php5-memcache
and make sure:
# php -m|grep memcache
returns correctly with “memcache”.

Then re-run the installation script.

27

Hi Jess - Thanks so much for your guidance. After re-installation I see both Kaltura Admin console and Management console are accessible :slight_smile: . Apologies while I was creating this thread, somehow I missed to mention regd. php7, but as per your directions its now removed.

Kindly suggest on the next steps.

KAC & KMC:

kadminconsole.png1366×728 31.5 KB

KMC_login.png1366×728 26 KB

Output of installation script:

root@684386-slrs01va9f1sv01:/opt/_installable/kaltura# dpkg -l “kaltura”|grep ii
dpkg-query: no packages found matching kaltura
root@684386-slrs01va9f1sv01:/opt/_installable/kaltura# apachectl -t -DDUMP_VHOSTS
VirtualHost configuration:
root@684386-slrs01va9f1sv01:/opt/_installable/kaltura# clear
root@684386-slrs01va9f1sv01:/opt/_installable/kaltura# rm -rf /opt/kaltura
root@684386-slrs01va9f1sv01:/opt/_installable/kaltura# rm -rf /etc/kaltura.d
root@684386-slrs01va9f1sv01:/opt/_installable/kaltura# aptitude install php5-cli php5-memcache
No packages will be installed, upgraded, or removed.
0 packages upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
Need to get 0 B of archives. After unpacking 0 B will be used.

root@684386-slrs01va9f1sv01:/opt/_installable/kaltura# php -m|grep memcache
memcache
root@684386-slrs01va9f1sv01:/opt/_installable/kaltura# clear
root@684386-slrs01va9f1sv01:/opt/_installable/kaltura# wget http://installrepo.origin.kaltura.org/repo/apt/debian/install_kaltura_all_in_1.sh
–2017-06-19 12:00:00-- http://installrepo.origin.kaltura.org/repo/apt/debian/install_kaltura_all_in_1.sh
Resolving installrepo.origin.kaltura.org (installrepo.origin.kaltura.org)… 216.200.17.80
Connecting to installrepo.origin.kaltura.org (installrepo.origin.kaltura.org)|216.200.17.80|:80… connected.
HTTP request sent, awaiting response… 200 OK
Length: 1583 (1.5K) [application/x-sh]
Saving to: ‘install_kaltura_all_in_1.sh.1’

100%[==============================================================================================================================>] 1,583 --.-K/s in 0s

2017-06-19 12:00:00 (79.6 MB/s) - ‘install_kaltura_all_in_1.sh.1’ saved [1583/1583]

root@684386-slrs01va9f1sv01:/opt/_installable/kaltura# chmod +x install_kaltura_all_in_1.sh
root@684386-slrs01va9f1sv01:/opt/_installable/kaltura# ./install_kaltura_all_in_1.sh
–2017-06-19 12:00:31-- http://installrepo.kaltura.org/repo/apt/debian/kaltura-deb.gpg.key
Resolving installrepo.kaltura.org (installrepo.kaltura.org)… 52.84.7.91, 52.84.7.117, 52.84.7.207, …
Connecting to installrepo.kaltura.org (installrepo.kaltura.org)|52.84.7.91|:80… connected.
HTTP request sent, awaiting response… 200 OK
Length: 1727 (1.7K) [text/plain]
Saving to: ‘STDOUT’

100%[==============================================================================================================================>] 1,727 --.-K/s in 0s

2017-06-19 12:00:31 (182 MB/s) - written to stdout [1727/1727]

OK
/usr/bin/aptitude
Hit http://installrepo.kaltura.org lynx InRelease
Ign http://mirror.rackspace.com trusty InRelease
Hit http://security.ubuntu.com trusty-security InRelease
Hit http://stable.packages.cloudmonitoring.rackspace.com cloudmonitoring InRelease
Hit http://installrepo.kaltura.org lynx/main amd64 Packages
Get: 1 http://repo.pbis.beyondtrust.com pbiso InRelease [3,112 B]
Get: 2 http://mirror.rackspace.com trusty-updates InRelease [65.9 kB]
Hit http://security.ubuntu.com trusty-security/main Sources
Get: 3 http://repo.pbis.beyondtrust.com pbiso/main amd64 Packages [1,812 B]
Hit http://security.ubuntu.com trusty-security/restricted Sources
Hit http://stable.packages.cloudmonitoring.rackspace.com cloudmonitoring/main amd64 Packages
Hit http://security.ubuntu.com trusty-security/universe Sources
Get: 4 http://repo.pbis.beyondtrust.com pbiso/main i386 Packages [1,820 B]
Hit http://stable.packages.cloudmonitoring.rackspace.com cloudmonitoring/main i386 Packages
Hit http://security.ubuntu.com trusty-security/multiverse Sources
Hit http://mirror.rackspace.com trusty-backports InRelease
Hit http://security.ubuntu.com trusty-security/main amd64 Packages
Get: 5 http://ppa.launchpad.net trusty InRelease [15.5 kB]
Hit http://security.ubuntu.com trusty-security/restricted amd64 Packages
Hit http://mirror.rackspace.com trusty Release.gpg
Hit http://security.ubuntu.com trusty-security/universe amd64 Packages
Get: 6 http://mirror.rackspace.com trusty-updates/main Sources [400 kB]
Hit http://security.ubuntu.com trusty-security/multiverse amd64 Packages
Hit http://security.ubuntu.com trusty-security/main i386 Packages
Hit http://security.ubuntu.com trusty-security/restricted i386 Packages
Ign http://archive.ubuntu.com trusty InRelease
Hit http://security.ubuntu.com trusty-security/universe i386 Packages
Hit http://nginx.org trusty InRelease
Hit http://security.ubuntu.com trusty-security/multiverse i386 Packages
Get: 7 http://ppa.launchpad.net trusty/main amd64 Packages [3,397 B]
Hit http://security.ubuntu.com trusty-security/main Translation-en
Get: 8 http://archive.ubuntu.com trusty Release.gpg [933 B]
Get: 9 http://mirror.rackspace.com trusty-updates/restricted Sources [6,331 B]
Hit http://security.ubuntu.com trusty-security/multiverse Translation-en
Hit http://security.ubuntu.com trusty-security/restricted Translation-en
Hit http://nginx.org trusty/nginx amd64 Packages
Get: 10 http://ppa.launchpad.net trusty/main i386 Packages [3,397 B]
Hit http://security.ubuntu.com trusty-security/universe Translation-en
Get: 11 http://mirror.rackspace.com trusty-updates/universe Sources [184 kB]
Hit http://archive.ubuntu.com trusty Release
Hit http://nginx.org trusty/nginx i386 Packages
Ign http://stable.packages.cloudmonitoring.rackspace.com cloudmonitoring/main Translation-en_US
Get: 12 http://ppa.launchpad.net trusty/main Translation-en [1,556 B]
Hit http://archive.ubuntu.com trusty/multiverse amd64 Packages
Get: 13 http://mirror.rackspace.com trusty-updates/multiverse Sources [7,747 B]
Ign http://stable.packages.cloudmonitoring.rackspace.com cloudmonitoring/main Translation-en
Get: 14 http://mirror.rackspace.com trusty-updates/main amd64 Packages [987 kB]
Ign http://installrepo.kaltura.org lynx/main Translation-en_US
Hit http://archive.ubuntu.com trusty/multiverse i386 Packages
Ign http://installrepo.kaltura.org lynx/main Translation-en
Get: 15 http://mirror.rackspace.com trusty-updates/restricted amd64 Packages [17.1 kB]
Hit http://archive.ubuntu.com trusty/multiverse Translation-en
Get: 16 http://mirror.rackspace.com trusty-updates/universe amd64 Packages [417 kB]
Ign http://repo.pbis.beyondtrust.com pbiso/main Translation-en_US
Ign http://repo.pbis.beyondtrust.com pbiso/main Translation-en
Get: 17 http://mirror.rackspace.com trusty-updates/multiverse amd64 Packages [14.3 kB]
Get: 18 http://mirror.rackspace.com trusty-updates/main i386 Packages [943 kB]
Ign http://archive.ubuntu.com trusty/multiverse Translation-en_US
Get: 19 http://mirror.rackspace.com trusty-updates/restricted i386 Packages [16.9 kB]
Get: 20 http://mirror.rackspace.com trusty-updates/universe i386 Packages [418 kB]
Ign http://nginx.org trusty/nginx Translation-en_US
Ign http://nginx.org trusty/nginx Translation-en
Get: 21 http://mirror.rackspace.com trusty-updates/multiverse i386 Packages [14.6 kB]
Hit http://mirror.rackspace.com trusty-updates/main Translation-en
Hit http://mirror.rackspace.com trusty-updates/multiverse Translation-en
Hit http://mirror.rackspace.com trusty-updates/restricted Translation-en
Hit http://mirror.rackspace.com trusty-updates/universe Translation-en
Hit http://mirror.rackspace.com trusty-backports/main Sources
Hit http://mirror.rackspace.com trusty-backports/restricted Sources
Hit http://mirror.rackspace.com trusty-backports/universe Sources
Hit http://mirror.rackspace.com trusty-backports/multiverse Sources
Hit http://mirror.rackspace.com trusty-backports/main amd64 Packages
Hit http://mirror.rackspace.com trusty-backports/restricted amd64 Packages
Hit http://mirror.rackspace.com trusty-backports/universe amd64 Packages
Hit http://mirror.rackspace.com trusty-backports/multiverse amd64 Packages
Hit http://mirror.rackspace.com trusty-backports/main i386 Packages
Hit http://mirror.rackspace.com trusty-backports/restricted i386 Packages
Hit http://mirror.rackspace.com trusty-backports/universe i386 Packages
Hit http://mirror.rackspace.com trusty-backports/multiverse i386 Packages
Hit http://mirror.rackspace.com trusty-backports/main Translation-en
Hit http://mirror.rackspace.com trusty-backports/multiverse Translation-en
Hit http://mirror.rackspace.com trusty-backports/restricted Translation-en
Hit http://mirror.rackspace.com trusty-backports/universe Translation-en
Hit http://mirror.rackspace.com trusty Release
Hit http://mirror.rackspace.com trusty/main Sources
Hit http://mirror.rackspace.com trusty/restricted Sources
Hit http://mirror.rackspace.com trusty/universe Sources
Hit http://mirror.rackspace.com trusty/multiverse Sources
Hit http://mirror.rackspace.com trusty/main amd64 Packages
Hit http://mirror.rackspace.com trusty/restricted amd64 Packages
Hit http://mirror.rackspace.com trusty/universe amd64 Packages
Hit http://mirror.rackspace.com trusty/multiverse amd64 Packages
Ign http://packages.vmware.com precise InRelease
Hit http://mirror.rackspace.com trusty/main i386 Packages
Hit http://packages.vmware.com precise Release.gpg
Hit http://mirror.rackspace.com trusty/restricted i386 Packages
Hit http://packages.vmware.com precise Release
Hit http://mirror.rackspace.com trusty/universe i386 Packages
Hit http://packages.vmware.com precise/main amd64 Packages
Hit http://mirror.rackspace.com trusty/multiverse i386 Packages
Hit http://packages.vmware.com precise/main i386 Packages
Hit http://mirror.rackspace.com trusty/main Translation-en
Hit http://mirror.rackspace.com trusty/multiverse Translation-en
Hit http://mirror.rackspace.com trusty/restricted Translation-en
Hit http://mirror.rackspace.com trusty/universe Translation-en
Ign http://mirror.rackspace.com trusty/main Translation-en_US
Ign http://mirror.rackspace.com trusty/multiverse Translation-en_US
Ign http://mirror.rackspace.com trusty/restricted Translation-en_US
Ign http://mirror.rackspace.com trusty/universe Translation-en_US
Ign http://packages.vmware.com precise/main Translation-en_US
Ign http://packages.vmware.com precise/main Translation-en
Fetched 3,524 kB in 11s (319 kB/s)

No packages will be installed, upgraded, or removed.
0 packages upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
Need to get 0 B of archives. After unpacking 0 B will be used.

‘multiverse’ distribution component is already enabled for all sources.
No packages will be installed, upgraded, or removed.
0 packages upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
Need to get 0 B of archives. After unpacking 0 B will be used.

The following NEW packages will be installed:
kaltura-postinst
0 packages upgraded, 1 newly installed, 0 to remove and 1 not upgraded.
Need to get 76.3 kB of archives. After unpacking 330 kB will be used.
Get: 1 http://installrepo.kaltura.org/repo/apt/debian/ lynx/main kaltura-postinst all 1.0.33-1+b1 [76.3 kB]
Fetched 76.3 kB in 0s (590 kB/s)
Selecting previously unselected package kaltura-postinst.
(Reading database … 169259 files and directories currently installed.)
Preparing to unpack …/kaltura-postinst_1.0.33-1+b1_all.deb …
Unpacking kaltura-postinst (1.0.33-1+b1) …
Setting up kaltura-postinst (1.0.33-1+b1) …

The following NEW packages will be installed:
kaltura-base
0 packages upgraded, 1 newly installed, 0 to remove and 1 not upgraded.
Need to get 0 B/82.9 MB of archives. After unpacking 209 MB will be used.
Preconfiguring packages …
Selecting previously unselected package kaltura-base.
(Reading database … 169332 files and directories currently installed.)
Preparing to unpack …/kaltura-base_12.17.0-2_all.deb …
Unpacking kaltura-base (12.17.0-2) …
Setting up kaltura-base (12.17.0-2) …

  • apache2 is running
  • Stopping web server apache2 *
  • Stopping daemon monitor monit [ OK ]
  • Starting web server apache2 *

The following NEW packages will be installed:
kaltura-clipapp{a} kaltura-html5-studio kaltura-html5lib kaltura-kclip{a} kaltura-kcw{a} kaltura-kdp{a} kaltura-kdp3{a} kaltura-kdp3wrapper{a}
kaltura-kdpwrapper{a} kaltura-kmc{a} kaltura-krecord{a} kaltura-kupload{a} kaltura-widgets
0 packages upgraded, 13 newly installed, 0 to remove and 1 not upgraded.
Need to get 365 MB/556 MB of archives. After unpacking 877 MB will be used.
Get: 1 http://installrepo.kaltura.org/repo/apt/debian/ lynx/main kaltura-clipapp all 1.3-1+b2 [105 kB]
Get: 2 http://installrepo.kaltura.org/repo/apt/debian/ lynx/main kaltura-html5-studio all 2.0.9-1 [645 kB]
Get: 3 http://installrepo.kaltura.org/repo/apt/debian/ lynx/main kaltura-kclip all 1.1.2.1-1 [1,341 kB]
Get: 4 http://installrepo.kaltura.org/repo/apt/debian/ lynx/main kaltura-kcw all 2.2.4-1+b3 [1,524 kB]
Get: 5 http://installrepo.kaltura.org/repo/apt/debian/ lynx/main kaltura-kdp all 2.7.0-1 [1,939 kB]
Get: 6 http://installrepo.kaltura.org/repo/apt/debian/ lynx/main kaltura-kdp3 amd64 3.9.9-1+b3 [1,256 kB]
Get: 7 http://installrepo.kaltura.org/repo/apt/debian/ lynx/main kaltura-kdp3wrapper all 37-1 [5,134 B]
Get: 8 http://installrepo.kaltura.org/repo/apt/debian/ lynx/main kaltura-kdpwrapper all 11-1 [4,714 B]
Get: 9 http://installrepo.kaltura.org/repo/apt/debian/ lynx/main kaltura-kmc all 5.42.0-2 [358 MB]
Get: 10 http://installrepo.kaltura.org/repo/apt/debian/ lynx/main kaltura-krecord all 1.7-1 [98.9 kB]
Get: 11 http://installrepo.kaltura.org/repo/apt/debian/ lynx/main kaltura-kupload all 1.2.16-1 [96.4 kB]
Get: 12 http://installrepo.kaltura.org/repo/apt/debian/ lynx/main kaltura-widgets all 10.9.0-1+b4 [1,230 B]
Fetched 365 MB in 16s (21.7 MB/s)
Selecting previously unselected package kaltura-clipapp.
(Reading database … 186077 files and directories currently installed.)
Preparing to unpack …/kaltura-clipapp_1.3-1+b2_all.deb …
Unpacking kaltura-clipapp (1.3-1+b2) …
Selecting previously unselected package kaltura-html5-studio.
Preparing to unpack …/kaltura-html5-studio_2.0.9-1_all.deb …
Unpacking kaltura-html5-studio (2.0.9-1) …
Selecting previously unselected package kaltura-html5lib.
Preparing to unpack …/kaltura-html5lib_2.57-1_all.deb …
Unpacking kaltura-html5lib (2.57-1) …
Selecting previously unselected package kaltura-kclip.
Preparing to unpack …/kaltura-kclip_1.1.2.1-1_all.deb …
Unpacking kaltura-kclip (1.1.2.1-1) …
Selecting previously unselected package kaltura-kcw.
Preparing to unpack …/kaltura-kcw_2.2.4-1+b3_all.deb …
Unpacking kaltura-kcw (2.2.4-1+b3) …
Selecting previously unselected package kaltura-kdp.
Preparing to unpack …/kaltura-kdp_2.7.0-1_all.deb …
Unpacking kaltura-kdp (2.7.0-1) …
Selecting previously unselected package kaltura-kdp3.
Preparing to unpack …/kaltura-kdp3_3.9.9-1+b3_amd64.deb …
Unpacking kaltura-kdp3 (3.9.9-1+b3) …
Selecting previously unselected package kaltura-kdp3wrapper.
Preparing to unpack …/kaltura-kdp3wrapper_37-1_all.deb …
Unpacking kaltura-kdp3wrapper (37-1) …
Selecting previously unselected package kaltura-kdpwrapper.
Preparing to unpack …/kaltura-kdpwrapper_11-1_all.deb …
Unpacking kaltura-kdpwrapper (11-1) …
Selecting previously unselected package kaltura-kmc.
Preparing to unpack …/kaltura-kmc_5.42.0-2_all.deb …
Unpacking kaltura-kmc (5.42.0-2) …
Selecting previously unselected package kaltura-krecord.
Preparing to unpack …/kaltura-krecord_1.7-1_all.deb …
Unpacking kaltura-krecord (1.7-1) …
Selecting previously unselected package kaltura-kupload.
Preparing to unpack …/kaltura-kupload_1.2.16-1_all.deb …
Unpacking kaltura-kupload (1.2.16-1) …
Selecting previously unselected package kaltura-widgets.
Preparing to unpack …/kaltura-widgets_10.9.0-1+b4_all.deb …
Unpacking kaltura-widgets (10.9.0-1+b4) …
Setting up kaltura-clipapp (1.3-1+b2) …
Setting up kaltura-html5-studio (2.0.9-1) …
Setting up kaltura-html5lib (2.57-1) …
Setting up kaltura-kclip (1.1.2.1-1) …
Setting up kaltura-kcw (2.2.4-1+b3) …
Setting up kaltura-kdp (2.7.0-1) …
Setting up kaltura-kdp3 (3.9.9-1+b3) …
Setting up kaltura-kdp3wrapper (37-1) …
Setting up kaltura-kdpwrapper (11-1) …
Setting up kaltura-kmc (5.42.0-2) …
Setting up kaltura-krecord (1.7-1) …
Setting up kaltura-kupload (1.2.16-1) …
Setting up kaltura-widgets (10.9.0-1+b4) …

The following NEW packages will be installed:
kaltura-ffmpeg{a} kaltura-ffmpeg-aux{a} kaltura-front
0 packages upgraded, 3 newly installed, 0 to remove and 1 not upgraded.
Need to get 31.8 MB of archives. After unpacking 50.2 kB will be used.
Get: 1 http://installrepo.kaltura.org/repo/apt/debian/ lynx/main kaltura-ffmpeg amd64 3.2-1+b1 [18.8 MB]
Get: 2 http://installrepo.kaltura.org/repo/apt/debian/ lynx/main kaltura-ffmpeg-aux amd64 2.1.3-1 [13.1 MB]
Get: 3 http://installrepo.kaltura.org/repo/apt/debian/ lynx/main kaltura-front all 12.17.0-1 [5,560 B]
Fetched 31.8 MB in 3s (10.2 MB/s)
Preconfiguring packages …
Selecting previously unselected package kaltura-ffmpeg.
(Reading database … 235894 files and directories currently installed.)
Preparing to unpack …/kaltura-ffmpeg_3.2-1+b1_amd64.deb …
Unpacking kaltura-ffmpeg (3.2-1+b1) …
Selecting previously unselected package kaltura-ffmpeg-aux.
Preparing to unpack …/kaltura-ffmpeg-aux_2.1.3-1_amd64.deb …
Unpacking kaltura-ffmpeg-aux (2.1.3-1) …
Selecting previously unselected package kaltura-front.
Preparing to unpack …/kaltura-front_12.17.0-1_all.deb …
Unpacking kaltura-front (12.17.0-1) …
Setting up kaltura-ffmpeg (3.2-1+b1) …
Setting up kaltura-ffmpeg-aux (2.1.3-1) …
Setting up kaltura-front (12.17.0-1) …
ERROR: No site found matching zzzkaltura*!
Enabling site zzzkaltura.
To activate the new configuration, you need to run:
service apache2 reload
Enabling site apps.
To activate the new configuration, you need to run:
service apache2 reload
Enabling site var.
To activate the new configuration, you need to run:
service apache2 reload
Enabling site admin.
To activate the new configuration, you need to run:
service apache2 reload

  • Reloading web server apache2 *
  • Restarting daemon monitor monit /etc/monit/conf.d/batch.rc:3: Warning: Program does not exist: ‘/etc/init.d/kaltura-batch’
    /etc/monit/conf.d/batch.rc:4: Warning: Program does not exist: ‘/etc/init.d/kaltura-batch’
    /etc/monit/conf.d/batch.rc:14: Warning: Program does not exist: ‘/etc/init.d/kaltura-batch’
    [ OK ]
    Processing triggers for libc-bin (2.19-0ubuntu6.11) …

The following NEW packages will be installed:
kaltura-sphinx
0 packages upgraded, 1 newly installed, 0 to remove and 1 not upgraded.
Need to get 5,549 kB of archives. After unpacking 15.5 MB will be used.
Get: 1 http://installrepo.kaltura.org/repo/apt/debian/ lynx/main kaltura-sphinx amd64 2.2.1-4 [5,549 kB]
Fetched 5,549 kB in 2s (1,891 kB/s)
Selecting previously unselected package kaltura-sphinx.
(Reading database … 236363 files and directories currently installed.)
Preparing to unpack …/kaltura-sphinx_2.2.1-4_amd64.deb …
Unpacking kaltura-sphinx (2.2.1-4) …
Processing triggers for ureadahead (0.100.0-16) …
Setting up kaltura-sphinx (2.2.1-4) …
Adding system startup for /etc/init.d/kaltura-sphinx …
/etc/rc0.d/K20kaltura-sphinx -> …/init.d/kaltura-sphinx
/etc/rc1.d/K20kaltura-sphinx -> …/init.d/kaltura-sphinx
/etc/rc6.d/K20kaltura-sphinx -> …/init.d/kaltura-sphinx
/etc/rc2.d/S20kaltura-sphinx -> …/init.d/kaltura-sphinx
/etc/rc3.d/S20kaltura-sphinx -> …/init.d/kaltura-sphinx
/etc/rc4.d/S20kaltura-sphinx -> …/init.d/kaltura-sphinx
/etc/rc5.d/S20kaltura-sphinx -> …/init.d/kaltura-sphinx
Adding system startup for /etc/init.d/kaltura-populate …
/etc/rc0.d/K20kaltura-populate -> …/init.d/kaltura-populate
/etc/rc1.d/K20kaltura-populate -> …/init.d/kaltura-populate
/etc/rc6.d/K20kaltura-populate -> …/init.d/kaltura-populate
/etc/rc2.d/S20kaltura-populate -> …/init.d/kaltura-populate
/etc/rc3.d/S20kaltura-populate -> …/init.d/kaltura-populate
/etc/rc4.d/S20kaltura-populate -> …/init.d/kaltura-populate
/etc/rc5.d/S20kaltura-populate -> …/init.d/kaltura-populate

  • Starting daemon monitor monit /etc/monit/conf.d/batch.rc:3: Warning: Program does not exist: ‘/etc/init.d/kaltura-batch’
    /etc/monit/conf.d/batch.rc:4: Warning: Program does not exist: ‘/etc/init.d/kaltura-batch’
    /etc/monit/conf.d/batch.rc:14: Warning: Program does not exist: ‘/etc/init.d/kaltura-batch’
    [ OK ]
    Processing triggers for ureadahead (0.100.0-16) …
    Processing triggers for libc-bin (2.19-0ubuntu6.11) …

The following NEW packages will be installed:
kaltura-db
0 packages upgraded, 1 newly installed, 0 to remove and 1 not upgraded.
Need to get 4,444 B of archives. After unpacking 8,192 B will be used.
Get: 1 http://installrepo.kaltura.org/repo/apt/debian/ lynx/main kaltura-db all 12.15.0-1+b4 [4,444 B]
Fetched 4,444 B in 0s (17.4 kB/s)
Preconfiguring packages …
Selecting previously unselected package kaltura-db.
(Reading database … 236384 files and directories currently installed.)
Preparing to unpack …/kaltura-db_12.15.0-1+b4_all.deb …
Unpacking kaltura-db (12.15.0-1+b4) …
Setting up kaltura-db (12.15.0-1+b4) …
Checking MySQL version…

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
Generating UI confs…
Generating Studio UI confs…

  • Restarting daemon monitor monit /etc/monit/conf.d/batch.rc:3: Warning: Program does not exist: ‘/etc/init.d/kaltura-batch’
    /etc/monit/conf.d/batch.rc:4: Warning: Program does not exist: ‘/etc/init.d/kaltura-batch’
    /etc/monit/conf.d/batch.rc:14: Warning: Program does not exist: ‘/etc/init.d/kaltura-batch’
    [ OK ]

The following NEW packages will be installed:
kaltura-batch
0 packages upgraded, 1 newly installed, 0 to remove and 1 not upgraded.
Need to get 4,064 B of archives. After unpacking 8,192 B will be used.
Get: 1 http://installrepo.kaltura.org/repo/apt/debian/ lynx/main kaltura-batch all 12.17.0-1 [4,064 B]
Fetched 4,064 B in 0s (12.5 kB/s)
Selecting previously unselected package kaltura-batch.
(Reading database … 236384 files and directories currently installed.)
Preparing to unpack …/kaltura-batch_12.17.0-1_all.deb …
Unpacking kaltura-batch (12.17.0-1) …
Processing triggers for ureadahead (0.100.0-16) …
Setting up kaltura-batch (12.17.0-1) …
Adding system startup for /etc/init.d/kaltura-batch …
/etc/rc0.d/K20kaltura-batch -> …/init.d/kaltura-batch
/etc/rc1.d/K20kaltura-batch -> …/init.d/kaltura-batch
/etc/rc6.d/K20kaltura-batch -> …/init.d/kaltura-batch
/etc/rc2.d/S20kaltura-batch -> …/init.d/kaltura-batch
/etc/rc3.d/S20kaltura-batch -> …/init.d/kaltura-batch
/etc/rc4.d/S20kaltura-batch -> …/init.d/kaltura-batch
/etc/rc5.d/S20kaltura-batch -> …/init.d/kaltura-batch

  • Reloading web server apache2 *
    Starting Batch Manager…
    Batch Manager started with PID [ OK ]
  • Starting daemon monitor monit [ OK ]

The following NEW packages will be installed:
kaltura-dwh kaltura-pentaho{a}
0 packages upgraded, 2 newly installed, 0 to remove and 1 not upgraded.
Need to get 299 MB of archives. After unpacking 490 MB will be used.
Get: 1 http://installrepo.kaltura.org/repo/apt/debian/ lynx/main kaltura-pentaho amd64 4.2.1+b2 [240 MB]
Get: 2 http://installrepo.kaltura.org/repo/apt/debian/ lynx/main kaltura-dwh amd64 12.14.0-1+b1 [59.8 MB]
Fetched 299 MB in 13s (22.9 MB/s)
Preconfiguring packages …
Selecting previously unselected package kaltura-pentaho.
(Reading database … 236385 files and directories currently installed.)
Preparing to unpack …/kaltura-pentaho_4.2.1+b2_amd64.deb …
Unpacking kaltura-pentaho (4.2.1+b2) …
Selecting previously unselected package kaltura-dwh.
Preparing to unpack …/kaltura-dwh_12.14.0-1+b1_amd64.deb …
Unpacking kaltura-dwh (12.14.0-1+b1) …
Setting up kaltura-pentaho (4.2.1+b2) …
Setting up kaltura-dwh (12.14.0-1+b1) …
Deploying analytics warehouse DB, please be patient as this may take a while…
Output is logged to /opt/kaltura/dwh/logs/dwh_setup.log.

sending incremental file list
MySQLInserter/
MySQLInserter/TOP.png
MySQLInserter/mysqlinserter.jar
MySQLInserter/plugin.xml

sent 2,653,098 bytes received 77 bytes 5,306,350.00 bytes/sec
total size is 2,652,205 speedup is 1.00
sending incremental file list
MappingFieldRunner/
MappingFieldRunner/MAP.png
MappingFieldRunner/mappingfieldrunner.jar
MappingFieldRunner/plugin.xml

sent 90,692 bytes received 77 bytes 181,538.00 bytes/sec
total size is 90,413 speedup is 1.00
sending incremental file list
GetFTPFileNames/
GetFTPFileNames/FTP.png
GetFTPFileNames/getftpfilenames.jar
GetFTPFileNames/plugin.xml

sent 7,318,633 bytes received 77 bytes 14,637,420.00 bytes/sec
total size is 7,316,592 speedup is 1.00
sending incremental file list
FetchFTPFile/
FetchFTPFile/FTP.png
FetchFTPFile/fetchftpfile.jar
FetchFTPFile/plugin.xml

sent 5,791,135 bytes received 77 bytes 11,582,424.00 bytes/sec
total size is 5,789,476 speedup is 1.00
sending incremental file list
DimLookup/
DimLookup/CMB.png
DimLookup/lookup.jar
DimLookup/plugin.xml

sent 3,697,148 bytes received 77 bytes 7,394,450.00 bytes/sec
total size is 3,696,010 speedup is 1.00
sending incremental file list
UserAgentUtils.jar
ksDecrypt.jar

sent 34,747 bytes received 54 bytes 69,602.00 bytes/sec
total size is 34,569 speedup is 0.99
current version 5999
DWH configured.

The following NEW packages will be installed:
kaltura-nginx
0 packages upgraded, 1 newly installed, 0 to remove and 1 not upgraded.
Need to get 805 kB of archives. After unpacking 1,900 kB will be used.
Get: 1 http://installrepo.kaltura.org/repo/apt/debian/ lynx/main kaltura-nginx amd64 1.12-3 [805 kB]
Fetched 805 kB in 1s (503 kB/s)
Preconfiguring packages …
Selecting previously unselected package kaltura-nginx.
(Reading database … 248244 files and directories currently installed.)
Preparing to unpack …/kaltura-nginx_1.12-3_amd64.deb …
Unpacking kaltura-nginx (1.12-3) …
Processing triggers for ureadahead (0.100.0-16) …
Setting up kaltura-nginx (1.12-3) …
Adding system startup for /etc/init.d/kaltura-nginx …
/etc/rc0.d/K20kaltura-nginx -> …/init.d/kaltura-nginx
/etc/rc1.d/K20kaltura-nginx -> …/init.d/kaltura-nginx
/etc/rc6.d/K20kaltura-nginx -> …/init.d/kaltura-nginx
/etc/rc2.d/S20kaltura-nginx -> …/init.d/kaltura-nginx
/etc/rc3.d/S20kaltura-nginx -> …/init.d/kaltura-nginx
/etc/rc4.d/S20kaltura-nginx -> …/init.d/kaltura-nginx
/etc/rc5.d/S20kaltura-nginx -> …/init.d/kaltura-nginx
Restarting nginx: nginx.
Processing triggers for ureadahead (0.100.0-16) …
Processing triggers for libc-bin (2.19-0ubuntu6.11) …

Starting nginx: nginx.
root@684386-slrs01va9f1sv01:/opt/_installable/kaltura#

Regards - Srikar

28

Hi @SrikarVR,

Please see what I wrote before:

Thanks,

29

Hi Jess - Thanks for your continued support. As suggested I created the accounts for Publisher but could not find email getting sent to the recipients, due to which password cannot be updated. I checked that “postfix” is not installed in our system and mail command when executed does not give any error/message (strangely no service seems to be listening on port 25. No result for > netstat -plnt | grep 25).

mail -s test -r kaltura.admin@domain.com srikar.vr@domain.com < /etc/issue

However, the error message from > tail -25 /var/log/mail.log is as below. Please can we configure an external SMTP server for Kaltura to send mail notifications? I have the details of an external SMTP server which is already been used in a different application and is working.

root@684386-slrs01va9f1sv01:/etc# tail -10 /var/log/mail.log
Jun 20 13:56:04 684386-slrs01va9f1sv01 dma[9ef0.e43910]: connect to amrxv1004.domain.com [10.10.160.64] failed: Connection refused
Jun 20 13:56:09 684386-slrs01va9f1sv01 dma[7b0.1ea0910]: connect to amrxv1004.domain.com [10.10.160.64] failed: Connection refused
Jun 20 13:56:09 684386-slrs01va9f1sv01 dma[9ee5.1450910]: connect to amrxv1003.domain.com [10.10.160.63] failed: Connection refused
Jun 20 13:56:11 684386-slrs01va9f1sv01 dma[9ef2.1ff6910]: connect to amrxv1004.domain.com [10.10.160.64] failed: Connection refused
Jun 20 13:58:26 684386-slrs01va9f1sv01 dma[10a0]: new mail from user=root uid=8 envelope_from=kaltura.admin@domain.com
Jun 20 13:58:26 684386-slrs01va9f1sv01 dma[10a0]: mail to=srikar.vr@domain.com queued as 10a0.11638a0
Jun 20 13:58:26 684386-slrs01va9f1sv01 dma[10a0.11638a0]: trying delivery
Jun 20 13:58:26 684386-slrs01va9f1sv01 dma[10a0.11638a0]: trying remote delivery to amrxv1003.domain.com [10.10.160.63] pref 10
Jun 20 13:58:49 684386-slrs01va9f1sv01 dma[10a0.11638a0]: connect to amrxv1003.domain.com [10.10.160.63] failed: Connection refused
Jun 20 13:58:49 684386-slrs01va9f1sv01 dma[10a0.11638a0]: trying remote delivery to amrxv1004.domain.com [10.10.160.64] pref 10

Regards - Srikar

30

Hello @SrikarVR,

Which MTA to use and how to configure it is entirely up to you. For the platform, it does not matter at all, so long as you have a properly configured MTA [Mail Transfer Agent] listening on port 25.
You can manually set a password for the partner by going to Admin Console->Publishers->Your Partner->KMC Users->Action->reset password

However, you really should fix your MTA so that emails are sent since the password setting email is not the only type of email the platform sends.

31

Hi Jess - I have been able to reset the passwords of Publisher accounts created. Please can you answer my last question on this thread? We can have this thread closed with that.

Where do we specify the SMTP details for Kaltura to send emails? I do not find details like similar ones mentioned below in /opt/kaltura/app/configurations/local.ini. Is there any other config file where similar details can be mentioned for Kaltura.

Outbound Email Configuration

mail.host=email-smtp.host
mail.port=25
mail.username=uname
mail.password=pwd
mail.encoding=UTF-8
mail.from.enabled=false
mail.from.default=kaltura.admin@domain.com
mail.smtp.auth=true
mail.smtp.starttls.enable=true
mail.protocol=smtp

Thanks so much for your support so far. It is a great learning I got from this thread :slight_smile: :slight_smile: . Appreciate your support !!!. For my further queries/issues, I shall open new threads.

Regards - Srikar

32

Hello @SrikarVR,

First, thanks for the kind words and of course, you’re welcome.

As I explained before, the Kaltura Server does not require, nor does it accept the SMTP server info. The Kaltura Server is written in PHP where, the mail() function implementation on UNIX, by default, simply uses whatever MTA is running on the machine.

Therefore, you need to make sure the machine is running an MTA. From your output, I can see that it does [though I don’t know which]. The mail log says:

Jun 20 13:56:09 684386-slrs01va9f1sv01 dma[7b0.1ea0910]: connect to amrxv1004.domain.com [10.10.160.64] failed: Connection refused

This of course makes perfect sense because there really isn’t such a domain. I don’t know if you masked the actual domain intentionally or not but either way, you need to make sure your MTA is properly configured.
There are a lot of available MTAs for Linux, to name just a few: Postfix, Sendmail and Exim…

The configuration varies according to the one you choose to use. Most MTAs can either send the emails themselves directly or relay it to an external SMTP.

Which MTA to use is up to you. At Kaltura, for our own machines, we use Postfix.
Here is a basic configuration example for /etc/postfix/main.cf:

smtpd_banner = $myhostname ESMTP $mail_name (Ubuntu)
biff = no

# appending .domain is the MUA's job.
append_dot_mydomain = no

# Uncomment the next line to generate "delayed mail" warnings
#delay_warning_time = 4h

readme_directory = no

# TLS parameters
smtpd_tls_cert_file=/etc/ssl/certs/ssl-cert-snakeoil.pem
smtpd_tls_key_file=/etc/ssl/private/ssl-cert-snakeoil.key
smtpd_use_tls=yes
smtpd_tls_session_cache_database = btree:${data_directory}/smtpd_scache
smtp_tls_session_cache_database = btree:${data_directory}/smtp_scache

# See /usr/share/doc/postfix/TLS_README.gz in the postfix-doc package for
# information on enabling SSL in the smtp client.
smtp_generic_maps = hash:/etc/postfix/generic
myhostname = YOUR_HOSTNAME
alias_maps = hash:/etc/aliases
alias_database = hash:/etc/aliases
myorigin = /etc/mailname
mydestination =  localhost.localdomain, localhost
mynetworks = 127.0.0.0/8 [::ffff:127.0.0.0]/104 [::1]/128
mailbox_size_limit = 0
recipient_delimiter = +
inet_interfaces = all

smtp_sasl_auth_enable = yes
smtp_sasl_password_maps = static:MY_SMTP_USER:MY_SMTP_PASSWD
smtpd_use_tls = yes
smtp_sasl_security_options = noanonymous
smtp_tls_security_level = may
smtp_tls_CAfile = /etc/ssl/certs/ca-certificates.crt
header_size_limit = 4096000
relayhost = [mysmtp.example.com]:587

This will cause Postfix to relay all emails to mysmtp.example.com, passing MY_SMTP_USER and MY_SMTP_PASSWD as the user and passwd.
Of course, you need to replace these with actual values as well as YOUR_HOSTNAME.

You can opt not to relay and send directly from Postfix [you will be prompted about that when installing the Postfix deb package] but I recommend you use a valid, qualified SMTP to avoid messages being marked as spam. Postfix can also be configured that way, of course, just need to make sure the DNS records for the host are in order.

From the application itself you can control which email and display name will be set in the FROM header when messages are sent, the relevant directives are in /opt/kaltura/app/configurations/local.ini:

default_email = customer_service@jessex
default_email_name = "Kaltura Video Platform" Automated Response
partner_registration_confirmation_email = registration_confirmation@jessex
partner_notification_email = customer_service@jessex
partner_change_email_email = customer_service@jessex
partner_change_email_name = "Kaltura Video Platform" Automated Response
purchase_package_email = customer_service@jessex
batch_download_video_sender_email = download_video@jessex
batch_flatten_video_sender_email = download_video@jessex
batch_notification_sender_email = notifications@jessex  
batch_alert_email = alert@jessex  
bulk_notification_sender_email = notifications@jessex  
live_report_sender_email = live_report@jessex

After editing, be sure to reload Apache.

33

Hi Jess - Thank you for this detailed information!

I understand now what to get next done for email notifications to work in my Kaltura setup. I shall work with my admin team to gather required information and do the required configurations. Hope this thread would also come useful for many other members like me who are working on the setup.

Have a great day ahead :+1:…Great support :clap:

Regards - Srikar

34

Most welcome && happy to help, @SrikarVR:)