KMC issues with Docker image

I’m trying to get Kaltura’s KMC page to load I have been trying over and over again throughout the day and havent had any luck. I had the flash issues earlier but resolved that by using “localhost” host name, after which now I render a blank page when I browse to it (tried in FF, Chrome, Safari) when I look at browser console logs I see the following:

Uncaught SyntaxError: Unexpected token <
A Parser-blocking, cross-origin script, http://www.google-analytics.com/ga.js,
is invoked via document.write.     This may be blocked by the browser if the device has poor network connectivity. See https://www.chromestatus.com/feature/5718547946799104 for more details.
Uncaught ReferenceError: logout is not defined
at <anonymous>:1:1

I have tried reseting the install by doing the following:

docker exec -i -t kaltura /root/install/install.sh
rm /opt/kaltura/app/base-config.lock
/opt/kaltura/bin/kaltura-base-config.sh

I have also tried removing the docker container completely and reinstalling (twice):

docker stop kaltura && docker rm Kaltura
docker run -d --name=kaltura -p 80:80 -p 443:443 -p 1935:1935 kaltura/server
docker exec -i -t kaltura /root/install/install.sh password

Here is my configuration file:

TIME_ZONE="Etc/UTC"
KALTURA_FULL_VIRTUAL_HOST_NAME="localhost"
KALTURA_VIRTUAL_HOST_NAME="localhost"
DB1_HOST="127.0.0.1"
DB1_PORT="3306"
DB1_PASS="kX3QD7WZ8DzJ6st"
DB1_NAME="kaltura"
DB1_USER="kaltura"
SERVICE_URL="http://localhost"
SPHINX_SERVER1="127.0.0.1"
SPHINX_SERVER2="127.0.0.1"
DWH_HOST="127.0.0.1"
DWH_PORT="3306"
ADMIN_CONSOLE_ADMIN_MAIL=“email@gmail.com"
ADMIN_CONSOLE_PASSWORD=“password"
CDN_HOST=“localhost"
KALTURA_VIRTUAL_HOST_PORT="80"
SUPER_USER="root"
SUPER_USER_PASSWD=“password"
ENVIRONMENT_NAME="Kaltura Video Platform"
DWH_PASS="kX3QD7RRZ8DzJ6st"
PROTOCOL="http"
PRIMARY_MEDIA_SERVER_HOST="833703453f2a"
USER_CONSENT="0"
CONTACT_MAIL="NO"
VOD_PACKAGER_HOST="833703453f2a"
VOD_PACKAGER_PORT="88"
IP_RANGE="0.0.0.0-255.255.255.255"
WWW_HOST="localhost"

Please help!! I just want to get Kaltura running just once so that I can evaluate it.

Hello,

In the shell on the server, run:
# . /etc/profile.d/kaltura*base.sh
# kaltlog

Then make the request and look at the log to find the error.
kaltlog is an alias that uses grep to find erroneous patterns in the logs so it should provide an initial direction as to what the issue is. Also, take a look at the browser’s dev tools, under the “Network” tab to see if there are failing requests, HTTP 404 or 500…

Thanks,

@jess thanks for the reply!

Here is the stack trace:

==> /opt/kaltura/log/kaltura_apache_errors.log <==
[Thu Feb 23 05:13:02 2017] [error] [client 172.17.0.1] File does not exist: /opt/kaltura/web/content/docs/pdf, referer: http://localhost/index.php/kmc/kmc1?partner_id=-2&subp_id=-200&ks=YzRiY2RhZDBlNjE1NDk1OTRkMDEyZDRkMTFhZWM0NGQzMDQzNjAzMHwtMjstMjsxNDg3ODg1NjgyOzI7MTQ4Nzc5OTI4Mi42NDM0O2lhbXBpZXJyZWFuZHJlQGdtYWlsLmNvbTtkaXNhYmxlZW50aXRsZW1lbnQ7Ow==&uid=&screen_name=&email=


==> /opt/kaltura/log/kaltura_scripts.log <==
Stack trace:
#0 /opt/kaltura/app/alpha/scripts/utils/permissions/addPermissionsAndItems.php(253): KalturaLog::err(‘Skipping call t…’)

2017-02-23 05:00:37 [1568599569] [addPermissionsAndItems.php] [addItemToPermissions] ALERT: exception ‘Exception’ with message ‘ERROR - Permission name [BATCH_BASE] for partner [0] not found in database - skipping!’ in /opt/kaltura/app/infra/log/KalturaLog.php:65
Stack trace:
#0 /opt/kaltura/app/alpha/scripts/utils/permissions/addPermissionsAndItems.php(284): KalturaLog::alert(‘ERROR - Permiss…’)

Suggestions on what this means?

Hi @ifeatu,

I believe I know what happened. You first configuration attempt failed, leaving a half baked DB, hence the

2017-02-23 05:00:37 [1568599569] [addPermissionsAndItems.php] [addItemToPermissions] ALERT: exception 'Exception' with message 'ERROR - Permission name [BATCH_BASE] for partner [0] not found in database - skipping!' in /opt/kaltura/app/infra/log/KalturaLog.php:65

error.

I recommend you drop the existing DB with:
# /opt/kaltura/bin/kaltura-drop-db.sh
and then rerun the install.sh script from outside or, from within the container, run:
# /opt/kaltura/bin/kaltura-config-all.sh /root/install/config.ans
which is basically what install.sh does, after it sets up MySQL and other things.

@jess ok so I watched the entire install from start to finish…I didnt see one hiccup…but then right after everything completed I check kaltlog and i see this again:

==> /opt/kaltura/log/kaltura_scripts.log <==
Stack trace:
#0 /opt/kaltura/app/alpha/scripts/utils/permissions/addPermissionsAndItems.php(253): KalturaLog::err(‘Skipping call t…’)

2017-02-23 16:10:56 [1760061325] [addPermissionsAndItems.php] [addItemToPermissions] ALERT: exception ‘Exception’ with message ‘ERROR - Permission name [BATCH_BASE] for partner [0] not found in database - skipping!’ in /opt/kaltura/app/infra/log/KalturaLog.php:65
Stack trace:
#0 /opt/kaltura/app/alpha/scripts/utils/permissions/addPermissionsAndItems.php(284): KalturaLog::alert(‘ERROR - Permiss…’)

Did you run /opt/kaltura/bin/kaltura-drop-db.sh?

@jess yes. In fact I dropped the whole container and rebuilt:
docker stop kaltura && docker rm kaltura
docker run -d --name=kaltura -p 80:80 -p 443:443 -p 1935:1935 kaltura/server
docker exec -i -t kaltura /root/install/install.sh password

@jess More Errors:


2017-02-23 17:56:48 [0.000216] [::1] [1580789400] [6] [API] [KalturaFrontController->getExceptionObject] ALERT: exception ‘PropelException’ with message ‘Unable to open PDO connection dsn[mysql:host=127.0.0.1;port=3306;dbname=kaltura;] user[kaltura] password[lnKhMZfa6VGfZLt] [wrapped: SQLSTATE[28000] [1045] Access denied for user ‘kaltura’@‘localhost’ (using password: YES)]’ in /opt/kaltura/app/vendor/propel/Propel.php:649
Stack trace:
#0 /opt/kaltura/app/vendor/propel/Propel.php(532): Propel::initConnection(Array, ‘propel’)

==> /opt/kaltura/log/batch/kschedulehelper-0-2017-02-23.err.log <==
PHP Fatal error: Uncaught exception ‘KalturaException’ with message ‘Internal database error’ in /opt/kaltura/app/batch/client/KalturaClientBase.php:894
Stack trace:
#0 /opt/kaltura/app/batch/client/KalturaClient.php(4694): KalturaClientBase->throwExceptionIfError(Array)

2017-02-23 17:57:02 [0.000285] [::1] [407140390] [6] [API] [KalturaFrontController->getExceptionObject] ALERT: exception ‘PropelException’ with message ‘Unable to open PDO connection dsn[mysql:host=127.0.0.1;port=3306;dbname=kaltura;] user[kaltura] password[lnKhMZfa6VGfZLt] [wrapped: SQLSTATE[28000] [1045] Access denied for user ‘kaltura’@‘localhost’ (using password: YES)]’ in /opt/kaltura/app/vendor/propel/Propel.php:649
Stack trace:
#0 /opt/kaltura/app/vendor/propel/Propel.php(532): Propel::initConnection(Array, ‘propel’)

[2017-02-23 17:57:01]failed to connect [1] [0.0015511512756348] mysql:host=127.0.0.1;port=3306;dbname=kaltura_sphinx_log;
PHP Fatal error: Uncaught exception ‘PropelException’ with message ‘Unable to open PDO connection dsn[mysql:host=127.0.0.1;port=3306;dbname=kaltura_sphinx_log;] user[kaltura] password[lnKhMZfa6VGfZLt] [wrapped: SQLSTATE[28000] [1045] Access denied for user ‘kaltura’@‘localhost’ (using password: YES)]’ in /opt/kaltura/app/vendor/propel/Propel.php:649
Stack trace:
#0 /opt/kaltura/app/vendor/propel/Propel.php(532): Propel::initConnection(Array, ‘sphinx_log_read’)

2017-02-23 17:57:02 [0.000078] [282577189] [11] [BATCH] [KalturaClientBase->doQueue] INFO: execution time for [http://localhost/api_v3/service/dropfolder_dropfolder/action/list]: [0.011632919311523]
2017-02-23 17:57:02 [0.000101] [282577189] [12] [BATCH] [KAsyncDropFolderWatcher->getDropFoldersList] ERR: exception ‘Exception’ with message ‘Cannot get drop folder list - Internal database error’ in /opt/kaltura/app/infra/log/KalturaLog.php:83
Stack trace:
#0 /opt/kaltura/app/plugins/drop_folder/batch/DropFolderWatcher/KAsyncDropFolderWatcher.class.php(108): KalturaLog::err(‘Cannot get drop…’)

2017-02-23 17:57:03 [0.000264] [::1] [767543919] [6] [API] [KalturaFrontController->getExceptionObject] ALERT: exception ‘PropelException’ with message ‘Unable to open PDO connection dsn[mysql:host=127.0.0.1;port=3306;dbname=kaltura;] user[kaltura] password[lnKhMZfa6VGfZLt] [wrapped: SQLSTATE[28000] [1045] Access denied for user ‘kaltura’@‘localhost’ (using password: YES)]’ in /opt/kaltura/app/vendor/propel/Propel.php:649
Stack trace:
#0 /opt/kaltura/app/vendor/propel/Propel.php(532): Propel::initConnection(Array, ‘propel’)

==> /opt/kaltura/log/batch/kschedulehelper-0-2017-02-23.err.log <==
PHP Fatal error: Uncaught exception ‘KalturaException’ with message ‘Internal database error’ in /opt/kaltura/app/batch/client/KalturaClientBase.php:894
Stack trace:
#0 /opt/kaltura/app/batch/client/KalturaClient.php(4694): KalturaClientBase->throwExceptionIfError(Array)

Hi @ifeatu,

Clearly, the code cannot access the DB. The password for the kaltura DB user defined in /opt/kaltura/app/configurations/db.ini. Not sure what happened here exactly but I think it would be most helpful for you to drop the DB again, rerun the config script and post the full output.
Also, the passwords for the operational and DWH DBs are cached here from previous install attempts: /etc/kaltura.d/system.ini, please make sure they match whatever you put in your answer file.

@jess So I tried manually getting into the database:

mysql -u kaltura -p

I used the password that is noted in the system.ini file and it works fine. However it appears the installer is still not working.

==> /opt/kaltura/log/kaltura_scripts.log <==
Stack trace:
#0 /opt/kaltura/app/alpha/scripts/utils/permissions/addPermissionsAndItems.php(253): KalturaLog::err(‘Skipping call t…’)

2017-02-23 21:23:01 [403565341] [addPermissionsAndItems.php] [addItemToPermissions] ALERT: exception ‘Exception’ with message ‘ERROR - Permission name [BATCH_BASE] for partner [0] not found in database - skipping!’ in /opt/kaltura/app/infra/log/KalturaLog.php:65
Stack trace:
#0 /opt/kaltura/app/alpha/scripts/utils/permissions/addPermissionsAndItems.php(284): KalturaLog::alert(‘ERROR - Permiss…’)

thrown in /opt/kaltura/app/batch/client/KalturaClientBase.php on line 894
PHP Fatal error: Uncaught exception ‘KalturaException’ with message ‘Internal database error’ in /opt/kaltura/app/batch/client/KalturaClientBase.php:894
Stack trace:
#0 /opt/kaltura/app/batch/client/KalturaClient.php(1321): KalturaClientBase->throwExceptionIfError(Array)

thrown in /opt/kaltura/app/batch/client/KalturaClientBase.php on line 894
PHP Fatal error: Uncaught exception ‘KalturaException’ with message ‘Internal database error’ in /opt/kaltura/app/batch/client/KalturaClientBase.php:894
Stack trace:
#0 /opt/kaltura/app/batch/client/KalturaClient.php(1159): KalturaClientBase->throwExceptionIfError(Array)

thrown in /opt/kaltura/app/batch/client/KalturaClientBase.php on line 894
PHP Fatal error: Uncaught exception ‘KalturaException’ with message ‘Internal database error’ in /opt/kaltura/app/batch/client/KalturaClientBase.php:894
Stack trace:
#0 /opt/kaltura/app/batch/client/KalturaClient.php(4694): KalturaClientBase->throwExceptionIfError(Array)

thrown in /opt/kaltura/app/batch/client/KalturaClientBase.php on line 894
PHP Fatal error: Uncaught exception ‘KalturaException’ with message ‘Internal database error’ in /opt/kaltura/app/batch/client/KalturaClientBase.php:894
Stack trace:
#0 /opt/kaltura/app/batch/client/KalturaClient.php(1144): KalturaClientBase->throwExceptionIfError(Array)

==> /opt/kaltura/log/batch/synchronizedistribution-0-2017-02-23.err.log <==
PHP Fatal error: Uncaught exception ‘KalturaException’ with message ‘Internal database error’ in /opt/kaltura/app/batch/client/KalturaClientBase.php:894
Stack trace:
#0 /opt/kaltura/app/batch/client/KalturaPlugins/KalturaContentDistributionClientPlugin.php(2758): KalturaClientBase->throwExceptionIfError(Array)

thrown in /opt/kaltura/app/batch/client/KalturaClientBase.php on line 894
PHP Fatal error: Uncaught exception ‘KalturaException’ with message ‘Internal database error’ in /opt/kaltura/app/batch/client/KalturaClientBase.php:894
Stack trace:
#0 /opt/kaltura/app/batch/client/KalturaClient.php(2318): KalturaClientBase->throwExceptionIfError(Array)

Here is the output on the system.ini:

sh-4.1# more /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=email@gmail.com
ADMIN_CONSOLE_ADMIN_MAIL=email@gmail.com

DB1_HOST=127.0.0.1
DB1_NAME=kaltura
DB1_USER=kaltura
DB1_PASS=lwtbblsbNBRhO9c

DWH_HOST=127.0.0.1
DWH_PORT=3306
DWH_USER=etl
DWH_PASS=lwtbblsbNBRhO9c
SERVICE_URL=http://localhost
SPHINX_HOST=127.0.0.1
DB1_PORT=3306
SUPER_USER=root
SUPER_USER_PASSWD="password"
KALTURA_VIRTUAL_HOST_NAME=localhost
PRIMARY_MEDIA_SERVER_HOST=cf55c2f8dde0

Any other suggestions? I tried tearing down the host completly removing the docker image and pulling it down again, that didnt work. I also tried dropping the database and re-adding

This is the EXACT moment when it happened:

Configuring your Kaltura DB…

Checking MySQL version…
Ver 5.1.73 found compatible

CREATE USER kaltura;
CREATE USER etl;
CREATE DATABASE kaltura;

Here are the errors (kaltlog):

[2017-02-23 21:44:23]failed to connect [1] [0.0015690326690674] mysql:host=127.0.0.1;port=3306;dbname=kaltura_sphinx_log;
PHP Fatal error: Uncaught exception ‘PropelException’ with message ‘Unable to open PDO connection dsn[mysql:host=127.0.0.1;port=3306;dbname=kaltura_sphinx_log;] user[kaltura] password[RlO2ywX10Zt1YIz] [wrapped: SQLSTATE[42000] [1044] Access denied for user ‘kaltura’@’%’ to database ‘kaltura_sphinx_log’]’ in /opt/kaltura/app/vendor/propel/Propel.php:649
Stack trace:
#0 /opt/kaltura/app/vendor/propel/Propel.php(532): Propel::initConnection(Array, ‘sphinx_log_read’)

[2017-02-23 21:44:24]exception ‘Exception’ with message ‘Scheduler already running - pid[6395]’ in /opt/kaltura/app/infra/log/KalturaLog.php:83
Stack trace:
#0 /opt/kaltura/app/plugins/sphinx_search/scripts/populateFromLog.php(51): KalturaLog::err(‘Scheduler alrea…’)

The installation continues however without a hitch:

Checking MySQL version…
Ver 5.1.73 found compatible

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

@jess Any ideas? This is still not working. Can you confirm this isn’t happening for everyone? Seems to me that if I run this thing from scratch, I shouldnt be getting this error.

@jess When I try and “drop” the db while I’m running kaltlog I see these errors:


2017-02-24 15:03:03 [0.000324] [::1] [1484876603] [6] [API] [KalturaFrontController->getExceptionObject] ALERT: exception ‘PropelException’ with message ‘Unable to open PDO connection dsn[mysql:host=127.0.0.1;port=3306;dbname=kaltura;] user[kaltura] password[RlO2ywX10Zt1YIz] [wrapped: SQLSTATE[28000] [1045] Access denied for user ‘kaltura’@‘localhost’ (using password: YES)]’ in /opt/kaltura/app/vendor/propel/Propel.php:649
Stack trace:
#0 /opt/kaltura/app/vendor/propel/Propel.php(532): Propel::initConnection(Array, ‘propel’)

2017-02-24 15:03:03 [0.000317] [::1] [30576462] [6] [API] [KalturaFrontController->getExceptionObject] ALERT: exception ‘PropelException’ with message ‘Unable to open PDO connection dsn[mysql:host=127.0.0.1;port=3306;dbname=kaltura;] user[kaltura] password[RlO2ywX10Zt1YIz] [wrapped: SQLSTATE[28000] [1045] Access denied for user ‘kaltura’@‘localhost’ (using password: YES)]’ in /opt/kaltura/app/vendor/propel/Propel.php:649
Stack trace:
#0 /opt/kaltura/app/vendor/propel/Propel.php(532): Propel::initConnection(Array, ‘propel’)

2017-02-24 15:03:03 [0.001342] [::1] [1885884083] [6] [API] [KalturaFrontController->getExceptionObject] ALERT: exception ‘PropelException’ with message ‘Unable to open PDO connection dsn[mysql:host=127.0.0.1;port=3306;dbname=kaltura;] user[kaltura] password[RlO2ywX10Zt1YIz] [wrapped: SQLSTATE[28000] [1045] Access denied for user ‘kaltura’@‘localhost’ (using password: YES)]’ in /opt/kaltura/app/vendor/propel/Propel.php:649
Stack trace:
#0 /opt/kaltura/app/vendor/propel/Propel.php(532): Propel::initConnection(Array, ‘propel’)

2017-02-24 15:03:03 [0.000233] [::1] [1211449695] [6] [API] [KalturaFrontController->getExceptionObject] ALERT: exception ‘PropelException’ with message ‘Unable to open PDO connection dsn[mysql:host=127.0.0.1;port=3306;dbname=kaltura;] user[kaltura] password[RlO2ywX10Zt1YIz] [wrapped: SQLSTATE[28000] [1045] Access denied for user ‘kaltura’@‘localhost’ (using password: YES)]’ in /opt/kaltura/app/vendor/propel/Propel.php:649
Stack trace:
#0 /opt/kaltura/app/vendor/propel/Propel.php(532): Propel::initConnection(Array, ‘propel’)

==> /opt/kaltura/log/batch/dbcleanup-0-2017-02-24.err.log <==
PHP Fatal error: Uncaught exception ‘KalturaException’ with message ‘Internal database error’ in /opt/kaltura/app/batch/client/KalturaClientBase.php:894
Stack trace:
#0 /opt/kaltura/app/batch/client/KalturaClient.php(1321): KalturaClientBase->throwExceptionIfError(Array)

2017-02-24 15:03:03 [0.000128] [1736018558] [11] [BATCH] [KalturaClientBase->doQueue] INFO: execution time for [http://localhost/api_v3/service/dropfolder_dropfolder/action/list]: [0.011459112167358]
2017-02-24 15:03:03 [0.000106] [1736018558] [12] [BATCH] [KAsyncDropFolderWatcher->getDropFoldersList] ERR: exception ‘Exception’ with message ‘Cannot get drop folder list - Internal database error’ in /opt/kaltura/app/infra/log/KalturaLog.php:83
Stack trace:
#0 /opt/kaltura/app/plugins/drop_folder/batch/DropFolderWatcher/KAsyncDropFolderWatcher.class.php(108): KalturaLog::err(‘Cannot get drop…’)

==> /opt/kaltura/log/batch/jobsuspender-0-2017-02-24.err.log <==
PHP Fatal error: Uncaught exception ‘KalturaException’ with message ‘Internal database error’ in /opt/kaltura/app/batch/client/KalturaClientBase.php:894
Stack trace:
#0 /opt/kaltura/app/batch/client/KalturaClient.php(1159): KalturaClientBase->throwExceptionIfError(Array)

==> /opt/kaltura/log/batch/partnerloadcleanup-0-2017-02-24.err.log <==
PHP Fatal error: Uncaught exception ‘KalturaException’ with message ‘Internal database error’ in /opt/kaltura/app/batch/client/KalturaClientBase.php:894
Stack trace:
#0 /opt/kaltura/app/batch/client/KalturaClient.php(1144): KalturaClientBase->throwExceptionIfError(Array)

2017-02-24 15:03:05 [0.001427] [::1] [832560044] [6] [API] [KalturaFrontController->getExceptionObject] ALERT: exception ‘PropelException’ with message ‘Unable to open PDO connection dsn[mysql:host=127.0.0.1;port=3306;dbname=kaltura;] user[kaltura] password[RlO2ywX10Zt1YIz] [wrapped: SQLSTATE[28000] [1045] Access denied for user ‘kaltura’@‘localhost’ (using password: YES)]’ in /opt/kaltura/app/vendor/propel/Propel.php:649
Stack trace:
#0 /opt/kaltura/app/vendor/propel/Propel.php(532): Propel::initConnection(Array, ‘propel’)

==> /opt/kaltura/log/batch/kschedulehelper-0-2017-02-24.err.log <==
PHP Fatal error: Uncaught exception ‘KalturaException’ with message ‘Internal database error’ in /opt/kaltura/app/batch/client/KalturaClientBase.php:894
Stack trace:
#0 /opt/kaltura/app/batch/client/KalturaClient.php(4694): KalturaClientBase->throwExceptionIfError(Array)

Hi @ifeatu,

You get these errors continuously, because the code cannot access your DB. That’s not because of the drop-db script which simply drops all the Kaltura schemas and users [kaltura and etl].
The real question is why the code cannot access your DB. Is the password in /opt/kaltura/app/configurations/db.ini correct?

I am unable to reproduce an issue when installing inside a Docker container [or any other method for that matter] nor have I gotten any other reports to that effect so, other than prompting you for information to help fix your specific issue, there’s not much I can do.

Can you start a new container, deploy from scratch, share the full output and, if that does not reveal anything new, perhaps share the resulting container image so I can debug it locally?

@jess I’m happy to send you the container image for local trouble shooting however the one I am using I just pulled from this repo. https://hub.docker.com/r/kaltura/server/

I just tried a yum update inside of the image the following packages were out of date:

bash x86_64 4.1.2-41.el6_8 updates 909 k
bind-libs x86_64 32:9.8.2-0.47.rc1.el6_8.4 updates 890 k
bind-utils x86_64 32:9.8.2-0.47.rc1.el6_8.4 updates 187 k
expat x86_64 2.0.1-13.el6_8 updates 77 k
kaltura-base noarch 12.10.0-6 Kaltura-noarch 70 M
kaltura-batch noarch 12.10.0-1 Kaltura-noarch 22 k
kaltura-front noarch 12.10.0-1 Kaltura-noarch 14 k
kaltura-html5lib noarch v2.53-1 Kaltura-noarch 86 M
kaltura-kmc noarch v5.41.2-3 Kaltura-noarch 216 M
kaltura-release noarch 12.10.0-1 Kaltura-noarch 9.9 k
kaltura-server noarch 12.10.0-1 Kaltura-noarch 9.8 k
kernel-firmware noarch 2.6.32-642.13.2.el6 updates 28 M
kernel-headers x86_64 2.6.32-642.13.2.el6 updates 4.4 M
libgcrypt x86_64 1.4.5-12.el6_8 updates 229 k
nss-util x86_64 3.21.3-1.el6_8 updates 67 k
openssl updates
tzdata
vim-minimal

I’m going to update these packages and see what happens when I try again.

@jess the kaltura db user pw is autogenerated…I did not create or touch it. When I run mysql -u kaltura -p from the CLI and use the pw in that file it works, I can get in.

@jess update attempted and kaltura-base package update failed:

ERROR 1045 (28000): Access denied for user ‘kaltura’@‘localhost’ (using password: YES)
warning: %post(kaltura-base-12.10.0-6.noarch) scriptlet failed, exit status 255
Non-fatal POSTIN scriptlet failure in rpm package kaltura-base-12.10.0-6.noarch

Same thing. Bazaaro.

Hi @ifeatu,

What I meant is for you to send me the container POST the installation attempt.
From within the container, do upgrade to the latest packages, then, drop the DB, make sure the kaltura schemas and users were indeed dropped and run /opt/kaltura/bin/kaltura-config-all.sh

This script can accept an answer file as the first argument but in light of the current situation, it may be best to run it interactively and the post the entire flow [minus sensitive info, of course] for further inspection.

Thanks,

as for:

Not strange at all considering the whole problem is the code cannot access the DB. Asking again, are the DB creds in /opt/kaltura/app/configurations/db.ini correct?
Can you access the DB manually from the shell using them?

@jess Yes I can get in using the password in db.ini

sh-4.1# mysql -u kaltura -p
Enter password:
Welcome to the MySQL monitor. Commands end with ; or \g.
Your MySQL connection id is 283
Server version: 5.1.73 Source distribution

Copyright © 2000, 2013, 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> show databases;
±-------------------+
| Database |
±-------------------+
| information_schema |
| kaltura |
| kaltura_sphinx_log |
±-------------------+
3 rows in set (0.00 sec)

mysql> use kaltura;
Reading table information for completion of table and column names
You can turn off this feature to get a quicker startup with -A

Database changed
mysql> show tables;
±-------------------------------------+
| Tables_in_kaltura |
±-------------------------------------+
| access_control |
| api_server |
| app_token |
| audit_trail |
| audit_trail_config |
| audit_trail_data |
| batch_job_lock |