Install kaltura-base-13.16.0-1.noarch breaks console&KMC


#1

I managed to setup kaltura-base-13.16.0-1.noarch on a redhat 7.4 system via yum and had it running relatively smoothly. But, I removed this version, ran yum update and got the latest version (kaltura-base-13.17.0-19.noarch), though now I’m able to install successfully without errors, but can only get to the start/index.php page.

Attempting to open the admin console produces a white screen with the following error in the browser:

An error occurred
(error code: Server:INVALID_KS)

====

The following is output by kaltlog when the admin console loads

===

2018-04-19 13:30:11 [0.000519] [10.111.46.15] [1007347536] [4] [API] [ks->logError] ERR: exception ‘Exception’ with message ‘Hash [3fd73955b4f548ab87c1fc2bca2f2dc728fd8a21] doesn’t match the sha1 on the salt on partner [-2].’ in /opt/kaltura/app/infra/log/KalturaLog.php:83
Stack trace:
#0 /opt/kaltura/app/alpha/apps/kaltura/lib/webservices/kSessionUtils.class.php(743): KalturaLog::err(‘Hash [3fd73955b…’)

#9 {main}
2018-04-19 13:30:11 [0.000386] [10.111.46.15] [1007347536] [5] [API] [kCoreException->__construct] ERR: exception ‘kCoreException’ with message ‘INVALID_STR’ in /opt/kaltura/app/alpha/apps/kaltura/lib/kCurrentContext.class.php:219
Stack trace:
#0 /opt/kaltura/app/api_v3/lib/KalturaDispatcher.php(79): kCurrentContext::initKsPartnerUser(‘M2ZkNzM5NTViNGY…’, NULL, ‘’)

2018-04-19 13:30:11 [0.000091] [1511924712] [10] [%context%] [Kaltura_Client_ClientBase->doQueue] DEBUG: execution time for [****://videos.de.ryerson.ca/api_v3/service/systempartner_systempartner/action/getPackages]: [0.0089931488037109]
2018-04-19 13:30:11 [0.001029] [1511924712] [11] [%context%] [ErrorController->errorAction] ERR: exception ‘Kaltura_Client_Exception’ with message ‘Invalid KS “M2ZkNzM5NTViNGY1NDhhYjg3YzFmYzJiY2EyZjJkYzcyOGZkOGEyMXwtMjstMjsxNTIzNjM5ODE3OzI7MTUyMzU1MzQxNy4yMjgyO2dyZWcuZ2F5QHJ5ZXJzb24uY2E7ZGlzYWJsZWVudGl0bGVtZW50Ozs=”, Error “-1,INVALID_STR”’ in /opt/kaltura/app/admin_console/lib/Kaltura/Client/ClientBase.php:937
Stack trace:
#0 /opt/kaltura/app/admin_console/lib/Kaltura/Client/ClientBase.php(953): Kaltura_Client_ClientBase->getKalturaAPIException(‘Invalid KS "M2Z…’, ‘INVALID_KS’, Array)

===

Opening the KMC produces a blank screen, and the following kaltlog output

===
2018-04-19 13:31:58 [0.000069] [1374602145] [10] [%context%] [Kaltura_Client_ClientBase->doQueue] DEBUG: execution time for [http://videos.de.ryerson.ca/api_v3/service/systempartner_systempartner/action/getPackages]: [0.0065040588378906]
2018-04-19 13:31:58 [0.000771] [1374602145] [11] [%context%] [ErrorController->errorAction] ERR: exception ‘Kaltura_Client_Exception’ with message ‘Invalid KS “M2ZkNzM5NTViNGY1NDhhYjg3YzFmYzJiY2EyZjJkYzcyOGZkOGEyMXwtMjstMjsxNTIzNjM5ODE3OzI7MTUyMzU1MzQxNy4yMjgyO2dyZWcuZ2F5QHJ5ZXJzb24uY2E7ZGlzYWJsZWVudGl0bGVtZW50Ozs=”, Error “-1,INVALID_STR”’ in /opt/kaltura/app/admin_console/lib/Kaltura/Client/ClientBase.php:937
Stack trace:
#0 /opt/kaltura/app/admin_console/lib/Kaltura/Client/ClientBase.php(953): Kaltura_Client_ClientBase->getKalturaAPIException(‘Invalid KS "M2Z…’, ‘INVALID_KS’, Array)

===

Running the kaltura-sanity.sh, the following, truncated, errors occur that I’m not sure how to address. Other than these everything else passes

===

[Check kaltura-batch daemon status] [PASSED, RC: 0] - [.027489203]
/opt/kaltura/bin/kaltura-sanity.sh: line 77: monit: command not found
Napping 1 seconds to allow the daemon kaltura-batch to finish its init after monit restarted it…
Napping 2 seconds to allow the daemon kaltura-batch to finish its init after monit restarted it…
Napping 3 seconds to allow the daemon kaltura-batch to finish its init after monit restarted it…
Napping 4 seconds to allow the daemon kaltura-batch to finish its init after monit restarted it…
Napping 5 seconds to allow the daemon kaltura-batch to finish its init after monit restarted it…
/opt/kaltura/bin/kaltura-sanity.sh: line 77: monit: command not foundNapping 6 seconds to allow the daemon kaltura-batch to finish its init after monit restarted it…

[Check memcached daemon status] [PASSED, RC: 0] - [.020086648]
/opt/kaltura/bin/kaltura-sanity.sh: line 77: monit: command not found

[expected]
[DWH cycle] [FAILED, RC: 255] - [28.392236643]

[expected]
[Red5 file upload] [SKIPPED as OflaDemo isn’t configured]
see: ****github.com/kaltura/platform-install-packages/blob/master/doc/install-kaltura-redhat-based.md#configure-red5-server

===

Here’s to answer file content, with the PWDs and http’s replaced with **** (cant post more than two http://)
videos.de.ryerson.ca won’t be accessible outside our local network.

TIME_ZONE=“America/Toronto”
KALTURA_FULL_VIRTUAL_HOST_NAME=“videos.de.ryerson.ca”
KALTURA_VIRTUAL_HOST_NAME=“videos.de.ryerson.ca”
DB1_HOST=“127.0.0.1”
DB1_PORT=“3306”
DB1_PASS=“"
DB1_NAME=“kaltura”
DB1_USER=“kaltura”
SERVICE_URL="://videos.de.ryerson.ca"
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=“greg.gay@ryerson.ca”
ADMIN_CONSOLE_PASSWORD="
"
CDN_HOST=“videos.de.ryerson.ca”
KALTURA_VIRTUAL_HOST_PORT=“80”
SUPER_USER=“root”
SUPER_USER_PASSWD="
"
ENVIRONMENT_NAME=“Ryerson Video Platform”
DWH_PASS="
****”
PROTOCOL=“http”
PRIMARY_MEDIA_SERVER_HOST=“videos.de.ryerson.ca”
USER_CONSENT=“1”
CONTACT_MAIL=“greg.gay@ryerson.ca”
VOD_PACKAGER_HOST=“videos.de.ryerson.ca”
VOD_PACKAGER_PORT=“88”
IP_RANGE=“141.117.217.0-141.117.217.255”
WWW_HOST=“videos.de.ryerson.ca”

===

Not sure where to go from here. Any help would be appreciated.


#2

Interestingly things seems to have resolved themselves. I went away for a day, came back and the errors were gone, and Kaltura fired up as it should. No idea why.

Any thought to what the issue might have been? Possibly caching causing the issue?

For future reference if we, or others run into these errors again.


#3

Hi @gregware,

‘Kaltura_Client_Exception’ with message ‘Invalid KS

can be explained away by browser caching. This can happen if you redeployed the DB [which would regenerate all partner secrets] and didn’t clear your browser’s cache.

In regards to the batch daemon, it has a dedicated partner [ID -1] which is used for generating a KS [Kaltura Session]. That’s required since all the server components [and also the web admin interfaces - Admin Console and KMC] make API requests to achieve their various goals. If you’re having problems with the kaltura-batch service, check /opt/kaltura/app/configurations/batch/batch.ini and make sure the string the secret directive is set to corresponds with:

mysql> select admin_secret from batch where id=-1;