We have Drupal 6.22 and Kaltura CE 4.0.12.5 running in separate virtual hosts on the same linux box.
We are experiencing 2 separate issues, I am guessing they are related.
First, the Kaltura Management Console (http://kaltura.localhost/kmc) throws "Internal server error occurred" pop-up messages for each page under "Content" tab. I can't access the content of any pages under this tab.
Second, the "Import entries from Kaltura" page (admin/settings/kaltura/entries/import) throws HTTP Error 500 (Internal Server Error). It generates following message in Apache2 error.log
PHP Fatal error: Uncaught exception 'KalturaException' with message 'Internal server error occured' in /var/www/sites/all/modules/contrib/kaltura/kaltura_client/KalturaClientBase.php:310
Stack trace:
#0 /var/www/sites/all/modules/contrib/kaltura/kaltura_client/KalturaClient.php(3469): KalturaClientBase->throwExceptionIfError(Array)
#1 /var/www/sites/all/modules/contrib/kaltura/includes/kaltura.admin.inc(664): KalturaMediaService->listAction(Object(KalturaMediaEntryFilter), Object(KalturaFilterPager))
#2 /var/www/sites/all/modules/contrib/kaltura/includes/kaltura.admin.inc(476): kaltura_get_my_entries(Object(KalturaMediaEntryFilter), 1, 30, 1)
#3 [internal function]: kaltura_import_entries_page()
#4 /var/www/includes/menu.inc(349): call_user_func_array('kaltura_import_...', Array)
#5 /var/www/index.php(17): menu_execute_active_handler()
#6 {main}
thrown in /var/www/sites/all/modules/contrib/kaltura/kaltura_client/KalturaClientBase.php on line 310, referer: http://localhost/admin/settings/kaltura/entries
I suspect the kaltura instance is missing -something-, but I am not sure what. I already checked the issues at drupal.org and kaltura.org but nothing similar.
Has anyone experienced anything similar to this?
Thanks in advance.
Osman
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | 1252340-uncaught_exception_in_kaltura_get_my_entries.patch | 4.07 KB | xurizaemon |
Comments
Comment #1
xurizaemonI'm afraid this issue is outside the scope of the Drupal Kaltura module - that issue can't be fixed in the Kaltura module because it is occurring on a separate server entirely. You'll need to debug and/or look for support either via Kaltura community or commercial providers.
This is triggered by the first issue, but we should catch the Kaltura exception rather than crashing. I'll look into that.
Comment #2
xurizaemonPlease try this patch, and mark RTBC if you're happy with it.
Comment #3
xurizaemon