search

kaltura / platform-install-packages

Official deployment packages to install the Kaltura platform on a server or cluster environments using native OS package managers
GNU Affero General Public License v3.0
520 stars 241 forks source link

Kaltura admin console error code: API:-1 #286

Closed ilgatto closed 9 years ago

ilgatto commented 9 years ago

Hi I noticed kaltura have some instable behaviour. My issue now is cannot login in admin_console due to an "Error code: API -1" instead kmc works fine.

"An error occurred (error code: API:-1)"

i paste kaltlog output in succession post.

ilgatto commented 9 years ago

==> /opt/kaltura/log/kaltura_apache_errors.log <== [Fri Dec 05 10:07:14 2014] [error] [client 95.243.215.82] PHP Notic e: The language 'it_IT' has to be added before it can be used. in /opt/kaltura/app/vendor/ZendFramework/library/Zend/Translate/Adapte r.php on line 322, referer: http://54.154.36.245/admin_console/ [Fri Dec 05 10:07:14 2014] [error] [client 95.243.215.82] PHP Notic e: No translation for the language 'it' available. in /opt/kaltura /app/vendor/ZendFramework/library/Zend/Translate/Adapter.php on lin e 335, referer: http://54.154.36.245/admin_console/ [Fri Dec 05 10:08:18 2014] [error] [client 95.243.215.82] File does not exist: /opt/kaltura/app/alpha/web/opt, referer: http://54.154. 36.245/admin_console/index.php/user/login [Fri Dec 05 10:13:13 2014] [error] [client 95.243.215.82] PHP Notic e: The language 'it_IT' has to be added before it can be used. in /opt/kaltura/app/vendor/ZendFramework/library/Zend/Translate/Adapte r.php on line 322, referer: http://54.154.36.245/admin_console/ [Fri Dec 05 10:13:13 2014] [error] [client 95.243.215.82] PHP Notic e: No translation for the language 'it' available. in /opt/kaltura /app/vendor/ZendFramework/library/Zend/Translate/Adapter.php on lin e 335, referer: http://54.154.36.245/admin_console/ [Fri Dec 05 10:13:26 2014] [error] [client 95.243.215.82] PHP Notic e: The language 'it_IT' has to be added before it can be used. in /opt/kaltura/app/vendor/ZendFramework/library/Zend/Translate/Adapte r.php on line 322 [Fri Dec 05 10:13:26 2014] [error] [client 95.243.215.82] PHP Notic e: No translation for the language 'it' available. in /opt/kaltura /app/vendor/ZendFramework/library/Zend/Translate/Adapter.php on lin e 335 [Fri Dec 05 10:13:38 2014] [error] [client 95.243.215.82] PHP Notic e: The language 'it_IT' has to be added before it can be used. in /opt/kaltura/app/vendor/ZendFramework/library/Zend/Translate/Adapte r.php on line 322, referer: http://54.154.36.245/admin_console/ [Fri Dec 05 10:13:38 2014] [error] [client 95.243.215.82] PHP Notic e: No translation for the language 'it' available. in /opt/kaltura /app/vendor/ZendFramework/library/Zend/Translate/Adapter.php on lin e 335, referer: http://54.154.36.245/admin_console/ [Fri Dec 05 10:14:41 2014] [error] [client 95.243.215.82] File does not exist: /opt/kaltura/app/alpha/web/opt, referer: http://54.154. 36.245/admin_console/index.php/user/login

2014-12-05 11:18:51 [312748311] [KSchedulerConfig->load] NOTICE: lo ading configuration /opt/kaltura/app/configurations/batch at 141777 0972 PHP Fatal error: Uncaught exception 'Zend_Config_Exception' with m essage 'Section 'ip-172-31-21-95' cannot be found in /opt/kaltura/a pp/cache//batch/config.ini' in /opt/kaltura/app/vendor/ZendFramewor k/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...', 'ip-172-31-21-9 5', true)

thrown in /opt/kaltura/app/batch/client/KalturaClientBase.php on line 357 PHP Fatal error: Uncaught exception 'KalturaClientException' with message 'couldn't connect to host' in /opt/kaltura/app/batch/client /KalturaClientBase.php:357 Stack trace:

0 /opt/kaltura/app/batch/client/KalturaClient.php(1309): KalturaCl ientBase->doQueue()

thrown in /opt/kaltura/app/batch/client/KalturaClientBase.php on line 357 PHP Fatal error: Uncaught exception 'KalturaClientException' with message 'couldn't connect to host' in /opt/kaltura/app/batch/client /KalturaClientBase.php:357 Stack trace:

0 /opt/kaltura/app/batch/client/KalturaClient.php(1309): KalturaCl ientBase->doQueue()

2014-12-05 09:38:07 [1421132509] [KalturaClientBase->doCurl] DEBUG: curl: 54.194.188.5/api_v3/index.php?service=dropfolder_dropfolder& action=list&apiVersion=3.1.6&format=3&clientTag=batch%3A+ip-172-31- 21-95+KAsyncDropFolderWatcher+index%3A+0+sessionId%3A+1421132509&ig noreNull=1&filter%3AobjectType=KalturaDropFolderFilter&filter%3Acur rentDc=1&filter%3AstatusIn=1%2C3&pager%3AobjectType=KalturaFilterPa ger&pager%3ApageSize=500&partnerId=-1&ks=ZGM4ZmQyZTBmNzMxODk4ZWQ0ZT ZmOGJkNzY1Nzk3ZTYwY2YzNjNlOHwtMTs7MTQyMDM2MDY4NzsyOzE0MTc3Njg2ODcuM TM4ODtiYXRjaFVzZXI7ZGlzYWJsZWVudGl0bGVtZW50Oy0xOw%3D%3D&kalsig=99ca 5d0e70241955d50f0e65c767fb39 2014-12-05 09:39:10 [1421132509] [KAsyncDropFolderWatcher->getDropF oldersList] ERR: exception 'Exception' with message 'Cannot get dro p folder list - couldn't connect to host' in /opt/kaltura/app/infra /log/KalturaLog.php:82 Stack trace:

0 /opt/kaltura/app/plugins/drop_folder/batch/DropFolderWatcher/KAs yncDropFolderWatcher.class.php(110): KalturaLog::err('Cannot get dr op...')

thrown in /opt/kaltura/app/batch/client/KalturaClientBase.php on line 357 PHP Fatal error: Uncaught exception 'KalturaClientException' with message 'couldn't connect to host' in /opt/kaltura/app/batch/client /KalturaClientBase.php:357 Stack trace:

0 /opt/kaltura/app/batch/client/KalturaClient.php(1144): KalturaCl ientBase->doQueue()

thrown in /opt/kaltura/app/batch/client/KalturaClientBase.php on line 357 PHP Fatal error: Uncaught exception 'KalturaClientException' with message 'couldn't connect to host' in /opt/kaltura/app/batch/client /KalturaClientBase.php:357 Stack trace:

0 /opt/kaltura/app/batch/client/KalturaClient.php(1144): KalturaCl ientBase->doQueue()

2014-12-05 09:38:24 [1449146081] [KalturaClientBase->doCurl] NOTICE : curl: 54.194.188.5/api_v3/index.php?service=system&action=ping&ap iVersion=3.1.6&format=3&clientTag=batch%3A+ip-172-31-21-95+KSchedul eHelper+index%3A+0+sessionId%3A+1449146081&ignoreNull=1&partnerId=- 1&ks=MzI3YjAyMWY2MDAzZDczZDM0ODZlYWRlNzhiMGI5ZWFkYzhkYTcyZHwtMTs7MT QyMDM2MDcwNDsyOzE0MTc3Njg3MDQuMjQ2O2JhdGNoVXNlcjtkaXNhYmxlZW50aXRsZ W1lbnQ7LTE7&kalsig=13b003572f1f25b7235582e1f384bd52 2014-12-05 09:39:27 [1449146081] [KScheduleHelper->run] ERR: except ion '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): Ka lturaLog::err('System is not y...')

thrown in /opt/kaltura/app/batch/client/KalturaClientBase.php on line 357 PHP Fatal error: Uncaught exception 'KalturaClientException' with message 'couldn't connect to host' in /opt/kaltura/app/batch/client /KalturaClientBase.php:357 Stack trace:

0 /opt/kaltura/app/batch/client/KalturaClient.php(1127): KalturaCl ientBase->doQueue()

thrown in /opt/kaltura/app/batch/client/KalturaClientBase.php on line 357 PHP Fatal error: Uncaught exception 'KalturaClientException' with message 'couldn't connect to host' in /opt/kaltura/app/batch/client /KalturaClientBase.php:357 Stack trace:

0 /opt/kaltura/app/batch/client/KalturaClient.php(1127): KalturaCl ientBase->doQueue()

thrown in /opt/kaltura/app/batch/client/KalturaClientBase.php on line 357 PHP Fatal error: Uncaught exception 'KalturaClientException' with message 'couldn't connect to host' in /opt/kaltura/app/batch/client /KalturaClientBase.php:357 Stack trace:

0 /opt/kaltura/app/batch/client/KalturaPlugins/KalturaContentDistr ibutionClientPlugin.php(2425): KalturaClientBase->doQueue()

==> /opt/kaltura/log/batch/synchronizedistribution-0-2014-12-05.err .log <== PHP Fatal error: Uncaught exception 'KalturaClientException' with message 'couldn't connect to host' in /opt/kaltura/app/batch/client /KalturaClientBase.php:357 Stack trace:

0 /opt/kaltura/app/batch/client/KalturaPlugins/KalturaContentDistr ibutionClientPlugin.php(2425): KalturaClientBase->doQueue()

thrown in /opt/kaltura/app/batch/client/KalturaClientBase.php on line 357 PHP Fatal error: Uncaught exception 'KalturaClientException' with message 'couldn't connect to host' in /opt/kaltura/app/batch/client /KalturaClientBase.php:357 Stack trace:

0 /opt/kaltura/app/batch/client/KalturaClient.php(3995): KalturaCl ientBase->doQueue()

thrown in /opt/kaltura/app/batch/client/KalturaClientBase.php on line 357 PHP Fatal error: Uncaught exception 'KalturaClientException' with message 'couldn't connect to host' in /opt/kaltura/app/batch/client /KalturaClientBase.php:357 Stack trace:

0 /opt/kaltura/app/batch/client/KalturaClient.php(3995): KalturaCl ientBase->doQueue()

ilgatto commented 9 years ago

I am trying reinstall with a static ip now but I get new issues, no start page running no kmc and no admin console running. Error on /start page is:

Not Found

The requested URL /start was not found on this server.

Apache/2.2.15 (CentOS) Server at xxx.xxx.xxx.xxx Port 80

ilgatto commented 9 years ago

The /opt/kaltura/bin/kaltura-sanity.sh shows this errors:

[Space on /] [PASSED, RC: 0] - [.016906480] [Space on /opt/kaltura/web] [PASSED, RC: 0] - [.011655439] [Check httpd daemon status] [PASSED, RC: 0] - [.101366357] Napping 1 seconds to allow the daemon httpd to finish its init after monit restarted it.. Napping 1 seconds to allow the daemon httpd to finish its init after monit restarted it.. Napping 1 seconds to allow the daemon httpd to finish its init after monit restarted it.. Napping 1 seconds to allow the daemon httpd to finish its init after monit restarted it.. Napping 1 seconds to allow the daemon httpd to finish its init after monit restarted it.. Napping 1 seconds to allow the daemon httpd to finish its init after monit restarted it.. Napping 1 seconds to allow the daemon httpd to finish its init after monit restarted it.. Napping 1 seconds to allow the daemon httpd to finish its init after monit restarted it.. [Check httpd daemon is started by Monit] [PASSED, RC: 0] - [8.668575024] [check daemon httpd init status] [PASSED, RC: 0] - [.021497340] [Check kaltura-sphinx daemon status] [PASSED, RC: 0] - [.177876964] Napping 1 seconds to allow the daemon kaltura-sphinx to finish its init after monit restarted it.. Napping 1 seconds to allow the daemon kaltura-sphinx to finish its init after monit restarted it.. Napping 1 seconds to allow the daemon kaltura-sphinx to finish its init after monit restarted it.. Napping 1 seconds to allow the daemon kaltura-sphinx to finish its init after monit restarted it.. Napping 1 seconds to allow the daemon kaltura-sphinx to finish its init after monit restarted it.. Napping 1 seconds to allow the daemon kaltura-sphinx to finish its init after monit restarted it.. Napping 1 seconds to allow the daemon kaltura-sphinx to finish its init after monit restarted it.. Napping 1 seconds to allow the daemon kaltura-sphinx to finish its init after monit restarted it.. Napping 1 seconds to allow the daemon kaltura-sphinx to finish its init after monit restarted it.. Napping 1 seconds to allow the daemon kaltura-sphinx to finish its init after monit restarted it.. Napping 1 seconds to allow the daemon kaltura-sphinx to finish its init after monit restarted it.. Napping 1 seconds to allow the daemon kaltura-sphinx to finish its init after monit restarted it.. Napping 1 seconds to allow the daemon kaltura-sphinx to finish its init after monit restarted it.. Napping 1 seconds to allow the daemon kaltura-sphinx to finish its init after monit restarted it.. Napping 1 seconds to allow the daemon kaltura-sphinx to finish its init after monit restarted it.. Napping 1 seconds to allow the daemon kaltura-sphinx to finish its init after monit restarted it.. Napping 1 seconds to allow the daemon kaltura-sphinx to finish its init after monit restarted it.. Napping 1 seconds to allow the daemon kaltura-sphinx to finish its init after monit restarted it.. Napping 1 seconds to allow the daemon kaltura-sphinx to finish its init after monit restarted it.. Napping 1 seconds to allow the daemon kaltura-sphinx to finish its init after monit restarted it.. Napping 1 seconds to allow the daemon kaltura-sphinx to finish its init after monit restarted it.. Napping 1 seconds to allow the daemon kaltura-sphinx to finish its init after monit restarted it.. Napping 1 seconds to allow the daemon kaltura-sphinx to finish its init after monit restarted it.. Napping 1 seconds to allow the daemon kaltura-sphinx to finish its init after monit restarted it.. Napping 1 seconds to allow the daemon kaltura-sphinx to finish its init after monit restarted it.. Napping 1 seconds to allow the daemon kaltura-sphinx to finish its init after monit restarted it.. Napping 1 seconds to allow the daemon kaltura-sphinx to finish its init after monit restarted it.. Napping 1 seconds to allow the daemon kaltura-sphinx to finish its init after monit restarted it.. Napping 1 seconds to allow the daemon kaltura-sphinx to finish its init after monit restarted it.. Napping 1 seconds to allow the daemon kaltura-sphinx to finish its init after monit restarted it.. Napping 1 seconds to allow the daemon kaltura-sphinx to finish its init after monit restarted it.. Napping 1 seconds to allow the daemon kaltura-sphinx to finish its init after monit restarted it.. Napping 1 seconds to allow the daemon kaltura-sphinx to finish its init after monit restarted it.. Napping 1 seconds to allow the daemon kaltura-sphinx to finish its init after monit restarted it.. Napping 1 seconds to allow the daemon kaltura-sphinx to finish its init after monit restarted it.. Napping 1 seconds to allow the daemon kaltura-sphinx to finish its init after monit restarted it.. Napping 1 seconds to allow the daemon kaltura-sphinx to finish its init after monit restarted it.. Napping 1 seconds to allow the daemon kaltura-sphinx to finish its init after monit restarted it.. Napping 1 seconds to allow the daemon kaltura-sphinx to finish its init after monit restarted it.. Napping 1 seconds to allow the daemon kaltura-sphinx to finish its init after monit restarted it.. Napping 1 seconds to allow the daemon kaltura-sphinx to finish its init after monit restarted it.. Napping 1 seconds to allow the daemon kaltura-sphinx to finish its init after monit restarted it.. Napping 1 seconds to allow the daemon kaltura-sphinx to finish its init after monit restarted it.. Napping 1 seconds to allow the daemon kaltura-sphinx to finish its init after monit restarted it.. Napping 1 seconds to allow the daemon kaltura-sphinx to finish its init after monit restarted it.. Napping 1 seconds to allow the daemon kaltura-sphinx to finish its init after monit restarted it.. Napping 1 seconds to allow the daemon kaltura-sphinx to finish its init after monit restarted it.. Napping 1 seconds to allow the daemon kaltura-sphinx to finish its init after monit restarted it.. Napping 1 seconds to allow the daemon kaltura-sphinx to finish its init after monit restarted it.. Napping 1 seconds to allow the daemon kaltura-sphinx to finish its init after monit restarted it.. Napping 1 seconds to allow the daemon kaltura-sphinx to finish its init after monit restarted it.. Napping 1 seconds to allow the daemon kaltura-sphinx to finish its init after monit restarted it.. Napping 1 seconds to allow the daemon kaltura-sphinx to finish its init after monit restarted it.. Napping 1 seconds to allow the daemon kaltura-sphinx to finish its init after monit restarted it.. Napping 1 seconds to allow the daemon kaltura-sphinx to finish its init after monit restarted it.. Napping 1 seconds to allow the daemon kaltura-sphinx to finish its init after monit restarted it.. Napping 1 seconds to allow the daemon kaltura-sphinx to finish its init after monit restarted it.. Napping 1 seconds to allow the daemon kaltura-sphinx to finish its init after monit restarted it.. Napping 1 seconds to allow the daemon kaltura-sphinx to finish its init after monit restarted it.. Napping 1 seconds to allow the daemon kaltura-sphinx to finish its init after monit restarted it.. [Check kaltura-sphinx daemon is started by Monit] [FAILED, RC: 1] - [64.978212265] [check daemon kaltura-sphinx init status] [PASSED, RC: 0] - [.016153551] [Check kaltura-batch daemon status] [PASSED, RC: 0] - [.072181645] Napping 1 seconds to allow the daemon kaltura-batch to finish its init after monit restarted it.. Napping 1 seconds to allow the daemon kaltura-batch to finish its init after monit restarted it.. Napping 1 seconds to allow the daemon kaltura-batch to finish its init after monit restarted it.. Napping 1 seconds to allow the daemon kaltura-batch to finish its init after monit restarted it.. Napping 1 seconds to allow the daemon kaltura-batch to finish its init after monit restarted it.. Napping 1 seconds to allow the daemon kaltura-batch to finish its init after monit restarted it.. Napping 1 seconds to allow the daemon kaltura-batch to finish its init after monit restarted it.. Napping 1 seconds to allow the daemon kaltura-batch to finish its init after monit restarted it.. Napping 1 seconds to allow the daemon kaltura-batch to finish its init after monit restarted it.. Napping 1 seconds to allow the daemon kaltura-batch to finish its init after monit restarted it.. [Check kaltura-batch daemon is started by Monit] [PASSED, RC: 0] - [10.635728749] [check daemon kaltura-batch init status] [PASSED, RC: 0] - [.013731804] [Check kaltura-monit daemon status] [PASSED, RC: 0] - [.053201256] [check daemon kaltura-monit init status] [PASSED, RC: 0] - [.014013008] [Check memcached daemon status] [PASSED, RC: 0] - [.048440024] Napping 1 seconds to allow the daemon memcached to finish its init after monit restarted it.. Napping 1 seconds to allow the daemon memcached to finish its init after monit restarted it.. Napping 1 seconds to allow the daemon memcached to finish its init after monit restarted it.. Napping 1 seconds to allow the daemon memcached to finish its init after monit restarted it.. Napping 1 seconds to allow the daemon memcached to finish its init after monit restarted it.. Napping 1 seconds to allow the daemon memcached to finish its init after monit restarted it.. Napping 1 seconds to allow the daemon memcached to finish its init after monit restarted it.. Napping 1 seconds to allow the daemon memcached to finish its init after monit restarted it.. Napping 1 seconds to allow the daemon memcached to finish its init after monit restarted it.. Napping 1 seconds to allow the daemon memcached to finish its init after monit restarted it.. Napping 1 seconds to allow the daemon memcached to finish its init after monit restarted it.. Napping 1 seconds to allow the daemon memcached to finish its init after monit restarted it.. Napping 1 seconds to allow the daemon memcached to finish its init after monit restarted it.. Napping 1 seconds to allow the daemon memcached to finish its init after monit restarted it.. Napping 1 seconds to allow the daemon memcached to finish its init after monit restarted it.. Napping 1 seconds to allow the daemon memcached to finish its init after monit restarted it.. Napping 1 seconds to allow the daemon memcached to finish its init after monit restarted it.. Napping 1 seconds to allow the daemon memcached to finish its init after monit restarted it.. Napping 1 seconds to allow the daemon memcached to finish its init after monit restarted it.. Napping 1 seconds to allow the daemon memcached to finish its init after monit restarted it.. Napping 1 seconds to allow the daemon memcached to finish its init after monit restarted it.. Napping 1 seconds to allow the daemon memcached to finish its init after monit restarted it.. Napping 1 seconds to allow the daemon memcached to finish its init after monit restarted it.. Napping 1 seconds to allow the daemon memcached to finish its init after monit restarted it.. Napping 1 seconds to allow the daemon memcached to finish its init after monit restarted it.. Napping 1 seconds to allow the daemon memcached to finish its init after monit restarted it.. Napping 1 seconds to allow the daemon memcached to finish its init after monit restarted it.. Napping 1 seconds to allow the daemon memcached to finish its init after monit restarted it.. Napping 1 seconds to allow the daemon memcached to finish its init after monit restarted it.. Napping 1 seconds to allow the daemon memcached to finish its init after monit restarted it.. Napping 1 seconds to allow the daemon memcached to finish its init after monit restarted it.. Napping 1 seconds to allow the daemon memcached to finish its init after monit restarted it.. Napping 1 seconds to allow the daemon memcached to finish its init after monit restarted it.. Napping 1 seconds to allow the daemon memcached to finish its init after monit restarted it.. Napping 1 seconds to allow the daemon memcached to finish its init after monit restarted it.. Napping 1 seconds to allow the daemon memcached to finish its init after monit restarted it.. Napping 1 seconds to allow the daemon memcached to finish its init after monit restarted it.. Napping 1 seconds to allow the daemon memcached to finish its init after monit restarted it.. Napping 1 seconds to allow the daemon memcached to finish its init after monit restarted it.. Napping 1 seconds to allow the daemon memcached to finish its init after monit restarted it.. Napping 1 seconds to allow the daemon memcached to finish its init after monit restarted it.. Napping 1 seconds to allow the daemon memcached to finish its init after monit restarted it.. Napping 1 seconds to allow the daemon memcached to finish its init after monit restarted it.. Napping 1 seconds to allow the daemon memcached to finish its init after monit restarted it.. Napping 1 seconds to allow the daemon memcached to finish its init after monit restarted it.. Napping 1 seconds to allow the daemon memcached to finish its init after monit restarted it.. Napping 1 seconds to allow the daemon memcached to finish its init after monit restarted it.. Napping 1 seconds to allow the daemon memcached to finish its init after monit restarted it.. Napping 1 seconds to allow the daemon memcached to finish its init after monit restarted it.. Napping 1 seconds to allow the daemon memcached to finish its init after monit restarted it.. Napping 1 seconds to allow the daemon memcached to finish its init after monit restarted it.. Napping 1 seconds to allow the daemon memcached to finish its init after monit restarted it.. Napping 1 seconds to allow the daemon memcached to finish its init after monit restarted it.. Napping 1 seconds to allow the daemon memcached to finish its init after monit restarted it.. Napping 1 seconds to allow the daemon memcached to finish its init after monit restarted it.. Napping 1 seconds to allow the daemon memcached to finish its init after monit restarted it.. Napping 1 seconds to allow the daemon memcached to finish its init after monit restarted it.. Napping 1 seconds to allow the daemon memcached to finish its init after monit restarted it.. Napping 1 seconds to allow the daemon memcached to finish its init after monit restarted it.. Napping 1 seconds to allow the daemon memcached to finish its init after monit restarted it.. [Check memcached daemon is started by Monit] [FAILED, RC: 1] - [62.957812087] [check daemon memcached init status] [PASSED, RC: 0] - [.013446365] [kaltura-html5lib ver in KMC config.ini] [PASSED, RC: 0] - [.134454837] [kaltura-kdp3 ver in KMC config.ini] [PASSED, RC: 0] - [.078830649] [kaltura-kmc ver in KMC config.ini] [PASSED, RC: 0] - [.088082819] PHP Warning: file_get_contents(http://xxx.xxx.xxx.xxx:80/kmc): failed to open stream: HTTP request failed! HTTP/1.1 404 Not Found in /opt/kaltura/bin/get_kmc_swfs.php on line 9 [Get KMC SWFs] [FAILED, RC: 255] - [.249511235] curl: no URL specified! curl: try 'curl --help' or 'curl --manual' for more information [check_testme_page] [FAILED, RC: 1] - [.084618266] [check_kmc_index_page] [FAILED, RC: 1] - [.044923624] curl: no URL specified! curl: try 'curl --help' or 'curl --manual' for more information [check_admin_console_index_page] [FAILED, RC: 1] - [.084195776] [check_studio_index_page] [FAILED, RC: 1] - [.733610500] [Create Partner] [FAILED, RC: 255] - [.226032999] Partner creation failed. I will skip all tests that require it. [Red5 file upload] [PASSED, RC: 0] - [3.397273735]

jessp01 commented 9 years ago

Hi Gabriel,

Did you reconfigure the service URL using kaltura-base-config.sh? If not you should, if yes, what's the output for:

apachectl -t -DDUMP_VHOSTS

Thanks,

May the source be with you,

Jess Portnoy

On Wed, 10 Dec 2014, Gabriele wrote:

I am trying reinstall with a static ip now but I get new issues, no start page running no kmc and no admin console running. Error on /start page is:

Not Found

The requested URL /start was not found on this server.

Apache/2.2.15 (CentOS) Server at xxx.xxx.xxx.xxx Port 80

— Reply to this email directly or view it on GitHub.[AFBqvXgm7U2F-0ZccUm-qNtB297ivVAUks5nWEUggaJpZM4DEtJ9.gif]

ilgatto commented 9 years ago

Thank Jess. I reconfigured with kaltura-base.config.sh and it did successfull.

Here the output of # apachectl -t -DDUMP_VHOSTS

VirtualHost configuration: wildcard NameVirtualHosts and default servers: default:443 ip-172-31-21-95.eu-west-1.compute.internal (/etc/httpd/conf.d/ssl.conf:74) Syntax OK

It stills get me

Not Found

The requested URL /start was not found on this server.

Apache/2.2.15 (CentOS) Server at xxx.xxx.xxx.xxx Port 80

jessp01 commented 9 years ago

Hi Gabriel,

So is everything OK now or do you still need assistance? does the kaltura-sanity pass successfully now? If not, can you do:

curl -I -v $SERVICE_URL/kmc

curl -I -v $SERVICE_URL/api_v3/

And look at the result?

May the source be with you,

Jess Portnoy

On Wed, 10 Dec 2014, Gabriele wrote:

Thank Jess. I reconfigured with kaltura-base.config.sh and it did successfull.

Here the output of # apachectl -t -DDUMP_VHOSTS

VirtualHost configuration: wildcard NameVirtualHosts and default servers: default:443 ip-172-31-21-95.eu-west-1.compute.internal (/etc/httpd/conf.d/ssl.conf:74) Syntax OK

— Reply to this email directly or view it on GitHub.[AFBqvRd-Swm2erLCn4pPx6sWK5BxnWAhks5nWFTegaJpZM4DEtJ9.gif]

ilgatto commented 9 years ago

No it doesn't, the kaltura-sanity.sh fail again and shows 'Not found' on /start, /kmc and /admin_console.

The output of 'curl' are

curl -I -v $SERVICE_URL/kmc

<

curl -I -v $SERVICE_URL/api_v3/

<

KalturaCommunity-zz commented 9 years ago

Looking at the apachectl -t -DDUMP_VHOSTS output, I do not see the kaltura vhosts...

Did you also run kaltura-front-config.sh? it is the one responsible for setting it up. You should have a symlink: /etc/httpd/conf.d/zzzkaltura.ssl.conf -> /opt/kaltura/app/configurations/apache/kaltura.ssl.conf

Or zzzkaltura.conf if its HTTP.

May the source be with you,

Jess Portnoy

On Wed, 10 Dec 2014, Gabriele wrote:

No it doesn't, the kaltura-sanity.sh fail again and shows 'Not found' on /start, /kmc and /admin_console.

The output of 'curl' are

                                               curl -I -v $SERVICE_URL/kmc
  • About to connect() to xxx.xxx.xxx.xxx port 80 (#0)
  • Trying xxx.xxx.xxx.xxx... connected
  • Connected to xxx.xxx.xxx.xxx (xxx.xxx.xxx.xxx) port 80 (#0) > HEAD /kmc HTTP/1.1 > User-Agent: curl/7.19.7 (x86_64-redhat-linux-gnu) libcurl/7.19.7 NSS/3.16.1 Basic ECC zlib/1.2.3 libidn/1.18 libssh2/1.4.2 > Host: xxx.xxx.xxx.xxx > Accept: / > < HTTP/1.1 404 Not Found HTTP/1.1 404 Not Found < Date: Wed, 10 Dec 2014 15:07:50 GMT Date: Wed, 10 Dec 2014 15:07:50 GMT < Server: Apache/2.2.15 (CentOS) Server: Apache/2.2.15 (CentOS) < Connection: close Connection: close < Content-Type: text/html; charset=iso-8859-1 Content-Type: text/html; charset=iso-8859-1

<

  • Closing connection #0 curl -I -v $SERVICE_URL/api_v3/
  • About to connect() to xxx.xxx.xxx.xxx port 80 (#0)
  • Trying xxx.xxx.xxx.xxx... connected
  • Connected to xxx.xxx.xxx.xxx (xxx.xxx.xxx.xxx) port 80 (#0) > HEAD /api_v3/ HTTP/1.1 > User-Agent: curl/7.19.7 (x86_64-redhat-linux-gnu) libcurl/7.19.7 NSS/3.16.1 Basic ECC zlib/1.2.3 libidn/1.18 libssh2/1.4.2 > Host: xxx.xxx.xxx.xxx > Accept: / > < HTTP/1.1 404 Not Found HTTP/1.1 404 Not Found < Date: Wed, 10 Dec 2014 15:07:59 GMT Date: Wed, 10 Dec 2014 15:07:59 GMT < Server: Apache/2.2.15 (CentOS) Server: Apache/2.2.15 (CentOS) < Connection: close Connection: close < Content-Type: text/html; charset=iso-8859-1 Content-Type: text/html; charset=iso-8859-1

<

  • Closing connection #0

— Reply to this email directly or view it on GitHub.[ACH7XuM_LSfUvjRGftlaCeQIuAPLncJ3ks5nWFrUgaJpZM4DEtJ9.gif]

ilgatto commented 9 years ago

Yes I did, I runned the kaltura-front-config.sh with the option N, but still doesn't work neither /start /kmc or /admin_console.

jessp01 commented 9 years ago

Can you do:

apachectl -t -DDUMP_VHOSTS

curl -I -v $SERVICE_URL/kmc

curl -I -v $SERVICE_URL/api_v3

And paste the output?

ilgatto commented 9 years ago

ok..

apachectl -t -DDUMP_VHOSTS

VirtualHost configuration: wildcard NameVirtualHosts and default servers: default:443 ip-172-31-21-95.eu-west-1.compute.internal (/etc/httpd/conf.d/ssl.conf:74) Syntax OK

curl -I -v $SERVICE_URL/kmc

<

curl -I -v $SERVICE_URL/api_v3 -> NO OUTPUT

This time the api_v3 get no output

jessp01 commented 9 years ago

It seems you do not have the Kaltura vhost configured at all. I suggest you re-run the config scripts and make sure to pass correct values. Please paste the full output for the config scripts should you still have issues.

ilgatto commented 9 years ago

ok i'll do it

ilgatto commented 9 years ago

This is the command output Jess

/opt/kaltura/bin/kaltura-config-all.sh

Running base config...

kaltura-base-9.19.8-3.noarch Welcome to Kaltura Server 9.19.8 post install setup.

To keep up with the bi-weekly Kaltura releases, and stay up to date with the latest news, security and bug updates, and connect with the global Kaltura community - sign up for our regular Kaltura Community updates. Please enter your email to sign up, or enter NO to pass.

my@email.com Registering for the newsletter... this will take a few seconds.

In order to finalize the system configuration, please input the following:

CDN hostname [ip-172-31-21-95]: xxx.xxx.xxx.xxx Apache virtual hostname [ip-172-31-21-95](Must be accessible from both inside the machine and from any clients / browsers that will use Kaltura):

xxx.xxx.xxx.xxx Vhost port to listen on [80]: 80 DB port [3306]: 3306 MySQL super user [only for install, default root]: root Analytics DB hostname [127.0.0.1]:127.0.0.1 Analytics DB port [3306]:3306 Sphinx hostname [127.0.0.1]: 127.0.0.1 Secondary Sphinx hostname [leave empty if none]: Admin user login password (must be minimum 8 chars and include at least one of each: upper-case, lower-case, number and a special character): Confirm passwd: Your time zone [see http://php.net/date.timezone], or press enter for [UTC]: Europe/Rome Your Kaltura install name (this name will show as the From field in emails sent by the system) [Kaltura Video Platform]:Kaltura Video Platform Your website Contact Us URL [http://corp.kaltura.com/company/contact-us]: Your 'Contact us' phone number [+1 800 871 5224]:

Kaltura install answer file written to /tmp/kaltura_11_12_11_25.ans - Please save it!

This answers file can be used to silently-install re-install this machine or deploy other hosts in your cluster.

Configuration of Kaltura Server 9.19.8 finished successfully! Running FrontEnd config...

base-config completed successfully, if you ever want to re-configure your system (e.g. change DB hostname) run the following script:

rm /opt/kaltura/app/base-config.lock

/opt/kaltura/bin/kaltura-base-config.sh

kaltura-front-9.19.8-1.noarch It is recommended that you do work using HTTPs. Would you like to continue anyway?[N/y] N Exiting.

            Archving logs to /opt/kaltura/log/log_11_12_14_11_25.tar.gz...
jessp01 commented 9 years ago

Hi,

It is recommended that you do work using HTTPs. Would you like to continue anyway?[N/y] N

You should hit 'y' or else, if you have a SSL certificate, choose to configure over HTTPs and provide the relevant info.

The way it is now, you are saying you wish to abort so the install exists.

Thanks,

May the source be with you,

Jess Portnoy

On Thu, 11 Dec 2014, Gabriele wrote:

This is the command output Jess

                                          /opt/kaltura/bin/kaltura-config-all.sh

Running base config...

kaltura-base-9.19.8-3.noarch Welcome to Kaltura Server 9.19.8 post install setup.

To keep up with the bi-weekly Kaltura releases, and stay up to date with the latest news, security and bug updates, and connect with the global Kaltura community - sign up for our regular Kaltura Community updates. Please enter your email to sign up, or enter NO to pass.

my@email.com Registering for the newsletter... this will take a few seconds.

In order to finalize the system configuration, please input the following:

CDN hostname [ip-172-31-21-95]: xxx.xxx.xxx.xxx Apache virtual hostname ip-172-31-21-95:

xxx.xxx.xxx.xxx Vhost port to listen on [80]: 80 DB port [3306]: 3306 MySQL super user [only for install, default root]: root Analytics DB hostname [127.0.0.1]:127.0.0.1 Analytics DB port [3306]:3306 Sphinx hostname [127.0.0.1]: 127.0.0.1 Secondary Sphinx hostname [leave empty if none]: Admin user login password (must be minimum 8 chars and include at least one of each: upper-case, lower-case, number and a special character): Confirm passwd: Your time zone [see http://php.net/date.timezone], or press enter for [UTC]: Europe/Rome Your Kaltura install name (this name will show as the From field in emails sent by the system) [Kaltura Video Platform]:Kaltura Video Platform Your website Contact Us URL [http://corp.kaltura.com/company/contact-us]: Your 'Contact us' phone number [+1 800 871 5224]:

Kaltura install answer file written to /tmp/kaltura_11_12_11_25.ans - Please save it!

     This answers file can be used to silently-install re-install this machine or deploy other hosts in your cluster.

Configuration of Kaltura Server 9.19.8 finished successfully! Running FrontEnd config...

base-config completed successfully, if you ever want to re-configure your system (e.g. change DB hostname) run the following script:

                                           rm /opt/kaltura/app/base-config.lock

                                         /opt/kaltura/bin/kaltura-base-config.sh

kaltura-front-9.19.8-1.noarch It is recommended that you do work using HTTPs. Would you like to continue anyway?[N/y] N Exiting.

        Archving logs to /opt/kaltura/log/log_11_12_14_11_25.tar.gz...

— Reply to this email directly or view it on GitHub.[AFBqveIp6wdacTIcj4UypVSfY3dvnFx5ks5nWXfxgaJpZM4DEtJ9.gif]

ilgatto commented 9 years ago

Ok, my boss tell me hit N last time in this step, now I reperform the config-all script with https Yes

ilgatto commented 9 years ago

Thanks Jess! I did the config-all and the db-config. Now I can access on admin_console. Only one thing again.. to access on kmc I have to create a publisher account? Cause the administrator account doesn't work on kmc.

jessp01 commented 9 years ago

Yes, that is correct. You need to create a publisher.

sincerbex commented 5 years ago

hi @jessp01 , i have installed kaltura on ubuntu 16.04 server. the installation was successful but I am unable to enter the admin. blank page with An error occurred (error code: API: -1). I installed kaltura with ssl. what can I check to find the problem? thanks for the support. best regards