I have been having trouble getting my Kaltura server back to functional. I tried to change from a non SSL to an SSL install but now I can not get batch to start or my KMC and admin console pages to load. I get the same exact errors as the issue found here https://github.com/kaltura/server/issues/3278 and probably due to the same reason for the errors is my host name was changed. I tried changing it back and ditching the SSL attempt and reverting back to my non-SSL config by re-running the kaltura-config-all.sh script The install runs fine but then the KMC page does not load at all Is there anyway to manually edit tables in my database and not do a db drop seeing as this server has been in production for a while now and contains about 7 TB worth of videos. Thanks for any input
Please explain exactly what errors you are encountering.
Easiest way to debug is to open your browser’s dev tools, make the request that fails [on KMC and Admin Console] and look at the “Network” and “Console” tabs for errors. In parallel, from a super user shell, run:
# kaltlog
and look at the errors outputted to STDOUT and STDERR.
kaltlog is an alias for
So it should output all erroneous log lines, giving you an indication as to the final failure, then, you need to view the relevant log [in your case, it will probably be /opt/kaltura/log/kaltura_api_v3.log, /opt/kaltura/log/kaltura_apache_errors*.log and /opt/kaltura/log/kaltura_prod.log] to trace the root cause.
Feel free to paste all that info here so I can help you troubleshoot further.
when I try to load KMC and Admin console in a browser (Firefox) although the issue happens in any browser, the dev tools return an error 500 and say internal server error and the pages remain blank no login widows or anything.
running kaltlog while loading either KMC or admin console I see the bellow pasted output the log files /opt/kaltura/log/kaltura_prod.log and /opt/kaltura/log/kaltura_api_v3.log are empty
==> /opt/kaltura/log/kaltura_apache_errors.log <== [Sat May 06 10:49:10 2017] [error] [client 127.0.1.1] PHP Fatal error: Uncaught exception ‘Zend_Log_Exception’ with message ‘"/opt/kaltura/log/kaltura_api_v3.log" cannot be opened with mode “a”’ in /opt/kaltura/app/vendor/ZendFramework/library/Zend/Log/Writer/Stream.php:69\nStack trace:\n#0 /opt/kaltura/app/infra/log/KalturaSerializableStream.php(25): Zend_Log_Writer_Stream->__construct(’/opt/kaltura/lo…’, ‘a’)\n#1 /opt/kaltura/app/infra/log/KalturaLogFactory.php(59): KalturaSerializableStream->__construct(’/opt/kaltura/lo…’, ‘a’)\n#2 /opt/kaltura/app/infra/log/KalturaLogFactory.php(18): KalturaLogFactory::getWriter(Object(Zend_Config))\n#3 /opt/kaltura/app/infra/log/KalturaLog.php(39): KalturaLogFactory::getLogger(Object(Zend_Config))\n#4 /opt/kaltura/app/alpha/apps/kaltura/lib/cache/kLoggerCache.php(39): KalturaLog::initLog(Object(Zend_Config))\n#5 /opt/kaltura/app/api_v3/bootstrap.php(31): kLoggerCache::InitLogger(‘api_v3’)\n#6 /opt/kaltura/app/api_v3/web/index.php(8): require_once(’/opt/kaltura/ap…’)\n#7 {main}\n thrown in /opt/kaltura/app/vendor/ZendFramework/library/Zend/Log/Writer/Stream.php on line 69 [Sat May 06 10:49:10 2017] [error] [client 127.0.1.1] PHP Fatal error: Uncaught exception ‘Zend_Log_Exception’ with message ‘"/opt/kaltura/log/kaltura_api_v3.log" cannot be opened with mode “a”’ in /opt/kaltura/app/vendor/ZendFramework/library/Zend/Log/Writer/Stream.php:69\nStack trace:\n#0 /opt/kaltura/app/infra/log/KalturaSerializableStream.php(25): Zend_Log_Writer_Stream->__construct(’/opt/kaltura/lo…’, ‘a’)\n#1 /opt/kaltura/app/infra/log/KalturaLogFactory.php(59): KalturaSerializableStream->__construct(’/opt/kaltura/lo…’, ‘a’)\n#2 /opt/kaltura/app/infra/log/KalturaLogFactory.php(18): KalturaLogFactory::getWriter(Object(Zend_Config))\n#3 /opt/kaltura/app/infra/log/KalturaLog.php(39): KalturaLogFactory::getLogger(Object(Zend_Config))\n#4 /opt/kaltura/app/alpha/apps/kaltura/lib/cache/kLoggerCache.php(39): KalturaLog::initLog(Object(Zend_Config))\n#5 /opt/kaltura/app/api_v3/bootstrap.php(31): kLoggerCache::InitLogger(‘api_v3’)\n#6 /opt/kaltura/app/api_v3/web/index.php(8): require_once(’/opt/kaltura/ap…’)\n#7 {main}\n thrown in /opt/kaltura/app/vendor/ZendFramework/library/Zend/Log/Writer/Stream.php on line 69
– ==> /opt/kaltura/log/kaltura_apache_errors.log <== [Sat May 06 10:49:10 2017] [error] [client 127.0.1.1] PHP Fatal error: Uncaught exception ‘Zend_Log_Exception’ with message ‘"/opt/kaltura/log/kaltura_api_v3.log" cannot be opened with mode “a”’ in /opt/kaltura/app/vendor/ZendFramework/library/Zend/Log/Writer/Stream.php:69\nStack trace:\n#0 /opt/kaltura/app/infra/log/KalturaSerializableStream.php(25): Zend_Log_Writer_Stream->__construct(’/opt/kaltura/lo…’, ‘a’)\n#1 /opt/kaltura/app/infra/log/KalturaLogFactory.php(59): KalturaSerializableStream->__construct(’/opt/kaltura/lo…’, ‘a’)\n#2 /opt/kaltura/app/infra/log/KalturaLogFactory.php(18): KalturaLogFactory::getWriter(Object(Zend_Config))\n#3 /opt/kaltura/app/infra/log/KalturaLog.php(39): KalturaLogFactory::getLogger(Object(Zend_Config))\n#4 /opt/kaltura/app/alpha/apps/kaltura/lib/cache/kLoggerCache.php(39): KalturaLog::initLog(Object(Zend_Config))\n#5 /opt/kaltura/app/api_v3/bootstrap.php(31): kLoggerCache::InitLogger(‘api_v3’)\n#6 /opt/kaltura/app/api_v3/web/index.php(8): require_once(’/opt/kaltura/ap…’)\n#7 {main}\n thrown in /opt/kaltura/app/vendor/ZendFramework/library/Zend/Log/Writer/Stream.php on line 69
==> /opt/kaltura/log/batch/dbcleanup-0-2017-05-06.err.log <== PHP Fatal error: Uncaught exception ‘KalturaClientException’ with message 'failed to unserialize server result ’ in /opt/kaltura/app/batch/client/KalturaClientBase.php:396 Stack trace: #0 /opt/kaltura/app/batch/client/KalturaClient.php(1309): KalturaClientBase->doQueue() – ==> /opt/kaltura/log/batch/partnerloadcleanup-0-2017-05-06.err.log <== PHP Fatal error: Uncaught exception ‘KalturaClientException’ with message 'failed to unserialize server result ’ in /opt/kaltura/app/batch/client/KalturaClientBase.php:396 Stack trace: #0 /opt/kaltura/app/batch/client/KalturaClient.php(1127): KalturaClientBase->doQueue() – ==> /opt/kaltura/log/batch/jobsuspender-0-2017-05-06.err.log <== PHP Fatal error: Uncaught exception ‘KalturaClientException’ with message 'failed to unserialize server result ’ in /opt/kaltura/app/batch/client/KalturaClientBase.php:396 Stack trace: #0 /opt/kaltura/app/batch/client/KalturaClient.php(1144): KalturaClientBase->doQueue()
/opt/kaltura/log/kaltura_apache_errors*.log has :
[Sat May 06 11:03:35 2017] [error] [client 127.0.1.1] PHP Fatal error: Uncaught exception ‘Zend_Log_Exception’ with message ‘"/opt/kaltura/log/kaltura_api_v3.log" cannot be opened with mode “a”’ in /opt/kaltura/app/vendor/ZendFramework/library/Zend/Log/Writer/Stream.php:69\nStack trace:\n#0 /opt/kaltura/app/infra/log/KalturaSerializableStream.php(25): Zend_Log_Writer_Stream->__construct(’/opt/kaltura/lo…’, ‘a’)\n#1 /opt/kaltura/app/infra/log/KalturaLogFactory.php(59): KalturaSerializableStream->__construct(’/opt/kaltura/lo…’, ‘a’)\n#2 /opt/kaltura/app/infra/log/KalturaLogFactory.php(18): KalturaLogFactory::getWriter(Object(Zend_Config))\n#3 /opt/kaltura/app/infra/log/KalturaLog.php(39): KalturaLogFactory::getLogger(Object(Zend_Config))\n#4 /opt/kaltura/app/alpha/apps/kaltura/lib/cache/kLoggerCache.php(39): KalturaLog::initLog(Object(Zend_Config))\n#5 /opt/kaltura/app/api_v3/bootstrap.php(31): kLoggerCache::InitLogger(‘api_v3’)\n#6 /opt/kaltura/app/api_v3/web/index.php(8): require_once(’/opt/kaltura/ap…’)\n#7 {main}\n thrown in /opt/kaltura/app/vendor/ZendFramework/library/Zend/Log/Writer/Stream.php on line 69
OK, your first problem has to do with file permissions then.
/opt/kaltura/log and /opt/kaltura/app/cache need to be owned by the apache user [‘apache’ for RHEL/CentOS, ‘www-data’ for Debian/Ubuntu].
nice. some progress. I can now open the KMC page and the login window pops open, but when I put in my credentials I get Error # 2032 and as I try to log in I get this from kaltlog:
==> /opt/kaltura/log/kaltura_apache_errors.log <== [Sat May 06 15:48:11 2017] [error] [client 136.63.12.240] PHP Fatal error: Uncaught exception ‘Zend_Log_Exception’ with message ‘"/opt/kaltura/log/kaltura_api_v3_tests.log" cannot be opened with mode “a”’ in /opt/kaltura/app/vendor/ZendFramework/library/Zend/Log/Writer/Stream.php:69\nStack trace:\n#0 /opt/kaltura/app/infra/log/KalturaSerializableStream.php(25): Zend_Log_Writer_Stream->__construct(’/opt/kaltura/lo…’, ‘a’)\n#1 /opt/kaltura/app/infra/log/KalturaLogFactory.php(59): KalturaSerializableStream->__construct(’/opt/kaltura/lo…’, ‘a’)\n#2 /opt/kaltura/app/infra/log/KalturaLogFactory.php(18): KalturaLogFactory::getWriter(Object(Zend_Config))\n#3 /opt/kaltura/app/infra/log/KalturaLog.php(39): KalturaLogFactory::getLogger(Object(Zend_Config))\n#4 /opt/kaltura/app/alpha/apps/kaltura/lib/cache/kLoggerCache.php(39): KalturaLog::initLog(Object(Zend_Config))\n#5 /opt/kaltura/app/api_v3/bootstrap.php(31): kLoggerCache::InitLogger(‘api_v3’)\n#6 /opt/kaltura/app/api_v3/web/index.php(8): require_once(’/opt/kaltura/ap…’)\n#7 {main}\n thrown in /opt/kaltura/app/vendor/ZendFramework/library/Zend/Log/Writer/Stream.php on line 69, referer: http://kaltura.wrcservers.com/flash/kmc/login/v1.2.5/login.swf
– 2017-05-06 15:49:10 [508498123] [KSchedulerConfig->load] NOTICE: loading configuration /opt/kaltura/app/configurations/batch at 1494095605 PHP Fatal error: Uncaught exception ‘Zend_Config_Exception’ with message ‘Section ‘kaltura’ 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…’, ‘kaltura’, true)
also the Admin console page still does not open at all kaltlog returns this when trying to open Admin Console
==> /opt/kaltura/log/kaltura_apache_errors.log <== [Sat May 06 15:53:59 2017] [error] [client 136.63.12.240] PHP Fatal error: Uncaught exception ‘Zend_Log_Exception’ with message ‘"/opt/kaltura/log/kaltura_admin.log" cannot be opened with mode “a”’ in /opt/kaltura/app/vendor/ZendFramework/library/Zend/Log/Writer/Stream.php:69\nStack trace:\n#0 /opt/kaltura/app/infra/log/KalturaSerializableStream.php(25): Zend_Log_Writer_Stream->__construct(’/opt/kaltura/lo…’, ‘a’)\n#1 /opt/kaltura/app/infra/log/KalturaLogFactory.php(59): KalturaSerializableStream->__construct(’/opt/kaltura/lo…’, ‘a’)\n#2 /opt/kaltura/app/infra/log/KalturaLogFactory.php(18): KalturaLogFactory::getWriter(Object(Zend_Config))\n#3 /opt/kaltura/app/infra/log/KalturaLog.php(39): KalturaLogFactory::getLogger(Object(Zend_Config))\n#4 /opt/kaltura/app/ui_infra/InfraBootstrapper.php(50): KalturaLog::initLog(Object(Zend_Config))\n#5 /opt/kaltura/app/vendor/ZendFramework/library/Zend/Application/Bootstrap/BootstrapAbstract.php(662): InfraBootstrapper->_initLog()\n#6 /opt/kaltura/app/vendor/ZendFramework/library/Zend/Application/Bootstrap/BootstrapAbstract.php(615): Zend_Application in /opt/kaltura/app/vendor/ZendFramework/library/Zend/Log/Writer/Stream.php on line 69, referer: http://kaltura.wrcservers.com/start/index.php
– 2017-05-06 15:55:03 [295219561] [KSchedulerConfig->load] NOTICE: loading configuration /opt/kaltura/app/configurations/batch at 1494095605 PHP Fatal error: Uncaught exception ‘Zend_Config_Exception’ with message ‘Section ‘kaltura’ 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…’, ‘kaltura’, true)
According to your output, you still have logs with bad permissions under /opt/kaltura/log, make sure all logs are owned by apache.kaltura and have 664 permissions so that both the kaltura and apache users can write to them.
Also, your batch configuration is incorrect. To fix it, run:
RHEL/CentOS:
I changed the permissions to /opt/kaltura/log/kaltura_admin.log and now the Admin Console page opens with the login window but get an error when trying to login now
An error occurred
(error code: API:-1) Message: . RC : 500
and kaltlog returns this which still looks like permissions issues but not sure what those should be?
=> /opt/kaltura/log/kaltura_apache_errors.log <== [Sat May 06 16:05:36 2017] [error] [client 127.0.1.1] PHP Fatal error: Uncaught exception ‘Zend_Log_Exception’ with message ‘"/opt/kaltura/log/kaltura_api_v3_tests.log" cannot be opened with mode “a”’ in /opt/kaltura/app/vendor/ZendFramework/library/Zend/Log/Writer/Stream.php:69\nStack trace:\n#0 /opt/kaltura/app/infra/log/KalturaSerializableStream.php(25): Zend_Log_Writer_Stream->__construct(’/opt/kaltura/lo…’, ‘a’)\n#1 /opt/kaltura/app/infra/log/KalturaLogFactory.php(59): KalturaSerializableStream->__construct(’/opt/kaltura/lo…’, ‘a’)\n#2 /opt/kaltura/app/infra/log/KalturaLogFactory.php(18): KalturaLogFactory::getWriter(Object(Zend_Config))\n#3 /opt/kaltura/app/infra/log/KalturaLog.php(39): KalturaLogFactory::getLogger(Object(Zend_Config))\n#4 /opt/kaltura/app/alpha/apps/kaltura/lib/cache/kLoggerCache.php(39): KalturaLog::initLog(Object(Zend_Config))\n#5 /opt/kaltura/app/api_v3/bootstrap.php(31): kLoggerCache::InitLogger(‘api_v3’)\n#6 /opt/kaltura/app/api_v3/web/index.php(8): require_once(’/opt/kaltura/ap…’)\n#7 {main}\n thrown in /opt/kaltura/app/vendor/ZendFramework/library/Zend/Log/Writer/Stream.php on line 69
– ==> /opt/kaltura/log/kaltura_admin.log <== 2017-05-06 16:05:36 [1722308741] [ErrorController->errorAction] ERR: exception ‘Kaltura_Client_ClientException’ with message ‘. RC : 500’ in /opt/kaltura/app/admin_console/lib/Kaltura/Client/ClientBase.php:239 Stack trace: #0 /opt/kaltura/app/admin_console/lib/Kaltura/Client/UserService.php(177): Kaltura_Client_ClientBase->doQueue() – ==> /opt/kaltura/log/kaltura_apache_errors.log <== [Sat May 06 16:05:37 2017] [error] [client 104.131.27.150] File does not exist: /opt/kaltura/app/alpha/web/opt, referer: http://kaltura.wrcservers.com/admin_console/index.php/user/login
Ok thanks so much for your help by the way I think its almost better now but still seeing some errors when running kaltlog when i first run the command i get this print out:
==> /opt/kaltura/log/kaltura_apache_errors.log <==
[Sat May 06 16:12:41 2017] [error] [client 212.237.24.5] File does not exist: /opt/kaltura/app/alpha/web/xampp
[Sat May 06 16:12:42 2017] [error] [client 212.237.24.5] File does not exist: /opt/kaltura/app/alpha/web/web
[Sat May 06 16:12:43 2017] [error] [client 212.237.24.5] File does not exist: /opt/kaltura/app/alpha/web/php-my-admin
[Sat May 06 16:12:43 2017] [error] [client 212.237.24.5] File does not exist: /opt/kaltura/app/alpha/web/websql
[Sat May 06 16:12:44 2017] [error] [client 212.237.24.5] File does not exist: /opt/kaltura/app/alpha/web/phpMyAdmin-2
[Sat May 06 16:12:44 2017] [error] [client 212.237.24.5] File does not exist: /opt/kaltura/app/alpha/web/_phpmyadmin
[Sat May 06 16:12:45 2017] [error] [client 212.237.24.5] File does not exist: /opt/kaltura/app/alpha/web/administrator
[Sat May 06 16:12:46 2017] [error] [client 212.237.24.5] File does not exist: /opt/kaltura/app/alpha/web/apache-default
[Sat May 06 16:12:46 2017] [error] [client 212.237.24.5] File does not exist: /opt/kaltura/app/alpha/web/blog
[Sat May 06 16:53:49 2017] [error] [client 191.96.249.136] File does not exist: /opt/kaltura/app/alpha/web/phpmyadmin
–
[2017-05-05 13:07:48]exception ‘Exception’ with message ‘Configuration file [/opt/kaltura/app/configurations/sphinx/populate/kaltura.wrcservers.com.ini] not found.’ in /opt/kaltura/app/infra/log/KalturaLog.php:82
Stack trace: #0 /opt/kaltura/app/plugins/sphinx_search/scripts/populateFromLog.php(36): KalturaLog::err(‘Configuration f…’)
thrown in /opt/kaltura/app/batch/client/KalturaClientBase.php on line 396
PHP Fatal error: Uncaught exception ‘KalturaClientException’ with message ‘failed to unserialize server result
’ in /opt/kaltura/app/batch/client/KalturaClientBase.php:396
Stack trace: #0 /opt/kaltura/app/batch/client/KalturaClient.php(1309): KalturaClientBase->doQueue()
thrown in /opt/kaltura/app/batch/client/KalturaClientBase.php on line 396
PHP Fatal error: Uncaught exception ‘KalturaClientException’ with message ‘failed to unserialize server result
’ in /opt/kaltura/app/batch/client/KalturaClientBase.php:396
Stack trace: #0 /opt/kaltura/app/batch/client/KalturaClient.php(1309): KalturaClientBase->doQueue()
thrown in /opt/kaltura/app/batch/client/KalturaClientBase.php on line 396
PHP Fatal error: Uncaught exception ‘KalturaClientException’ with message ‘failed to unserialize server result
’ in /opt/kaltura/app/batch/client/KalturaClientBase.php:396
Stack trace: #0 /opt/kaltura/app/batch/client/KalturaClient.php(1144): KalturaClientBase->doQueue()
thrown in /opt/kaltura/app/batch/client/KalturaClientBase.php on line 396
PHP Fatal error: Uncaught exception ‘KalturaClientException’ with message ‘failed to unserialize server result
’ in /opt/kaltura/app/batch/client/KalturaClientBase.php:396
Stack trace: #0 /opt/kaltura/app/batch/client/KalturaClient.php(1144): KalturaClientBase->doQueue()
==> /opt/kaltura/log/batch/kschedulehelper-0-2017-05-05.err.log <==
PHP Fatal error: Uncaught exception ‘KalturaClientException’ with message ‘failed to unserialize server result
’ in /opt/kaltura/app/batch/client/KalturaClientBase.php:396
Stack trace: #0 /opt/kaltura/app/batch/client/KalturaClient.php(643): KalturaClientBase->doQueue()
2017-05-05 22:59:34 [1084883606] [KalturaClientBase->doQueue] NOTICE: result (serialized):
2017-05-05 22:59:34 [1084883606] [KScheduleHelper->run] ERR: exception ‘Exception’ with message ‘System is not yet ready - ping failed’ in /opt/kaltura/app/infra/log/KalturaLog.php:82
Stack trace: #0 /opt/kaltura/app/batch/batches/KScheduleHelper.class.php(44): KalturaLog::err(‘System is not y…’)
thrown in /opt/kaltura/app/batch/client/KalturaClientBase.php on line 396
PHP Fatal error: Uncaught exception ‘KalturaClientException’ with message ‘failed to unserialize server result
’ in /opt/kaltura/app/batch/client/KalturaClientBase.php:396
Stack trace: #0 /opt/kaltura/app/batch/client/KalturaClient.php(643): KalturaClientBase->doQueue()
thrown in /opt/kaltura/app/batch/client/KalturaClientBase.php on line 396
PHP Fatal error: Uncaught exception ‘KalturaClientException’ with message ‘failed to unserialize server result
’ in /opt/kaltura/app/batch/client/KalturaClientBase.php:396
Stack trace: #0 /opt/kaltura/app/batch/client/KalturaClient.php(1127): KalturaClientBase->doQueue()
thrown in /opt/kaltura/app/batch/client/KalturaClientBase.php on line 396
PHP Fatal error: Uncaught exception ‘KalturaClientException’ with message ‘failed to unserialize server result
’ in /opt/kaltura/app/batch/client/KalturaClientBase.php:396
Stack trace: #0 /opt/kaltura/app/batch/client/KalturaClient.php(1127): KalturaClientBase->doQueue()
’ in /opt/kaltura/app/batch/client/KalturaClientBase.php:396
Stack trace: #0 /opt/kaltura/app/batch/client/KalturaPlugins/KalturaContentDistributionClientPlugin.php(2425): KalturaClientBase->doQueue()
thrown in /opt/kaltura/app/batch/client/KalturaClientBase.php on line 396
PHP Fatal error: Uncaught exception ‘KalturaClientException’ with message ‘failed to unserialize server result
’ in /opt/kaltura/app/batch/client/KalturaClientBase.php:396
Stack trace: #0 /opt/kaltura/app/batch/client/KalturaPlugins/KalturaContentDistributionClientPlugin.php(2425): KalturaClientBase->doQueue()
thrown in /opt/kaltura/app/batch/client/KalturaClientBase.php on line 396
PHP Fatal error: Uncaught exception ‘KalturaClientException’ with message ‘failed to unserialize server result
’ in /opt/kaltura/app/batch/client/KalturaClientBase.php:396
Stack trace: #0 /opt/kaltura/app/batch/client/KalturaClient.php(3976): KalturaClientBase->doQueue()
thrown in /opt/kaltura/app/batch/client/KalturaClientBase.php on line 396
PHP Fatal error: Uncaught exception ‘KalturaClientException’ with message ‘failed to unserialize server result
’ in /opt/kaltura/app/batch/client/KalturaClientBase.php:396
Stack trace: #0 /opt/kaltura/app/batch/client/KalturaClient.php(3976): KalturaClientBase->doQueue()
thrown in /opt/kaltura/app/batch/client/KalturaClientBase.php on line 396
PHP Fatal error: Uncaught exception ‘KalturaClientException’ with message ‘failed to unserialize server result
’ in /opt/kaltura/app/batch/client/KalturaClientBase.php:396
Stack trace: #0 /opt/kaltura/app/batch/client/KalturaClient.php(1144): KalturaClientBase->doQueue()
thrown in /opt/kaltura/app/batch/client/KalturaClientBase.php on line 396
PHP Fatal error: Uncaught exception ‘KalturaClientException’ with message ‘failed to unserialize server result
’ in /opt/kaltura/app/batch/client/KalturaClientBase.php:396
Stack trace: #0 /opt/kaltura/app/batch/client/KalturaClient.php(1144): KalturaClientBase->doQueue()
==> /opt/kaltura/log/batch/kschedulehelper-0-2017-05-05.err.log <==
PHP Fatal error: Uncaught exception ‘KalturaClientException’ with message ‘failed to unserialize server result
’ in /opt/kaltura/app/batch/client/KalturaClientBase.php:396
Stack trace: #0 /opt/kaltura/app/batch/client/KalturaClient.php(643): KalturaClientBase->doQueue()
2017-05-05 22:59:34 [1084883606] [KalturaClientBase->doQueue] NOTICE: result (serialized):
2017-05-05 22:59:34 [1084883606] [KScheduleHelper->run] ERR: exception ‘Exception’ with message ‘System is not yet ready - ping failed’ in /opt/kaltura/app/infra/log/KalturaLog.php:82
Stack trace: #0 /opt/kaltura/app/batch/batches/KScheduleHelper.class.php(44): KalturaLog::err(‘System is not y…’)
thrown in /opt/kaltura/app/batch/client/KalturaClientBase.php on line 396
PHP Fatal error: Uncaught exception ‘KalturaClientException’ with message ‘failed to unserialize server result
’ in /opt/kaltura/app/batch/client/KalturaClientBase.php:396
Stack trace: #0 /opt/kaltura/app/batch/client/KalturaClient.php(643): KalturaClientBase->doQueue()
thrown in /opt/kaltura/app/batch/client/KalturaClientBase.php on line 396
PHP Fatal error: Uncaught exception ‘KalturaClientException’ with message ‘failed to unserialize server result
’ in /opt/kaltura/app/batch/client/KalturaClientBase.php:396
Stack trace: #0 /opt/kaltura/app/batch/client/KalturaClient.php(1127): KalturaClientBase->doQueue()
thrown in /opt/kaltura/app/batch/client/KalturaClientBase.php on line 396
PHP Fatal error: Uncaught exception ‘KalturaClientException’ with message ‘failed to unserialize server result
’ in /opt/kaltura/app/batch/client/KalturaClientBase.php:396
Stack trace: #0 /opt/kaltura/app/batch/client/KalturaClient.php(1127): KalturaClientBase->doQueue()
’ in /opt/kaltura/app/batch/client/KalturaClientBase.php:396
Stack trace: #0 /opt/kaltura/app/batch/client/KalturaPlugins/KalturaContentDistributionClientPlugin.php(2425): KalturaClientBase->doQueue()
thrown in /opt/kaltura/app/batch/client/KalturaClientBase.php on line 396
PHP Fatal error: Uncaught exception ‘KalturaClientException’ with message ‘failed to unserialize server result
’ in /opt/kaltura/app/batch/client/KalturaClientBase.php:396
Stack trace: #0 /opt/kaltura/app/batch/client/KalturaPlugins/KalturaContentDistributionClientPlugin.php(2425): KalturaClientBase->doQueue()
thrown in /opt/kaltura/app/batch/client/KalturaClientBase.php on line 396
PHP Fatal error: Uncaught exception ‘KalturaClientException’ with message ‘failed to unserialize server result
’ in /opt/kaltura/app/batch/client/KalturaClientBase.php:396
Stack trace: #0 /opt/kaltura/app/batch/client/KalturaClient.php(3976): KalturaClientBase->doQueue()
thrown in /opt/kaltura/app/batch/client/KalturaClientBase.php on line 396
PHP Fatal error: Uncaught exception ‘KalturaClientException’ with message ‘failed to unserialize server result
’ in /opt/kaltura/app/batch/client/KalturaClientBase.php:396
Stack trace: #0 /opt/kaltura/app/batch/client/KalturaClient.php(3976): KalturaClientBase->doQueue()