So I have attempted to install Kaltura dozens of times now. At least 20-30 times on Docker, 20 times in ubuntu, and now in CentOS. Not one time have I gotten a clean installation. Here are some more errors:
2017-03-07 15:42:48 [0.000231] [172.31.20.146] [1480679800] [10] [API] [kPermissionManager::getFromCache] DEBUG: Found a cache value for key [role_2_partner_-1_internal_1] map hash [29681363e4c233db1cf7872489bb2f84] in layer [apcSerialized]
2017-03-07 15:42:48 [0.000229] [172.31.20.146] [1480679800] [11] [API] [kPermissionManager::isActionPermitted] ERR: exception ‘Exception’ with message ‘Service is not permitted’ in /opt/kaltura/app/infra/log/KalturaLog.php:83
Stack trace:
0 /opt/kaltura/app/alpha/apps/kaltura/lib/kPermissionManager.php(800): KalturaLog::err(‘Service is not …’)
8 {main}
2017-03-07 15:42:48 [0.000102] [172.31.20.146] [1480679800] [12] [API] [KalturaBaseService->isPermitted] ERR: exception ‘Exception’ with message ‘Action is not permitted’ in /opt/kaltura/app/infra/log/KalturaLog.php:83
Stack trace:
0 /opt/kaltura/app/api_v3/lib/KalturaBaseService.php(192): KalturaLog::err(‘Action is not p…’)
7 {main}
2017-03-07 15:42:48 [0.000082] [172.31.20.146] [1480679800] [13] [API] [KalturaBaseService->isPermitted] ERR: exception ‘Exception’ with message ‘Kaltura network is not allowed’ in /opt/kaltura/app/infra/log/KalturaLog.php:83
This looks like a deployment where the DB population partially failed. Pretty similar to what you initially reported in this thread: KMC issues with Docker image
Please post the full output of running the install script as well as any errors in the following logs:
/opt/kaltura/log/installPlugins.log
/opt/kaltura/log/insertDefaults.log
/opt/kaltura/log/insertPermissions.log
/opt/kaltura/log/insertContent.log
/opt/kaltura/log/kaltura_api_v3.log
If you don’t have the output from the previous attempt, please drop the DB as I explained in your original thread and run it again. Please also provide the answer file used or the interactive answers you provided when prompted.
Of course, be sure to mask sensitive info.
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(1071): 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(1295): 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(1381): 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/KalturaPlugins/KalturaContentDistributionClientPlugin.php(2792): 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(2316): KalturaClientBase->throwExceptionIfError(Array)
2017-03-07 17:44:13 [0.006350] [172.31.18.146] [1383353661] [18] [API] [KalturaObject->generateFromObjectClass] ALERT: exception ‘Exception’ with message ‘getter for property videoOffsetInPercentage was not found on object thumbParamsOutput’ in /opt/kaltura/app/infra/log/KalturaLog.php:65
Stack trace:
0 /opt/kaltura/app/api_v3/lib/types/KalturaObject.php(153): KalturaLog::alert(‘getter for prop…’)
@jess Your CentOS 7 install instructions are missing installation of PHP
Error:
Error: Package: kaltura-base-12.11.0-10.noarch (Kaltura-noarch)
Requires: php-mbstring
Error: Package: kaltura-mencoder-3.4.6-9.x86_64 (Kaltura)
Requires: liboil-0.3.so.0
Error: Package: xvidcore-1.3.2-16.x86_64 (Kaltura)
Requires: /usr/sbin/ldconfig
Removing: glibc-2.17-157.el7.x86_64 (@anaconda/7.3)
Not found
Updated By: glibc-2.17-157.el7_3.1.x86_64 (rhui-REGION-rhel-server-releases)
Not found
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest
FYI if you’re running your host inside of a host in AWS please enable the right repo:
/opt/kaltura/bin/kaltura-mysql-settings.sh
package mysql-server is not installed
package mariadb-server is not installed
Redirecting to /bin/systemctl restart mysql.service
Failed to restart mysql.service: Unit not found.
Not sure I understand what you mean by that… the Kaltura RPM and deb packages declare all needed PHP dependencies and they will therefore be retrieved automatically. You do not need to manually install any PHP packages in order for it to work.
2017-03-08 22:55:12 [921861904] [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…’)
]
2017-03-08 23:46:54 [0.001910] [172.31.13.139] [1026557596] [4] [API] [ks->logError] ERR: exception ‘Exception’ with message ‘Hash [195e9a7c3cd47db16dcf58658de6b7d1db9b0921] doesn’t match the sha1 on the salt on partner [-1].’ in /opt/kaltura/app/infra/log/KalturaLog.php:83
Stack trace: #0 /opt/kaltura/app/alpha/apps/kaltura/lib/webservices/kSessionUtils.class.php(735): KalturaLog::err(‘Hash [195e9a7c3…’)
After dropping the db and reattempting…more stacktracing:
]
2017-03-08 23:59:26 [0.002868] [172.31.13.139] [485541339] [4] [API] [ks->logError] ERR: exception ‘Exception’ with message ‘Hash [2d2ac13997109e21fb0313c0410eee71a7515be5] doesn’t match the sha1 on the salt on partner [-1].’ in /opt/kaltura/app/infra/log/KalturaLog.php:83
Stack trace: #0 /opt/kaltura/app/alpha/apps/kaltura/lib/webservices/kSessionUtils.class.php(735): KalturaLog::err(‘Hash [2d2ac1399…’)
]
2017-03-08 23:59:41 [0.002917] [172.31.13.139] [459086002] [4] [API] [ks->logError] ERR: exception ‘Exception’ with message ‘Hash [a087de64af2b5924d0f681d2c51249e2162f4f68] doesn’t match the sha1 on the salt on partner [-1].’ in /opt/kaltura/app/infra/log/KalturaLog.php:83
Stack trace: #0 /opt/kaltura/app/alpha/apps/kaltura/lib/webservices/kSessionUtils.class.php(735): KalturaLog::err(‘Hash [a087de64a…’)
]
2017-03-08 23:59:42 [0.002526] [172.31.13.139] [1556917620] [4] [API] [ks->logError] ERR: exception ‘Exception’ with message ‘Hash [e32c9338e03fb5d7181c62102e241f7576463312] doesn’t match the sha1 on the salt on partner [-1].’ in /opt/kaltura/app/infra/log/KalturaLog.php:83
Stack trace: #0 /opt/kaltura/app/alpha/apps/kaltura/lib/webservices/kSessionUtils.class.php(735): KalturaLog::err(‘Hash [e32c9338e…’)