ok i dont need Webcam recording so i should skip this, right?
and after that i am have still problem with KMC
it is loading now(Login page), after signing in it is giving connection error.
but after refreshing it by root page we can open KMC.
But it is just giving me a blank page with its header row of tabs(Dashboard content Application Studio etc)
Is the service URL you’ve used resolvable and available from both the server itself and the client from which you’re running the browser?
Open your dev tools console and the browser and look for failing calls under the network and console tabs and also, use kaltlog, as I indicated initially to check the errors in the server logs.
i have already told that /etc/profile.d/kaltura-base.sh is available in this directory but giving error as follows:
"./etc/profile.d/kaltura-base.sh
bash: ./etc/profile.d/kaltura-base.sh: No such file or directory"
==> /opt/kaltura/log/kaltura_populate.log <==
PHP Fatal error: Uncaught exception ‘PropelException’ with message ‘No connection information in your runtime configuration file for datasource [sphinx_log_read]’ in /opt/kaltura/app/vendor/propel/Propel.php:529
Stack trace: #0 /opt/kaltura/app/alpha/apps/kaltura/lib/myDbHelper.class.php(30): Propel::getConnection(‘sphinx_log_read’)
2015-08-03 12:05:19 [1144486006] [addPermissionsAndItems.php] [addItemToPermissions] ALERT: exception ‘Exception’ with message ‘ERROR - Permission name [] for partner [0] not found in database - skipping!’ in /opt/kaltura/app/infra/log/KalturaLog.php:64
Stack trace: #0 /opt/kaltura/app/alpha/scripts/utils/permissions/addPermissionsAndItems.php(280): KalturaLog::alert(‘ERROR - Permiss…’)
oot@grid803 ~]# kaltlog
thrown in /opt/kaltura/app/vendor/propel/Propel.php on line 529
PHP Fatal error: Uncaught exception ‘PropelException’ with message ‘No connection information in your runtime configuration file for datasource [sphinx_log_read]’ in /opt/kaltura/app/vendor/propel/Propel.php:529
Stack trace: #0 /opt/kaltura/app/alpha/apps/kaltura/lib/myDbHelper.class.php(30): Propel::getConnection(‘sphinx_log_read’)
==> /opt/kaltura/log/batch/validatelivemediaservers-0-2015-08-17.err.log <==
PHP Fatal error: Uncaught exception ‘KalturaClientException’ with message ‘couldn’t connect to host’ in /opt/kaltura/app/batch/client/KalturaClientBase.php:362
Stack trace: #0 /opt/kaltura/app/batch/client/KalturaClient.php(4175): KalturaClientBase->doQueue()
^C
[root@grid803 ~]# cat /opt/kaltura/log/batch/validatelivemediaservers-0-2015-08-17.err.log
PHP Fatal error: Uncaught exception ‘KalturaClientException’ with message ‘couldn’t connect to host’ in /opt/kaltura/app/batch/client/KalturaClientBase.php:362
Stack trace: #0 /opt/kaltura/app/batch/client/KalturaClient.php(4175): KalturaClientBase->doQueue() #1 /opt/kaltura/app/batch/batches/ValidateLiveMediaServers/KAsyncValidateLiveMediaServers.class.php(45): KalturaLiveStreamService->listAction(Object(KalturaLiveStreamEntryFilter), Object(KalturaFilterPager)) #2 /opt/kaltura/app/batch/batches/ValidateLiveMediaServers/KAsyncValidateLiveMediaServersExe.php(11): KAsyncValidateLiveMediaServers->run() #3 {main}
thrown in /opt/kaltura/app/batch/client/KalturaClientBase.php on line 362
[root@grid803 ~]#
Am getting similar error here after fresh installation using rpm
looks like the config_all trying to conncet and look for sphinx_log_read datasource, which doesn’t exist in the db.ini or db_template.ini
subsequent partner id permission also failed from kaltlog but oevrall config sucessfully.
However, login to kmc gives a grey screen (only top toolbar appeared). Any idea? Thanks.
oot@grid803 ~]# kaltlog
thrown in /opt/kaltura/app/vendor/propel/Propel.php on line 529
PHP Fatal error: Uncaught exception ‘PropelException’ with message ‘No connection information in your runtime configuration file for datasource [sphinx_log_read]’ in /opt/kaltura/app/vendor/propel/Propel.php:529
Stack trace: #0 /opt/kaltura/app/alpha/apps/kaltura/lib/myDbHelper.class.php(30): Propel::getConnection(‘sphinx_log_read’)
==> /opt/kaltura/log/batch/validatelivemediaservers-0-2015-08-17.err.log <==
PHP Fatal error: Uncaught exception ‘KalturaClientException’ with message ‘couldn’t connect to host’ in /opt/kaltura/app/batch/client/KalturaClientBase.php:362
Stack trace: #0 /opt/kaltura/app/batch/client/KalturaClient.php(4175): KalturaClientBase->doQueue()
^C
[root@grid803 ~]# cat /opt/kaltura/log/batch/validatelivemediaservers-0-2015-08-17.err.log
PHP Fatal error: Uncaught exception ‘KalturaClientException’ with message ‘couldn’t connect to host’ in /opt/kaltura/app/batch/client/KalturaClientBase.php:362
Stack trace: #0 /opt/kaltura/app/batch/client/KalturaClient.php(4175): KalturaClientBase->doQueue() #1 /opt/kaltura/app/batch/batches/ValidateLiveMediaServers/KAsyncValidateLiveMediaServers.class.php(45): KalturaLiveStreamService->listAction(Object(KalturaLiveStreamEntryFilter), Object(KalturaFilterPager)) #2 /opt/kaltura/app/batch/batches/ValidateLiveMediaServers/KAsyncValidateLiveMediaServersExe.php(11): KAsyncValidateLiveMediaServers->run() #3 {main}
thrown in /opt/kaltura/app/batch/client/KalturaClientBase.php on line 362
[root@grid803 ~]#
The error from kartlog during kaltura-config-all.sh. I hv reinstall many times on centos 6.7, same error:
[root@grid803 ~]# kaltlog
tail: cannot open `/opt/kaltura/log/batch/*.log’ for reading: No such file or directory
==> /opt/kaltura/log/kaltura_populate.log <==
PHP Fatal error: Uncaught exception ‘PropelException’ with message ‘No connection information in your runtime configuration file for datasource [sphinx_log_read]’ in /opt/kaltura/app/vendor/propel/Propel.php:529
Stack trace: #0 /opt/kaltura/app/alpha/apps/kaltura/lib/myDbHelper.class.php(30): Propel::getConnection(‘sphinx_log_read’)
2015-08-17 17:51:50 [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(280): KalturaLog::alert(‘ERROR - Permiss…’)
2015-08-17 17:52:12 [addItemToPermissions] ALERT: exception ‘Exception’ with message ‘ERROR - Permission name [] 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(280): KalturaLog::alert(‘ERROR - Permiss…’)
2015-08-17 17:52:43 [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(280): KalturaLog::alert(‘ERROR - Permiss…’)
Start by opening your browser’s dev tools and looking at the “network” and “console” tabs for errors and failing requests.
In parallel, run:
# kaltlog
in the server’s root shell and then look at the respective logs under /opt/kaltura/log/ to find what led to the final error.
Mostly these will be under /opt/kaltura/log/kaltura_api_v3.log and /opt/kaltura/log/kaltura_apache_error.log
Then share it here.